JP6500316B2 - Reward grant method, user terminal, reward grant program, and server - Google Patents

Description

  The present invention relates to a reward giving method, a user terminal, a reward giving program, and a server.

  Application is installed in a user terminal such as a smartphone to enjoy the content of the application. Such an application is registered so as to be downloadable, for example, to a store site selling the application or a dedicated site of each application. The user can then download the desired application from these sites and install it on his own user terminal.

  Also, an advertisement (banner) of an application not yet installed is displayed on a display screen displayed while using an application installed on the user terminal, and the above-mentioned store site is selected when the advertisement (banner) is selected. Or to a dedicated site, and then, when the selected application is downloaded and installed on the user terminal, the original application provider (advertiser) is displayed with the advertisement (banner) that triggered the download On the other hand, there is a reward advertisement system in which a reward is given to the user's own use of the original application (see, for example, Patent Document 1).

Patent No. 5107455 gazette

  According to the above-described reward advertisement system, it is possible to give rewards to motivate customers to send between applications, which can lead to promotion of sales of applications. Therefore, there is a demand for a system for sending customers between more convenient applications.

  The present invention has been made in view of such a situation, and provides a reward giving method, a user terminal, a reward giving program, and a server that can improve the convenience of customer sending between applications.

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

  In order to solve the problems described above, one aspect of the present invention is a reward giving method in a user terminal in which the first application and the second application can be installed, wherein the user terminal is the user terminal in the user terminal. Sending a reward request including a second user identifier different from the first user identifier identifying the user in the first application to the server when a predetermined operation related to the second application is performed; Receiving from the server a grant of a reward in the first application to a user identified by the first user identifier corresponding to the second user identifier. It is a method.

  Further, one aspect of the present invention is a reward provision method in a user terminal in which a first application and a second application having a user identifier different from the first application can be installed, wherein the user terminal is the user terminal Sending a reward request including a second user identifier identifying the user in the second application to the server when a predetermined operation related to the second application is performed; and the second request based on the reward request. Receiving from the server a grant of a reward in the first application to a user identified by a first user identifier identifying the user in the first application, corresponding to a user identifier. It is a reward giving method.

  Further, one aspect of the present invention is a reward provision method in a user terminal in which a first application and a second application having a user identifier different from the first application can be installed, wherein the user terminal is the user terminal Sending a reward request including a second user identifier that can specify the user terminal or user to the server when a predetermined operation related to the second application is performed; and based on the reward request, the second Receiving from the server a grant of a reward in the first application to a user identified by a first user identifier identifying the user in the first application, corresponding to a user identifier. It is a reward giving method.

  Further, one aspect of the present invention is a reward provision method in a user terminal in which a first application and a second application having a user identifier different from the first application can be installed, wherein the user terminal is the user terminal Sending to the server a reward request including a second user identifier identifying the user in the management of reward when the predetermined operation related to the second application is performed; and based on the reward request, the second user Receiving from the server a grant of a reward in the first application to a user identified by a first user identifier identifying the user in the first application corresponding to the identifier. It is a grant method.

  Moreover, one aspect of the present invention is a user terminal in which a first application and a second application can be installed, and when a predetermined operation related to the second application is performed, the user is identified in the first application Sending a reward request including a second user identifier different from the first user identifier to the server, and based on the reward request, identified by the first user identifier corresponding to the second user identifier It is a user terminal which receives grant of the remuneration in said 1st application to a user from said server.

  Further, according to one aspect of the present invention, in the case where a predetermined function related to the second application is performed in the user terminal on a computer that functions as a user terminal in which the first application and the second application can be installed, Transmitting to the server a reward request comprising a second user identifier different from a first user identifier identifying a user in one application, and corresponding to the second user identifier based on the reward request, Receiving a reward from the server for the user identified by the one user identifier from the server.

  Further, one aspect of the present invention is a reward granting method in a server capable of communicating with a user terminal in which the first application and the second application can be installed, wherein the server is the second application in the user terminal. Receiving a reward request including a second user identifier different from a first user identifier identifying the user in the first application, when the predetermined operation is performed; and, based on the reward request, Providing a reward in the first application to the user identified by the first user identifier, which corresponds to the user identifier in the above.

  Further, one aspect of the present invention is a server capable of communicating with a user terminal in which the first application and the second application can be installed, and in the case where the predetermined operation related to the second application is performed in the user terminal Receiving a reward request including a second user identifier different from a first user identifier identifying a user in the first application, the first application corresponding to the second user identifier based on the reward request A server for giving a reward in the first application to a user identified by a user identifier of

  Further, according to an aspect of the present invention, a predetermined function of the second application is performed in the user terminal in a computer that functions as a server capable of communicating with the user terminal in which the first application and the second application can be installed. Receiving a reward request including a second user identifier different from the first user identifier identifying the user in the first application, and corresponding to the second user identifier based on the reward request Providing a reward in the first application to the user identified by the first user identifier.

  As described above, according to the present invention, the convenience of customer sending between applications can be improved.

It is an explanatory view explaining an outline of a mutual customer sending system of a 1st embodiment. 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 an explanatory view explaining an example of composition and processing of a mutual customer sending system of this embodiment. It is a block diagram which shows an example of a 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 this embodiment. It is a figure which shows an example of the information memorize | stored in a target application information storage part. It is a figure which shows an example of the information memorize | stored in a normal reward information storage part. It is a figure which shows an example of the information memorize | stored in a campaign information storage part. It is a figure which shows an example of the information memorize | stored in a campaign participating application information storage part. It is a figure which shows an example of the information memorize | stored in an installation information storage part. It is a figure which shows an example of the information memorize | stored in a customer referrals information storage part. It is a figure which shows an example of the information memorize | stored in a reward formation information storage part. It is a first flowchart showing an example of the operation of the mutual customer feed processing according to the present embodiment. It is a 2nd flow chart which shows an example of operation of mutual customer sending processing by this embodiment. It is a figure which shows an example of the information memorize | stored in the filter storage part between applications. It is a flow chart explaining operation of establishment processing of a communication session. It is an explanatory view explaining an outline of a mutual customer sending system of a 3rd embodiment. It is a block diagram which shows an example of a function structure performed based on SDK of the user terminal 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 the object application information storage part by 3rd Embodiment. It is a figure which shows an example of the information memorize | stored in the installation information storage part by 3rd Embodiment. It is a flow chart which shows an example of operation of a mutual customer sending system by a 3rd embodiment. It is a block diagram which shows an example of a function structure performed based on SDK of the user terminal by 4th Embodiment. It is a block diagram which shows an example of a structure of the management server by 4th Embodiment. It is a flow chart which shows an example of operation of a mutual customer sending system by a 4th embodiment. It is a block diagram which shows an example of a function structure performed based on SDK of the user terminal by 5th Embodiment. It is a flowchart which shows an example of operation | movement of the mutual customer sending system by 5th Embodiment. It is a figure which shows the example of a display of the list of object application by 5th Embodiment. It is an explanatory view explaining an outline of a mutual customer sending system of a 6th embodiment. It is an explanatory view explaining an outline of a mutual customer sending system of a 7th embodiment. It is a block diagram which shows an example of a structure of the management server by 7th Embodiment. It is a figure which shows an example of the information memorize | stored in the installation information storage part by 7th Embodiment. It is a flow chart which shows an example of operation of a mutual customer sending system by a 7th embodiment. It is a figure which shows another example of the information memorize | stored in the installation information storage part by 7th Embodiment. It is an explanatory view explaining an outline of a mutual customer sending system of an 8th embodiment. It is a block diagram which shows an example of a structure of the management server by 8th Embodiment. It is a flowchart which shows an example of the initialization process by 8th Embodiment. It is an explanatory view explaining an outline of a mutual customer sending system of a 9th embodiment. It is a block diagram which shows an example of a function structure performed based on the exclusive application of the user terminal by 9th Embodiment. It is a flowchart which shows an example of operation | movement of the mutual customer sending system by 9th Embodiment.

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

[Overview of mutual customer delivery system]
First, an overview of the mutual customer delivery system according to the present embodiment will be described. From the original application (hereinafter, also referred to as “customer origin application”) already installed and used in the user terminal, this mutual customer support system is configured to use an application (hereinafter, “send A system for mutually sending customers between applications so as to install a customer application (also referred to as “customer application”). However, since the user information of the user registered for each application may be different, matching of the user information between the applications can not be achieved, and sending from the customer sending application to the customer receiving application in the user terminal of the same user It may not be easy to determine if the customer has been made. Therefore, in the present embodiment, it is an object of the present invention to provide a mutual customer feed system capable of mutual customer feed even between applications managed by the same user but different user information. Even if they are different from each other, they can be configured to be able to easily perform cross-customers between applications.

  Here, the customer sending from the customer sending source application to the customer sending destination application refers to the user sending the user so that the user using the customer sending source application does not use the customer using destination application yet. It means sending customers to the destination application. Further, “inter-customer sending” indicates that applications can send customers to each other because each application can be either a customer sending source or a customer sending destination. For example, when a customer-sending application is performed from the customer-sending application to the customer-sending application, the customer-sending application performs a customer-sending to another customer-sending application that has not yet been installed on the user terminal. It can be an original application.

  Further, in the mutual customer support system in which a reward is given when the customer destination application is installed, there is a possibility that the customer destination application may not be used for the purpose of reward acquisition only. Therefore, in the present invention, the reward is given when the installed customer-sending destination application reaches a predetermined outcome point. Furthermore, by setting multiple different output points, it is possible to receive a reward for each output point achieved. It becomes possible to raise the use of the customer destination application by making it a reward of such an achievement achievement type.

  In the present embodiment, provision of a reward (reward) when the customer-sending destination application is installed based on the customer-sending source application is classified into each of a normal period and a specific period (hereinafter referred to as a “campaign period”). It is different reward processing. In addition, a campaign is a measure (event having a specific period) to be implemented to enhance mutual customer service only for a specific period among a plurality of applications.

  Specifically, in the mutual customer support system of the present embodiment, a reward is given when the customer destination application is installed in a normal period (ie, a period other than the campaign period), and in the campaign period, Providing a system that enables mutual customer service among multiple applications in which a reward (reward) is given when achievement is achieved in the customer destination application. Hereinafter, the reward performed in the normal period is referred to as “normal reward”, and the reward (campaign reward) performed in the campaign period is referred to as “CP reward”.

  CP rewards are cross-customers between specific applications participating in the campaign during the campaign period, whereas rewards are usually cross between any application that covers all of the applications corresponding to the system. Become a customer.

  FIG. 1 is an explanatory view for explaining an outline of the mutual customer sending system of the present embodiment. In this figure, four types of applications, "application A", "application B", "application C", and "application D", are used as an application corresponding to the mutual customer feed system of the present embodiment. "App A" is a customer-sending source application installed on the user terminal. “App B”, “App C”, and “App D” are applications that are not installed in the user terminal and can be customer-sending destination applications for “application A” (sender-sender application). is there. Note that "App B" is in the campaign period with "App A", and "App C" and "App D" are in the normal period during the campaign period with "App A". .

  The user terminal displays, on the display screen of the user terminal, a list LT of target applications that can be selected as a customer-sending destination application for “application A”, which is a customer-sending source application. Here, labels L 1, L 2 and L 3 on which the application names and reward contents of “application B”, “application C” and “application D” are displayed are arranged side by side as selectable operators as customer destination applications. It is displayed. The label L1 displays the application name of "application B", information indicating that the campaign period is underway, and the link destination of the site where the content of the reward by CP reward is posted. In the label L2, the application name of “application C” and the contents of remuneration by ordinary reward are displayed. The label L3 displays the application name of "application D" and the contents of the reward by the ordinary reward.

  Here, in the case of the normal reward, the granting of points that can be used by the own user in the customer sending source application is displayed as the content of the reward. On the other hand, in the case of CP reward, for example, the application manages the outcome points as compensation condition in the game and the contents of compensation when the achievement points are achieved (providing points, granting items, etc.) In order to be posted on the linked site. The result point can be arbitrarily set on the application side, for example, the end of the tutorial in the game, the end of a predetermined stage in the game progress, and acquisition of a predetermined point.

  When “App C” or “App D” is selected as the customer destination application, the selected “App C” or “App D” is installed and can be executed or executed (start In some cases, a reward is given to the customer “application A”, which is the customer origin, by a normal reward. On the other hand, when "application B" is selected as the customer destination application, "application B" is activated on the condition that "application B" is installed on the user terminal and becomes executable during the campaign period. After that, when achieving the result point set in advance corresponding to the campaign (satisfying the reward giving condition), the reward is given by CP reward for the “app A” which is the customer sending source. In addition, for example, a reward giving period which starts from the beginning or in the middle of the campaign period and ends after the end of the campaign period is set, and a reward by CP reward is achieved when an achievement point is achieved within this reward giving period. Once the grant is made and the reward point has passed, CP reward will not be awarded even if the achievement point is achieved. If multiple outcome points are set, CP reward will be awarded for each achievement of the outcome points. In this way, the end point of the reward period is set to be later than the end point of the campaign period, and for the user installed at the end of the campaign period, the period until the achievement point is achieved is considered. ing.

  In addition, even if the users of the plurality of applications installed in the user terminal are the same, user information registered for each application (for example, user ID which is identification information for uniquely identifying the user) may be different. Therefore, in the mutual customer sending system according to the present embodiment, it is unique identification information which is information uniquely identifiable for each user terminal, and the user terminal can be specified (a user using the user terminal can be specified) ) Management is performed using unique identification information (hereinafter referred to as "reward user ID"). As a result, even when the user ID differs between the applications, the user terminal can be specified using the reward user ID, and mutual customer feed between the applications can be easily performed.

  Furthermore, in the mutual customer feed system of the present embodiment, the reward user ID and the user ID registered in each application (hereinafter, referred to as “application user ID”) are associated and managed. Thereby, even when the user ID differs between applications, the application user ID between the applications is associated via the reward user ID, so that the user of the customer sending source application can be easily specified and rewarded. Is also possible. In the following description, identification information for uniquely identifying an application is referred to as an "application ID".

  In addition, when customer-sending from the customer-sending application to the customer-sending application is performed, the customer-sending application can be the customer-sending application. For example, when customer sending from "application A" to "application B" is performed, "application B" uses "application C" or "application D" for which customer sending has not been performed as a customer destination application, It can be a customer-sending source application that sends a customer to “application C” or “application D”. At this time, if "App C" or "App D" is not eligible for the campaign period with "App B", it will normally be eligible for reward, and if it is in the campaign period for "App B" Is subject to CP rewards. Also, for example, in the case where the customer sending from "application A" to "application C" is performed, "application C" in which the customer sending has been performed is "application B" in which the customer sending has not yet been performed or It can be a customer-sending source application that sends a customer to “application D”.

In addition, as an example of the state of the application, a non-operating state (Not running), a normal operating state (Active) in which some processing is being performed, and a background state in which some processing is being performed but not displayed on the screen There are (BackGround) and a suspended state (Suspended) suspended without executing any processing. Here, “start of target application” refers to transition from a non-operating state (Not running), a suspended state (Suspended), or a suspended state (Suspended) to a normal operating state (Active). Also, “end of target application” refers to transition from a normal operation state (Active) to a non-operation state (Not running), a suspended state (Suspended), or a suspended state (Suspended). In addition, when a plurality of applications can be in the normal operation state simultaneously, “start of target application” can be operated for the user, for example, by displaying the target application on the foreground of the screen. It means to shift to the state.
Also, installing an application includes not only introducing a program of an application that has not been installed in the user terminal anew, but also updating (updating) the program of the application to correspond to the mutual customer delivery system. That is, it includes downloading and updating an update program for supporting the mutual customer delivery system with respect to the application installed in the user terminal.

[Network system configuration]
FIG. 2 is a schematic block diagram showing an example of the configuration of the network system 1 according to the first embodiment of the present invention for realizing the mutual customer feed 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, an application server 320,... And an application store 400, and these computer devices are communicably connected via a network NW. Here, since the plurality of user terminals 100 -N have the same configuration, unless otherwise specified, the description of “−1”, “−2” and the like will be omitted and the user terminal 100 will be described.

  The application server 300 is a server device corresponding to an application that can be installed on the user terminal 100. Here, the application server 310 corresponding to the game A and the application server 320 corresponding to the game B communicate with the user terminal 100 via the network NW, assuming that the application installed on the user terminal 100 is a game as an example. It shows that it is connected. The network system 1 is not limited to the application server 310 and the application server 320, and includes a plurality of application servers 300 corresponding to games that can be installed and played on the user terminal 100. Here, the application installed on the user terminal 100 means that the user terminal 100 performs processing (for example, processing of a game) on the application based on the installed program by installing the program of the application on the user terminal 100. It is a so-called native type application. The user terminal 100 transmits, to the application server 300, user information corresponding to a user who plays a game, and acquires, from the application server 300, necessary information during game play.

  The application store 400 is a server device that provides a store site (download service site) capable of downloading an application installable to the user terminal 100. The user downloads and installs the purchased application to the user terminal 100 by connecting to the application store 400 from the user terminal 100 via the network NW and purchasing the desired application for a fee or free of charge. Can.

Here, from the provider of the application (game), it is desirable to provide a service that motivates the purchase so that more users can purchase the provided application.
For example, an advertisement (banner) of an application not yet installed is displayed on a display screen displayed while using an application installed in the user terminal 100 or a display screen transitioned by a user operation, and the advertisement (banner) When the) is directed to the above-mentioned store site, and then the selected application is downloaded and installed on the user terminal 100 and becomes executable or is executed, the advertisement that triggered the download ( It is conceivable to provide a service in which a reward is given to the user's own use of the original application on which the banner is displayed. In this case, a reward available to the original application (e.g., an item usable in the game, a game point, etc.) is given to the user himself, which motivates the user who wants to obtain the reward to purchase a new application. . This makes it possible to promote sales of applications.

  The management server 200 manages information on applications corresponding to the mutual customer feed system of the present embodiment and information on normal rewards or CP rewards, and communicates with the user terminal 100 to manage customer feed information between the applications and the like. It is a management device that controls the processing of the reward. Specifically, the management server 200 associates, for example, the application ID of the customer sending application, the application ID of the customer sending application, and the reward user ID as customer sending information from the customer sending application to the customer sending application. to manage.

  The user terminal 100 is a terminal device used by a user, and 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 is described as a smart phone.

  FIG. 3 is a schematic block diagram showing 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 receives an instruction of the user according to an operation from the user and generates input instruction information according to the content of the instruction. 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 integrated as a touch panel that 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, a hard disk drive (HDD), or a combination thereof. A program for control (for example, an OS (Operating System) for causing the terminal control unit 150 to perform a basic operation), a program of an installed application, various information, and the like are stored.

  The terminal control unit 150 includes an information processing apparatus 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 the processing of the basic operation based on the OS stored in the terminal storage unit 140 and executes the processing based on the program of the application (the program of the game). In addition, the terminal control unit 150 executes, via the OS, the functions of various applications (a web browser, an application for displaying a store page of a store site provided by the application store 400, etc.) operable on the OS. Do.

  The network NW may be, for example, a mobile telephone network, a personal handy-phone system (PHS) network, a virtual private network (VPN) network, a dedicated communication network, a wide area network (WAN), a local area network (LAN), or a public network (PSTN). It is an information communication network configured by a switched telephone network (public switched telephone network) or the like or a combination thereof.

[Configuration and processing of mutual customer delivery system]
Next, the configuration and processing of the mutual customer delivery system will be described with reference to FIG.
FIG. 4 is an explanatory diagram for explaining an example of the configuration and processing of the mutual customer sending system in the network system 1 of the present embodiment.
Here, customer sending application 10 (game A) is already installed in user terminal 100 used by user X, and customer sending application 10 (game A) is executed, and based on the operation of user X, When the customer application 20 (game B) is installed in the user terminal 100 and executed, an example in which a reward is given to the user X in the customer sending application 10 (game A) will be described. Although the customer-sending source application 10 (game A) is not a customer-sending source at the time of installation, it is referred to as the customer-sending source application 10 for convenience.

  In this figure, in the user terminal 100, the installed customer sending source application 10 (game A) executed by the control of the terminal control unit 150 and the store 30 (store site store page activated during the customer sending process) And the customer destination application 20 (game B) to be newly installed and executed.

  The customer sending source application 10 (game A) transmits a user ID corresponding to the user X who plays the game A to the application server 310 (game A), or the information necessary for playing the game A Get from game A). Similarly, when the customer destination application 20 (game B) is installed on the user terminal 100, the customer destination application 20 (game B) uses the user ID corresponding to the user X who plays the game B as an application server. It transmits to 320 (game B), and acquires required information during play of the game B from the application server 320 (game B).

  Further, software (hereinafter referred to as SDK (Software Development Kit) 11) for mutual customer processing is incorporated in the application corresponding to the mutual customer support system of the present embodiment. The SDK 11 is, for example, a collection of APIs (Application Programming Interfaces) for mediating the management server 200 with each application corresponding to the mutual customer sending system installed in the user terminal 100. In this figure, the SDK 11A is incorporated in the customership source application 10 (game A), and the SDK 11B is incorporated in the customership destination application 20 (game B). Each of the SDK 11A and the SDK 11B has a configuration for executing a function corresponding to each of the customer-delivery source application 10 and the customer-destination application 20, and a necessary function is executed according to each application. Since the application corresponding to the mutual customer feed system can be either the customer feed source application 10 or the customer feed destination application 20, the SKD 11 having the configuration of both the SDK 11A and the SDK 11B is incorporated.

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

  Among the applications corresponding to the mutual customer feed system, there may be applications corresponding to the customer destination application 20 only. In that case, only the SDK 11B may be incorporated, or the SDK 11 may be incorporated so as not to operate the SDK 11A. Moreover, in the case of the application corresponding only to the customer sending destination application 20, there is no need to have an application server corresponding to the application, so for example, an application operating in a stand-alone in the user terminal 100 corresponds to the mutual customer sending system. It can be the target of the application.

  Further, among the applications corresponding to the mutual customer feed system, there may be applications corresponding to only the customer feed source application 10. In that case, only the SDK 11A may be incorporated, or the SDK 11 may be incorporated so as not to function the SDK 11B. For example, an application that does not accept registration of a new user when it is determined that the provision of a service by the application is terminated may not have a function as the customer sending destination application 20.

  The configuration provided with the above-described SDK 11 (in this figure, SDK 11A, SDK 11B) and the management server 200 is the main configuration of the mutual customer sending system of the present embodiment (see reference numeral 500). And write.

  The management server 200 communicates with the SDK 11 incorporated in the application corresponding to the mutual customer referral system 500 installed in the user terminal 100 to execute mutual customer referral processing. Further, the management server 200 transmits information on the reward to the application server 310 (game A) corresponding to the customer sending source application 10 (game A). Thereby, a reward is given from the application server 310 (game A) to the user X in the customer sending source application 10 (game A).

As shown in this figure, the management server 200 includes a communication unit 210, a management unit 220, a storage unit 230, and a control unit 240. 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 management unit 220 stores, in the storage unit 230, information on applications corresponding to the mutual customer sending system 500, information on applications participating in the campaign, information on customer sending between applications, information on ordinary rewards and CP rewards, etc. to manage. The storage unit 230 stores various information under the control of the management unit 220 or the control unit 240. The control unit 240 controls the exchange of information related to the mutual customer sending process with the user terminal 100 or the application server 310 (game A) and controls the process related to the reward.
In the following description, an application corresponding to the mutual customer sending system 500 to be managed by the management unit 220 is also referred to as a “target application”, and a specific application participating in a campaign among the target applications. Is also referred to as a "specific application".

Subsequently, a schematic flow of mutual customer feed processing will be described.
Here, it is assumed that the information of the target application corresponding to the mutual customer feed system 500 is managed in advance by the management server 200. In addition, the user terminal 100 has already acquired the reward user ID of the user X, which is unique identification information corresponding to the user terminal 100, and the mutual customer support system 500 in which the acquired reward user ID is installed in the user terminal 100. It is assumed that it is stored in a predetermined area (inter-application shared area) of the terminal storage unit 140 so as to be able to refer to the corresponding application.

(1) When the customer sending application 10 (game A) is installed in the user terminal 100, the SDK 11A incorporated in the customer sending application 10 (game A) is installed the customer sending application (game A) Installation notification information indicating that the connection has been made is transmitted to the management server 200 (REQ 11). Here, the installation notification information includes, for example, the application ID of the customer sending source application 10 (game A) and the reward user ID.

(2) Upon acquiring the installation notification information transmitted from the user terminal 100 (SDK 11A), the management server 200 transmits response information (notification result) indicating acquisition to the user terminal 100 (SDK 11A) RES 11). Further, the management server 200 manages the application ID of the customer sending source application 10 (game A) included in the acquired installation notification information and the reward user ID in association with each other.

(3) The user terminal 100 (SDK 11A) is a list for requesting an application list of at least one target application of target applications corresponding to the mutual customer sending system 500 (information indicating target applications to be candidates for the customer destination application 20). Request notification information is sent to the management server 200 (REQ12).

(4) When the management server 200 acquires list request notification information from the user terminal 100 (SDK 11A), the management server 200 does not acquire installation notification information from the user terminal 100 among a plurality of target applications to be managed (that is, An application list of at least one target application that has not been installed in the user terminal 100 is transmitted to the user terminal 100 (SDK 11A) (RES 12). At this time, the management server 200 associates information on the campaign with a specific application participating in the campaign and transmits it.
When acquiring the application list from the management server 200, the user terminal 100 (SDK 11A) displays a list LT of target applications based on the acquired application list on the display unit 120.

(5) When one of the target applications is selected by the user X from the list LT of target applications displayed on the display unit 120, the user terminal 100 (SDK 11A) receives the customer request source application 10 (game A). And sends to the management server 200 customer sending information indicating that the selected target application (here, the customer sending destination application 20 (game B)) has been sent the customer (REQ 13). Here, the customer-sending information includes, for example, an application ID of the customer-sending source application 10 (game A), an application ID of the customer-sending destination application 20 (game B), and a reward user ID.

(6) When the management server 200 acquires customer-sending information from the user terminal 100 (SDK 11A), the management server 200 instructs the customer-sending application 20 (game B) to be an installable screen based on the acquired customer-sending information. (For example, instruction information for displaying the screen on the display unit 120 of the user terminal 100) is transmitted to the user terminal 100 (SDK 11A) (RES 13). Further, the management server 200 associates the application ID of the customer sending source application 10 (game A) included in the customer sending information acquired, the application ID of the customer sending destination application 20 (game B), and the reward user ID with each other. to manage.

(7) The store 30 is an application that displays the store page of the store site where the customer destination application 20 (game B) can be installed (downloadable) when the user terminal 100 acquires the above-described instruction information from the management server 200. Start up The store 30 acquires, from the application store 400, a store page on which the customer-delivery application 20 (game B) can be installed and causes the display unit 120 to display the store page. After the customer destination application 20 (game B) is downloaded and installed in the user terminal 100 by the operation of the user X, the customer destination application 20 (game B) installed by the operation of the user X continues to be activated.

(8) The user terminal 100 (SDK 11B) transmits installation notification information indicating that the customer sending destination application 20 (game B) has been installed to the management server 200 (REQ 14). Here, the installation notification information includes, for example, the application ID of the customer sending destination application 20 (game B) and the reward user ID.

(9) Upon acquiring the installation notification information transmitted from the user terminal 100 (SDK 11B), the management server 200 transmits response information indicating the acquisition to the user terminal 100 (SDK 11B) (RES 14). Also, the management server 200 uses the customer terminal application 20 (game B) on the user terminal 100 based on the acquired installation notification information and customer management information being managed. It is determined that the customer is sent from.

(10) Here, it is assumed that the customer destination application 20 (game B) is a specific application and is in a campaign with the customer origin application 10 (game A). In this case, the user terminal 100 (SDK 11 B) based on satisfaction of the reward giving condition set in advance corresponding to the campaign in the customer sending destination application 20 (game B). Sends to the management server 200 reward notification information (information indicating that the achievement point has been reached) indicating that the reward condition has been satisfied (REQ 15). When there are a plurality of outcome points, the user terminal 100 (SDK 11B) sends, to the management server 200, the reward granting notification information (information indicating the achievement point arrival) for that number based on reaching each outcome point. Send.

(11) When the management server 200 acquires the reward granting notification information from the user terminal 100 (SDK 11B), the management server 200 is reward granting information based on the obtained reward granting notification information, and is a result point in the customer sending application 20 (game B). Are sent to the application server 310 (game A) corresponding to the customer sending source application 10 (game A) (processing of CP reward). In the case where there are a plurality of outcome points, the management server 200 transmits, to the application server 310 (game A), reward granting information based on the reward granting notification information of the number.
Here, the management server 200 transmits, to the application server 310 (game A) corresponding to the customer sending source application 10 (game A), information indicating arrival of the result point in the customer sending destination application 20 (game B). Setting contents of the result points in the customer sending destination application 20 (game B), and reward contents given to the customer sending application 10 (game A) when the respective result points are reached. Not involved. When a list LT of target applications is displayed on the display screen of the user terminal 100, the link content of the site on which the reward content due to CP reward is posted is displayed without displaying the reward content due to CP reward on the display screen. The reason is that the management server 200 is not involved in the content of the reward.

  If the customer sending destination application 20 (game B) is a target application that is not a specific application (or if it is a specific application but outside the campaign period), the management server 200 determines that the user terminal 100 (SDK 11B) If install notification information indicating that the customer destination application 20 (game B) transmitted from the client is installed is acquired, reward granting information indicating that the result point by ordinary reward has been reached is sent to the application server 310 (game A). Send to (normally reward process).

  With the flow of such processing, the customer-sending source application 10 (game A) sends a customer to the customer-sending destination application 20 (game B). Here, in the mutual customer sending system 500, each piece of information exchanged between the SDK 11A and the SDK 11B and the management server 200 is associated by the reward user ID corresponding to the user terminal 100 directly or via any information. It is done. As a result, even if the application user IDs of the customer feed application 10 (game A) and the customer send destination application 20 (game B) differ, the mutual customer feed system 500 performs mutual customer feed processing between applications or Reward processing can be easily performed.

  Next, details of each configuration of the SDK 11 (SDK 11A and SDK 11B) and the management server 200 included in the mutual customer feed system 500 will be described.

[Functional Configuration of User Terminal 100 (SDK 11)]
FIG. 5 is a block diagram showing an example of a functional configuration of mutual customer feed processing executed by the terminal control unit 150 based on the SDK 11 in the user terminal 100 according to the present embodiment. With reference to FIG. 5, the functional configuration of the mutual customer feed processing executed by the user terminal 100 (SDK 11) in the mutual customer referral system 500 will be described.

The SDK 11 includes an initialization processing unit 101, a list request unit 104, a display control unit 105, a customer information notification unit 106, and a reward assignment notification unit 107.
When the application into which the SDK 11 is to be incorporated is installed on the user terminal 100, the initialization processing unit 101 acquires information (for example, an application ID, an application user ID, etc.) related to the application as processing at the time of initial activation. The initialization processing unit 101 further includes a unique identification information acquisition unit 102 and an installation notification unit 103.

The unique identification information acquisition unit 102 acquires a reward user ID which is unique identification information uniquely set for each user terminal 100 and is unique identification information capable of uniquely identifying a user who uses the user terminal 100. . For example, the unique identification information acquisition unit 102 generates a pseudo random number sequence, and uses the generated pseudo random number sequence to obtain a reward user ID corresponding to the user terminal 100 so as not to overlap with the reward user IDs of other user terminals 100. Generate and get. Also, the unique identification information acquisition unit 102 stores the acquired reward user ID in the inter-application shared area of the terminal storage unit 140 so that any target application installed in the user terminal 100 can refer to it.
Here, the unique identification information acquisition unit 102 acquires a reward user ID when the installed target application is a target application installed in the user terminal 100 first among a plurality of target applications. That is, when the reward user ID is not stored in the inter-application shared area of the terminal storage unit 140, the reward user ID is acquired. And this acquired reward user ID is used also in the object application installed after that.

  The installation notification unit 103 transmits installation notification information indicating that the target application installed in the user terminal 100 has been installed, to the management server 200. Here, the installation notification information described above includes the application ID of the installed target application and the reward user ID corresponding to the user terminal 100. It should be noted that the case where the user has downloaded from the store site and installed the target application without passing through the customer feed process by the mutual customer feed system 500 and the case where the user installed via the customer feed process by the mutual customer feed system 500 Installation notification information is transmitted from the user terminal 100 in any case where the target application is installed. When the target application installed is a specific application, the installation notification unit 103 transmits, to the management server 200, installation notification information indicating that the specific application installed in the user terminal 100 has been installed. Become.

  Further, the installation notification unit 103 may transmit, to the management server 200, installation notification information further including the application user ID of the installed target application of the user who has installed the installed target application. Accordingly, the management server 200 that has acquired the installation notification information can manage the application user ID and the reward user ID in the installed target application in association with each other. The transmission timing of the application user ID may be included in other information without being included in the installation notification information.

  Here, the process in which the installation notification unit 103 transmits installation notification information to the management server 200 is the same whether the SDK 11A of the customer sending application 10 or the SDK 11B of the customer sending application 20 is the same. Executed when each installed application is launched.

The list request unit 104 is list request notification information for requesting an application list of at least one target application (or specific application) of a plurality of target applications based on a predetermined operation (first operation) in the customer sending source application 10 Are sent to the management server 200. Here, the predetermined operation described above is, for example, an operation performed by the user on the input unit 110 for acquiring an application list of a target application (or a specific application) from the management server 200 in the customer sending source application 10. Further, in the list request notification information described above, for example, the application ID (send customer source information) of the customer send source application 10 (target application (or specific application)) and the reward user ID corresponding to the user terminal 100 included.
Further, the list request unit 104 acquires the application list transmitted from the management server 200 based on the transmitted list request notification information.
The list request unit 104 transmits list request notification information for requesting an application list of a target application including a specific application for which a campaign has been set with the customer sending source application 10 to the management server 200. Alternatively, list request notification information for requesting an application list of a target application not including the specific application may be transmitted to the management server 200. Further, the list request unit 104 may transmit list request notification information for requesting an application list of only specific applications for which a campaign is set with the customer sending source application 10 to the management server 200.

  The display control unit 105 causes the display unit 120 to display a list LT of target applications based on the application list acquired by the list request unit 104. For example, the display control unit 105 displays a list LT of target applications by overlapping or switching the display screen displayed on the display unit 120 by the customer sending source application 10.

The customer-sending information notification unit 106 transmits, to the management server 200, customer-sending information indicating that the customer has been sent to the target application (or specific application) selected from the customer-sending source application 10. Here, the target application (or specific application) selected from the customer sending source application 10 is a user's operation from one or more target applications (or specific applications) included in the application list displayed on the display unit 120 The second application refers to any application selected based on the second operation).
Further, the above-mentioned customer sending information includes, for example, an application ID (sending customer source information) of the customer sending source application 10, a selected target application (or specific application), ie, an application ID of the customer sending destination application 20 The reward user ID corresponding to the terminal 100 is included.

  For example, when a specific application during the campaign period is selected from the list of target applications LT based on the above-described second operation during the campaign period, the customer-sending information notification unit 106, for example, sends a customer The customer ID information including the application ID (sender source information) of the original application 10, the selected specific application, that is, the application ID of the customer destination application 20, and the reward user ID corresponding to the user terminal 100 is sent to the management server 200 To send.

  The reward granting notification unit 107 indicates reward granting notification information indicating that the reward granting condition has been satisfied based on satisfaction of the reward granting condition set in advance for the campaign in the specific application during the campaign period. Are sent to the management server 200. Here, the above-mentioned reward giving notification information includes, for example, an application ID (send customer information) of a specific application (send customer application 20) during the campaign period, a reward user ID corresponding to this user terminal 100, and the like. Is included.

  Among the functional configurations based on the SDK 11 shown in FIG. 5, for example, the initialization processing unit 101 (the unique identification information acquisition unit 102, the installation notification unit 103), the list request unit 104, the display control unit 105, The information notification unit 106 corresponds to the functional configuration of the SDK 11A (that is, the functional configuration of the customer sending source) corresponding to the customer sending source application 10. Further, for example, the initialization processing unit 101 (the unique identification information acquisition unit 102, the installation notification unit 103) and the reward giving notification unit 107 have the functional configuration of the SDK 11B corresponding to the customer sending application 20 (that is, the customer sending Corresponding to the functional configuration of

[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 block diagram showing an example of the configuration of the management server 200 according to this embodiment. As described with reference to FIG. 4, the management server 200 includes the communication unit 210, the management unit 220, the storage unit 230, and the control unit 240. Here, the management unit 220 and the storage unit The respective configurations of 230 and the control unit 240 will be described in detail.

  The management unit 220 includes an application management unit 221, an installation information management unit 222, and a customer-sending information management unit 223. The management unit 220 associates each information to be managed, stores the information in the storage unit 230, and manages it.

  The application management unit 221 manages information (target application information) related to a plurality of target applications corresponding to the mutual customer sending system 500. The application management unit 221 also manages information on a campaign having a campaign period (an example of a first period) set for a plurality of specific applications. For example, the application management unit 221 manages the information indicating the campaign (the name of the campaign etc.) and the information related to the campaign (the campaign period, the information showing the link destination of the publication place of the information showing the reward, etc.) in association with each other.

Based on the installation notification information acquired from the user terminal 100, the installation information management unit 222 manages, as installation information, the reward user ID included in the installation notification information and the application ID of the installed target application.
The installation information management unit 222 may manage, as installation information, the reward user ID included in the installation notification information, the application ID of the target application, and the application user ID of the target application.

The customer-sending information management unit 223 includes the reward user ID included in the customer-sending information sent from the user terminal 100 and acquired by the management server 200, the application ID of the customer-sending source application 10, and the application ID of the customer-sending destination application 20. It manages it as a record of customer sending information in association.
Note that, when a campaign is set for the customer sending application 10 and the customer receiving application 20, the customer information management unit 223 may further manage as information on customer information associated with information indicating a campaign. .

The storage unit 230 stores various types of information managed by the management unit 220 or the control unit 240.
The storage unit 230 includes a target application information storage unit 231, a normal reward information storage unit 232, an inter-application filter storage unit 233, a campaign information storage unit 234, a campaign participation application information storage unit 235, and an installation information storage unit 236. And a customer satisfaction information storage unit 237 and a reward establishment information storage unit 238. The various information may be stored in a format suitable for the use of the information, such as a database table format or a JSON (JavaScript (registered trademark) Object Notation) format.

The target application information storage unit 231 stores target application information related to a target application corresponding to the mutual customer sending system 500. FIG. 7 is a diagram showing an example of target application information stored in the target application information storage unit 231. As shown in FIG. The target application information includes the application ID (ApID) of the target application, the notification destination URL (Notice URL), the store URL (ApStore URL), the application name (ApNAME) indicating the name of the target application, and the description of the target application. An application description (ApDOC) which is information, an application icon image (ApICO) which is an icon image indicating the target application, and an application price (ApPRICE) are associated with each other.
The notification destination URL (Notice URL) is a URL (Uniform Resource Locator) of the notification destination of the reward, and for example, the URL of the application server 300 corresponding to the target application is set. The store URL (ApStore URL) is a URL of a page of a sales site (application store 400) that can download the target application. The application price (ApPRICE) is a sales price of the target application. These pieces of target application information are used, for example, in the list LT of target applications displayed on the user terminal 100.
Note that these pieces of target application information are, for example, preset and stored in the target application information storage unit 231 before being downloadable from the application store 400, and managed by the application management unit 221.

The normal reward information storage unit 232 stores information (normal reward information) on the normal reward for each target application. FIG. 8 is a diagram showing an example of the normal reward information stored in the normal reward information storage unit 232. As shown in FIG. The normal reward information indicates an item ID (Item ID) identifying an item given as a normal reward in the target application, an application ID (ApID) of the target application, a minimum price (min_price), and a name of the item The reward item name (ItemName) is associated with the number of reward items (ItemNum) indicating the number of rewards of the item. The lowest price (min_price) is usually set to the price of the target application targeted for the reward. These pieces of normal reward information are used, for example, in a list LT of target applications displayed on the user terminal 100.
The normal reward information is set, for example, when the target application information is stored in the target application information storage unit 231, and is stored in the normal reward information storage unit 232, and is managed by the application management unit 221.

  The inter-application filter storage unit 233 stores filter information (inter-application filter information) between applications for limiting target applications that can be mutually sent. The process of limiting the target applications that can be mutually sent to customers will be described in detail in the second embodiment.

  The campaign information storage unit 234 stores information (campaign information) on a campaign of a specific application that participates in a campaign among target applications. FIG. 9 is a diagram showing an example of the campaign information stored in the campaign information storage unit 234. As shown in FIG. The campaign information includes a campaign ID (CpID), a campaign name (CpNAME), a campaign start date (CpStartDATE), a campaign end date (CpEndDATE), a reward grant start date (RewardStartDATE), and a reward grant end date (RewardEndDATE). ) Is associated with.

  Campaign ID (CpID) is identification information for identifying a campaign. The campaign name (CpNAME) indicates the name of the campaign. The campaign start date (CpStartDATE) and the campaign end date (CpEndDATE) indicate the start date and the end date of the campaign period, respectively. Here, when the customer destination application 20 is installed in the campaign period defined by the campaign start date and the campaign end date and time, the qualification of the CP reward can be obtained.

Moreover, in CP reward, for example, a plurality of outcome points are set, and it is defined that a user who has started using the customer destination application 20 during the campaign period defines when the outcome point should be reached. It is a reward granting period defined by the date and time (RewardStartDATE) and the reward granting end date (RewardEndDATE). For example, with respect to a campaign period (an example of a first period), a reward provision period (an example of a second period) which starts from the beginning or the middle of the campaign period and ends after the campaign period is set. As an example, the same date is set as the campaign start date and the reward giving start date, and the reward giving end date is set one week after the campaign end date. The campaign information is set in advance before the start date and time of the campaign, stored in the campaign information storage unit 234, and managed by the application management unit 221. Further, as the campaign information, similar information is set in the application server 300 and the management server 200 corresponding to each specific application that implements the campaign.
Note that the reward giving period may not be set separately from the campaign period, or the reward giving period may be the same as the campaign period.

  The campaign participation application information storage unit 235 stores information (a campaign participation application information) indicating a specific application that participates in the campaign set in the campaign information storage unit 234. Here, at least two applications are set in one campaign because it is a campaign for mutual customer sending between applications. FIG. 10 is a diagram showing an example of campaign participation application information stored in the campaign participation application information storage unit 235. As shown in FIG. The campaign participation application information is associated with a campaign ID (CpID), an application ID (ApID) of a specific application participating in the campaign of this campaign ID, and a campaign page URL (CpPage URL). The campaign ID (CpID) corresponds to the campaign ID included in the campaign information stored in the campaign information storage unit 234.

  The campaign page URL (CpPage URL) is information indicating a page (website page) on which information on a CP reward reward given when the application is installed and used during a campaign period is posted. Also on this page, information (description and price) related to the application will be posted. For example, when a campaign is set for the customer sending source application 10 (game A) and the customer sending destination application 20 (game B), a page in the application server 310 (game A) corresponding to each application and the application server Each URL with the page in 320 (game B) may be set as a campaign page URL. In addition, a campaign dedicated site may be separately provided, and the same URL for the campaign dedicated site may be set for any of the customer sending application 10 (game A) and the customer sending application 20 (game B). . Also, the campaign dedicated site may be provided in the management server 200.

As described above, the information related to the CP reward reward is set to be posted on the application server 300 or the page of the campaign dedicated site, and the management server 200 does not have to manage it.
The above-mentioned campaign participation application information is set when the target application participates in the campaign as a specific application, is stored in the campaign participation application information storage unit 235, and is managed by the application management unit 221.

  The information included in the campaign information and the campaign participation application information is managed in the management server 200 as described above, and is similarly managed in the application server 300 corresponding to the specific application participating in the campaign. . In addition, the user terminal 100 having installed a specific application participating in the campaign can acquire, from the application server 300 corresponding to the specific application, information included in the campaign information and the campaign participation application information of the application. .

  The installation information storage unit 236 stores installation information managed by the installation information management unit 222 based on the installation notification information transmitted from the user terminal 100 and acquired by the management server 200. FIG. 11 is a diagram showing an example of installation information stored in the installation information storage unit 236. As shown in FIG. The installation information is associated with, for example, a reward user ID (Reward UID) included in the acquired installation notification information, an application ID (Ap ID), and an application user ID (Ap UID).

  Here, from the user terminal 100 either in the case where the target application is simply installed without the customer sending process by the mutual customer sending system 500 or in the case where the target application is installed via the customer sending process by the mutual customer sending system 500. The installation notification information is transmitted, and installation information based on the installation notification information acquired by the management server 200 is stored in the installation information storage unit 236. That is, the installation information storage unit 236 records installation information of all target applications installed in the user terminal 100. Therefore, even if the target application once installed is uninstalled and then installed again, the installation information of the target application is stored in the installation information storage unit 236, so that the management server 200 gives a double reward. Can be prevented.

  The customer-sending information storage unit 237 stores (records) the customer-sending information managed by the customer-sending information management unit 223 based on the customer-sending information transmitted from the user terminal 100 and acquired by the management server 200. FIG. 12 is a diagram illustrating an example of customer-sending information stored in the customer-sending information storage unit 237. Customer sending information is associated with reward management ID (Reward ID), reward user ID (Reward UID), customer sending application ID (ApIDfrom), customer sending application ID (ApIDto), and campaign ID (CpID). It is done. The reward management ID (Reward ID) is a management ID issued in order of acquisition of each customer information so that it can be identified for each customer information. The customer sending application ID (ApIDfrom) is an application ID of the customer sending application 10, and the customer application ID (ApIDto) is an application ID of the customer sending application 20. At this time, if the customer-sending application 10 and the customer-sending application 20 are both in the same campaign campaign period, the campaign ID of the campaign is stored, and if it is not a campaign period, "null" is set as the campaign ID. Ru.

  Also, since the application list does not include the target application already installed on the user terminal 100 or the target application that has been installed (target application uninstalled thereafter), the target to be newly installed Customer-sending information to the application is stored in the customer-sending information storage unit 237. Even when customer-sending information is stored in the customer-sending information storage unit 237, the customer-sending application 20 for the customer-sending information is not necessarily downloaded and installed.

  Reward establishment information storage unit 238 is customer sending source application 10 (game A) when the conditions for awarding rewards for normal reward and CP reward are satisfied by the customer sending process indicated by the customer sending information stored in customer sending information storage unit 237. The reward establishment information indicating whether or not the reward giving information has been notified to the application server 310 (game A) corresponding to

  In the case of the normal reward, for example, the installation information of the target application corresponding to the customer sending application ID of the customer sending information stored in the customer sending information storage unit 237 is stored in the installation information storage unit 236 as the reward establishment information. At the same time, a new record (data of one piece of reward establishment information) corresponding to the customer information is generated and stored in the reward establishment information storage unit 238.

  Further, in the case of CP reward, this reward establishment information is obtained, for example, from the user terminal 100 when reward grant notification information corresponding to the customer destination application ID of the customer referral information stored in the customer referral information storage unit 237 is obtained. A new record corresponding to the customer information is generated and stored in the reward establishment information storage unit 238.

FIG. 13 is a diagram showing an example of the reward establishment information stored in the reward establishment information storage unit 238. As shown in FIG. The reward establishment information is associated with a reward management ID (RewardID), an outcome point ID (RewardSpotID), and an established state (RewardStatus). The reward management ID (Reward ID) corresponds to the reward management ID included in the customer referral information stored in the customer referral information storage unit 237.

The result point ID (RewardSpot ID) is identification information of a result point to which a reward is given in the customer destination application 20 set based on the reward giving condition.
In the case of CP reward, identification information indicating a result point (reward grant condition in the customer destination application 20) set in advance corresponding to the campaign is set in the result point ID (RewardSpotID). When there are a plurality of outcome points, a plurality of records in which a plurality of outcome point IDs are associated with the same reward management ID are generated and stored in the reward establishment information storage unit 238.

In the case of the normal reward, that is, when “null” is set in the campaign ID included in the customer referral information stored in the customer referral information storage unit 237, the outcome point (reward provision condition) is the customer destination application 20. Is installed, and "null" is set to the result point ID.
In addition, even in the case of CP reward, if the identification information on the condition that the customer destination application 20 is installed is set in the outcome point ID, the outcome point (reward provision condition as in the case of the normal reward) ) Is when the customer destination application 20 is installed and becomes executable or is executed.

  The establishment status (RewardStatus) is set with flag information indicating whether or not the reward application information has been notified to the application server 310 (game A) corresponding to the customer sending source application 10 (game A). That is, when a new record is generated in association with the reward management ID corresponding to the customer-sending information stored in the customer-sending information storage unit 237, the flag “0” (initial value) in the established state (RewardStatus) Not notified) is set. Thereafter, when the notification of the reward granting information to the application server 310 (game A) is completed, the establishment status (RewardStatus) is updated to the flag “1” (notified). When a response to the notification of the reward giving information from the application server 310 (game A) is acquired, the flag may be updated to “1” (notified).

Next, returning to FIG. 6, the configuration of the control unit 240 will be described.
The control unit 240 includes an installation notification acquisition unit 241, a list notification unit 242, a customer sending information acquisition unit 243, an installation guidance unit 244, a reward processing unit 245, and a clock unit 246.

  The installation notification acquisition unit 241 sets installation notification information indicating that the target application installed in the user terminal 100 specified by the reward user ID among the plurality of target applications is installed to the target application (the SDK 11 of the target application). Get from). As described above, the installation notification information includes, for example, the reward user ID corresponding to the user terminal 100 and the application ID of the target application. Further, the installation notification information may further include an application user ID of the target application. Then, the installation notification acquisition unit 241 supplies the acquired installation notification information to the installation information management unit 222.

  When the list notification unit 242 acquires the list request notification information transmitted from the customer sending application 10 (SDK 11A of the customer sending application 10) installed in the user terminal 100, the list notification unit 242 obtains the list request notification information based on the acquired list request notification information. At least one target application (or specific application) that has not acquired installation notification information from the user terminal 100 (that is, has not been installed on the user terminal 100) with reference to the target application information storage unit 231 and the installation information storage unit 236 Is sent to the user terminal 100.

Further, the list notification unit 242 refers to the campaign information storage unit 234 or the campaign participation application information storage unit 235, and transmits information on a campaign corresponding to one or more specific applications included in the application list.
At this time, the list notification unit 242 may display information related to the target application (application name, description, price, etc.), information related to the reward content of the normal reward, or information related to the campaign of the CP reward (information indicating a campaign period or reward corresponding to the campaign). A list LT of target applications based on the application list including the link destination of the publication place generates the data of the application list page that can be displayed on the user terminal 100 and transmits it to the user terminal 100. For example, the list notification unit 242 generates and generates data of an application list page in which a list LT of the target application described in HTML (HyperText Markup Language) format that can be displayed by a browser function that can be executed by the SDK 11 is displayed. The information indicating the link destination of the page to be transmitted is transmitted to the user terminal 100.

  The customer-sending information acquisition unit 243 is customer-sending information for the customer-sending-destination application 20 from the customer-sending-source application 10, and includes the reward user ID, the application ID of the customer-sending-source application 10, and the application ID of the customer sending-side application 20. Customer-included information including is acquired from the user terminal 100. Then, the customer-sending information acquisition unit 243 supplies the acquired customer-sending information to the customer-sending information management unit 223.

  The installation guiding instruction unit 244 instructs the user to instruct the customer destination application 20 to a screen that can be installed based on the application ID of the customer destination application 20 included in the customer sending information acquired by the customer information acquisition unit 243. It transmits to the terminal 100. For example, the installation guiding instruction unit 244 transmits, to the user terminal 100, instruction information for activating the store 30, which is an application for displaying the store page of the store site where the customer sending destination application 20 can be installed (downloadable).

  The reward processing unit 245 executes a first reward giving process (CP reward process) on CP reward and a second reward giving process (normal reward process) on normal reward.

  In the reward processing unit 245, when the installation notification acquisition unit 241 acquires installation notification information corresponding to the customer sending destination application 20, the customer sending information from the customer sending source application 10 to the customer sending destination application 20 is the customer sending information storage unit 237. It is determined whether or not it is stored in Then, when the customer referral information is stored in the customer referral information storage unit 237 (i.e., recording of the customer referral information for the customer referral destination application 20 is managed by the customer referral information management unit 223). It is determined that the customer sending destination application 20 is a target application sent from the customer sending source application 10 by the mutual customer sending system 500 under the condition that the request is made), and the CP reward process or the normal reward process is executed. Here, the reward processing unit 245 rewards the application server 310 corresponding to the customer sending application 10 so that a reward is given to the user in the customer sending application 10 in the CP reward processing or the normal reward processing. Send grant information. As described above, the installation notification information is transmitted to the management server 200 even when the target application is simply installed without the customer-sending process by the mutual customer-sending system 500. Therefore, by condition that the record of customer referral information for the customer referral destination application 20 is managed in the customer referral information management unit 223, the CP reward or the normal reward is simply taken when the customer referral destination application 20 is installed. It becomes possible to prevent giving.

  It is assumed that the customer sending application 20 has a campaign set with the customer sending application 10. In this case, the reward processing unit 245 determines that the customer destination application 20 has been installed within the campaign period, and sends it based on that the reward giving condition set in advance corresponding to the campaign is satisfied. When the reward application notification information is acquired from the customer application 20, a CP reward process based on the acquired reward application notification information is executed. On the other hand, it is assumed that the customer sending destination application 20 selected by the user terminal 100 does not have a campaign set with the customer sending source application 10. In this case, the reward processing unit 245 executes the normal reward processing when it is determined that the customer destination application 20 has been installed.

  Here, if the customer sending application 20 is a specific application for which a campaign has been set with the customer sending application 10, the reward processing unit 245 causes the installation notification acquiring unit 241 to send the customer notification 20 to the customer sending application 20. When the timing at which the corresponding installation notification information has been acquired is within the campaign period, it is determined that the customer destination application 20 has been installed in the user terminal 100 within the campaign period. Note that, even when the customer sending application 20 is set up with the customer sending application 10, the reward processing unit 245 installs the customer receiving application 20 on the user terminal 100 outside the campaign period even if a campaign is set. In general, the reward process is executed instead of the CP reward process.

  In the normal reward process, the reward processing unit 245 sends the customer notification associated with the reward user ID included in the acquired installation notification information based on the installation notification information acquired by the installation notification acquisition unit 241 from the customer destination application 20. The application user ID of the original application 10 is acquired with reference to the installation information storage unit 236. Then, the reward giving information including the application user ID is transmitted to the application server 310 corresponding to the customer sending source application 10.

  In the CP reward process, the reward processing unit 245 uses the installation information storage unit 236 for the application user ID of the customer sending source application 10 associated with the reward user ID included in the reward giving notification information acquired from the customer sending application 20. Get by reference. And based on the acquired reward provision notification information, the reward provision information containing the said application user ID is transmitted to the application server 310 corresponding to the customer-delivery origin application 10. FIG. In addition, even if the reward processing unit 245 further includes the campaign ID, the performance point ID, and the like included in the acquired reward giving notification information in the above-mentioned reward giving information and transmits it to the application server 310 corresponding to the customer sending application 10. Good.

  Further, in the case of the normal reward, the reward processing unit 245 stores, in the installation information storage unit 236, installation information of the target application corresponding to the customer destination application ID of the customer referral information stored in the customer referral information storage unit 237. Sometimes, a new record of the reward establishment information corresponding to the customer information is generated and stored in the reward establishment information storage unit 238. At this time, the reward processing unit 245 sets a flag “0” (not notified) in the established state (RewardStatus) included in the reward establishment information.

  On the other hand, in the case of CP reward, for example, when the reward processing unit 245 acquires, from the user terminal 100, reward granting notification information corresponding to the customer destination application ID of the customer referral information stored in the customer referral information storage unit 237. Then, a new record of the reward establishment information corresponding to the customer information is generated and stored in the reward establishment information storage unit 238. At this time, the reward processing unit 245 sets a flag “0” (not notified) in the established state (RewardStatus) included in the reward establishment information.

  For example, in the case of a CP reward, the reward processing unit 245 selects payment notification information corresponding to the customer destination application ID of the customer information stored in the customer information storage unit 237 for the campaign period corresponding to the customer information. When acquired internally from the user terminal 100, a new record of the reward establishment information corresponding to the customer information is generated and stored in the reward establishment information storage unit 238. In addition, when the reward giving period is set to the campaign, the reward processing unit 245 pays the reward giving notification information corresponding to the customer destination application ID of the customer sending information stored in the customer sending information storage unit 237 When the reward granting notification information is acquired from the customer destination application 20 within the grant period, a new record of the reward establishment information corresponding to the customer referral information may be generated and stored in the reward establishment information storage unit 238. .

  Then, in any of the normal reward process and the CP reward process, the reward processing unit 245 establishes the reward establishment in response to the notification of the reward provision information corresponding to the reward establishment information being transmitted to the application server 310 (game A). The establishment status (RewardStatus) of the information is updated to the flag "1" (notified).

  The clock unit 246 measures the time to acquire the current date and time. The clocking unit 246 may acquire the current date and time from the date and time information provision server (not shown) that provides the current date and time data via the network NW. For example, the reward processing unit 245 determines, based on information indicating the current date and time counted by the clock unit 246, whether or not the current date and time is within a campaign period, and whether or not it is within a reward provision period. The various information storage units (231 to 238) stored and managed in the storage unit 230 indicate data registration dates and times indicating dates and times when the records were generated and dates and times when a part of the generated records was updated. The data update date may be stored in each record. For example, in the data registration date and time stored in the installation information storage unit 236, the date and time when the installation information acquired from the user terminal 100 clocked by the clock unit 246 is acquired is recorded, and the application corresponding to the installation information is installed in the user terminal 100 It becomes data indicating the date and time of

[Details of operation of mutual customer processing]
Next, with reference to FIG. 14 and FIG. 15, the detail of the operation | movement of the mutual customer sending process of the mutual customer sending system 500 by this embodiment is demonstrated. FIG.14 and FIG.15 is a flowchart which shows an example of operation | movement of the mutual customer sending process by this embodiment. The process shown in FIGS. 14 and 15 shows a detailed example of the flow of the outline process described with reference to FIG.

  First, with reference to FIG. 14, the process on the side of the customer sending source application 10 (game A) installed in the user terminal 100 will be described. That is, the management server 200 can install the customer-delivery-destination application 20 (game B) from the process (process (1)) executed by the SDK 11A after the customer-delivery-source application 10 (game A) shown in FIG. A detailed example up to the process (process of (6)) of transmitting to the user terminal 100 instruction information for guiding the user to the screen will be described.

  When the customer sending application 10 (game A) is installed on the user terminal 100, the initialization processing unit 101 of the SDK 11A incorporated in the customer sending application 10 (game A) is a process executed only at the first activation As an application ID (ApID) of the customer sending source application 10, an application user ID (ApUID) of the user X registered in the customer sending source application 10, and a campaign ID (CpID) when a campaign is set. Are acquired from the customer service source application 10 (game A) (step SA11).

  Next, the initialization processing unit 101 of the SDK 11A executes the initialization process of the SDK 11A. First, the initialization processing unit 101 determines whether or not initialization processing has been completed in the initialization processing (step SA12). If it is determined that the initialization processing has been completed (step SA12: YES), the initialization processing unit 101 terminates without executing the subsequent initialization processing, and proceeds to step SA17. On the other hand, when it is determined that the initialization process is not completed (step SA12: NO), the unique identification information acquisition unit 102 refers to the terminal storage unit 140 and determines whether or not the reward user ID has been acquired. (Step SA13). It is determined whether or not this reward user ID has already been acquired by storing the reward user ID in the inter-application shared area of the terminal storage unit 140 so that any target application installed in the user terminal 100 can refer to it. It is judged whether or not

  If it is determined that the reward user ID has already been acquired (step SA13: YES), the unique identification information acquisition unit 102 of the SDK 11A reads the reward user ID from the terminal storage unit 140, and proceeds to step SA16.

  On the other hand, when it is determined that the reward user ID has not been acquired (step SA13: NO), the unique identification information acquisition unit 102 determines the reward user ID (ID unique in the mutual customer sending system 500) corresponding to the user terminal 100. It generates and acquires (step SA14).

  Next, the unique identification information acquisition unit 102 stores the acquired reward user ID in the inter-application shared area of the terminal storage unit 140 (step SA15).

  Subsequently, the installation notification unit 103 of the SDK 11A transmits installation notification information indicating that the customer sending source application 10 (game A) has been installed to the user terminal 100 to the management server 200 (REQ 11, step SA16). . Here, the installation notification information includes a reward user ID (Reward UID) corresponding to the user terminal 100, an application ID (ApID) of the installed customer sending source application 10 (game A), and the customer sending source application 10 ( The application user ID (ApUID) of the user X registered in the game A) is included.

  Next, the installation notification acquisition unit 241 of the management server 200 acquires the installation notification information transmitted from the user terminal 100 (SDK 11A). Then, the installation notification acquisition unit 241 transmits response information (notification result) indicating that the installation notification information has been acquired to the user terminal 100 (SDK 11A) (RES 11). In addition, the installation information management unit 222 of the management server 200 receives the reward user ID (Reward UID) included in the installation notification information acquired by the installation notification acquisition unit 241 and the application ID (ApID) of the customer sending application 10 (game A). And the application user ID (ApUID) of the user X in the customer sending source application 10 (game A) are stored in the installation information storage unit 236 as installation information (step SE11).

  Upon acquiring the response information (notification result) transmitted from the management server 200, the initialization processing unit 101 of the SDK 11A sets a flag indicating that initialization has been completed, and ends the initialization processing (step SA17).

Next, with respect to the customer sending source application 10 (game A) operating in the user terminal 100, the user X applies a predetermined value to the input unit 110 for acquiring the application list of the target application that can be installed in the user terminal 100. It is assumed that the operation (first operation) is performed.
Based on a predetermined operation (first operation) in the customership source application 10, the list request unit 104 of the SDK 11A reads the reward user ID from the inter-application shared area of the terminal storage unit 140 (step SA23), The list request notification information for requesting the application list of the at least one target application of the target applications (information of the target application to be a candidate of the customer sending destination application 20) is transmitted to the management server 200 (REQ12, step SA24).
Here, the list request notification information includes a reward user ID (Reward UID) corresponding to the user terminal 100, an application ID (ApID) of the customer sending source application 10 (game A), and a campaign ID (CpID). . In addition, when a campaign is not set to customer-delivery origin application 10 (game A), "null" is set to campaign ID (CpID). Further, even if the list request notification information does not include the campaign ID (CpID), the application ID of the customer sending source application 10 (game A) is referred to with reference to the campaign participating application information storage unit 235 and the campaign information storage unit 234. Based on ApID), whether or not the customer feed source application 10 (game A) is executing a campaign, and when executing a campaign, acquires a corresponding campaign ID (CpID) in the management server 200 It is also possible.

  When the list notification unit 242 of the management server 200 acquires the list request notification information transmitted from the user terminal 100 (SDK 11A of the customer sending source application 10), the installation notification is issued from the user terminal 100 based on the acquired list request notification information. At least one target application which has not acquired information (that is, not installed in the user terminal 100) is extracted. Specifically, the list notification unit 242 targets the application ID associated with the reward user ID (RewardUID) included in the acquired list request notification information in the installation information stored in the installation information storage unit 236. By excluding (filtering) the application ID of the target application managed by the application information storage unit 231, at least one target application not installed in the user terminal 100 is extracted (step SE15). The list notification unit 242 is not installed in the user terminal 100 based on the application ID (ApID) of the customer sending source application 10 (game A) included in the list request notification information and the campaign ID (CpID). Only the specific application in which the campaign is set between the customer application 10 (game A) may be extracted from among the target applications. Note that there may be cases where the target application (specific application) that is not installed in the user terminal 100 can not be extracted because it does not exist.

  The filtering process for filtering the target application included in the application list that the list notification unit 242 transmits to the user terminal 100 according to the acquisition of the list request notification information is the condition stored in the inter-application filter storage unit 233 ( It can also be performed based on filter information. This filtering process will be described in the second embodiment.

  Next, the list notification unit 242 generates data of the application list page for displaying the target application list LT based on the extracted application list of the target applications on the user terminal 100 (step SE16), and the generated application list page Is sent to the user terminal 100, and is redirected to the application list page (RES12, step SE17). In addition, when there is no target application (specific application) which is not installed in the user terminal 100, an application list page describing that the target application (specific application) does not exist instead of the list LT of the target applications is displayed. Generate

When the user terminal 100 (SDK 11A) acquires the redirect instruction information corresponding to the application list page from the management server 200, the display control unit 105 of the SDK 11A causes the display unit 120 to display the application list page by the browser function (step SA25). .
Here, the display control unit 105 overlaps the display screen of the customer sending source application 10 (game A), which has been displayed on the display unit 120 until then, and displays this application list page. As a result, on the display unit 120 of the user terminal 100, a list LT of target applications selectable as the customer sending destination application 20 is displayed on the application list page.

When one of the target applications is selected by the user X from the list LT of target applications displayed on the display unit 120 of the user terminal 100, the customer sending information notifying unit 106 of the SDK 11A From A), customer sending information indicating that the customer is sent to the selected target application (here, the customer sending destination application 20 (game B)) is sent to the management server 200 (REQ 13, step SA26). Here, the customer sending information includes the application ID (ApID) of the customer sending source application 10 (game A), the application ID (ApID) of the customer sending destination application 20 (game B), and the reward user ID (Reward UID). , Campaign ID (CpID). In addition, when the campaign is not set to the customer sending source application 10 (game A) and the customer sending destination application 20 (game B), "null" is set to the campaign ID (CpID). In addition, it is also possible to acquire campaign ID (CpID) in the management server 200 based on the application ID (ApID) of the customer sending source application 10 (game A) without acquiring from the user terminal 100.
When the customer sending application 20 (game B) is selected, the display control unit 105 of the SDK 11A closes the application list page displayed on the display unit 120 in step SA25, and the customer sending application 10 (game A) Return to the) display screen.

  The customer information acquisition unit 243 of the management server 200 acquires customer information from the user terminal 100 (SDK 11A). Then, the customer-sending information management unit 223 receives the customer ID of the customer-sending source application 10 (game A) included in the customer-sending information acquired by the customer-sending information acquisition unit 243 (ApID) and the customer-sending application 20 (the game B). Are associated with the application ID (ApID), the reward user ID (RewardUID), and the campaign ID (CpID), and stored in the customer information storage unit 237 as a record of customer information (step SE18).

  Subsequently, the installation guiding instruction unit 244 of the management server 200 sends the customer sending application 20 based on the application ID of the customer sending application 20 (game B) included in the customer sending information acquired by the customer sending information acquiring unit 243. The instruction information for guiding to the installable screen is transmitted to the user terminal 100. For example, the installation guiding instruction unit 244 transmits, to the user terminal 100, instruction information for activating the store 30, which is an application for displaying the store page of the store site where the customer destination application 20 (game B) can be installed (downloadable). To do (step SE19).

  When the user terminal 100 acquires the instruction information for activating the store 30 from the management server 200, the user terminal 100 activates the store 30, and stores the store page of the store site where the customer sending application 20 (game B) can be installed (downloadable). It is displayed on the display unit 120 (step SC11). Here, the user terminal 100 causes the display unit 120 to display the store page by overlapping the display screen of the customer sending source application 10 (game A) which has been displayed on the display unit 120 so far.

  After the customer destination application 20 (game B) is downloaded and installed in the user terminal 100 by the operation of the user X from the store page displayed in the store 30, the customer destination installed continuously by the operation of the user X The application 20 (game B) is activated.

  Next, with reference to FIG. 15, a process after the customer destination application 20 (game B) installed in the user terminal 100 is activated will be described. That is, from the process (the process of (8)) executed by the SDK 11B after the customer destination application 20 (game B) shown in FIG. 4 is installed, the management server 200 corresponds to the customer origin application 10 (game A). A detailed example up to the processing (processing of (11)) of transmitting the reward granting information to the application server 310 (game A) will be described. In addition, when the customer-sending destination application 20 (game B) is installed in the user terminal 100, at the first activation when the customer-sending source application 10 (game A) is installed described with reference to FIG. The same processing as the processing of and the initialization processing is performed.

  First, the initialization processing unit 101 of the SDK 11B incorporated in the customer sending destination application 20 (game B) processes the application ID (ApID) of the customer sending destination application 20 as a process to be executed only at the first activation. The app user ID (ApUID) of the user X registered in the destination application 20 and the campaign ID (CpID) when the campaign is set are acquired from the customer sending application 20 (game B) (step SB11) ).

  Next, the initialization processing unit 101 of the SDK 11B executes the initialization process of the SDK 11B. The initialization processing unit 101 determines whether or not the initialization process has been completed (step SB12), and when it is determined that the initialization process has been completed (step SB12: YES), the initialization process ends. If it is determined that the initialization process has not been completed (step SB12: NO), the process proceeds to the process of the unique identification information acquisition unit 102 of the SDK 11B. Here, since the reward user ID of the user terminal 100 has already been acquired, the process continues to the process of installation notification in step SB16.

  The installation notification unit 103 of the SDK 11B transmits, to the management server 200, installation notification information indicating that the customer sending destination application 20 (game B) has been installed in the user terminal 100 (REQ 14, step SB16). Here, the installation notification information includes a reward user ID (Reward UID) corresponding to the user terminal 100, an application ID (ApID) of the installed customer sending destination application 20 (game B), and the customer sending destination application 20 ( The application user ID (ApUID) of the user X registered in the game B) is included.

Next, the installation notification acquisition unit 241 of the management server 200 acquires the installation notification information transmitted from the user terminal 100 (SDK 11B) as in the process of step SE11. Then, the installation notification acquisition unit 241 transmits response information (notification result) indicating that the installation notification information has been acquired to the user terminal 100 (SDK 11B) (RES 14). Further, the installation information management unit 222 of the management server 200 receives a reward user ID (Reward UID) included in the installation notification information acquired by the installation notification acquisition unit 241 and an application ID (ApID) of the customer sending application 20 (game B). And the application user ID (ApUID) of the user X in the customer sending destination application 20 (game B) are stored in the installation information storage unit 236 as installation information (step SE21).
When acquiring the response information (notification result) from the management server 200, the user terminal 100 (SDK 11B) sets a flag indicating that it has been initialized, as in the process of step SA22, and ends the initialization process (step SB17).

  Next, as the installation notification acquiring unit 241 acquires installation notification information corresponding to the customer sending destination application 20, the reward processing unit 245 transmits the customer sending application 20 (game B) from the customer sending application 10 (game A). It is determined whether or not the customer-sending information for iii) is stored in the customer-sending information storage unit 237. Then, when the customer referral information is stored in the customer referral information storage unit 237 (i.e., recording of the customer referral information for the customer referral destination application 20 is managed by the customer referral information management unit 223). It is determined that the customer sending destination application 20 is a target application sent from the customer sending source application 10 by the mutual customer sending system 500 under the condition that the request is made), and the CP reward process or the normal reward process is executed. Here, in the processing of step SE18, the target application to which the customer sending destination application 20 is sent from the customer sending source application 10 by the mutual customer sending system 500 by the recording of the customer sending information stored in the customer sending information storage unit 237. It is determined that

  Subsequently, the reward processing unit 245 determines whether the timing at which the installation notification acquisition unit 241 acquires installation notification information corresponding to the customer destination application 20 (game B) is within the campaign period (step SE22). .

  For example, when the customer sending application 20 (game B) is a specific application for which a campaign is set with the customer sending application 10 (game A), the reward processing unit 245 selects the campaign information storage unit 234. It is determined whether or not the timing at which the installation notification information is acquired (the date and time counted by the clock unit 246 when the installation notification information is acquired) is within the campaign period of the campaign with reference to FIG.

  If it is determined in step SE22 that the timing at which the installation notification information has been acquired is within the campaign period (step SE22: YES), the reward processing unit 245 receives a reward from the SDK 11B of the customer destination application 20 of the user terminal 100. The CP reward process is executed based on the acquisition notification information being acquired.

  On the other hand, when it is determined in step SE22 that the timing at which the installation notification information has been acquired is not within the campaign period (step SE22: NO), the reward processing unit 245 executes the normal reward processing. Note that, even when the customer sending application 20 (game B) is a target application for which a campaign has not been set with the customer sending application 10 (game A), the installation notification information is acquired in this step SE22. It is determined that the timing is not within the campaign period (step SE22: NO), and the reward processing unit 245 executes the normal reward processing.

  First, the operation of the normal reward process will be described. When it is determined in step SE22 that the timing at which the installation notification information has been acquired is not within the campaign period (step SE22: NO), the installation notification information from the customer destination application 20 is the installation notification information of the install notification acquisition unit 241. And, based on the fact that the record of customer-sending information for the customer-sending destination application 20 is managed by the customer-sending information management unit 223, it is associated with the reward management ID stored in the customer-sending information. Reward establishment information with the point ID (RewardSpotID) set to “null” and the established state (RewardStatus) set to the flag “0” (not notified) is generated and stored in the reward establishment information storage unit 238 (step SE23).

  Next, the reward processing unit 245 acquires customer-sending information corresponding to the reward management ID associated with the generated reward establishment information with reference to the customer-sending information management unit 223. Then, with respect to the application server 310 (game A) corresponding to the customer sending source application 10 (game A) included in the customer sending information, the reward processing unit 245 uses the application user of the customer sending source application 10 (game A) Remuneration grant information (information indicating that ordinary reward is established) including an ID (ApUID) is transmitted (step SE24). The application server 310 (game A) serving as the transmission destination is indicated by a notification destination URL (Notice URL) corresponding to the application server 310 (game A) stored in the target application information storage unit 231.

  Next, the reward processing unit 245 updates the establishment status (RewardStatus) of the reward establishment information corresponding to the transmitted reward giving information as a flag “1” (notified).

  When the application server 310 (game A) receives the reward granting information (information indicating normal reward establishment) by the normal reward from the management server 200 (step SF21), the application user ID (application of the user X) included in the reward granting information The user is given a preset normal reward for the user ID) (step SF22).

  Next, the operation of the CP reward process will be described. When it is determined in step SE22 that the timing at which the installation notification information has been acquired is within the campaign period (step SE22: YES), the reward processing unit 245 notifies the user of the customer terminal application 20 of the user terminal 100 of payment award notification from the SDK 11B. Execute CP reward processing based on the acquisition of information.

  In the user terminal 100, the user X plays the customer sending destination application 20 (game B) to advance the game (step SD11). Then, the customer destination application 20 (game B) determines whether or not the reward giving condition set in advance corresponding to the campaign is satisfied (whether or not the result point of the CP reward has been reached) (step SD12) ). Note that the processing of step SD11 and step SD12 is not the processing executed by the SDK 11B, but the processing executed by the customer sending destination application 20 (game B).

  It is assumed that it is determined that the reward giving condition set in advance corresponding to the campaign is satisfied (the result point of the CP reward is reached) according to the progress of the game of the customer sending destination application 20 (game B) (step SD12) : YES).

  In this case, the customer destination application 20 (game B) notifies the SDK 11B of the result point ID (RewardSpotID) corresponding to the reached result point. The reward giving notification unit 107 of the SDK 11B that has received the notification reads the reward user ID from the inter-application shared area of the terminal storage unit 140 (step SB31), reads the reward user ID (RewardUID), and sends the customer destination application 20 (game B). Management server 200 with reward giving notification information (result point attainment notification) including the application ID (ApID), the campaign ID (CpID), and the result point ID (RewardSpotID) acquired from the customer destination application 20 (game B)). And transmit (REQ 15, step SB32). In addition, when there are a plurality of outcome points, the process returns to the process of steps SD11 and SD12, and every time the outcome point is reached, the customer destination application 20 (game B) is an outcome point ID (RewardSpot ID) corresponding to the reached outcome point. ) To SDK11B. Then, the reward assignment notifying unit 107 of the SDK 11B transmits the reward assignment notification information (result point arrival notification) to the management server 200.

  The reward processing unit 245 of the management server 200 acquires the reward assignment notification information (result point arrival notification) transmitted from the user terminal 100 (SDK 11B), and the record of the customer sending information for the customer destination application 20 is a customer sending. Based on being managed in the information management unit 223, the performance point ID (RewardSpotID) included in the acquired reward provision notification information is set in association with the reward management ID corresponding to the customer referral information, and the establishment status ( Reward status information with RewardStatus) set to a flag “0” (not notified) is generated and stored in the reward status information storage unit 238 (step SE25).

  Next, the reward processing unit 245 acquires customer-sending information corresponding to the reward management ID associated with the generated reward establishment information with reference to the customer-sending information management unit 223. Then, for the application server 310 (game A) corresponding to the customer sending source application 10 (game A) included in the customer sending information, the application user ID (ApUID) of the customer sending source application 10 (game A), the campaign Remuneration grant information (information indicating establishment of CP reward establishment) including the ID (CpID) and the outcome point ID (RewardSpotID) is transmitted (step SE26).

  Next, the reward processing unit 245 updates the establishment status (RewardStatus) of the reward establishment information corresponding to the transmitted reward giving information as a flag “1” (notified).

  In addition, when there are multiple result points, the reward processing unit 245 rewards the customer information recorded in the customer information management unit 223 every time the reward giving notification information (notice of reaching the result points) is acquired. Reward establishment information that generates a flag “0” (not notified) of the established state (RewardStatus) is generated in association with the management ID, and stored in the reward establishment information storage unit 238. Then, the reward processing unit 245 uses the application server 310 corresponding to the customer sending application 10 (game A) to calculate the reward granting information (information indicating the establishment of CP reward) based on the respective reward granting notification information (notice of achievement point arrival notification). Send to (Game A). Then, the establishment status (RewardStatus) of the reward establishment information corresponding to the transmitted reward giving information is updated as a flag "1" (notified).

  When the application server 310 (game A) receives the reward granting information (information indicating CP reward establishment) by CP reward from the management server 200 (step SF31), the application user ID (user X's application's app) included in the reward granting information. A reward of CP reward set in advance corresponding to the campaign is given to the user ID (step SF32).

[Summary of First Embodiment]
(1) As described above, in the mutual customer sending system 500 of the present embodiment, the management server 200 (an example of the management device) includes the application management unit 221, the installation notification acquisition unit 241, and the list notification unit 242. , And a reward processing unit 245.
The application management unit 221 has a campaign (an example of a first period) set for a plurality of specific applications among a plurality of target applications to be managed (applications corresponding to the present system) (an example of a first period) Manage an example event). The installation notification acquisition unit 241 indicates that the target application installed in the user terminal 100 (an example of the terminal device) specified by the reward user ID (an example of the unique identification information) among the plurality of target applications is installed. Obtain installation notification information from the target application. The list notification unit 242 receives installation notification information from the user terminal 100 based on a request from a target application (an example of the first application, the customer sending source application 10) installed in the user terminal 100 among a plurality of target applications. The application list of at least one target application not acquired is transmitted to the user terminal 100.
Here, the target application (an example of the second application, the customer sending destination application 20) selected by the user terminal 100 from one or more target applications included in the application list notified by the list notification unit 242 is the customer sending source application 10 It is assumed that a campaign is set up with (an example of the first application). In this case, the reward processing unit 245 determines that the customer destination application 20 (an example of the second application) is installed within the campaign period, and the reward giving condition set in advance corresponding to the campaign is satisfied. When the reward granting notification information indicating that the reward granting condition has been satisfied is acquired from the customer destination application 20 based on the received, the CP reward processing (first reward based on the acquired reward granting notification information) Execute an example of the granting process).
On the other hand, it is assumed that the customer sending destination application 20 selected by the user terminal 100 does not have a campaign set with the customer sending source application 10. In this case, when it is determined that the customer destination application 20 has been installed, the reward processing unit 245 executes a normal reward process (an example of a second reward giving process).

The list notification unit 242 of the management server 200 is a user terminal based on a request from a specific application (an example of the first application, the customer sending application 10) installed in the user terminal 100 among a plurality of specific applications. The application list of at least one target application for which the installation notification information has not been acquired from 100 may be transmitted to the user terminal 100.
Then, the reward processing unit 245 determines that the specific application (an example of the second application, the customer sending destination application 20) selected by the user terminal 100 from one or more specific applications included in the application list is installed within the campaign period. Based on the fact that the reward giving condition determined in advance and set in advance corresponding to the campaign is satisfied, reward giving notification information indicating that the reward giving condition is satisfied is obtained from the customer sending destination application 20 In this case, CP reward processing may be performed based on the acquired reward granting notification information.

  Thus, when the customership source application 10 is a specific application, the management server 200 sends, to the user terminal 100, an application list including at least a specific application for which a campaign has been set with the customership source application 10. Can be sent to. The management server 200 may transmit, to the user terminal 100, an application list of only specific applications for which a campaign has been set with the customer sending source application 10. Then, the management server 200 performs CP reward processing when the customer sending to the customer sending destination application 20 from the customer sending source application 10 in which the campaign is set is established. In this CP reward process, unlike the normal reward process, a reward is provided based on satisfaction of a preset reward giving condition corresponding to a campaign, so the customer destination application 20 is simply installed. Not only can it be rewarded, but also can be rewarded on condition of use of the customer destination application 20.

  That is, in the mutual customer delivery system 500 according to the present embodiment, a plurality of target applications to be managed may execute only the CP reward process, and a plurality of target applications to be managed may be the CP reward process and the normal It may execute both of the reward processing. In the case of the mutual customer sending system 500 that executes only the CP reward process, one or more specific applications are included in the application list that the list notification unit 242 transmits to the user terminal 100. On the other hand, in the case of the mutual customer sending system 500 that executes both CP reward processing and normal reward processing, one or more target applications are included in the application list that the list notification unit 242 transmits to the user terminal 100. is there. The target application includes a specific application.

  In the mutual customer delivery system 500, when the target application installed once is uninstalled and then installed again, the installation information when the target application is first installed in the management server 200 is managed. Can be identified as having been installed. Therefore, in the present system, when this target application is re-installed, it is possible not to be a target of normal reward processing or CP reward processing.

(2) In the mutual customer sending system 500 of the present embodiment, the user terminal 100 is a terminal device capable of communicating with the management server 200 described above. Here, the management server 200 described above has a campaign (an example of an event) having a campaign period (an example of a first period) set for a plurality of specific applications included in a plurality of target applications to be managed. Manage Further, the management server 200 is customer-sending information for one specific application to another specific application, which is notified in the campaign period from the user terminal 100 specified by the reward user ID (an example of the unique identification information). The customer management information associated with customer origin information indicating one specific application, customer destination information indicating the other specific application, and a reward user ID (an example of unique identification information) corresponding to the user terminal 100 is managed. Also, the management server 200 is installed based on the fact that the application corresponding to the customer destination information based on the managed customer destination information is installed, and the reward giving condition set in advance corresponding to the event is satisfied. When the predetermined reward granting notification information is received, the reward granting information corresponding to the campaign is transmitted to the application corresponding to the customer referral source information.
The user terminal 100 includes an installation notification unit 103, a list request unit 104, and a customer information notification unit 106.
The installation notification unit 103 is installation notification information indicating that the specific application installed in the user terminal 100 (an example of the own terminal device) has been installed, and the application ID (an example of identification information) of the specific application And transmits installation notification information including the reward user ID of the user terminal 100 to the management server 200. The list request unit 104 is list request notification information for requesting an application list of at least one specific application of a plurality of specific applications based on the first operation, and the specific application in operation (sender source application 10 List request notification information including customer sending source information indicating the application ID in (an example) and the reward user ID corresponding to the user terminal 100 to the management server 200. The customer-sending information notification unit 106 is selected by customer-sending source information indicating the application ID of the operating specific application (an example of the customer-sending source application 10) based on the second operation during the campaign period, Customer sending information including customer ID information indicating the application ID of the specific application (an example of the customer destination application 20) and the reward user ID corresponding to the user terminal 100 is transmitted to the management server 200.

  In addition, the user terminal 100 according to the present embodiment includes the reward provision notifying unit 107. For example, as described above, based on the fact that the reward giving condition set in advance corresponding to the campaign is satisfied, the reward giving notifying unit 107 indicates the application ID of the specific application that has satisfied the reward giving condition. Remuneration grant notification information including customer information and a reward user ID corresponding to the user terminal 100 is transmitted to the management server 200. Note that the user terminal 100 may be configured not to include the reward assignment notifying unit 107, in which case, the application server 300 satisfies the preset reward assignment condition corresponding to the campaign. The reward assignment notification information may be transmitted to the management server 200. The process in the case where the application server 300 transmits the reward assignment notification information to the management server 200 will be described in (3) of the modification described later.

As described above, in the mutual customer support system 500 of the present embodiment, the management server 200 that manages the campaigns set in the plurality of specific applications included in the target application corresponding to the mutual customer support system 500, and the management server 200. With the user terminal 100 capable of communication, another specific application (an example of the customer sending destination application 20) is installed from the one specific application (an example of the customer sending application 10) in the user terminal 100. A customer can be sent to a specific application (an example of the customer destination application 20). Further, in the mutual customer delivery system 500, user information registered in a plurality of applications installed in one user terminal 100 by using a reward user ID that can uniquely identify the user terminal 100 (an example of the application user ID) Even in the case of different), it is possible to easily perform mutual customer feed processing and reward processing between applications. Furthermore, in the mutual customer-sending system 500, when the customer-sending is established, a reward is usually given by a reward or a CP reward, which motivates the user who wants to obtain the reward to purchase a new application. This makes it possible to promote sales of applications.
Therefore, according to the present embodiment, the convenience of mutual customer feed between applications can be improved.

(3) The function of the above-mentioned installation notification unit 103, the function of the list request unit 104, the function of the customer sending information notification unit 106, and the function of the reward giving notification unit 107 are incorporated in each of a plurality of target applications. It is executed based on SDK11 (software). For example, the SDK 11A incorporated in the customer referral source application 10 executes the function of the installation notification unit 103, the function of the list request unit 104, and the function of the customer referral information notification unit 106, and incorporates it into the customer referral destination application 20. The acquired SDK 11B executes the function of the installation notification unit 103 and the function of the reward giving notification unit 107. The SDK 11A and the SDK 11B have the same functions, and execute the corresponding functions depending on whether they are incorporated in the customer sending source application 10 or the customer sending destination application 20.

  As a result, by incorporating the SDK 11 into the application, it is possible to make the target application compatible with the mutual customer delivery system 500 of the present embodiment. Therefore, for example, even in an existing application or an application to be developed, if the program of the application is updated or slightly changed so that the SDK 11 can be incorporated, the application can be made a target application corresponding to the mutual customer sending system 500. it can.

(4) In the reward processing unit 245 of the management server 200, the customer destination application 20 (an example of the second application) selected by the user terminal 100 from one or more target applications included in the application list is the customer source application 10 Even when a campaign (an example of an event) having a campaign period (an example of a first period) is set with (an example of the first application), the customer destination application 20 is out of the campaign period. When it is determined that the software has been installed, the normal reward process (an example of the second reward giving process) is executed.

  According to this, even if the customer-sending application 20 is set up with the customer-sending application 10, it can be considered as a normal reward if it is installed outside the campaign period of the campaign. . That is, when the customer-sending application 20 has a campaign set with the customer-sending application 10, the timing at which the customer-sending application 20 is installed is CP reward if it is within the campaign period, otherwise If it is a period, it can usually be considered as a reward.

(5) The timing at which the reward processing unit 245 of the management server 200 acquires the installation notification information corresponding to the customer destination application 20 (an example of the second application) in the installation notification acquiring unit 241 is within a campaign period (first period) If it is one of the examples), it is determined that the customer sending destination application 20 has been installed in the user terminal 100 (an example of the terminal device) within the campaign period.

  Thereby, the management server 200 determines whether the timing at which the customer terminal application 20 is installed at the user terminal 100 is within the campaign period, at the acquisition timing of the installation notification information of the customer destination application 20 transmitted from the user terminal 100. Can be determined.

  In addition, when the timing at which the reward processing unit 245 of the management server 200 acquires the customer-sending information for the customer-sending destination application 20 from the customer-sending source application 10 (an example of the first application) is within the campaign period, It may be determined that the application 20 is installed on the user terminal 100 within the campaign period. That is, if customer sending information is recorded within the campaign period, even if the acquisition timing of the installation notification information of the customer destination application 20 transmitted from the user terminal 100 is outside the campaign period, the user terminal 100 is received within the campaign period. Think of it as installed.

(6) The reward user ID (an example of unique identification information) is stored in the user terminal 100. The user terminal 100 acquires the reward user ID and obtains the acquired reward when the installed target application is the target application installed in the user terminal 100 (an example of the own terminal device) at first among the plurality of target applications. The unique identification information acquisition unit 102 stores the user ID in the terminal storage unit 140 (an example of a storage unit) so that the user ID can be referred to by any target application installed in the user terminal 100.

  Thereby, according to the mutual customer feed system 500, the user terminal 100 automatically acquires the reward user ID when the target application is installed for the first time, and the acquired reward user ID is common even to the target application to be installed later Therefore, the reward user ID can be obtained and the system can be used without requiring the user to perform a special operation.

(7) Specifically, the unique identification information acquisition unit 102 receives the reward user ID (an example of unique identification information) stored in the terminal storage unit 140 (storage unit) when the installed target application is installed in the user terminal 100. If it is determined that the reward user ID is not stored in the terminal storage unit 140, the reward user ID is acquired.
Thereby, the user terminal 100 can acquire the reward user ID when the target application is installed and started for the first time.

(8) The installation notification information includes a reward user ID (an example of unique identification information) associated with the user terminal 100 and an application ID (an example of identification information) of a target application that has transmitted the installation notification information. ing.
The installation notification unit 103 of the user terminal 100 (SDK 11) is installation notification information indicating that the installed target application is installed on the user terminal 100 (an example of the own terminal device), and is an application of the installed target application Installation notification information including the ID and the reward user ID is transmitted to the management server 200.
The installation information management unit 222 of the management server 200 manages the reward user ID included in the installation notification information acquired from the user terminal 100 (SDK 11) and the application ID of the target application in association with each other.

Thus, when the target application is installed on the user terminal 100, the management server 200 can manage the application ID of the installed target application and the reward user ID associated with the user terminal 100 in association with each other. . Thus, the management server 200 can identify the target application installed for each user terminal 100.
Even when the target application is installed without using the present system, the management server 200 manages the application ID of the installed target application and the reward user ID associated with the user terminal 100 in association with each other. Thus, the management server 200 can identify the target application installed in the user terminal 100.

(9) The installation notification information may further include an application user ID (an example of user information) of the target application that has transmitted the installation notification information. That is, the installation notification acquisition unit 241 functions as an application user information acquisition unit. That is, the management server 200 includes an application user information acquisition unit that acquires an application user ID of a target application in association with a reward user ID (an example of unique identification information). For example, the installation notification unit 103 of the user terminal 100 (SDK 11) sends, to the management server 200, installation notification information further including the application user ID of the installed target application of the user who installed the installed target application. Send. The management server 200 acquires the application user ID included in the installation notification information.
In addition, depending on the target application, the timing of registering user information may differ depending on the target application, not only when it is started for the first time, but also when, for example, the tutorial is completed. Therefore, the management server 200 may include the application user ID (in the information other than the installation notification information and acquire the application user ID from the user terminal 100 (SDK 11). You may make it acquire from the application server 300 corresponding to an object application.
The installation information management unit 222 of the management server 200 manages the reward user ID included in the installation notification information, the application ID of the target application (an example of identification information), and the application user ID of (in) the target application. Here, as described above, the application user ID managed by the installation information management unit 222 may be included in the installation notification information acquired by the management server 200, or may be included in information other than the installation notification information. It may be

  Thus, when the target application is installed on the user terminal 100, the management server 200 receives the application ID of the installed target application, the application user ID of the installed target application, and the reward associated with the user terminal 100. The user ID can be associated and managed. That is, the management server 200 can manage the application user ID of each target application installed in the user terminal 100 in association with the reward user ID.

(10) The application management unit 221 of the management server 200 associates information indicating a campaign (an example of an event) with information about the campaign, stores the information in the campaign information storage unit 234 or the campaign participation application information storage unit 235, and manages it.
The list notification unit 242 of the management server 200 refers to the above-mentioned information managed by the application management unit 221, and transmits information on a campaign corresponding to one or more specific applications included in the application list.

  Thereby, when the user terminal 100 displays the list LT of the target applications based on the application list acquired from the management server 200 on the display unit 120, the specific application for which the campaign is set is information on the campaign (the campaign A name, an explanation, a campaign period etc. can be associated and displayed.

(11) The application management unit 221 of the management server 200 manages, as information on a campaign (an example of an event), information including a link destination of a place of publication of information indicating a CP reward (an example of a reward).
The list notification unit 242 of the management server 200 refers to the above-described information managed by the application management unit 221, and indicates the above-described link destination corresponding to one or more specific applications included in the application list as information on a campaign. Send information

  Thus, when displaying a list LT of target applications based on the application list acquired from the management server 200 on the display unit 120, the user terminal 100 indicates the CP reward of the campaign to the specific application for which the campaign is set. The information which shows the link destination of the publication place of information can be matched and displayed. The link destination is the place where the information indicating the CP reward is posted, in order to allow flexibility in the posting method so that various actions can be taken according to the content and time of the campaign.

(12) Specifically, the application management unit 221 (an example of a first reward information management unit) of the management server 200 is configured to set a CP reward (first reward) set in advance corresponding to a campaign (an example of an event). The information which shows the link destination of the publication place of the information which shows an example) is memorize | stored in the campaign participating application information storage part 235, and is managed. In addition, the application management unit 221 (an example of a second reward information management unit) indicates a preset normal reward provided by each of the plurality of target applications and the normal reward process (an example of a second reward giving process). The normal reward information associated with the information is stored in the normal reward information storage unit 232 and managed.
Then, the list notification unit of the management server 200 normally receives information indicating a reward for a target application for which a campaign has not been set with the customer sending source application 10 (an example of the first application) among a plurality of target applications. An application list including information indicating a normal reward is transmitted to the user terminal 100 so as to be associated and displayed. On the other hand, the list notification unit is configured to display the information indicating the link destination described above in association with the target application for which the campaign is set with the customer sending source application 10 among the plurality of target applications. An application list including information indicating the link destination is transmitted to the user terminal 100.

  Thus, when displaying a list LT of target applications based on the application list acquired from the management server 200 on the display unit 120, the user terminal 100 displays information indicating a normal reward to the target applications for which a campaign is not set. In a specific application in which a campaign is set, information indicating a link destination of information posting location indicating a CP reward (an example of a reward) of the campaign can be displayed in association with the application.

(13) The customer sending information acquisition unit 243 of the management server 200 is customer sending information from the customer sending source application 10 (an example of the first application) to the customer sending destination application 20 (an example of the second application). Customer-sending information including an ID (an example of unique identification information), an application ID of the customer-sending source application 10 (an example of identification information), and an application ID of the customer-sending application 20 (an example of identification information) is acquired. When the customer-sending information acquisition unit 243 acquires the customer-sending information, the customer-sending information management unit 223 of the management server 200 determines the reward user ID included in the acquired customer-sending information, the application ID of the customer-sending source application 10, and thesending. The application ID of the customer application 20 is associated and stored in the customer-sending information storage unit 237 as a record of the customer-sending information and managed.
Then, when the reward processing unit 245 of the management server 200 acquires payment notification information from the customer sending application 20, the customer sending information management unit 223 manages recording of customer sending information for the customer sending application 20. Under the condition that there is, the normal reward process or the CP reward process (an example of the reward giving process) is executed.

  As a result, when the target application is installed regardless of the present system, the mutual customer sending system 500 can not normally record the customer sending information as a target for the reward and the CP reward.

(14) The installation guiding instruction unit 244 of the management server 200 receives the application ID (an example of identification information) of the customer sending application 20 (an example of the second application) included in the customer sending information acquired by the customer sending information acquiring unit 243. The instruction information for guiding the customer destination application 20 to the installable store page (screen) is transmitted to the user terminal 100 based on the above.

  As a result, when the target application to which customers are sent is selected from the customer sending source application 10 (an example of the first application), the user terminal 100 makes the user select a store page that can install the selected target application. It can be displayed automatically without any operation.

(15) Reward grant notification information includes a reward user ID (an example of unique identification information) associated with the user terminal 100 and an application ID (identification information) of the customer sending application 20 (an example of a second application) )It is included.
The reward assignment notifying unit 107 of the user terminal 100 (SDK 11) transmits, to the management server 200, reward assignment notification information including the above-described pieces of information.
The reward processing unit 245 of the management server 200 sends the customer sending application 10 (the first application associated with the reward user ID based on the reward giving notification information acquired from the customer destination application 20 installed in the user terminal 100). Remuneration grant information including an application user ID (an example of user information) of (an example) is transmitted to an application server 310 (an example of a server apparatus) corresponding to the customer sending source application 10.

  Thus, the management server 200 can specify the user terminal 100 and the customer sending destination application 20 that transmitted the acquired reward giving notification information, and the user (user who uses the customer sending source application 10 in this user terminal 100 (user Transmitting compensation granting information including the application user ID of the customer (user X) of the customer sending source application 10 to the application server 310 corresponding to the customer sending application 10 so that a reward is given to X) Can.

(16) The reward assignment notifying unit 107 of the user terminal 100 (SDK 11) transmits, to the management server 200, reward assignment notification information including the campaign ID (an example of identification information) of the campaign (an example of an event).

  As a result, the management server 200 refers to the campaign information storage unit 234 or the campaign participation application information storage unit 235, and identifies the campaign set in the customer destination application 20 to which the acquired reward giving notification information has been sent. , Information about the campaign (eg, a rewarding period) can be identified. In particular, when a plurality of campaigns are set in the customer sending destination application 20, it is effective that the campaign ID is included in the reward giving notification information. For example, a plurality of campaigns having different campaign periods can be set for one target application.

(17) It is assumed that a campaign period (an example of a first period) and a campaign (an example of an event) of another period not overlapping are set for a plurality of specific applications. At this time, the reward processing unit 245 of the management server 200 uses the CP reward corresponding to the campaign (an example of the first period) of the campaign period (an example of the first period) of the customer destination application 20 (an example of the second application) in the user terminal 100 When the process (an example of the reward giving process) is already performed, the CP reward process (an example of the reward giving process) corresponding to the above-mentioned campaign of another period is not performed.

  As a result, the mutual customer sending system 500 causes the CP reward processing for the same customer destination application 20 to again receive a CP reward for another campaign for a user who has been given a CP reward for one campaign. It can be made not to be granted. In other words, the customer destination application 20 for which the CP reward has been rewarded is not subject to another CP reward.

For example, a user who installs the customer destination application 20 during the campaign period of the campaign A is rewarded based on the achievement of the outcome points set in the campaign. When each of the plurality of provided outcome points is reached, a reward is given based on each arrival. However, even if campaign B different from campaign A is started in the subsequent period. Even if the achievement point set in the campaign B is reached, no reward is awarded.
Here, when the campaign period of the campaign B starts and reaches the outcome point set in the campaign B, the reward provision notification information is transmitted from the user terminal 100 to the management server 200. However, since the customer referral information corresponding to the campaign B is not transmitted from the user terminal 100 to the management server 200, the management server 200 does not manage the customer referral information corresponding to the campaign B (send customer information storage) There is no corresponding record in part 237). As a result, since the reward formation information corresponding to the campaign B is not managed in the reward formation information storage unit 238 as well, the management server 200 updates the reward formation information even if the reward giving notification information for the campaign B is acquired. It can not be done, and it can treat the said reward grant notice information as an invalid thing. Therefore, control to prevent dual reward giving of CP reward becomes possible.

(18) The reward processing unit 245 of the management server 200 performs CP reward processing (an example of a first reward giving process) and normal reward processing (a second reward processing) of the customer destination application 20 (an example of a second application) in the user terminal 100. If at least one of the reward granting processes in (1) has already been executed, the other reward granting process is not executed.

  For example, in the management server 200, the establishment status included in the reward establishment information of the customer destination application 20 for which normal reward processing or CP reward processing has been performed has already been updated to “1” (established). Therefore, even if the management server 200 acquires the reward granting notification information from the customer sending destination application 20 again, there is no reward establishment information that can update the establishment status to “1” (established), and the compensation grant notification information is It can be treated as invalid.

  As a result, the mutual customer support system 500 can prevent double reward reward and normal CP reward compensation from being applied to the same customer referral destination application 20. That is, the customer destination application 20 to which the reward awarding by the normal reward is performed is not the target of the CP reward. In addition, the customer destination application 20 for which the reward is provided by the CP reward is not normally targeted for the reward.

(19) In the above embodiment, for a campaign (an example of an event), a reward provision period (second example) which starts from the beginning or in the middle of a campaign period (an example of a first period) and ends after the end of the campaign period. An example of the period of) is set. The reward assignment notifying unit 107 of the user terminal 100 (SDK 11) transmits reward assignment notification information to the management server 200. Then, when the reward processing unit 245 of the management server 200 acquires the reward provision notification information from the customer destination application 20 (an example of the second application) installed in the user terminal 100 within the reward provision period, the reward processing unit 245 acquires the reward provision notification information. A CP reward process (an example of a reward giving process) based on the reward giving notification information is executed.

  Thereby, even if the customer destination application 20 is installed on the user terminal 100 immediately before the end of the campaign period, the mutual customer support system 500 reaches the achievement point to which the CP reward is awarded. The user can be given a time period for which the user will try. Further, the management server 200 can be made to be granted a CP reward (an example of a reward) when the reward granting notification information is obtained from the user terminal 100 within the reward granting period.

(20) In addition, the reward provision notification unit 107 of the user terminal 100 (SDK 11) receives the reward provision notification information when the timing at which the reward provision condition is satisfied is the reward provision period (an example of the second period). It may be sent to the management server 200. Then, the reward processing unit 245 of the management server 200 acquires the reward provision notification information from the customer destination application 20 (an example of the second application) when the timing when the reward provision condition is satisfied is within the reward provision period. At the same time, a CP reward process (an example of a reward giving process) based on the acquired reward giving notification information may be executed.

  In this case, the user terminal 100 transmits the reward provision notification information to the management server 200 only when the timing at which the reward provision condition is satisfied is the reward provision period. Therefore, the management server 200 may obtain reward grant notification information from the user terminal 100 to be granted a CP reward (an example of reward) when the reward grant condition is satisfied within the reward grant period. it can.

(21) A plurality of reward giving conditions set in advance corresponding to a campaign (an example of an event) may be provided. The reward granting notification unit 107 of the user terminal 100 (SDK 11) transmits reward granting notification information to the management server 200 based on satisfaction of each of the plurality of reward grant conditions. The reward processing unit 245 of the management server 200 notifies payment of reward from the customer destination application 20 (an example of the second application) installed in the user terminal 100 based on satisfaction of any of the plurality of reward assignment conditions. When the information is acquired, a CP reward process (an example of a reward giving process) based on the acquired reward giving notice information is executed.

  In this way, the mutual customer support system 500 can execute the corresponding CP reward processing in response to each of the plurality of reward provision conditions of the campaign set in the customer destination application 20 being satisfied. That is, the user continues to use the customer service destination application 20 in order to obtain a plurality of rewards set in the campaign period (an example of the reward giving period) as much as possible. Therefore, the use of the customer service application 20 can be enhanced.

(22) The reward processing unit 245 of the management server 200 acquires the reward provision notification information from the customer sending destination application 20 (an example of the second application) based on that one of the plurality of reward provision conditions is satisfied. When the acquired timing is within the reward giving period (an example of the second period), CP reward processing (one example of the reward giving processing) based on the reward giving notification information is executed.

  In other words, even when a plurality of reward giving conditions are set for the campaign, the management server 200 pays the timing at which each of the plurality of reward giving conditions is satisfied (the timing when the management server 200 acquires the reward giving notification information). A CP reward (an example of a reward) can be awarded only within the grant period.

(23) Each of the plurality of reward giving conditions is, for example, a timing at which each of the plurality of outcome points set in advance in the processing by the customer destination application 20 (an example of the second application) is reached. The reward granting notification unit 107 of the user terminal 100 (SDK 11) is an outcome point ID (result point information indicating an achieved outcome point among the plurality of outcome points, based on satisfaction of each of the plurality of reward assignment conditions). Each of the reward granting notification information including the above (1) is transmitted to the management server 200. Then, the reward processing unit 245 of the management server 200 outputs an outcome point ID indicating an achieved outcome point out of the plurality of outcome points from the customer destination application 20 based on satisfaction of each of the plurality of reward giving conditions. An application server corresponding to the customer origin application 10 (an example of the first application) which acquires reward granting notification information including (result point information) and includes the acquired result point ID (result point information) Transmit to 310 (an example of a server apparatus).

In other words, the management server 200 sends, to the customer sending source application 10, a result point ID indicating the result points that have reached each of the plurality of result points of the customer sending destination application 20 in the user terminal 100. It transmits to the corresponding application server 310.
Thereby, the mutual customer support system 500 receives CP reward corresponding to each of the reached result points in response to each of the plurality of outcome points of the campaign set in the customer destination application 20 being reached. An example can be given.

(24) The reward assignment notifying unit 107 of the user terminal 100 (SDK 11) includes arrival information indicating that any one of the plurality of outcome points has been reached based on satisfaction of each of the plurality of reward assignment conditions. The reward assignment notification information may be transmitted to the management server 200. Then, the reward processing unit 245 of the management server 200 reaches any of the plurality of result points from the customer sending destination application 20 (an example of the second application) based on that each of the plurality of reward giving conditions is satisfied. Correspond to the customer sending source application 10 (an example of the first application) with reward granting information according to the number of times of obtaining the reward granting notification information each time the reward granting notification information including arrival information indicating that it has been issued is obtained. May be transmitted to the application server 310 (an example of a server apparatus).

  That is, even if the management server 200 transmits the reward point information to the application server 310 corresponding to the customer sending source application 10 when any one of the plurality of outcome points is reached, the reward point notification is given without including the outcome point ID. Information indicating the number of times of information acquisition (that is, information indicating the number of times the result point has been reached and the number of the result point) may be included. In this case, the application server 310 and the management server 200 only need to make arrangements in advance to exchange reward giving information including information indicating the number of times described above. Therefore, even if the mutual customer support system 500 includes information indicating the number of acquisitions of the reward assignment notification information in place of the outcome point ID in the reward assignment information, the CP reward corresponding to each of the reached outcome points (an example of a reward) Can be given.

(25) The reward processing unit 245 of the management server 200 selects one of the plurality of outcome points from the customer sending destination application 20 (an example of the second application) based on that each of the plurality of reward giving conditions is satisfied. An application server 310 (server apparatus) corresponding to the customer sending application 10 (an example of the first application), acquiring reward granting notification information including arrival information indicating arrival, and also receiving compensation grant information including the acquired arrival information Example) may be sent.

  That is, the management server 200 transmits the reward giving information transmitted to the application server 310 corresponding to the customer sending source application 10 when any of the plurality of result points is reached without including the result point ID. Arrival information indicating that the outcome point has been reached (for example, flag information simply indicating that the outcome point has been reached) may be included. In this case, the application server 310 and the management server 200 only need to arrange in advance to exchange reward granting information including arrival information. Then, the application server 310 may count the number of acquisitions of arrival information and may provide a reward according to the counting result. Therefore, even if the mutual customer support system 500 simply includes the arrival information in the reward giving information instead of the result point ID, the CP reward (an example of a reward) corresponding to each of the reached result points is given. be able to.

  As described above, it is possible to provide a plurality of reward conditions for CP reward. Here, the mutual customer support system 500 does not need to know the setting contents of the respective reward giving conditions, the total number of the reward giving conditions, and the like, and each time the reward giving conditions are satisfied in the customer destination application 20 Each time it reaches, the result point ID, information indicating the number of times of obtaining reward notification information, arrival information and the like are only transmitted to the application server 310.

  In the present embodiment, the management server 200 manages information on a target application corresponding to the mutual customer sending system 500, so that it is possible to prevent an application that does not correspond to the present system from being a search target. Further, as a method of specifying an application installed in the user terminal 100, there is a method of using a URL scheme. In that case, it is necessary to configure so that the URL scheme can be acquired from the management server 200. On the other hand, in the present embodiment, the management server 200 manages the installation information of the target application installed in the user terminal 100. Therefore, in the present embodiment, it is possible to easily perform processing when generating an application list to be a candidate to be selected as the customer sending destination application 20.

  In addition, the process of downloading and installing the customer destination application 20 from the application store 400 (an example of a store site) and the process of activating the customer destination application 20 after the installation is completed are left to the operation of the user. It is unclear what kind of operation will be performed during that time. For example, a user who is directed to the app store 400 who purchases the customer destination app 20 may subsequently download another application. Even in such a case, since the mutual customer sending system 500 manages the customer sending information from the customer sending source application 10 to the customer sending destination application 20, the reward processing is correctly performed based on the fact of the customer sending. be able to.

Second Embodiment
Next, a second embodiment of the present invention will be described. The configuration of the mutual customer delivery system 500 of the present embodiment is the same as that of the first embodiment, and therefore, characteristic processing in the present embodiment will be described. In the first embodiment, referring to FIG. 14, the application list excluding the target application installed in the process of step SE15 or the application list of a specific application for which a campaign is set between the customer application 10 and the application list. Although the filtering process has been described, the present invention is not limited to this. In the present embodiment, a process (filtering process) of selecting a target application to be included in the application list based on a predetermined condition based on the condition (filter information) set in the inter-application filter storage unit 233 will be described.

  The inter-application filter storage unit 233 stores filter information (inter-application filter information) between applications for limiting target applications that can be mutually sent. The inter-application filter information for limiting the target applications which can mutually send mutual customers is, for example, set as posting prohibition information which prohibits the listing on the list LT of target applications which can be selected as the customer destination application 20.

  Note that this inter-application filter information is normally valid for rewards, and even if a campaign is set between a target application for which a campaign has not been set with the customer application 10 and a customer application 10. Information to filter for specific applications that are not in campaign period.

  FIG. 16 is a diagram showing an example of inter-application filter information stored in the inter-application filter storage unit 233. As shown in FIG. The inter-application filter information is associated with a filter ID (Filter ID), an application ID to be blocked (ApIDfrom), and an application ID to be blocked (ApIDto). The filter ID (Filter ID) is a management ID issued in the order in which each piece of filter information is set so as to be identifiable for each inter-application filter information.

  The application ID (ApIDfrom) to be blocked is set to the application ID of the setting side application that sets the prohibition of the listing on the target application list LT. On the other hand, in the blocked application ID (ApIDto), the application ID of the application to be set of the side for which posting of the target application of the setting side application on the list LT is prohibited is set. That is, the inter-application filter storage unit 233 stores inter-application filter information in which the blocked application ID (application ID of setting side application) and the blocked application ID (application ID of set side application) are combined.

The list notification unit 242 refers to the inter-application filter information stored in the inter-application filter storage unit 233, and sends the customer application from the target application set in the application ID (application ID of the setting side application) to be blocked. In this case, the target application set as the blocked application ID (application ID of the application to be set) is excluded from the application list that can be selected as the customer destination application 20.
For example, when it is desired to prohibit customer sending from the customer sending application 10 (game A) to the customer sending application 20 (game B), the application ID of the customer sending application 10 (game A) is set as the application ID to be blocked. The application ID of the customer sending application 20 (game B) may be set to the blocked application ID.

  Note that the blocking application ID (application ID of the setting application) in the inter-application filter information shown in FIG. It is also good. That is, the list notification unit 242 refers to the inter-application filter information stored in the inter-application filter storage unit 233, and starts from the target application set in the blocked application ID (application ID of the application to be set) In the case of customer feed, the target application set in the application ID to be blocked (application ID of setting side application) may be excluded from the application list selectable as the customer feed destination application 20.

  Also, when it is desired to participate only in CP reward without participating in normal reward depending on the target application, set the application ID of the target application to the application ID (ApIDto) to be blocked, and set the application ID to be blocked (ApIDfrom). Set "null". As a result, outside the campaign period, the target application is not listed in the list of target applications LT for customer transfers from any target application. For example, in a case where an existing application is implementing mutual rewards with other applications by participating in the mutual customer referral system 500, the CP reward only needs to participate in the present system. It can correspond. In addition, the information regarding the target application for which only the CP reward only wants to participate without participating in the reward is stored in the target application information storage unit 231 storing the target application information on the target application in association with the application ID (ApID) of the target application. You may make it

Summary of Second Embodiment
As described above, the application management unit 221 of the management server 200 sets the setting application on the side that sets the prohibition of the listing of the target application LT based on the application list, and the list LT of the target applications of the setting application. The inter-application filter storage unit 233 stores and manages inter-application filter information (an example of the first non-publication information) in combination with a set-side application on the side of which publication is prohibited.
Then, the list notification unit 242 of the management server 200 refers to the inter-application filter information managed by the application management unit 221, and sets the customer sending source application 10 (an example of the first application) as the application to be set If there is inter-application filter information present, and the setting-side application indicated by the inter-application filter information is not set up with the customer sending source application 10 with a campaign (an example of an event), the setting side An application list of target applications excluding the application is transmitted to the user terminal 100.

  In this way, in the mutual customer sending system 500, it is possible to set in the management server 200 the relationship of target applications that you do not want to be allowed to mutually feed in normal reward. For example, if there is a rating (age restriction) set in the target application, the customer sending source application 10 in which the rating is not set is sent to the customer sending destination application 20 in which the rating is set. You can try not to

  Further, the list notification unit 242 of the management server 200 refers to the inter-application filter information managed by the application management unit 221, and there is inter-application filter information in which the customer sending source application 10 is set as the setting application. In the case where the set side application indicated by the first posting prohibition information is not set up with the customer sending source application 10, the application list of the target application excluding the set side application Are transmitted to the user terminal 100.

  As a result, target applications set for each of the setting application and the setting application of the inter-application filter information can prohibit (block) posting in the application list (bi-directionally).

In addition, the application management unit 221 of the management server 200 determines the inter-application filter information (second posting prohibition information) in which only the set-side application on the side that is prohibited from being listed in the target application list LT based on the application list is registered. Is stored in the inter-application filter storage unit 233 and managed.
Then, the list notification unit 242 of the management server 200 refers to the inter-application filter information managed by the application management unit 221, and the set-side application indicated by the inter-application filter information is the customer sending source application 10 (first application When a campaign (an example of an event) is not set between the above-mentioned examples (1) and (2), an application list of target applications excluding the set-side application is transmitted to the user terminal 100.
The information corresponding to the inter-application filter information may be stored in the target application information storage unit 231 and managed. That is, for the target application for which information corresponding to the inter-application filter information is stored in the target application information storage unit 231, only the CP reward is made to participate.

  In this way, in the case of a target application that wants to participate in the inter-customer system 500 only for the campaign, outside the campaign period, it is made not to be listed in the target application list LT even for customers from any target application. Can.

<Modification of First and Second Embodiments>

  Although the embodiments of the present invention have been described in detail with reference to the drawings, the specific configuration is not limited to the above-described embodiments, and includes design and the like within the scope of the present invention. For example, the functions described in the first embodiment and the second embodiment described above can be arbitrarily combined.

(1) In the above embodiment, the communication unit 210 (transmission / reception unit) of the management server 200 includes the installation notification information (an example of the first information), the application list (an example of the second information, for example, at least one of a plurality of target applications). Information indicating one target application), list request notification information, customer sending information (for example, customer sending source information or customer sending destination information), instruction information (an example of information for causing the user terminal 100 to display an installable screen) Or the example of communicating reward grant notification information directly with the user terminal 100 has been described. Similarly, the terminal communication unit 130 (transmission / reception unit) of the user terminal 100 directly communicates the installation notification information, the application list, the list request notification information, the customer referral information, the instruction information, or the reward provision notification information with the management server 200. An example has been described.

  Here, the communication unit 210 (transmission / reception unit) of the management server 200 corresponds to the customer sending application 10 (first application) or the customer sending application 20 (second application), and an application server 300 (server apparatus) corresponding thereto. After establishing the communication session via the communication terminal 100, the communication with the user terminal 100 may be directly performed. Similarly, the terminal communication unit 130 (transmission / reception unit) of the user terminal 100 corresponds to the customer sending application 10 (target application installed) or the customer sending application 20 (selected target application), and the application server 300 corresponding thereto. After establishing a communication session via the (server apparatus), the communication may be directly communicated with the management server 200.

When the user terminal 100 directly communicates with the management server 200, a communication session may be established as needed. That is, both the case of directly communicating with the management server 200 before establishing the communication session and the case of communicating directly with the management server 200 after establishing the communication session may be included.
For example, the installation notification information may directly communicate with the management server 200 before establishing a communication session, and may communicate directly with the management server 200 after establishing a communication session for other information. Good. By doing this, an application that does not have the application server 320 corresponding to the customer destination application 20 as the customer destination application 20 that is normally targeted for reward, that is, an application that operates in a standalone mode in the user terminal 100 It becomes possible to treat as. That is, when transmitting installation notification information indicating that an application operating in a stand-alone mode has been installed, the user terminal 100 does not perform processing for establishing a communication session via the application server 300 (server apparatus). It can directly communicate with the management server 200.

  FIG. 17 is a flow chart for explaining the operation of communication session establishment processing. This communication session establishment process (communication session establishment process) is the case where the customer sending application 10 or the customer receiving application 20 is activated on the user terminal 100, and the SDKs 11A and 11B communicate with the management server 200 for the first time. For example, it is performed in the initialization processing described with reference to FIGS. 14 and 15. FIG. 17 shows a communication session establishment process performed in the initialization process shown in FIG. Note that this communication session establishment process can be performed similarly in the initialization process shown in FIG. In FIG. 17, parts corresponding to the respective processes in FIG. 14 are given the same reference numerals, and descriptions thereof will be omitted. The user terminal 100 and the application server 310 are assumed to have already established a communication session.

When the reward user ID has been acquired in the processing of steps SA12, SA13, SA14, and SA15, and the notification of installation notification information has been notified in the processing of steps SA16 and SA17, the initialization processing unit 101 of the SDK 11A acquires the one-time token. The requested one-time token acquisition request information is transmitted to the application server 310 (step SA21). When acquiring the one-time token acquisition request information from the user terminal 100 (SDK 11A), the application server 310 transmits one-time token generation request information based on the acquired one-time token acquisition request information to the management server 200 (step SF11). ). When the management server 200 acquires 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 SE12). When acquiring the one-time token from the management server 200, the application server 310 transmits the acquired one-time token to the user terminal 100 (SDK 11A) (step SF12). When acquiring the one-time token from the application server 310, the initialization processing unit 101 of the SDK 11A transmits session establishment request information including the acquired one-time token to the management server 200 (step SA22). When the management server 200 acquires session establishment request information from the user terminal 100 (SDK 11A), when the one-time token included in the acquired session establishment request information is correct information (sent to the user terminal 100 (SDK 11A) If it matches the one-time token), the communication session is established, and the communication by the mutual customer sending system 500 is permitted (step SE13). Thereafter, the process described with reference to FIG. 14 is performed. When 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 determines that a communication error occurs, and the communication by the mutual customer delivery system 500 is not permitted. Further, when the management server 200 can not acquire the session establishment request information from the user terminal 100 (SDK 11A), naturally, the communication by the mutual customer delivery system 500 is not permitted.
Thus, after establishing a communication session, by starting communication by the mutual customer referral system 500, security in the network system 1 including the mutual customer referral system 500 can be improved.

  In addition, installation notification information (an example of the first information), an application list (an example of the second information, for example, information indicating at least one target application among a plurality of target applications), list request notification information, customer referral information (for example, , Customer origin information or customer destination information), instruction information (an example of information for displaying an installable screen on the user terminal 100), or a part of the reward provision notification information directly from the user terminal 100. Communicate with the user terminal 100 via the application server 300 (server apparatus) corresponding to the customer sending source application 10 (first application) or the customer sending destination application 20 (second application) without communicating with the management server 200 It is also good. That is, the communication unit 210 (transmission / reception unit) of the management server 200 sends the installation notification information, the application list, the list request notification information, the customer sending information, the instruction information, or the reward giving notification information to the customer sending source application 10 (first application). Alternatively, communication with the user terminal 100 or directly with the user terminal 100 may be performed via the application server 300 (server device) corresponding to the customer sending destination application 20 (second application).

Furthermore, the communication unit 210 (transmission / reception unit) of the management server 200 transmits the installation notification information, the application list, the list request notification information, the customer sending information, the instruction information, or the reward giving notification information to the customer sending source application 10 (first application). Or you may communicate with the user terminal 100 via the application server 300 (server apparatus) corresponding to the customer sending destination application 20 (2nd application). Similarly, the terminal communication unit 130 (transmission / reception unit) of the user terminal 100 corresponds to the application server 300 (server apparatus) corresponding to the customer sending source application 10 (installed target application) or the customer sending destination application 20 (selected target application) May communicate with the management server 200 via
Thus, in the mutual customer feed system 500, even when the user terminal 100 and the management server 200 communicate via the application server 300, the same customer feed processing and reward as in the first and second embodiments. Processing can be performed and similar effects can be obtained.

(2) In the above embodiment, an example in which the management server 200 is transmitted from the user terminal 100 (SDK 11) by including the application user ID (ApUID) in the installation notification information or the like has been described, but the present invention is not limited thereto. For example, the application server 300 may transmit the application user ID to the management server 200 in association with the reward user ID in the communication session establishment process. Specifically, at step SA21, when transmitting the one-time token acquisition request information to the application server 300, the initialization processing unit 101 of the SDK 11A notifies the application server 300 of the reward user ID. Furthermore, the application server 300 transmits the reward user ID, the application ID, and the application user ID to the management server 200. The installation information management unit 222 of the management server 200 sets, as an application user ID (ApUID) corresponding to installation information corresponding to the acquired reward user ID and application ID among the installation information stored in the installation information storage unit 236, The application user ID acquired from the application server 300 is stored. As described above, by transmitting the application user ID not from the user terminal 100 (SDK 11) but from the application server 300, it becomes unnecessary to manage the application user ID in the user terminal 100 (SDK 11).

  As described above, when the application server 300 transmits the application user ID to the management server 200 in association with the reward user ID in the communication session establishment process, the communication is performed only after the user information is registered in the installed target application. Session establishment processing can not be performed. However, the transmission of installation notification information indicating the installation of the target application installed in the user terminal 100 to the management server 200 does not have to be directly related to the user information being registered. Therefore, the user terminal 100 transmits installation notification information to the management server 200 regardless of whether user information is registered or not in the installed target application. Therefore, when the user terminal 100 transmits the installation notification information, it is transmitted before the communication session is established.

(3) In the above embodiment, an example in which the reward processing unit 245 executes the CP reward processing based on the fact that the reward granting notification information is acquired from the SDK 11B of the customer destination application 20 of the user terminal 100 has been described It is not limited to For example, the CP reward process may be executed based on the fact that the reward giving notification information has been acquired from the application server 320 corresponding to the customer sending destination application 20. In this case, the application ID of the customer sending destination application 20, the application user ID, the campaign ID, and the result point ID (RewardSpot ID) may be included in the reward assignment notification information (result point arrival notification).
For example, the reward processing unit 245 of the management server 200 acquires the reward assignment notification information (result point arrival notification) transmitted from the application server 320. Next, the reward processing unit 245 identifies the installation information corresponding to the application ID and the application user ID of the customer sending destination application 20 from the installation information stored in the installation information storage unit 236, and corresponds to the specified installation information. Reverse reward user ID. Then, the reward processing unit 245 corresponds to the customer referral information based on the fact that the record of the customer referral information for the customer user application 20 and the reward user ID subjected to the reverse lookup is managed in the customer referral information management unit 223. It sets outcome point ID (RewardSpotID) included in the acquired reward giving notification information in association with reward management ID, generates reward establishment information that sets the establishment status (RewardStatus) to flag “0” (not notified), and rewards It is stored in the establishment information storage unit 238. The subsequent processing is the same as in the above embodiment. As described above, transmitting the reward assignment notification information (result point arrival notification) from the application server 320 can reduce the processing load on the user terminal 100 (SDK 11B).

(4) In the above embodiment, when the target application is installed for the first time, the reward user ID can uniquely identify the installed user terminal 100 (unique identification in the mutual customer sending system 500) Although the example produced | generated as information) was demonstrated, it is not restricted to this. For example, a terminal identification number or a telephone number (for example, in the case of a smartphone) uniquely set in the user terminal 100 may be used as the reward user ID. However, without using personal information such as a terminal identification number or a telephone number, it is possible to improve security by generating and using a reward user ID as in this embodiment. Further, by adopting unique identification information unique to the mutual customer sending system 500 without using a terminal identification number, a telephone number, etc. as the reward user ID, the user terminal 100 (terminal device) owned by the user is replaced and replaced. Even when changing by etc., using mutual sending customer system 500 by maintaining the state from user terminal 100 before changing by moving to user terminal 100 after changing reward user ID through a predetermined procedure. Is possible.

  Further, the processing of displaying the application list page (list of target applications LT) in step SA25 and step SA26 of FIG. 14 and the processing of transmitting customer information when the target application to be downloaded is selected from the application list are Instead of the process executed by the SDK 11, another application (for example, a browser) installed in the user terminal 100 unrelated to the process of the SDK 11 may be activated and executed. For example, by generating data of an application list page which is redirected from the management server 200 to the browser in the user terminal 100 and transmitting it to the user terminal 100, the browser is started in the user terminal 100, and the application list page It may be displayed. In addition, by transmitting the data of the application list page including the application ID (ApID) of the customer sending source application 10 (game A) included in the list request notification information, the customer destination application selected on the application list page Management server from the above-mentioned browser of customer sending information including application ID (ApID) of 20 (game B), application ID (ApID) of customer sending source application 10 (game A), and reward user ID (RewardUID) It may be sent to 200.

Also, in the CP reward process, as in the normal reward process, the CP customer process may be executed based on the customer destination application 20 being installed. In this case, the reward giving condition in the customer sending destination application 20 may be that the customer sending destination application 20 is installed in the user terminal 100.
In addition, if it is assumed that installation of the customer destination application 20 is the first outcome point for all the specific applications that carry out the campaign, the customer destination application 20 of the reward giving notification information corresponding to the achievement of the outcome point. You do not need to send from. In this case, the management server 200 performs a reward giving process similar to that of the normal reward, and transmits reward giving information including the campaign ID to the application server 310, whereby the CP corresponding to the normal reward from the application server 310. Rewards will be rewarded. Specifically, without performing the determination process of step SE22 in the flowchart of FIG. 15, the process of steps SE23 to 24 may be performed for either the CP reward or the normal reward.

(5) In the above embodiment, the game has been described as an example of the target application corresponding to the mutual customer feed system 500. However, the target application is not limited to the game, and any application other than the game may be used. .

  In addition, the storage unit 230 of the management server 200 may be included in a server device different from the management server 200. Then, the management unit 220 of the management server 200 or the control unit 240 communicates with the storage unit 230 provided in a server apparatus different from the management server 200 via the network NW, whereby each unit included in the storage unit 230 stores You may manage each information you

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

(6) A program for realizing the functions of the management unit 220, the control unit 240, or the SDK 11 described above is recorded in a computer readable recording medium, and the computer system reads the program recorded in the recording medium. The above-described processing may be performed by execution. Here, "to read and execute the program recorded on the recording medium into the computer system" includes installing the program on the computer system. The “computer system” mentioned here includes an OS and hardware such as peripheral devices. Also, the “computer system” may include a plurality of computer devices connected via a network including communication lines such as the Internet, WAN, LAN, and dedicated lines. The term "computer-readable recording medium" refers to a storage medium such as a flexible disk, a magneto-optical disk, a ROM, a portable medium such as a ROM or a CD-ROM, or a hard disk built 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 internally or externally accessible from the distribution server for distributing 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 executable in the terminal device. That is, the format stored in the distribution server does not matter 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, and the configuration may be such that the terminal device integrates after being downloaded at different timings, or the distribution server that distributes each of the divided programs may be different. Furthermore, "computer-readable recording medium" holds a program for a certain period of time, such as a volatile memory (RAM) in a computer system serving as a server or a client when the program is transmitted via a network. We shall include things. Further, the program may be for realizing a part of the functions described above. Furthermore, it may be a so-called difference file (difference program) that can realize the above-described functions in combination with a program already recorded in the computer system.

  In addition, some or all of the functions described above may be realized as an integrated circuit such as LSI (Large Scale Integration). Each function mentioned above may be processor-ized separately, and part or all may be integrated and processor-ized. Further, the method of circuit integration is not limited to LSI's, and implementation using dedicated circuitry or general purpose processors is also possible. In the case where an integrated circuit technology comes out to replace LSI's as a result of the advancement of semiconductor technology, integrated circuits based on such technology may also be used.

<About the first and second embodiments>
The first and second embodiments described above can be described as follows, but are not limited to the following description.

(1) In the mutual customer feed system 500 of the present embodiment, the management server 200 (an example of a management device) includes an application management unit 221, an installation notification acquisition unit 241 (an example of a first information acquisition unit), and a list notification unit 242 (an example of a second information notification unit) and a reward processing unit 245.
The application management unit 221 manages information on a plurality of target applications to be managed. Here, the management target refers to, for example, a target managed as a target application corresponding to the mutual customer delivery system 500.
When the target application among the plurality of target applications is executed by the user terminal 100 (an example of the terminal device), the installation notification acquisition unit 241 (an example of the first information acquisition unit) determines that the target application is the user terminal The installation notification information (an example of the first information) transmitted from the user terminal 100 in response to the execution by the user 100 is acquired.
The list notification unit 242 (an example of a second information notification unit) receives a request based on a target application (first application, customer sending source application 10) executed by the user terminal 100 among a plurality of target applications. An application list (an example of second information) including information indicating at least one target application for which installation notification information has not been acquired from the terminal 100 is transmitted to the user terminal 100.
Among the target applications indicated by the application list transmitted from the list notification unit 242 in response to the list notification unit 242 transmitting the application list, the reward processing unit 245 selects one of the target applications (an example of the second application, customer sending A reward granting process is performed based on that the destination application 20) has been executed by the user terminal 100 or is in an executable state.

Here, that the target application is executed by the user terminal 100 means, for example, that the target application is installed in the user terminal 100 and started up. Further, that the target application has become executable by the user terminal 100 means, for example, that the target application has been installed in the user terminal 100.
Note that a part of the program for executing the target application may be installed in the user terminal 100 in the user terminal 100, and the remaining part of the program may be included in an apparatus other than the user terminal 100. For example, the program for executing the target application installed in the user terminal 100 may be only the minimum necessary program for starting the execution of the target application. The remaining programs may be included in a server device (for example, the application server 300) capable of communicating with the user terminal 100 or another terminal device (for example, the other user terminal 100).
In addition, the configuration may be such that an apparatus other than the user terminal 100 has all the programs of the target application executed by the user terminal 100. That is, the program for executing the target application is not installed in the user terminal 100, and a server device (for example, the application server 300) or another terminal device (for example, the other user terminal 100) that can communicate with the user terminal 100 It may have a configuration. That is, the target application being executed by the user terminal 100 also includes the case where the target application is executed in a server apparatus connected to the user terminal 100 via the communication network according to an instruction from the user terminal 100. That is, the target application executed by the user terminal 100 may be a so-called cloud type or web type application. In this case, when the target application is in an executable state by the user terminal 100, for example, the user terminal 100 performs an available registration (for example, user registration) to a server device that is the subject of execution of the target application. It means that the target application can be executed via the communication network according to the instruction from.

Further, the first information described by taking the installation notification information as an example may be any information transmitted from the user terminal 100 in response to execution of the target application by the user terminal 100, and is information indicating that the installation has been performed. It may be present or may be information indicating something other than having been installed. The information indicating that it has not been installed may be, for example, information indicating that it has been started, information indicating that it has been executed, mere flag information, or the like.
That is, the management server 200 only needs to be able to recognize the target application executed by the user terminal 100 based on the above-described first information acquired in response to the target application being executed by the user terminal 100.
In the operation of the mutual customer feed processing described with reference to FIG. 14 described above, the first information (in FIG. 14, the installation notification information) when the user terminal 100 is first installed after the target application is installed. ) Has been described, but the present invention is not limited to this. For example, the user terminal 100 may transmit the first information (for example, installation notification information) to the management server 200 each time the target application is activated.

In addition, if the second information described using the application list as an example includes information indicating at least one target application for which the installation notification information has not been acquired from the user terminal 100, the form of the information may be any form. It may be. For example, the second information may be data of an application list page that can be displayed by the user terminal 100, or may be information indicating a link destination of the application list page (for example, redirect instruction information). In the application list page, information indicating a plurality of target applications may be displayed in vertical (vertical) alignment (so-called list display) or in horizontal (horizontal) alignment. Alternatively, it may be displayed in a grid-like arrangement (so-called grid display) in the vertical and horizontal directions. Further, the second information may be data simply including information indicating an object application (for example, an application name, an application icon image, an application ID, and the like) so as to be able to be displayed on the user terminal 100.
Note that the second information indicates at least one target application for which installation notification information has been acquired from the user terminal 100, in addition to information indicating at least one target application for which installation notification information has not been acquired from the user terminal 100. Information may be included. In this case, the second information includes information indicating at least one target application for which installation notification information has not been acquired from the user terminal 100, and information indicating at least one target application for which installation notification information has been acquired from the user terminal 100. And information that can be distinguished from

Thereby, the management server 200 transmits information indicating the target application not installed in the user terminal 100 to the user terminal 100 by receiving a request based on the customer sending source application 10 executed by the user terminal 100. Can.
Here, to receive a request based on the customer sending application 10 executed by the user terminal 100 means, for example, an application of a target application that can be installed in the user terminal 100 in the customer sending application 10 executed by the user terminal 100. The management server 200 acquires the list request notification information transmitted from the user terminal 100 in response to the user X performing a predetermined operation for acquiring the list. Note that the user terminal 100 may transmit list request notification information to the management server 200 in response to activation of the customer sending source application 10, for example, without user operation. That is, to receive a request based on the customer sending application 10 executed by the user terminal 100, for example, acquires list request notification information transmitted from the user terminal 100 in response to activation of the customer sending application 10. You may do it.

  In addition, the management server 200 performs a reward giving process based on the fact that the customer destination application 20 among the target applications not installed on the user terminal 100 has been executed by the user terminal 100 or has become executable. can do. For example, in response to transmitting, to the user terminal 100, information indicating a target application not installed on the user terminal 100, the management server 200 is selected by the user X among the target applications indicated by the information in the user terminal 100. Based on the fact that the customer service application 20 has been executed by the user terminal 100 or has become executable, it is determined that the customer service from the customer service application 10 to the customer service 20 has been established, For example, a reward can be given to the user X who uses the user terminal 100.

(2) For example, even if the customer processing destination application 20 (an example of the second application) is executed by the user terminal 100 or is in an executable state, the reward processing unit 245 may perform the above-described reward giving processing. Good.

  As a result, the management server 200 receives the customer-sending application 20 from the customer-sending source application 10 by the user terminal 100 being executed by the user terminal 100 or in an executable state (for example, installed). When it is determined that the customer feed has been established to 20, for example, a reward can be given to the user X who uses the user terminal 100.

(3) For the reward processing unit 245, for example, the installation notification information (one example of the first information acquisition unit) corresponds to the customer sending application 20 (one example of the second application). ) May be determined to have been executed by the user terminal 100. For example, the reward processing unit 245 receives an installation notification from the user terminal 100 in response to the customer destination application 20 being installed and activated in the user terminal 100 (ie, in response to the customer destination application 20 being executed). When the information is acquired, it may be determined that the customer sending destination application 20 has been executed by the user terminal 100. The reward processing unit 245 may determine that the customer sending application 20 has been executed by the user terminal 100 when acquiring the first information as well as the installation notification information.
Further, the reward processing unit 245 may display information indicating that the customer-sending destination application 20 is installed regardless of the first information, for example, a target application other than the customer-sending source application 10 installed in the user terminal 100. Alternatively, when the customer terminal application 20 is acquired by the function of the OS of the user terminal 100, it may be determined that the customer terminal application 20 has become executable by the user terminal 100.

  Thus, the management server 200 can determine that the customer sending application 20 has been executed by the user terminal 100 by acquiring the installation notification information of the customer sending application 20 transmitted from the user terminal 100. Note that the reward processing unit 245 may make the above determination based on the installation notification information acquired by the installation notification acquisition unit 241 or the installation information managed by the installation information management unit 222, or the installation information management unit 222 may be used to The reward processing unit 245 may obtain the determination result based on the above.

(4) The reward processing unit 245 determines that the customer terminal application 20 (an example of the second application) has been executed by the user terminal 100 or is in an executable state, and is set in the customer terminal application 20. A rewarding process may be performed based on satisfaction of the rewarding condition. For example, when the customer sending application 20 is installed in the user terminal 100 and the reward giving condition set in the customer sending application 20 is satisfied, the reward processing unit 245 sends the customer sending application from the customer sending application 10 The above-mentioned reward giving process may be performed assuming that the customer sending to 20 is established.

  As described above, since the management server 200 is given a reward based on satisfaction of the reward giving condition set in the customer sending destination application 20, only the customer sending destination application 20 is simply installed. Alternatively, a reward can be provided on the condition that the customer destination application 20 is used, not just being executed (for example, simply started).

(5) The application management unit 221 manages information on a campaign period (an example of a first period) set for part or all of a plurality of target applications. In addition, the list notification unit 242 (an example of the second information notification unit) is a target application (an example of a terminal apparatus) executed among the target applications (that is, the specific applications) for which the campaign period is set. By receiving a request based on an example of the first application, the customer feed source application 10), the target application (specific application) in which at least one of the above-mentioned campaign periods has not been acquired from the user terminal 100 is shown An application list (an example of second information) including information is transmitted to the user terminal 100. Then, in response to the list notification unit 242 transmitting the application list, the reward processing unit 245 transmits a target application (an example of a second application) of the target applications indicated by the application list transmitted from the list notification unit 242, Based on the fact that the customer sending destination application 20) has been executed by the user terminal 100 or has become executable within the campaign period, a reward giving process is performed.

Accordingly, when a campaign period is set in the customer sending application 10 executed by the user terminal 100 (that is, when the customer sending application 10 is a specific application), the management server 200 determines the customer sending application By receiving the request based on 10, it is possible to transmit, to the user terminal 100, information indicating at least one target application that has not been installed on the user terminal 100 among target applications for which a campaign period is set. The management server 200 sends, to the user terminal 100, information indicating at least one target application that has not been installed on the user terminal 100 among target applications for which a campaign period has been set with the customer sending source application 10. It may be sent.
In addition, the management server 200 has executed or becomes ready to execute the customer destination application 20 of the information indicating at least one target application not installed on the user terminal 100 within the campaign period. Based on the above, it is possible to determine that the customer-sending from the customer-sending source application 10 to the customer-sending-destination application 20 is established within the campaign period, and for example, to reward the user X who uses the user terminal 100.

(6) For example, the reward processing unit 245 causes the customer terminal application 20 (an example of the second application) to be executed or executable by the user terminal 100 within the campaign period (an example of the first period). The above reward giving process may be performed.

  As a result, the management server 200 sends the customer-sending application 20 from the customer-sending source application 10 only when the user terminal 100 has been executed or becomes executable (for example, installed) within the campaign period. It is determined that the customer sending to the customer application 20 is established within the campaign period, and, for example, a reward can be given to the user X who uses the user terminal 100.

  In the reward processing unit 245, the installation notification acquisition unit 241 (an example of the first information acquisition unit) acquires installation notification information (an example of the first information) corresponding to the customer sending application 20 (an example of the second application). In accordance with whether or not the performed timing is within the campaign period (an example of the first period), it is determined whether the customer terminal application 20 is executed by the user terminal 100 within the campaign period or outside the campaign period It is also good.

  For example, in the reward processing unit 245, the installation notification acquisition unit 241 (an example of the first information acquisition unit) acquires installation notification information (an example of the first information) corresponding to the customer sending application 20 (an example of the second application). It may be determined that the customer destination application 20 has been executed by the user terminal 100 within the campaign period if the timing at which the request is made is within the campaign period (an example of the first period).

  Thereby, the management server 200 determines whether the timing at which the customer destination application 20 is executed by the user terminal 100 is within the campaign period, at the acquisition timing of the installation notification information of the customer destination application 20 transmitted from the user terminal 100. It can be determined whether or not.

(7) The reward processing unit 245 determines that the customer terminal application 20 (an example of the second application) has been or has become executable by the user terminal 100 within the campaign period (an example of the first period) In addition, the reward giving process may be performed based on satisfaction of the reward giving condition set in the customer destination application 20.

  As described above, since the management server 200 is given a reward based on satisfaction of the reward giving condition set in the customer sending destination application 20, only the customer sending destination application 20 is simply installed. Alternatively, a reward can be provided on the condition that the customer destination application 20 is used, not just being executed (for example, simply started).

(8) For example, the application management unit 221 manages information on a campaign period (an example of a first period) set for a plurality of specific applications among a plurality of target applications to be managed. I assume. When the target application among the plurality of target applications is executed by the user terminal 100 (an example of the terminal device), the installation notification acquisition unit 241 (an example of the first information acquisition unit) determines that the target application is the user terminal The installation notification information (an example of the first information) transmitted from the user terminal 100 in response to the execution by the user 100 is acquired. In addition, the list notification unit 242 (an example of the second information notification unit) receives a request based on a target application (first application, customer sending source application 10) executed by the user terminal 100 among a plurality of target applications. An application list (an example of second information) including information indicating at least one target application for which installation notification information has not been acquired from the user terminal 100 is transmitted to the user terminal 100.
Then, in response to the list notification unit 242 transmitting the application list, the reward processing unit 245 transmits a target application (an example of a second application) of the target applications indicated by the application list transmitted from the list notification unit 242, When the campaign period is set for the customer delivery destination application 20), the customer delivery destination application 20 (an example of the second application) may be executed by the user terminal 100 or may be performed within the campaign period. Reward processing is performed based on the status of
On the other hand, the reward processing unit 245 transmits the campaign period to the target application (an example of the second application, the customer sending destination application 20) selected from among the target applications indicated by the application list transmitted from the list notification unit 242 Is not set, a reward giving process is performed based on the customer terminal application 20 (an example of the second application) being executed by the user terminal 100 or in an executable state.

  As a result, when a campaign period is not set in the customer sending destination application 20, the management server 200 is in the state where the customer sending source application 10 has been or can be executed by the user terminal 100 regardless of the period. If (for example, it is installed) reward processing (for example, normal reward processing) is performed, and a campaign period is set in the customer destination application 20, the customer origin application 10 is within the campaign period. The reward giving process (for example, a CP reward process) can be performed only when the user terminal 100 is in an executed or executable state (for example, when installed).

  In addition, the reward granting process (for example, normal reward process) when the campaign period is not set to the customer sending destination application 20 and the reward granting process when the campaign period is set to the customer sending destination application 20 (for example, The conditions of reward giving and the contents of the reward in the CP reward processing) may be the same or different.

  In addition, when the campaign period is set to the customer sending application 20, for example, as described in the first embodiment, the campaign period is set between the customer sending source application 10 and the customer sending destination application 20. Although it may have been, it is not limited to this. For example, in the case where a dedicated application specialized for the function of the customer origin sends customers to the customer destination application 20, a campaign period is not set for the dedicated application. In this case, the campaign period may be set for the customer-sending destination application 20 regardless of the customer-sending source when the campaign period is set for the customer-sending destination application 20. A configuration example of sending a customer to the customer destination application 20 from a dedicated application specialized for the function of the customer source will be described in the ninth embodiment.

  Further, the mutual customer support system 500 may be configured to perform only the reward giving process (for example, CP reward process) when the campaign period is set in the customer destination application 20, or when the campaign period is not set. Only the reward giving process (for example, the normal reward process) may be performed, or both the reward giving process may be performed.

(9) The reward processing unit 245 determines that the customer destination application 20 is a campaign when a campaign period (an example of a first period) is set for the customer destination application 20 (an example of the second application). Based on the fact that the user terminal 100 has been executed or is in an executable state within the period, and that the reward provision condition set in the customer destination application 20 is satisfied, the CP as the above-mentioned reward provision processing is performed. A reward process (an example of a first reward giving process) is performed.

  On the other hand, when the campaign period (an example of the first period) is not set for the customer sending destination application 20 (an example of the second application), the reward processing unit 245 determines that the customer sending destination application 20 is a user terminal Due to being executed by the computer 100 or being in an executable state, a normal reward process (an example of a second reward process) is performed as the above-described reward process.

  As described above, in the CP reward process when the campaign period is set for the customer sending destination application 20, the management server 200 merely executes or becomes ready to execute the customer sending destination application 20. Reward can be provided on the condition of use of the customer sending destination application 20, not only (for example, a state where the user has just started or has just been installed and not started). On the other hand, in the case of the normal reward process in which the campaign period is not set to the customer sending destination application 20, the management server 200 only installs or executes the customer sending destination application 20 (for example, simply starts up Can only give rewards.

(10) Even when the campaign period (an example of the first period) is set in the customer sending destination application 20 (an example of the second application), the reward processing unit 245 determines that the customer sending destination application 20 does not When it becomes executed or feasible outside the campaign period, a second reward giving process is performed.

  According to this, even if the campaign period is set in the customer destination application 20, it can be considered as a normal reward when it is executed or becomes executable outside the campaign period. That is, when the campaign period is set in the customer destination application 20, if the timing at which the customer destination application 20 is executed or becomes executable is within the campaign period, the CP reward process, otherwise If it is a period, it can usually be considered as a reward process.

  In the CP reward process, a reward may be provided by the customer destination application 20 being executed by the user terminal 100 within the campaign period or being in an executable state. That is, when the campaign period (one example of the first period) is set for the customer destination application 20 (one example of the second application), the reward processing unit 245 determines that the customer destination application 20 is the campaign period. Due to being executed by the terminal device or being in an executable state in the inside, CP reward processing (an example of a first reward granting process) may be performed as the above-mentioned reward granting process.

In the normal reward process, the customer destination application 20 has been or can be executed by the user terminal 100, and the reward giving condition set in the customer destination application 20 is satisfied. You may be rewarded on the basis of.
That is, when the campaign period (an example of the first period) is not set for the customer sending destination application 20 (an example of the second application), the reward processing unit 245 determines that the customer sending destination application 20 is a user terminal Generally, the reward process is performed as the above-described reward giving process based on that the process has been executed by the H.100 or when it becomes possible and that the reward giving condition set in the customer destination application 20 is satisfied. An example of the reward granting process of

(11) In the mutual customer feed system 500 of the present embodiment, the user terminal 100 (an example of a terminal device) is a terminal device that can communicate with the management server 200 described above (an example of a management device). Here, the management server 200 described above manages customer-sending information indicating customer-sending to a target application as a customer-sending destination from a target application serving as a customer-sending source among a plurality of target applications, and It manages that the target application of the said customer destination was installed based on it. For example, the management server 200 sends the target application serving as the customer serving source as the customer sending information indicating the customer serving from the target application serving as the customer sending source to the target application serving as the customer serving destination among the plurality of target applications. Customer source information and customer destination information indicating a target application to be a customer destination are associated and managed.
The user terminal 100 (SDK 11) includes an installation notification unit 103, a list request unit 104 (an example of a request unit), and a customer-sending information notification unit 106.
The installation notification unit 103 manages installation notification information (an example of first information) indicating that the target application has been installed in one target application installed in the user terminal 100 (an example of the own terminal device). Send to The list request unit 104 manages information indicating at least one target application among a plurality of target applications based on a first operation in one target application (for example, the customer sending source application 10, the first application). At the time of making a request to 200, customer sending source information (for example, the application ID of the customer sending source application 10) indicating the one target application is transmitted to the management server 200. The customer-sending information notification unit 106 is customer-sending destination information indicating a target application selected based on the second operation from among target applications indicated by the information indicating the at least one target application acquired from the management server 200. (For example, the application ID of the customer destination application 20, the application ID of the second application) is transmitted to the management server 200. For example, the customer-sending information notification unit 106 transmits, to the management server 200 as customer-sending information, customer-sending customer information indicating a target application selected based on the second operation.

As described above, in the mutual customer sending system 500 of the present embodiment, a management server 200 that manages a plurality of specific applications included in a target application corresponding to the mutual customer sending system 500, and a user terminal capable of communicating with the management server 200. In order to install another target application (for example, the customer sending destination application 20) from one target application (for example, the customer sending application 10) in the user terminal 100, the other target application (for example, 100). Customer sending to the customer destination application 20) can be performed.
Therefore, according to this embodiment, the convenience of customer sending between applications can be improved.

  Here, the customer-sending information is information indicating a customer-sending from the customer-sending source application 10 to the customer-sending destination application 20. Typically, the customer information is the list notification unit 242 (second information notification of the management server 200 by receiving a request based on the customer application 10 (an example of the first application) executed by the user terminal 100. According to the application list (an example of the second information) transmitted by the example of the unit, the information is an information indicating the customer sending destination application 20 (an example of the second application) among the target applications indicated by the transmitted application list. For example, the application ID of the customer destination application 20 may be used as the customer information. Further, the application ID of the customer sending application 20 (an example of customer sending information) may be used as the customer sending information in association with the application ID of the customer sending application 10 (an example of customer sending information). Further, the application ID of the customer sending destination application 20 may be used as the customer sending information in association with the reward user ID corresponding to the user terminal 100.

For example, the customer sending information notification unit 106 transmits the customer sending destination information to the management server 200 in association with the reward user ID (an example of unique identification information) corresponding to the user terminal 100 (an example of the own terminal device). You may
Thereby, the management server 200 can specify the user terminal 100 that has transmitted the customer-sending information.

(12) Further, the management server 200 may manage information on a campaign period (an example of a first period) set for a specific application that is a target application of a part or all of a plurality of target applications. . That is, the campaign period may be set for all of the plurality of target applications, or the campaign period may be set for part of the plurality of target applications.
The list request unit 104 (an example of a request unit) of the user terminal 100 (SDK 11) is the first of the specific applications (for example, the customer sending application 10) installed in the user terminal 100 (an example of the own terminal device). Customer request source information (for example, the customer service source application 10) indicating the one specific application when requesting the management server 200 for information indicating at least one specific application of the specific applications based on the operation. The application ID may be sent to the management server 200. Further, the customer-sending information notification unit 106 is selected based on the second operation in the campaign period from among the specific applications indicated by the information indicating the at least one specific application acquired from the management server 200. The customer destination information (for example, the application ID of the customer destination application 20) indicating the specific application may be transmitted to the management server 200.

  Thus, in the mutual customer support system 500 of the present embodiment, information on a campaign period set for a specific application which is a target application of a part or all of the target applications corresponding to the mutual customer support system 500 is managed. By the management server 200 and the user terminal 100 capable of communicating with the management server 200, in the user terminal 100, one specific application (an example of the customer sending source application 10) to another specific application (the customer sending destination application 20) Can be sent to another specific application (an example of the customer destination application 20) so that) is installed.

(13) The SDK 11 (the function of the installation notification unit 103 described above, the function of the list request unit 104 (an example of the request unit), and the function of the customer information notification unit 106 are incorporated in each of a plurality of target applications. It is executed based on an example of software. For example, the SDK 11A incorporated in the customer feed source application 10 executes the function of the installation notification unit 103, the function of the list request unit 104, and the function of the customer notification information unit 106. Note that the function of the above-described reward assignment notifying unit 107 may be executed based on the SDK 11 incorporated in each of a plurality of target applications. For example, the SDK 11B incorporated in the customer sending destination application 20 may execute the function of the installation notification unit 103 and the function of the reward giving notification unit 107. The SDK 11A and the SDK 11B may have similar functions and execute corresponding functions depending on whether they are incorporated in the customer service source application 10 or the customer destination application 20. .

  As a result, by incorporating the SDK 11 into the application, it is possible to make the target application compatible with the mutual customer delivery system 500 of the present embodiment. Therefore, for example, even in an existing application or an application to be developed, if the program of the application is updated or slightly changed so that the SDK 11 can be incorporated, the application can be made a target application corresponding to the mutual customer sending system 500. it can.

(14) The reward provision notifying unit 107 of the user terminal 100 (SDK 11) is set to the customer sending destination application 20 (an example of the target application or the specific application selected as the customer sending destination) indicated by the customer sending destination information. Customer destination information (for example, the application ID of the customer destination application 20) indicating the customer destination application 20 when the reward giving condition is satisfied, and a reward user ID (unique identification information associated with the user terminal 100) And the above-described compensation grant notification information is transmitted to the management server 200.

  Note that the reward granting notification information includes a reward user ID (an example of unique identification information) associated with the user terminal 100 and an application user ID (an example of user information) in the customer sending application 20 (an example of a second application). One example) may be associated. Then, the reward giving notification unit 107 of the user terminal 100 (SDK 11) manages the reward giving notification information in which the reward user ID associated with the user terminal 100 and the application user ID in the customer sending destination application 20 are associated. May be sent to

  In addition, the reward provision notification unit 107 may directly transmit the above-mentioned reward provision notification information to the management server 200, or the application server 300 (for example, the application server 320 corresponding to the customer destination application 20). May be sent to the management server 200 indirectly. In addition, the user terminal 100 may be configured not to include the reward assignment notifying unit 107, in which case the application server 300 (for example, the application server 320 corresponding to the customer sending destination application 20) corresponds in advance to the campaign. It is determined whether the set reward giving condition is satisfied, and when it is determined that the reward giving condition is satisfied, the reward giving notification information may be transmitted to the management server 200.

  Then, the reward processing unit 245 of the management server 200 determines that the reward giving condition is satisfied based on the satisfaction of the reward giving condition set in the customer sending destination application 20 (an example of the second application). When the reward granting notification information to be shown is acquired from the customer sending destination application 20 executed by the user terminal 100 or the application server 320 (an example of the server device) corresponding to the customer sending destination application 20, the obtained reward assignment notification information Processing of reward based on

  As described above, the management server 200 may perform the reward granting process by acquiring the reward granting notification information when the reward granting condition set in the customer sending destination application 20 is satisfied in the user terminal 100. it can.

For example, the reward processing unit 245 of the management server 200 determines the application user ID in the customer sending source application 10 based on satisfaction of the reward giving condition set in the customer sending destination application 20 (an example of the second application). Send the reward giving information associated with the user information of the first application) to the customer sending application 10 executed by the user terminal 100 or the application server 310 (an example of the server apparatus) corresponding to the customer sending application 10 Do.
Here, the management server 200 includes an application user information acquisition unit that acquires user information of a target application. For example, the application user information acquisition unit acquires the application user ID (an example of the user information of the first application) in the target application in association with the reward user ID (an example of the unique identification information) corresponding to the user terminal 100. Note that the installation notification acquisition unit 241 may function as an application user information acquisition unit. That is, the application notification ID may be included in the target application that has transmitted the installation notification information in the installation notification information. As described above, the function of the application user information acquisition unit may be included in another function.

  Accordingly, when the reward giving condition set in the customer sending destination application 20 is satisfied in the user terminal 100, the management server 200 sends the customer sending application to the user (user X) who uses the user terminal 100. The reward in 10 can be made to be granted.

  In addition, although the example of the process by which the reward in the customer sending origin application 10 is provided to a user was demonstrated as a reward provision process, it replaces with the customer sending application 10 and the process in which the reward in the customer sending destination application 20 is provided to a user It may be In this case, the management server 200, for example, includes a customer-sending-destination application ID (ApIDto) included in customer-sending information stored in the customer-sending information storage unit 237, and a target application stored in the target application information storage unit 231. The reward granting information may be transmitted to the application server 320 corresponding to the customer sending destination application 20 based on the notification destination URL (Notice URL) included in the information. It should be noted that, as the reward granting process, both the reward in the customer sending source application 10 and the reward in the customer sending destination application 20 may be given to the user, or the reward commonly available to a plurality of target applications is given to the user It may be a process to be given.

  Also, as a reward giving process, a reward that can be used by another application different from the target application, or a reward that can be used at a website (for example, a currency that can be used when buying and selling goods and services by communication via a communication network) It is good also as processing in which points etc. are given to a user. In this case, the management server 200 temporarily manages, for example, information related to the reward given to the user, and then a predetermined procedure is performed, thereby becoming a reward usable for another application or a reward usable for the website. As such, information on the managed reward may be transmitted to a server apparatus corresponding to another application or a server apparatus corresponding to a website.

(15) The customer feed information acquisition unit 243 of the management server 200 and the customer feed information management unit 223 are provided. The customer-sending information acquisition unit 243 acquires customer-sending information indicating the customer-sending to the customer-sending destination application 20 (second application). The customer-sending information management unit 223 manages the customer-sending information acquired by the customer-sending information acquisition unit 243. The reward processing unit 245 manages the customer-sending information corresponding to the customer-sending destination application 20 by the customer-sending information management unit 223 when the customer-sending destination application 20 is executed by the user terminal 100 or becomes executable. The above-mentioned reward giving process is performed on condition that it is done.

  Thus, when the customer destination application 20 is executed by the user terminal 100 or becomes executable by the present system, the mutual customer sending system 500 performs a reward giving process because there is customer sending information. When the target application is installed regardless of the present system, it is possible not to set the target for the reward giving process because there is no record of the customer information.

  Further, in the reward processing unit 245 of the management server 200, when the reward giving condition set in the customer sending destination application 20 is satisfied, the customer sending information corresponding to the customer sending destination application 20 is the customer sending information management unit 223. The above-mentioned reward giving process may be performed on the condition that it is managed.

  Thereby, the mutual customer support system 500 is configured to send customer information when the customer terminal application 20 is executed by the user terminal 100 according to the present system and the reward giving condition set in the customer destination application 20 is satisfied. Because there is a case in which the reward application process is performed, and the target application is installed without using the present system, it is possible not to perform the reward application process because there is no record of customer referral information.

For example, as the customer sending information described above, the customer sending information acquiring unit 243 may use an application of a reward user ID (an example of unique identification information) associated with the user terminal 100 and a customer sending application 10 (an example of a first application). An ID (an example of identification information) and an application ID (an example of identification information) of the customer sending destination application 20 (an example of a second application) are acquired in association with each other. Then, the customer-sending information management unit 223 associates the reward user ID associated with the customer-sending information, the application ID of the customer-sending source application 10, and the application ID of the customer-sending destination application 20, and manages it as recording of customer-sending information. .
Thus, the management server 200 can specify the user terminal 100 and the customer-sending source application 10 for which the customer-sending to the customer-sending destination application 20 has been performed. It is possible to perform a reward giving process in which a reward in the customer sending source application 10 is given.

  The customer referral information acquired by the customer referral information acquiring unit 243 includes the reward user ID associated with the user terminal 100, the application ID of the customer referral source application 10, and the application ID of the customer referral destination application 20. Even if the customer-sending information management unit 223 associates the reward user ID included in the customer-sending information, the application ID of the customer-sending source application 10, and the application ID of the customer-sending destination application 20, and manages the record as the customer-sending information Good. Further, the customer sending information includes at least the application ID of the customer sending destination application 20, and the customer sending information management unit 223 is associated with the application ID of the customer sending destination application 20 or the customer sending information. The reward user ID acquired as the information of 1 or the application ID of the customer sending source application 10 may be associated with the application ID of the customer sending destination application 20 and managed as a record of the customer sending information.

The customer support information managing unit 223 is an example of a reward user ID (specific identification information) associated with the user terminal 100 with an application ID (an example of identification information) of the customer destination application 20 (an example of a second application). ) And may be managed as a record of customer-sending information.
Thus, the management server 200 can specify at least the user terminal 100 in which the customer sending to the customer sending destination application 20 has been performed, and therefore, the user who uses the user terminal 100 can be a target of giving a reward. it can. For example, in the case of grant of rewards other than the reward in the customer-delivery source application 10, application ID of the customer-delivery source application 10 does not need to be linked | related and managed as recording of customer-delivery information.

In addition, the customer-sending information management unit 223 identifies the application ID (an example of identification information) of the customer-sending destination application 20 (an example of the second application) and the application ID (an example of the first application) It may be managed as a record of customer-sending information in association with an example of the information).
Thereby, the management server 200 can specify the customer sending source application 10 when the customer sending to the customer sending destination application 20 is performed, so that, for example, a reward to which a reward in the customer sending source application 10 is given It is possible to perform the granting process. For example, in the case where a reward in the customer sending source application 10 is given to all users who are not related to the user terminal 100 to which the customer is sent or a specific user, the reward user ID is used as a record of the customer sending information. It does not have to be associated and managed.

(16) The user terminal 100 (an example of a terminal device) is identified by a reward user ID (an example of unique identification information) associated with the user terminal 100. The reward user ID is acquired on the condition that the target application installed in the user terminal 100 is first activated among the plurality of target applications, and can be referred to from any target application executed by the user terminal 100. Are stored in the user terminal 100.

  For example, the user terminal 100 (SDK 11) includes the unique identification information acquisition unit 102. When the target application installed in the user terminal 100 is the target application installed in the user terminal 100 first among the plurality of target applications, the unique identification information acquisition unit 102 is a reward user ID (specific identification information An example is acquired, and the acquired reward user ID is stored in the terminal storage unit 140 (an example of a storage unit) so as to be referable also from other target applications installed in the user terminal 100.

  Thereby, according to the mutual customer feed system 500, the user terminal 100 automatically acquires the reward user ID when the target application is installed for the first time, and the acquired reward user ID is common even to the target application to be installed later Available to Therefore, the reward user ID can be acquired and the system can be used without the user performing a special operation.

(17) Specifically, the unique identification information acquisition unit 102 determines whether or not the reward user ID (an example of unique identification information) is stored in the terminal storage unit 140 (an example of the storage unit), and the reward user If it is determined that the ID is not stored in the terminal storage unit 140, the reward user ID is acquired.
Thereby, the user terminal 100 can acquire the reward user ID when the target application is installed and started for the first time.

  The unique identification information may be a unique device identifier (UDID) uniquely assigned to each user terminal 100, an IMEI (International Mobile Equipment Identity), or the unique user ID other than the reward user ID uniquely generated in the mutual customer sending system 500a. An identification number such as IMSI (International Mobile Subscriber Identity) may be used. In addition, these identification numbers may be used after being hashed or encrypted. That is, the identification information may be generated or set inside or outside the mutual customer sending system 500 and unique to the user terminal 100. In addition, the unique identification information is information different from each other associated with each user terminal 100 as a function of the OS of the user terminal 100 and is permitted to be used by each application (for example, advertisement identifier (Advertising) Identifier) may be used. Also, without acquiring from the user terminal 100 an ID associated with each user terminal 100 as unique identification information, for example, about 100 types of screen resolution / width, time zone time difference, etc. from the user terminal 100. The management server 200 may obtain the parameters of and use an ID generated using a predetermined algorithm. In this case, the unique identification information may not be stored in the user terminal 100.

(18) The installation notification unit 103 of the user terminal 100 (SDK 11) is a reward corresponding to the application ID (an example of identification information) of the target application installed in the user terminal 100 and the user terminal 100 (an example of the own terminal device) Installation notification information (an example of first information) is transmitted to the management server 200 in association with a user ID (an example of unique identification information).

  The installation notification acquisition unit 241 (an example of the first information acquisition unit) of the management server 200 includes a reward user ID (an example of unique identification information) associated with the user terminal 100, and an installation notification information (an example of the first information). Is associated with the application ID (an example of identification information) of the target application that has transmitted the notification information. The management server 200 further includes an installation information management unit 222 (an example of a first information management unit). The installation information management unit 222 manages installation information (an example of management information) in which the reward user ID associated with the installation notification information and the application ID of the target application are associated.

  Thus, when the target application is installed and activated in the user terminal 100 (that is, when the target application is executed in the user terminal 100), the management server 200 supports the application ID of the target application and the user terminal 100. It can be managed in association with the added reward user ID. Thus, the management server 200 can specify a target application installed (for example, installed and started) for each user terminal 100.

  In addition, the target application that transmits the reward user ID (an example of unique identification information) associated with the user terminal 100 and the installation notification information (an example of the first information) in the installation notification information (an example of the first information) Both application IDs may be included or one may be included. When one of the reward user ID and the application ID is included in the installation notification information, the other is associated with the one and transmitted from the user terminal 100 to the management server 200 as information other than the installation notification information. It is also good. In addition, the first information described using the installation notification information as an example as described above may be, for example, mere flag information. In this case, the reward user ID and the application ID may be associated with the flag information and transmitted from the user terminal 100 to the management server 200 as information other than the installation notification information.

(19) In addition, the management server 200 of the present embodiment includes an application user information acquisition unit that acquires user information of a target application. For example, the application user information acquisition unit acquires the application user ID (an example of the user information of the first application) in the target application in association with the reward user ID (an example of the unique identification information) corresponding to the user terminal 100. Note that the installation notification acquisition unit 241 may function as an application user information acquisition unit. That is, the application notification ID may be included in the target application that has transmitted the installation notification information in the installation notification information. As described above, the function of the application user information acquisition unit may be included in another function.

  The user terminal 100 (SDK 11) associates an application user ID (an example of user information in a target application) in a target application installed in the user terminal 100 with a reward user ID (an example of unique identification information) corresponding to the user terminal 100. An application user information notification unit to transmit to the management server 200 is provided. The installation notification unit 103 may function as an application user information notification unit. That is, the application notification ID may be included in the target application that has transmitted the installation notification information in the installation notification information. Thus, the function of the application user information notification unit may be included in other functions.

  Then, the installation information management unit 222 (an example of the first information management unit) of the management server 200 uses the installation user information (an example of the management information) of the application user ID (the user information of the target application acquired by the application user information acquisition unit). One example) is associated and managed. For example, the installation information management unit 222 may select the application user ID of the target application acquired by the application user information acquisition unit with the application ID of the target application or the reward user ID corresponding to the user terminal 100 associated with the installation information. Manage in association.

  Thus, when the target application is installed on the user terminal 100, the management server 200 receives the application ID of the installed target application, the application user ID of the installed target application, and the reward associated with the user terminal 100. The user ID can be associated and managed. That is, the management server 200 can manage the application user ID of each target application installed in the user terminal 100 in association with the reward user ID.

(20) The application management unit 221 (an example of a first reward information management unit) of the management server 200 sets a campaign period (an example of a first period) to the customer sending application 20 (an example of a second application) Information indicating a link destination of information posting location indicating CP reward (an example of a first reward) to be granted by CP reward processing (an example of a first reward giving process) performed as a reward giving process when being The campaign participation application information storage unit 235 is stored and managed. In addition, the application management unit 221 (an example of a second reward information management unit) indicates a preset normal reward provided by each of the plurality of target applications and the normal reward process (an example of a second reward giving process). The normal reward information associated with the information is stored in the normal reward information storage unit 232 and managed.
Then, the list notification unit of the management server 200 normally receives information indicating a reward for a target application for which a campaign has not been set with the customer sending source application 10 (an example of the first application) among a plurality of target applications. An application list including information indicating a normal reward is transmitted to the user terminal 100 so as to be associated and displayed. On the other hand, the list notification unit is configured to display the information indicating the link destination described above in association with the target application for which the campaign is set with the customer sending source application 10 among the plurality of target applications. An application list including information indicating the link destination is transmitted to the user terminal 100.

  Accordingly, when the user terminal 100 displays the list LT of target applications based on the application list acquired from the management server 200 on the display unit 120, the target application for which the campaign period is not set is normally given by reward. Display information related to the reward, and display in a specific application where the campaign is set, the information indicating the link destination of the publication location of the information related to the reward provided by the CP reward (an example of the reward) of the campaign. Can.

(21) The installation guiding instruction unit 244 (an example of the screen information notifying unit) of the management server 200 is the customer sending destination application 20 (an example of the second application) associated with the customer sending information acquired by the customer sending information acquiring unit 243. Information for causing the user terminal 100 to display a screen on which the customer destination application 20 can be installed is transmitted to the user terminal 100 based on the application ID (an example of identification information). Here, the information for displaying the screen on which the customer destination application 20 can be installed on the user terminal 100 is, for example, an application for displaying the store page of the store site where the customer destination application 20 can be installed (downloadable). This is instruction information for activating the store 30, which is information including the URL (store URL) of the page of the sales site (application store 400) to which the target application can be downloaded.

  Thereby, the user terminal 100 performs a special operation on the store page to which the selected customer destination application 20 can be installed for the user when the customer destination application 20 to be sent from the customer origin application 10 is selected. It can be displayed automatically without having to

(22) If another period not overlapping with the campaign period is set for part or all of the target application (that is, a plurality of specific applications) for which the campaign period (an example of the first period) is set Do. In this case, the reward processing unit 245 of the management server 200 performs CP reward processing (one example of reward giving processing) corresponding to the campaign period set in the customer destination application 20 (one example of the second application) in the user terminal 100. If it has already been performed, the CP reward process (an example of the reward giving process) corresponding to the above-mentioned other period is not performed.

  As a result, the mutual customer sending system 500 causes the CP reward processing for the same customer destination application 20 to again receive a CP reward for another campaign for a user who has been given a CP reward for one campaign. It can be made not to be granted. In other words, the customer destination application 20 for which the CP reward has been rewarded is not subject to another CP reward.

(23) The reward processing unit 245 of the management server 200 performs a reward giving process when a campaign period (an example of a first period) is set for the customer sending destination application 20 (an example of a second application). At least one of CP reward processing (an example of a first reward giving process) and normal reward processing (one example of a second reward giving process) performed as a reward giving process when a campaign period is not set. If it has been implemented at 100, the other reward giving process is not performed.

  For example, in the management server 200, the establishment status included in the reward establishment information of the customer destination application 20 for which normal reward processing or CP reward processing has been performed has already been updated to “1” (established). Therefore, even if the management server 200 acquires the reward granting notification information from the customer sending destination application 20 again, there is no reward establishment information that can update the establishment status to “1” (established), and the compensation grant notification information is It can be treated as invalid.

  As a result, the mutual customer support system 500 can prevent double reward reward and normal CP reward compensation from being applied to the same customer referral destination application 20. That is, the customer destination application 20 to which the reward awarding by the normal reward is performed is not the target of the CP reward. In addition, the customer destination application 20 for which the reward is provided by the CP reward is not normally targeted for the reward.

(24) The application management unit 221 of the management server 200 includes information on a campaign period (an example of a first period) set for a specific application that is a target application of a part or all of a plurality of target applications, and the information It manages information on at least an end date of a reward provision period (an example of a second period) including a part or all of the campaign period and ending after the end of the campaign period.

  The reward processing unit 245 carries out a reward giving process based on satisfaction of the reward giving condition set in the customer sending destination application 20 within the reward giving period.

  For example, when the reward giving condition set in the customer destination application 20 (an example of the second application) is satisfied, the reward giving notifying unit 107 of the user terminal 100 (SDK 11) satisfies the reward giving condition. And transmits to the management server 200 reward notification information indicating that.

  Then, when the reward processing unit 245 of the management server 200 acquires the reward provision notification information indicating that the reward provision condition is satisfied from the customer destination application 20 (an example of the second application) within the reward provision period, A reward giving process (for example, a CP reward process) is performed based on the obtained reward giving notification information.

  Thereby, even if the customer destination application 20 is installed on the user terminal 100 immediately before the end of the campaign period, the mutual customer support system 500 reaches the achievement point to which the CP reward is awarded. The user can be given a time period for which the user will try. Further, the management server 200 can be made to be rewarded when the reward granting notification information is acquired from the user terminal 100 within the reward granting period.

(25) A plurality of reward giving conditions may be provided corresponding to the customer sending destination application 20 (an example of the second application). The reward granting notification unit 107 of the user terminal 100 (SDK 11) transmits reward granting notification information to the management server 200 based on satisfaction of each of the plurality of reward grant conditions. The reward processing unit 245 of the management server 200 performs a reward giving process (for example, a normal reward process or a CP reward process) based on that one of the plurality of reward giving conditions is satisfied.

  Thus, the mutual customer feed system 500 can perform the reward giving process in response to each of the plurality of reward giving conditions corresponding to the customer sending destination application 20 being satisfied. That is, the user continues to use the customer service destination application 20 in order to obtain a plurality of rewards set in the campaign period (an example of the reward giving period) as much as possible. Therefore, the use of the customer service application 20 can be enhanced.

(26) When there are a plurality of reward provision conditions corresponding to the customer destination application 20 (an example of the second application), the reward processing unit 245 of the management server 200 satisfies one of the plurality of reward provision conditions When reward notification information is acquired from the customer destination application 20 within the reward provision period (an example of the second period) based on the received information, a reward provision process (for example, CP) based on the acquired reward notification information Perform reward process).

  Thus, even when the plurality of reward giving conditions are set in the customer sending destination application 20, the management server 200 obtains the timing at which each of the plurality of reward giving conditions is satisfied (the management server 200 acquires the reward giving notification information Remuneration can be awarded only when the timing at which the

(27) Each of the plurality of reward giving conditions is a timing at which each of the plurality of outcome points set in the process by the customer destination application 20 (an example of the second application) is reached. The reward granting notification unit 107 of the user terminal 100 (SDK 11) is an outcome point ID (result point information indicating an achieved outcome point among the plurality of outcome points, based on satisfaction of each of the plurality of reward assignment conditions). Each of the reward granting notification information associated with 1) is transmitted to the management server 200. Then, the reward processing unit 245 of the management server 200 outputs an outcome point ID indicating an achieved outcome point out of the plurality of outcome points from the customer destination application 20 based on satisfaction of each of the plurality of reward giving conditions. The customer offer source application 10 executed by the user terminal 100 to obtain reward granting notification information with which (result point information) is associated, and the reward grant information with which the obtained result point ID (result point information) is linked. (An example of the first application) or an application server 310 (an example of a server apparatus) corresponding to the customer sending source application 10.

In other words, the management server 200 sends, to the customer sending source application 10, a result point ID indicating the result points that have reached each of the plurality of result points of the customer sending destination application 20 in the user terminal 100. It transmits to the corresponding application server 310.
As a result, in response to each of the plurality of outcome points set in the customer destination application 20 having reached each other, the mutual customer delivery system 500 is provided with a reward corresponding to each of the achieved outcome points. Can be

(28) The reward assignment notifying unit 107 of the user terminal 100 (SDK 11) associates arrival information indicating that one of a plurality of outcome points has been reached based on satisfaction of each of the plurality of reward assignment conditions. The reward granting notification information may be transmitted to the management server 200. Then, the reward processing unit 245 of the management server 200 reaches any of the plurality of result points from the customer sending destination application 20 (an example of the second application) based on that each of the plurality of reward giving conditions is satisfied. Customer offer application which is executed by the user terminal 100 according to the number of acquisitions of the reward granting notification information each time the reward granting notification information associated with the arrival information indicating that it has been obtained is acquired 10 (an example of the first application) or the application server 310 (an example of the server apparatus) corresponding to the customer sending source application 10 may be transmitted.

  That is, even if the outcome point ID is not associated with the reward granting information transmitted to the application server 310 corresponding to the customer sending source application 10 when the management server 200 reaches any of the plurality of outcome points, the reward is awarded. Information indicating the number of times of acquisition of notification information (that is, information indicating the number of times the result point has been reached and which is the result point) may be associated. In this case, the application server 310 and the management server 200 only need to make arrangements in advance to exchange reward giving information including information indicating the number of times described above. Therefore, even if the mutual customer-sending system 500 includes information indicating the number of times of acquisition of the compensation giving notification information in place of the achievement point ID in the compensation giving information, the compensation is provided corresponding to each of the reached achievement points. Can be

(29) The reward processing unit 245 of the management server 200 selects one of the plurality of outcome points from the customer destination application 20 (an example of the second application) based on that each of the plurality of reward giving conditions is satisfied. The customer delivery source application 10 (first application executed by the user terminal 100 to obtain reward granting notification information associated with arrival information indicating arrival, and to which the reward arrival information associated with the acquired arrival information is (Example) or the application server 310 (an example of a server apparatus) corresponding to the customer sending source application 10 may be transmitted.

  That is, the management server 200 transmits the reward point information to the application server 310 corresponding to the customer sending source application 10 when any of the plurality of outcome points is reached, even if the outcome point ID is not associated. Arrival information (for example, flag information simply indicating that the outcome point has been reached) indicating that the outcome point of the event has been reached may be associated. In this case, the application server 310 and the management server 200 only need to arrange in advance to exchange reward granting information including arrival information. Then, the application server 310 may count the number of acquisitions of arrival information and may provide a reward according to the counting result. Therefore, the mutual customer support system 500 can be made to be rewarded corresponding to each of the reached result points, even if reward information is simply associated with the arrival information instead of the result point ID.

(30) The application management unit 221 of the management server 200 sets the setting application that sets the prohibition of the publication based on the application list (an example of the second information), and the application that the publication based on the application list of the setting application is prohibited It manages inter-application filter information (an example of first posting prohibition information) associated with the setting side application. Then, the list notification unit 242 (an example of the second information notification unit) of the management server 200 refers to the inter-application filter information managed by the application management unit 221, and the customer sending source application 10 (an example of the first application). When there is inter-application filter information in which the setting side application is set, the remaining information excluding the information indicating the setting side application from the application list is transmitted to the user terminal 100.

  In this way, in the mutual customer sending system 500, it is possible to set in the management server 200 the relationship of target applications that you do not want to be allowed to mutually feed in normal reward. For example, if there is a rating (age restriction) set in the target application, the customer sending source application 10 in which the rating is not set is sent to the customer sending destination application 20 in which the rating is set. You can try not to

  Further, the list notification unit 242 (an example of the second information notification unit) of the management server 200 refers to the inter-application filter information (an example of the first posting prohibition information) managed by the application management unit 221 and transmits it. When there is inter-application filter information in which the customer source application 10 is set as the setting side application, the remaining information excluding the information indicating the set side application from the application list is transmitted to the user terminal 100.

  As a result, target applications set for each of the setting application and the setting application of the inter-application filter information can prohibit (block) posting in the application list (bi-directionally).

In addition, the application management unit 221 of the management server 200 is inter-application filter information (an example of second posting prohibition information) in which an application on the set side to which posting based on the application list (an example of the second information) is prohibited is registered. Manage
Then, the list notification unit 242 (an example of the second information notification unit) of the management server 200 refers to the inter-application filter information managed by the application management unit 221, and the application to be set indicated by the inter-application filter information When a campaign period (an example of a first period) is not set with respect to and customer sending source application 10 (an example of the first application), the information indicating the application to be set is removed from the application list Is transmitted to the user terminal 100.

  In this way, in the case of a target application that wants to participate in the inter-customer system 500 only for the campaign, outside the campaign period, it is made not to be listed in the target application list LT even for customers from any target application. Can.

(31) Further, in the above embodiment, the reward user ID is included in various information such as installation notification information, list request notification information, customer sending information, remuneration giving notification information, etc. However, although the example associated with the reward user ID corresponding to the user terminal 100 that has transmitted these various information has been described, the present invention is not limited to this. For example, when a communication session is established between the management server 200 and the user terminal 100, the established communication session may be associated with the reward user ID corresponding to the user terminal 100. Thus, even if the various information does not include the reward user ID, the various information transmitted in the established communication session may be associated with the reward user ID associated with the communication session.
Note that the method of associating the various information with the reward user ID is an example, and the management server 200 associates the various information with the reward user ID for identifying the user terminal 100 that has transmitted the various information. For example, the method is not limited to the above.

Third Embodiment
Next, a third embodiment of the present invention will be described. First, an overview of the mutual customer delivery system 500a of the present embodiment will be described.
Generally, the target application installed in the user terminal 100 is installed by the user himself or herself accessing the application store 400 without being installed via the mutual feed system 500 or via the mutual feed system 500. There are cases where By the way, some target applications are compatible with the same system by upgrading from a previous version in which the SDK 11 is not incorporated to a version in which the SDK 11 is incorporated. In the following description, a target application in which the SDK 11 is not incorporated is referred to as “a target application of the old version”.
Since the target application of the old version does not have a communication function with the management server 200, even if the target application of the old version is installed on the user terminal 100, it can not notify the management server 200 that it has been installed. . Therefore, the management server 200 described above recognizes that the old version is not installed. That is, it can be said that the target application of the old version is the target application before being managed by the management server 200. Therefore, in the mutual customer support system 500 in the first and second embodiments, when presenting the target application for which the user is recommended to install, the target application of the old version is included in the list LT of the target applications to be presented to the user. May be included.

  Therefore, in the present embodiment, when the target application of the old version is installed in the user terminal 100, an embodiment of the mutual customer support system 500a that presents to the user a list LT of target applications excluding the target application of the old version. Will be explained.

[Overview of Mutual Customer Service System According to Third Embodiment]
FIG. 18 is an explanatory diagram for explaining the outline of the mutual customer support system 500 a according to the third embodiment.
In this figure, a network system 1a according to this embodiment includes a management server 200a and a user terminal 100.
Here, the user terminal 100 installs the target application 10A (for example, the game A) including the SDK 1011 corresponding to the mutual customer sending system 500a and the target application 10B (for example, the game C) of the old version not incorporating the SDK 1011 An outline of the mutual customer delivery system 500a according to this embodiment will be described with reference to FIG.

(1) When the target application 10A is installed on the user terminal 100 and is initially activated by the user X, the SDK 1011 incorporated in the target application 10A indicates that the target application 10A is installed on the user terminal 100 Send notification information (game A). Thus, the management server 200a manages installation information indicating that the target application 10A has been installed on the user terminal 100, based on the installation notification information acquired from the SDK 1011.

(2) The SDK 1011 of the target application 10A acquires, from the management server 200a, non-installed information indicating a target application for which the management server 200a has not acquired installation notification information from the user terminal 100. Here, the target application 10A corresponds to a customer-sending source application having the same function as the customer-sending source application 10 in the first and second embodiments.

(3) Among the target applications indicated in the non-installed information acquired from the management server 200a, the SDK 1011 of the target application 10A includes the target application (eg, the target application 10B) of the old version installed in the user terminal 100 Detect if installed on 100 (Install detection). That is, it can be said that the non-installed information indicates a candidate of “target application of old version” to be detected in the user terminal 100. The SDK 1011 detects, for example, whether the “target application of the old version” is installed in the user terminal 100 using the URL scheme. The details of the method of using the URL scheme will be described later.

(4) The SDK 1011 of the target application 10A transmits installation notification information indicating that the target application 10B (game C) of the old version is installed to the management server 200a. Thus, the management server 200a manages installation information indicating that the target application 10B is installed on the user terminal 100 based on the installation notification information (game C) acquired from the SDK 1011. The management server 200a may manage whether the target application installed in the user terminal 100 is an old version or not.

(5) The management server 200a transmits, to the user terminal 100, an application list (not including the game C) excluding the target application 10B of the old version when presenting the target application which recommends installation to the user. .
That is, among the plurality of target applications being managed, the management server 200 a includes the installation information of the target application installed and started in the user terminal 100 and the target application of the above-mentioned old version installed in the user terminal 100. Generate an application list of at least one target application that does not manage any of the installation information.
Then, the management server 200a transmits the generated application list to the user terminal 100. The user terminal 100 is a target application excluding the target application 10B of the old version installed in the user terminal 100 as a target application that recommends installation to the user based on the above-described application list transmitted from the management server 200a. Is displayed on the display unit 120.

  Thus, even if the target application of the old version is installed in the user terminal 100, the mutual customer sending system 500a according to the present embodiment displays a list LT of target applications excluding the target application of the old version. It can be displayed on the display unit 120 and presented to the user.

Next, the mutual customer feed system 500a according to the present embodiment will be described in detail.
The configuration of the network system 1a according to the third embodiment of the present invention and the configuration of the user terminal 100 are the same as the configuration of the network system 1 in the first embodiment shown in FIG. 2 and the first shown in FIG. Since the configuration is the same as that of the user terminal 100 in the embodiment, the description thereof is omitted here.
Further, the management server 200a according to the present embodiment manages installation information based on installation notification information transmitted from the target application 10A installed in the user terminal 100 among a plurality of target applications to be managed. Furthermore, the management server 200a is a provisional installation indicating that the target application of the old version is installed, which is transmitted from the target application 10A that detects that the target application 10B of the old version is installed in the user terminal 100. Manage installation information based on notification information.

[Functional Configuration of User Terminal 100 (SDK 1011) According to Third Embodiment]
FIG. 19 is a configuration diagram showing an example of a functional configuration executed based on the SDK 1011 of the user terminal 100 according to the present embodiment.
With reference to FIG. 19, a functional configuration of mutual customer feed processing executed by the user terminal 100 (SDK 1011) in the mutual customer referral system 500a will be described.
In this figure, the SDK 1011 includes an initialization processing unit 101, a list request unit 104, a display control unit 105, a customer sending information notification unit 106, a reward provision notification unit 107, a temporary installation notification unit 108, and list acquisition. A section 109 and an uninstalled information acquisition section 111 are provided. The initialization processing unit 101 further includes a unique identification information acquisition unit 102 and an installation notification unit 103.
The SDK 1011 according to the present embodiment is different from the first and second embodiments in that the temporary installation notification unit 108, the list acquisition unit 109, and the non-installed information acquisition unit 111 are provided. Further, in FIG. 19, the same components as in FIG. 5 are denoted by the same reference numerals, and the description thereof is omitted here.

The non-installed information acquisition unit 111 includes, among the plurality of target applications, non-installed information indicating target applications for which installation information corresponding to the user terminal 100 is not managed in the management server 200a (installation information management unit 222 described later). It is acquired from the management server 200a. That is, the non-installed information indicates a target application which has not acquired installation notification information from the target application 10A (an example of the first application) installed in the user terminal 100 among the plurality of target applications.
When the installation information based on the provisional installation notification information is managed by the management server 200a, the non-installed information is either of the installation notification information or the provisional installation notification information from the target application 10A among a plurality of target applications. It also indicates the target application that has not been acquired.
The non-installed information acquired by the non-installed information acquisition unit 111 includes the application ID (ApID) of the target application indicated in the non-installed information and the URL scheme corresponding to the target application. Here, the URL scheme corresponding to the target application is stored, for example, in the target application information storage unit 231 of the management server 200a in association with the application ID (ApID) as shown in FIG. 21 described later.

  The temporary installation notification unit 108 detects the target application of the old version installed in the user terminal 100, and transmits the temporary installation notification information of the detected target application to the management server 200a. As an example of a specific process, the provisional installation notification unit 108 targets the target application indicated in the non-installed information acquired by the non-installed information acquisition unit 111, and applies the target application of the old version installed in the user terminal 100. To detect. Then, temporary installation notification information of the detected target application of the old version is transmitted to the management server 200a. In addition, when detecting the target application of the old version from the target application, it is not possible to acquire internal information such as an application user ID other than the information indicating whether or not the application is installed. Thus, although the provisional installation notification information includes the reward user ID corresponding to the user terminal 100, it does not include the application ID of the target application of the old version.

Also, as an example of a specific process, when detecting the target application of the old version installed in the user terminal 100, the temporary installation notification unit 108 uses the URL scheme acquired by the non-installed information acquisition unit 111. . The provisional installation notification unit 108 confirms whether the URL scheme corresponding to the target application can be opened (used) using a predetermined method. If it is confirmed as open as a result of the use of the method, it is detected that the target application of the old version corresponding to the URL scheme is installed in the user terminal 100. Then, the provisional installation notification unit 108 transmits, to the management server 200a, provisional installation notification information corresponding to the target application of one or more old versions detected as being installed in the user terminal 100.
Thus, the URL scheme calls an application or a specific function in the application, and is defined for each application. Therefore, by using the URL scheme, it is possible to detect an application installed in the user terminal 100.

  When there is a target application for which the installation information corresponding to the user terminal 100 is not managed in the management server 200a, the list acquisition unit 109 acquires an application list of the target application from the management server 200a. The target applications included in the application list are at least one target application for which installation information corresponding to the user terminal 100 is not managed in the management server 200a, and may be part or all. For example, only target applications that satisfy predetermined conditions may be included. Here, the application list is data of an application list page that displays, on the user terminal 100, a list LT of target applications recommended to be installed to the user. If there is no target application for which the user is recommended to install (if the target application can not be extracted), information may be included in the data to notify the user to that effect.

Configuration of Management Server 200a According to Third Embodiment
Next, details of the configuration of the management server 200a according to the present embodiment will be described with reference to FIG.
FIG. 20 is a block diagram showing an example of the configuration of the management server 200a according to this embodiment. The management server 200a includes a communication unit 210, a management unit 220, a storage unit 230, and a control unit 240a. In addition, in this figure, the same code | symbol is attached | subjected to the structure similar to FIG. 6, and description is abbreviate | omitted here.
In FIG. 20, the control unit 240a includes an installation notification acquisition unit 241, a list notification unit 242, a customer sending information acquisition unit 243, an installation guidance instruction unit 244, a reward processing unit 245, a timing unit 246, and a temporary installation. A notification acquisition unit 247 and an uninstalled information notification unit 248 are provided.
The control unit 240a in this embodiment is different from the first and second embodiments in that the control unit 240a includes a temporary installation notification acquisition unit 247 and an uninstalled information notification unit 248.

  Furthermore, in the present embodiment, the data configuration of the target application information stored in the target application information storage unit 231 and the data configuration of the installation information stored in the installation information management unit 222 are the first and second embodiments. However, here, first, the data configuration of the target application information and the data configuration of the installation information in this embodiment will be described.

FIG. 21 is a diagram showing an example of target application information stored in the target application information storage unit 231 according to the present embodiment.
The target application information storage unit 231 according to the present embodiment stores target application information as shown in FIG. The target application information includes the application ID (ApID) of the target application, the notification destination URL (Notice URL), the store URL (ApStore URL), the URL scheme (ApURI) corresponding to the target application described above, and the target application An application name (ApNAME) indicating a name, an application description (ApDOC) which is explanatory information on the target application, an application icon image (ApICO) which is an icon image indicating the target application, and an application price (ApPRICE) are associated It is done.
The present embodiment differs from the first and second embodiments in that the target application information includes a URL scheme (ApURI).

FIG. 22 is a diagram showing an example of installation information stored in the installation information storage unit 236 according to the present embodiment.
The installation information storage unit 236 according to the present embodiment stores installation information as shown in FIG. The installation information is associated with a reward user ID (Reward UID), an application ID (Ap ID), an application user ID (Ap UID), and a notification type (Ttype). The reward user ID (Reward UID), the application ID (Ap ID), and the application user ID (Ap UID) are information included in the acquired installation notification information and temporary installation notification information. However, as described above, in the case of the target application of the old version, the provisional installation notification information does not include the application user ID (ApUID). The ID (ApUID) is set to “null”.
The present embodiment differs from the first and second embodiments in that the target application information includes a notification type (Ttype).

  Here, the notification type (Ttype) includes the installation information stored based on the installation notification information by the installation notification unit 103 described above, and the installation information stored based on the temporary installation notification information by the temporary installation notification unit 108. It is information to distinguish. That is, the notification type (Ttype) is information that distinguishes whether the application installed in the user terminal 100 is a target application provided with the SDK 1011 or a target application of the old version not provided with the SDK 1011.

  For example, in the example shown in FIG. 22, when the notification type (Ttype) is “0”, the installation information stored based on the installation notification information is shown, and when the notification type (Ttype) is “1”. And the installation information stored based on the provisional installation notification information. For example, the installation information storage unit 236 illustrated in FIG. 22 receives notification of “09634565” of the reward user ID (Reward UID), “001” of the application ID (ApID), and “5288” of the application user ID (ApUID). The type (Ttype) “0” is associated and stored as installation information. In this case, since the notification type (Ttype) is “0”, the installation information indicates that the application installed in the user terminal 100 is a target application including the SDK 1011. Further, for example, in the installation information storage unit 236 illustrated in FIG. 21, “09634565” of the reward user ID (Reward UID), “002” of the application ID (ApID), and “null” of the application user ID (ApUID) The notification type (Ttype) “1” is associated with each other and stored as installation information. In this case, since the notification type (Ttype) is “1”, the installation information indicates that the application installed in the user terminal 100 is a target application of the old version not provided with the SDK 1011.

Next, returning to FIG. 20, the configuration of the control unit 240 will be described.
The non-installed information notification unit 248 transmits the non-installed information to the SDK 1011. The non-installed information notification unit 248 transmits non-installed information to the target application 10A installed in the user terminal 100 by referring to information managed by the application management unit 221 and the installation information management unit 222, for example. Do. Here, the non-installed information indicates a target application for which the installation notification acquisition unit 241 has not acquired installation notification information from the target application 10A installed in the user terminal 100 among a plurality of target applications. The information managed by the application management unit 221 and the installation information management unit 222 is the target application information stored in the target application information storage unit 231 and the installation information stored in the installation information storage unit 236. .

  Specifically, the non-installed information notification unit 248 notifies, of the target application information stored in the target application information storage unit 231, a target application that is not included in the installation information stored in the installation information storage unit 236. Extract regardless of type (Ttype). Then, the non-installed information notification unit 248 acquires, for example, the application ID (ApID) of the extracted target application and the URL scheme corresponding to the target application from the target application information storage unit 231, and acquires the acquired application ID (ApID) And the URL scheme are transmitted to the target application 10A installed in the user terminal 100.

  When the target application of the previous version is installed on the user terminal 100, the temporary installation notification acquisition unit 247 acquires temporary installation notification information indicating that the target application of the previous version is installed from the target application 10A. . The provisional installation notification acquisition unit 247, for example, among the target applications indicated in the non-installation information transmitted by the non-installation information notification unit 248, the provisional installation notification information of the target application of the old version installed in the user terminal 100; Acquire from the target application 10A. Then, the temporary installation notification acquisition unit 247 supplies the acquired temporary installation notification information to the installation information management unit 222.

Note that, when there is a target application for which installation information corresponding to the user terminal 100 is not managed in the installation information management unit 222 among the plurality of target applications, the list notification unit 242 of the present embodiment The application list of part or all (at least one target application) is transmitted to the user terminal 100. The other functions of the list notification unit 242 are the same as those of the list notification unit 242 of the first and second embodiments.
The application management unit 221 according to the present embodiment manages information on a plurality of target applications to be managed. Further, the installation information management unit 222 of the present embodiment manages installation information of the target application installed in the user terminal 100 based on the installation notification information and the temporary installation notification information acquired from the target application 10A.

[Details of operation of mutual customer processing according to the third embodiment]
Next, the operation of the mutual customer sending system 500a of the present embodiment will be described.
The basic operation of the mutual customer sending system 500a of this embodiment is the same as that of the first embodiment shown in FIGS. 14 and 15, and here, with reference to FIG. The operation of the mutual customer delivery system 500a will be described focusing on the process of generating an application list of applications. The process shown in FIG. 23 shows a detailed example of the flow of the outline process described with reference to FIG.

  Here, processing of the target application 10A installed in the user terminal 100 will be described with reference to FIG. Further, it is assumed that an SDK 1011A similar to the above-described SDK 1011 is incorporated in the target application 10A.

In FIG. 23, since the process of step SA11 to step SA17 is the same as that of 1st Embodiment shown in FIG. 14, the description is abbreviate | omitted here.
In step SE11, the installation information management unit 222 of the management server 200a determines the reward user ID (Reward UID) included in the installation notification information acquired by the installation notification acquisition unit 241, the application ID (ApID) of the target application 10A (game A), The application user ID (ApUID) of the user X in the target application 10A (game A) and the notification type (Ttype) are associated with each other and stored in the installation information storage unit 236 as installation information. In this case, the installation information management unit 222 stores the notification type (Ttype) as “0” in the installation information storage unit 236.

  Next, the non-installed information acquisition unit 111 of the SDK 1011A generates non-installed information request notification information for requesting non-installed information corresponding to the reward user ID read out from the inter-application shared area of the terminal storage unit 140 in step SA170. The generated non-installed information request notification information includes a reward user ID. The non-installed information acquisition unit 111 transmits the generated non-installed information request notification information to the management server 200a (REQ11A, step SA171).

Next, the non-installed information notification unit 248 of the management server 200a extracts the non-installed target application based on the non-installed information request notification information transmitted from the SDK 1011A of the target application 10A (step SE111). Specifically, the non-installed information notification unit 248 is stored in the installation information storage unit 236 in association with the acquired reward user ID among the target application information stored in the target application information storage unit 231. Extract all not installed target applications that do not exist in the existing installation information. Then, the non-installed information notification unit 248 acquires, from the target application information storage unit 231, the application ID (ApID) corresponding to all the extracted non-installed target applications and the URL scheme. The non-installed information notification unit 248 generates non-installed information corresponding to all the extracted non-installed target applications, including the application ID (ApID) and the URL scheme corresponding to each target application.
Next, the non-installation information notification unit 248 notifies the SDK 1011A of the generated non-installation information (RES11A, step SE112). If the non-installed target application is not extracted, the non-installed information notification unit 248 may notify information indicating that the non-installed target application does not exist as the non-installed information.

  Next, the non-installed information acquisition unit 111 of the SDK 1011A acquires the non-installed information transmitted from the non-installed information notification unit 248 of the management server 200a (step SA172).

Next, the provisional installation notification unit 108 of the SDK 1011A confirms the installation of the target application not yet installed included in the acquired non-installation information (step SA173). Specifically, the temporary installation notification unit 108 uses the URL scheme included in the non-installed information acquired by the non-installed information acquisition unit 111, and among the non-installed target applications, the target installed in the user terminal 100. Detect the application The fact that the target application is detected using the URL scheme regardless of the target application whose installation information is not managed by the management server 200a indicates that the target application of the old version is installed in the user terminal 100. . That is, the provisional installation notification unit 108 detects the target application of the old version installed in the user terminal 100.
For example, the temporary installation notification unit 108 detects a target application of the old version installed in the user terminal 100 using a predetermined method as to whether or not the URL scheme corresponding to the target application can be opened.
If a function capable of detecting an installed application other than the URL scheme is provided, the temporary installation notification unit 108 may use the function.

  Next, the provisional installation notification unit 108 notifies the management server 200a of the result of the installation confirmation (step SA174). That is, the provisional installation notification unit 108 transmits, to the management server 200a, provisional installation notification information indicating the target application of the old version detected as being installed in the user terminal 100 (REQ11B). If there is no target application of the old version in the user terminal 100, information may be notified as temporary installation notification information that the target application of the old version does not exist. In addition, when the non-installed information acquired by the non-installed information acquisition unit 111 indicates that there is no non-installed target application, the temporary installation notification unit 108 does not transmit temporary installation notification information to the management server 200 a. You may do so.

  Next, the temporary installation notification acquisition unit 247 of the management server 200a acquires temporary installation notification information transmitted from the temporary installation notification unit 108 of the SDK 1011A (SE113). That is, the temporary installation notification acquiring unit 247 is, for example, a temporary installation notification information of the target application of the old version installed in the user terminal 100 among the target applications indicated in the non-installation information transmitted by the non-installation information notification unit 248. Are acquired from the SDK 1011A of the target application 10A. Then, the temporary installation notification acquisition unit 247 supplies the acquired temporary installation notification information to the installation information management unit 222.

The installation information management unit 222 includes the reward user ID (Reward UID) included in the temporary installation notification information acquired by the temporary installation notification acquiring unit 247, the application ID (ApID) of the target application 10A (game A), and the target application 10A (game The application user ID (ApUID) of the user X in A) and the notification type (Ttype) are associated with each other and stored in the installation information storage unit 236 as installation information. In this case, the installation information management unit 222 sets the application user ID (ApUID) to “null” and stores the notification type (Ttype) as “1” in the installation information storage unit 236.
Further, the temporary installation notification acquiring unit 247 transmits response information indicating that the temporary installation notification information has been acquired, to the SDK 1011A (RES11B).

  The temporary installation notification unit 108 acquires the response information transmitted from the management server 200a (step SA175).

The subsequent processing after step SA24 (note that illustration is omitted from step SE15 and after step SA25) is the same as the processing from step SA24 to step SA26 and step SE15 to step SE19 and step SC11 shown in FIG. Therefore, the description is omitted here.
In the present embodiment, in step SE15 and step SE16, the list notification unit 242 includes, among the plurality of target applications, a target application whose installation information management unit 222 does not manage installation information corresponding to the user terminal 100. In this case, an application list of part or all of the target application (at least one target application) is extracted. Then, the list notification unit 242 generates data of an application list page for displaying, on the user terminal 100, a list LT of target applications based on the extracted application list of target applications. When the list notification unit 242 can not also extract one target application, the list notification unit 242 may include, in the data, information for notifying the user of that. The application list of the target application is transmitted to the user terminal 100, and the SDK 1011A of the target application 10A generates data for displaying the list LT of the target applications on the user terminal 100 based on the acquired application list. May be

Summary of Third Embodiment
(1) As described above, in the mutual customer sending system 500a of this embodiment, the management server 200a (an example of the management apparatus) includes the application management unit 221, the installation notification acquisition unit 241, and the temporary installation notification acquisition unit 247, an installation information management unit 222, and a list notification unit 242.
The application management unit 221 manages information on a plurality of target applications to be managed. The installation notification acquisition unit 241 has the target application 10A installed in the user terminal 100 from the target application 10A (an example of the first application) installed in the user terminal 100 (an example of the terminal device) among a plurality of target applications. Obtain installation notification information indicating that. When the target application of the previous version is installed in the user terminal 100, the temporary installation notification acquisition unit 247 acquires temporary installation notification information indicating that the target application is installed from the target application 10A. Here, the target application of the old version is one of a plurality of target applications and is an application before being managed by the application management unit 221, and has a communication function with the management server 200a. It is not possessed. The installation information management unit 222 manages installation information of the target application installed in the user terminal 100 based on the installation notification information and the temporary installation notification information acquired from the target application 10A. Then, the list notification unit 242 sends, to the user terminal 100, an application list of at least one target application for which installation information corresponding to the user terminal 100 is not managed in the installation information management unit 222 among a plurality of target applications. Send. The list notification unit 242 can be regarded as transmitting the application list of at least one target application for which neither the installation notification information nor the temporary installation notification information has been acquired from the target application 10A to the user terminal 100. .

  Thus, for example, even if the target application of the old version not incorporating the SDK 1011 is installed in the user terminal 100, the management server 200a of the present embodiment excludes the target application excluding the target application of the old version. Can be transmitted to the user terminal 100. That is, in the management server 200 a of the present embodiment, for example, when the target application of the old version is installed, the target application for which the old version is already installed is mistakenly presented to the user in the application list of the target application. Can be prevented. Therefore, the management server 200a according to the present embodiment, when presenting a target application for which installation is recommended to the user, regardless of the version of the target application, the application list of the target application that the user has not used. Can be sent to As a result, when presenting a target application that recommends installation to the user, the user terminal 100 can present the user with a list LT of target applications that have not been used by the user.

(2) Further, the management server 200 a according to the present embodiment targets uninstalled information indicating target applications for which installation information corresponding to the user terminal 100 is not managed in the installation information management unit 222 among a plurality of target applications. The non-installed information notification unit 248 that transmits to the application 10A (an example of the first application) is provided. It can be said that the non-installed information indicates the candidate of the target application of the old version to be detected in the user terminal 100.
Then, the temporary installation notification acquisition unit 247 acquires temporary installation notification information of the target application of the old version installed in the user terminal 100 among the target applications indicated in the non-installation information transmitted by the non-installation information notification unit 248, Acquire from the target application 10A. The non-installed information notification unit 248 transmits, to the target application 10A, non-installed information indicating a target application for which the installation notification information and the temporary installation notification information have not been acquired from the target application 10A among the plurality of target applications. It can be understood as
Thereby, the management server 200a makes the target of detection of the target application of the old version in the user terminal 100 clear by notifying the candidate of the target application of the old version to be detected in the user terminal 100 as uninstalled information. be able to. As a result, compared with the case of extracting from all target applications, the processing amount of extraction of the target application of this old version can be reduced. Further, the target application 10A can shorten the processing time for extracting the target application of the old version as compared with the case of extracting from all the target applications.
In addition, the management server 200 a of the present embodiment can manage a target application of the old version installed in the user terminal 100. As a result, the management server 200 a of the present embodiment can transmit, to the user terminal 100, an application list of target applications excluding target applications of the old version installed in the user terminal 100. As a result, when presenting a target application for which installation is recommended to the user, the user terminal 100 can present the user with a list LT of the target applications excluding the target application of the old version.

(3) Further, the management server 200a according to the present embodiment indicates a target application that has not acquired installation notification information from the target application 10A (an example of the first application) installed in the user terminal 100 among a plurality of target applications. An uninstalled information notification unit 248 that transmits uninstalled information to the target application 10A is provided. It can be said that the non-installed information indicates the candidate of the target application of the old version to be detected in the user terminal 100.
Then, the temporary installation notification acquisition unit 247 acquires temporary installation notification information of the target application of the old version installed in the user terminal 100 among the target applications indicated in the non-installation information transmitted by the non-installation information notification unit 248, Acquire from the target application 10A.
Thereby, the management server 200a makes the target of detection of the target application of the old version in the user terminal 100 clear by notifying the candidate of the target application of the old version to be detected in the user terminal 100 as uninstalled information. be able to. As a result, compared with the case of extracting from all target applications, the processing amount of extraction of the target application of this old version can be reduced. Further, the target application 10A can shorten the processing time for extracting the target application of the old version as compared with the case of extracting from all the target applications.
In addition, the management server 200 a of the present embodiment can manage a target application of the old version installed in the user terminal 100. As a result, the management server 200 a of the present embodiment can transmit, to the user terminal 100, an application list of target applications excluding target applications of the old version installed in the user terminal 100. As a result, when presenting a target application for which installation is recommended to the user, the user terminal 100 can present the user with a list LT of the target applications excluding the target application of the old version.

(4) Further, in the management server 200 a of the present embodiment, the non-installed information notification unit 248 refers to the information managed by the application management unit 221 and the installation information management unit 222 to obtain the non-installed information as the user terminal 100. It transmits to target application 10A installed in. Here, the non-installed information indicates a target application of which installation information corresponding to the user terminal 100 is not managed in the installation information management unit 222 among a plurality of target applications.
In the case where the management server 200a according to the present embodiment acquires temporary installation notification information for the target application of the old version (a game of an old version different from the game C) from the target application 10A (an example of the first application). The installation information management unit 222 associates and manages the target application to which the installation notification information or the temporary installation notification information has been sent, and the user terminal 100 on which the target application is installed, and the non-installed information notification unit 248 Among the plurality of target applications, uninstalled information indicating target applications for which the installation notification information and the provisional installation notification information have not been obtained from the target application 10A is used as the target application. It may be transmitted to 10A.
Thus, the non-installed information notification unit 248 refers to information managed by the application management unit 221 that manages information on a plurality of target applications to be managed, and extracts all the target applications and the installation information management unit 222. The target application for which the installation information corresponding to the user terminal 100 is not managed is not indicated by comparing the target application for which the installation information corresponding to the user terminal 100 extracted with reference to the information to be managed is managed. It becomes possible to identify installation information. It can be said that the non-installed information indicates the candidate of the target application of the old version to be detected in the user terminal 100.

(5) Moreover, in the mutual customer sending system 500a of this embodiment, the user terminal 100 (an example of a terminal device) is a terminal device that can communicate with the management server 200a. Here, the management server 200a includes installation notification information indicating that the target application installed in the user terminal 100 among the plurality of target applications to be managed has been installed, and the target application of the old version (target of management The installation information of the target application installed in the user terminal 100 is managed based on provisional installation notification information indicating that the target application before becoming (1) is installed in the user terminal 100. The user terminal 100 includes an installation notification unit 103, a temporary installation notification unit 108, a list acquisition unit 109, and a display control unit 105.
The installation notification unit 103 transmits installation notification information of the target application installed in the own user terminal 100 to the management server 200a. The temporary installation notification unit 108 detects the target application of the old version installed in the own user terminal 100, and transmits the temporary installation notification information of the detected target application to the management server 200a. The list acquisition unit 109 acquires, from the management server 200a, an application list of at least one target application for which installation information corresponding to the user terminal 100 is not managed in the management server 200a. The list acquisition unit 109 can be regarded as acquiring from the management server 200a an application list of at least one target application to which neither the installation notification information nor the temporary installation notification information has been transmitted. Then, the display control unit 105 causes the display unit 120 to display a list LT of target applications based on the application list of the target applications acquired by the list acquisition unit 109. The list acquisition unit 109 may acquire, from the management server 200 a, a list LT of target applications indicating data to be displayed based on the application list. The list acquisition unit 109 can be understood as acquiring from the management server 200a an application list of at least one target application for which neither the installation notification information nor the temporary installation notification information has been transmitted from the user terminal 100.

  Thus, for example, when the target application of the old version not incorporating the SDK 1011 is installed in the user terminal 100, the user terminal 100 of the present embodiment is an application list of the target application excluding the target application of the old version. And a list LT of target applications based on the acquired application list can be presented to the user. Therefore, the user terminal 100 of the present embodiment can transmit, to the user terminal 100, the application list of the target application that has not been used by the user regardless of the version of the target application. As a result, when presenting a target application that recommends installation to the user, the user terminal 100 can present the user with a list LT of target applications that have not been used by the user.

(6) Further, the user terminal 100 according to the present embodiment acquires uninstalled information from the management server 200a, which acquires non-installed information indicating target applications for which installation information corresponding to the user terminal 100 is not managed in the management server 200a. The unit 111 is provided. The non-installed information acquisition unit 111 acquires, from the management server 200a, non-installed information indicating a target application for which neither the installation notification information nor the temporary installation notification information has been transmitted from the user terminal 100 among a plurality of target applications. It can be understood as
Then, the temporary installation notification unit 108 manages temporary installation notification information of the target application of the old version installed in the own user terminal 100 among the target applications indicated in the non-installed information acquired by the non-installed information acquisition unit 111. It transmits to the server 200a.
As a result, the target application 10A of the user terminal 100 according to the present embodiment extracts, for example, the target application of the old version installed in the user terminal 100 out of the acquired non-installed information. The processing amount of extraction of the target application of this old version can be reduced compared to the case of extraction from the above. Further, the user terminal 100 according to the present embodiment can shorten the processing time for extracting the target application of the old version as compared with the case of extracting it from all the target applications.

(7) Further, the user terminal 100 according to the present embodiment is not yet installed from the management server 200 a to acquire uninstalled information indicating a target application for which the installation notification information is not transmitted from the own user terminal 100 among a plurality of target applications. The information acquisition unit 111 may be provided. Then, the temporary installation notification unit 108 manages temporary installation notification information of the target application of the old version installed in the own user terminal 100 among the target applications indicated in the non-installed information acquired by the non-installed information acquisition unit 111. It transmits to the server 200a.
As a result, the target application 10A of the user terminal 100 according to the present embodiment extracts, for example, the target application of the old version installed in the user terminal 100 out of the acquired non-installed information. The processing amount of extraction of the target application of this old version can be reduced compared to the case of extraction from the above. Further, the user terminal 100 according to the present embodiment can shorten the processing time for extracting the target application of the old version as compared with the case of extracting it from all the target applications.

(8) Further, in the present embodiment, the non-installed information acquisition unit 111 acquires the URL scheme corresponding to the target application indicated in the non-installed information, which is included in the non-installed information. Then, using the URL scheme acquired by the non-installed information acquisition unit 111, the temporary installation notification unit 108 uses, as a target application indicated in the non-installed information, the target application of the old version installed in the user terminal 100 To detect
Thereby, the user terminal 100 according to the present embodiment can detect the target application of the old version by, for example, a simple means of determining whether the URL scheme can be opened in the user terminal 100.

(9) Further, in the present embodiment, the application management unit 221 sets a setting side application that sets prohibition of posting in the target application list LT based on the application list of the target application, and the target application of the setting side application. The inter-application filter information (first posting prohibition information) may be managed in combination with a set-side application on the side of which posting on the list LT is prohibited. In this case, the list notification unit 242 refers to the inter-application filter information (first posting prohibition information) managed by the application management unit 221, and the inter-application setting the target application 10A as the set-side application If there is filter information (first posting prohibition information), the application list of the target application excluding the setting side application is transmitted to the user terminal 100.
Further, in the present embodiment, the list notification unit 242 refers to the inter-application filter information (first posting prohibition information) managed by the application management unit 221, and sets the target application 10A as the setting-side application. When there is inter-application filter information, an application list of target applications excluding the set-side application may be transmitted to the user terminal 100.
Further, in the present embodiment, even if the application management unit 221 manages inter-application filter information (second posting prohibition information) in which only the set-side application on the side that is prohibited from being listed in the application list is registered. Good. In this case, the list notification unit 242 refers to the inter-application filter information managed by the application management unit 221, and transmits the application list of the target application excluding the application to be set to the user terminal 100.

  As a result, in the mutual customer delivery system 500a, when presenting a target application for which installation is recommended to the user, it is possible to set, in the management server 200a, the relationship between the target applications that the user does not want to recommend. For example, if there is a rating (age limitation) set in the target application, the target application 10A in which the rating is not set can not recommend the target application in which the rating is set. .

(10) Further, the management server 200a of the present embodiment includes the reward processing unit 245. The reward processing unit 245 determines a predetermined reward giving condition in the customer destination application 20 (an example of the second application) of the first embodiment selected by the user terminal 100 from one or more target applications included in the application list. When it is determined that the request is satisfied, the target application 10A (an example of the first application) corresponding to the customer sending source application 10 executes a reward granting process in which a predetermined reward is given.
In this way, in the mutual customer sending system 500a that rewards the target application of the customer sending source when the target application of the customer sending destination that has not been used by the user is installed, the target application that recommends installation for the user is presented. In this case, the application list of the target application which has not been used by the user who is the target of the reward giving can be transmitted to the user terminal 100 excluding the target application of the old version. As a result, when presenting a target application that recommends installation to the user, the user terminal 100 can present the user with a list LT of target applications that have not been used by the user. In addition, when the target application of the old version is included in the target application list LT and the target application of the old version is updated to the target application of the new version, the management server 200 a sends the customer sending application 10 Can be prevented from being given a reward.

(11) Further, the management server 200a of the present embodiment includes the customer referral information acquisition unit 243 and the customer referral information management unit 223, and the reward processing unit 245 satisfies the predetermined reward provision condition. If it is determined that the customer feed information for the second application is managed by the customer feed information management unit 223, the reward giving process may be executed. Here, the customer-sending information acquisition unit 243 acquires the customer-sending information for the second application from the target application 10A, and the customer-sending information management unit 223 manages the customer-sending information acquired by the customer-sending information acquisition unit 243. You may
As a result, when the target application is installed without using the present system, the mutual customer sending system 500a can not be a target of reward giving because there is no record of the customer sending information.
(12) Further, the predetermined reward giving condition may be when it is determined that the customer sending destination application 20 (an example of the second application) is installed in the user terminal 100. Further, the predetermined reward giving condition may be determined when it is determined that the customer sending destination application 20 is installed in the user terminal 100 and it is determined that the predetermined result is achieved in the customer sending destination application 20.
Thus, the mutual customer delivery system 500a can arbitrarily set the reward giving condition.
(13) Further, the application management unit 221 may manage an event having a predetermined period set for a plurality of specific applications among a plurality of target applications. In this case, the predetermined reward giving condition is determined that the second application is a specific application and the second application is installed in the user terminal 100 within a predetermined period, and the predetermined result is achieved in the second application. It may be determined that it has been done.

  As a result, among the plurality of target applications, only a specific application that is performing a campaign can be targeted for rewarding. Among the specific applications that are carrying out the campaign, even when the previous version of the specific application is installed on the user terminal 100, when presenting a specific application that recommends installation for the user, An application list of a specific application that has not been used by the user can be transmitted to the user terminal 100 excluding the version target application. As a result, it is possible to make the user present a list of target applications (specific applications) that have implemented a campaign that the user has never used.

(14) Further, the user terminal 100 according to the present embodiment includes the reward assignment notifying unit 107. When it is determined that the predetermined reward giving condition is satisfied in the target application installed in the own user terminal 100, the reward giving notifying unit 107 indicates that the predetermined reward giving condition is satisfied. Are sent to the management server 200a. Here, when it is determined that the predetermined reward provision condition in the target application selected by the user terminal 100 from the one or more target applications included in the application list is satisfied, the management server 200a determines the predetermined target application. Execute a reward granting process in which a reward for
Note that the predetermined reward giving condition may be when it is determined that the predetermined result is achieved in the target application installed in the own user terminal 100.
Further, a plurality of predetermined reward giving conditions are provided, and the reward giving notifying unit 107 transmits the reward giving notification information to the management server 200a based on that each of the plurality of reward giving conditions is satisfied. You may
Thus, for example, when the target application of the old version is installed, the user terminal 100 according to the present embodiment does not use the target application that has been used as a target of reward giving excluding the target application of the old version. The application list can be acquired to present the user with a list LT of target applications based on the application list. Alternatively, the application list of target applications based on the application list can be presented to the user by acquiring the application list of target applications that have not been used by the user who is the target of reward giving excluding the target application of the previous version. . As a result, when the target application of the old version is included in the list of target applications LT and the target application of the old version is updated to the target application of the new version, the management server 200 a sends the customer sending application 10. Can be prevented from being given a reward.
Further, when it is determined that the predetermined reward giving condition is satisfied, the user terminal 100 according to the present embodiment sends, to the management server 200a, reward giving notification information indicating that the predetermined reward giving condition is satisfied. Can be sent.

Fourth Embodiment
Next, a fourth embodiment of the present invention will be described.
In this embodiment, when a target application of an older version not incorporating the SDK 11 is installed (updated), a list LT of target applications excluding the target application of the previous version is presented to the user, Another embodiment different from the third embodiment will be described with respect to a method of excluding an older version of the target application from the application list of the target application. That is, in the third embodiment, when the management server 200a transmits to the user terminal 100 an application list for presenting to the user a target application for which installation is recommended, the old version installed in the user terminal 100 from the application list The target application of was excluded from the list. Therefore, in advance, the non-installed information that becomes a candidate of the target application of the old version is transmitted to the user terminal 100, and the installation information of the target application of the old version installed in the user terminal 100 is acquired from the candidates. I made it.
On the other hand, the present embodiment is a method in which the management server 200b (see FIG. 25) does not transmit in advance uninstalled information which becomes a candidate of the target application of the old version to the user terminal 100. That is, the user terminal 100 regards all target applications installed in the user terminal 100 and target applications of the old version as candidates of target applications of the old version without acquiring uninstalled information from the management server 200 b. The provisional installation notification information of the target application of the old version is transmitted to the management server 200b. At this time, the target application 10A may be excluded. Then, in the management server 200b, in comparison with the information managed by the installation information management unit 222, the target application not managed by the installation information management unit 222 is identified as the target application of the old version.

[Functional Configuration of User Terminal 100 (SDK 2011) According to Fourth Embodiment]
FIG. 24 is a block diagram showing an example of a functional configuration executed based on the SDK 2011 of the user terminal 100 according to the present embodiment.
With reference to FIG. 24, the functional configuration of mutual customer feed processing executed by the user terminal 100 (SDK 2011) in the mutual customer referral system 500a will be described.
In this figure, the SDK 2011 includes an initialization processing unit 101, a list request unit 104, a display control unit 105, a customer referral information notification unit 106, a reward provision notification unit 107, a temporary installation notification unit 108, and list acquisition. And a unit 109. The initialization processing unit 101 further includes a unique identification information acquisition unit 102 and an installation notification unit 103.
The SDK 2011 of this embodiment is different from the third embodiment in that the uninstalled information acquisition unit 111 is not provided. Further, in FIG. 24, the same components as in FIG. 19 will be assigned the same reference numerals and descriptions thereof will be omitted here.

  In the present embodiment, the temporary installation notification unit 108 detects a target application and a target application of the old version among the applications installed in the user terminal 100. Then, the provisional installation notification unit 108 regards the detected provisional installation notification information of the target application as a candidate of the target application of the old version, and transmits the provisional installation notification information of the application to the management server 200b.

Configuration of Management Server 200b According to Fourth Embodiment
Next, the configuration of the management server 200b according to the present embodiment will be described with reference to FIG.
FIG. 25 is a block diagram showing an example of the configuration of the management server 200b according to this embodiment. The management server 200b includes a communication unit 210, a management unit 220, a storage unit 230, and a control unit 240b. In addition, in this figure, the same code | symbol is attached | subjected to the structure similar to FIG. 20, and description is abbreviate | omitted here.
The control unit 240b according to the present embodiment includes an installation notification acquisition unit 241, a list notification unit 242, a customer sending information acquisition unit 243, an installation guidance instruction unit 244, a reward processing unit 245, a timing unit 246, and a temporary installation. And a notification acquisition unit 247. The control unit 240b of this embodiment differs from the third embodiment in that the non-installed information notification unit 248 is not provided.

  Note that the temporary installation notification acquisition unit 247 according to the present embodiment installs temporary installation notification information excluding the target application managed by the application management unit 221 among the temporary installation notification information acquired from the temporary installation notification unit 108, for example. The information management unit 222 is supplied. That is, the temporary installation notification acquisition unit 247 temporarily installs the target application information corresponding to the target application information stored in the target application information storage unit 231 from the temporary installation notification information acquired from the temporary installation notification unit 108. Extract notification information. Then, the temporary installation notification acquisition unit 247 supplies the extracted temporary installation notification information to the installation information management unit 222.

[Details of operation of mutual customer sending processing according to the fourth embodiment]
Next, the operation of the mutual customer sending system 500a of the present embodiment will be described.
The basic operation of the mutual customer sending system 500a of this embodiment is the same as that of the first embodiment shown in FIGS. 14 and 15, and here, with reference to FIG. The operation of the mutual customer delivery system 500a will be described focusing on the process of generating an application list of applications.

  The process illustrated in FIG. 26 indicates the process of the target application 10A installed in the user terminal 100.

In FIG. 26, since the process of step SA11 to step SA17 is the same as that of 1st Embodiment shown in FIG. 14, the description is abbreviate | omitted here. The target application 10A incorporates an SDK 2011A similar to the above-described SDK 2011.
In step SE11, the installation information management unit 222 of the management server 200b determines the reward user ID (Reward UID) included in the installation notification information acquired by the installation notification acquisition unit 241, the application ID (ApID) of the target application 10A (game A), The application user ID (ApUID) of the user X in the target application 10A (game A) and the notification type (Ttype) are associated with each other and stored in the installation information storage unit 236 as installation information. In this case, the installation information management unit 222 stores the notification type (Ttype) as “0” in the installation information storage unit 236.

  Next, the SDK 2011A reads the reward user ID from the inter-application shared area of the terminal storage unit 140 (step SA170). Then, the temporary installation notification unit 108 confirms installation of the application in the user terminal 100 (step SA173a). In an example of a specific process, the provisional installation notification unit 108 detects a target application installed in the user terminal 100 and a target application of the old version using the URL scheme. For example, it is assumed that the user terminal 100 prestores, in the inter-application shared area of the terminal storage unit 140, URL scheme information in which the URL scheme of the target application and the application ID are associated with each other. The temporary installation notification unit 108 confirms whether the URL scheme corresponding to the target application present in the URL scheme information associated with the application ID can be opened (used) using a predetermined method. If it is confirmed as open as a result of the use of the method, it is specified that the target application corresponding to the URL scheme or the target application of the previous version is installed in the user terminal 100. In other words, it is detected that the target application managed by the management server 200b being installed is mixed with the target application of the old version not managed by the management server 200b. Become. That is, the temporary installation notification unit 108 detects the detected target application and the target application of the old version as a candidate of the target application of the old version, and generates the temporary installation notification information.

  Next, the provisional installation notification unit 108 notifies the management server 200b of the result of the installation confirmation (step SA174a, REQ11C). That is, the provisional installation notification unit 108 transmits, to the management server 200b, provisional installation notification information indicating candidates for the target application of the old version detected to be installed in the user terminal 100.

Next, the temporary installation notification acquisition unit 247 of the management server 200b acquires temporary installation notification information transmitted from the temporary installation notification unit 108 (SE 113a).
The temporary installation notification information transmitted by the temporary installation notification unit 108 is a candidate for the target application of the previous version, and it is managed that the installed target application is managed by the management server 200 b and that the installed target application is installed. The target application of the old version not managed by the server 200 b is included. Therefore, the installation information management unit 222 excludes the target application of the true old version excluding the target application already stored in the installation information storage unit 236 from the temporary installation notification information acquired by the temporary installation notification acquisition unit 247. Extract. In some cases, it may not be possible to extract the true previous version of the target application. In this case, it indicates that the user terminal 100 does not have a target application of an older version that is not managed by the management server 200b.
The installation information management unit 222 uses the extracted target application of the old version as the reward user ID (Reward UID) included in the temporary installation notification information, the application ID (ApID) of the target application 10B (game C), and the user in the target application 10B. The application user ID (ApUID) of X and the notification type (Ttype) are associated with each other and stored in the installation information storage unit 236. In this case, the installation information management unit 222 sets the application user ID (ApUID) to “null” and stores the notification type (Ttype) as “1” in the installation information storage unit 236.
Further, the temporary installation notification acquiring unit 247 transmits response information indicating that the temporary installation notification information has been acquired, to the user terminal 100 (SDK 2011A) (RES11C).

The processing of the following step SA175 is the same as that of the third embodiment shown in FIG.
Further, the processes after step SA24 (note that illustration is omitted from step SE15 and after step SA25) are the process from step SA24 to step SA26 and step SE15 to step SE19 shown in FIG. 14 and the process from step SC11. The description is omitted here because it is similar.
In the present embodiment, at step SE15 and step SE16, the list notification unit 242 acquires at least one target application 10B that has not acquired either the installation notification information or the temporary installation notification information from the target application 10A (game A). Extract the application list of game C). Then, the list notification unit 242 displays data of an application list page for displaying a list LT of target applications based on the extracted application list of target applications as a list LT of target applications that recommend installation to the user in the user terminal 100. Generate Note that, when there is no target application that recommends the user to install (cannot extract the target application), the list notification unit 242 includes, in the data, information for notifying the user of that effect. It is also good.

Summary of Fourth Embodiment
As described above, in the mutual customer feed system 500a of the present embodiment, the temporary installation notification unit 108 of the user terminal 100 receives the application installed in the own user terminal 100 and the target application of the old version (a management target Detection of the previous target application, and the provisional installation notification information of the detected target application is transmitted to the management server 200b as a candidate of the target application of the old version.
As a result, the management server 200b does not transmit uninstalled information, which is a candidate of the target application of the old version, to the user terminal 100 as in the third embodiment, and among the candidates of the target application of the old version The target application of the old version not managed from can be extracted and added as a management target. Therefore, regardless of the version of the target application, the target application installed in the own user terminal 100 can be managed. Therefore, the user terminal 100 according to the present embodiment has never used the user, regardless of the version of the target application, when presenting the target application whose installation is recommended to the user, as in the third embodiment. A list LT of target applications can be presented to the user.

  In addition, if a function capable of detecting an installed application other than the URL scheme is provided, the temporary installation notification unit 108 may use the function. In addition, if the temporary installation notification unit 108 can acquire the application ID of the application, the temporary installation notification unit 108 may transmit temporary installation notification information including the application ID of the detected application to the management server 200b. Further, the temporary installation notification unit 108 transmits temporary installation notification information in which the application name of the detected application is replaced with the application ID to the management server 200b, and the management server 200b converts the application name into the application ID and registers it. You may

Fifth Embodiment
Next, a fifth embodiment of the present invention will be described.
In this embodiment, when a target application of an older version not incorporating the SDK 11 is installed (updated), a list LT of target applications excluding the target application of the previous version is presented to the user, Another embodiment different from the third and fourth embodiments will be described. That is, in the third and fourth embodiments, when the application list for presenting the target application whose installation is recommended to the management server 200a (200b) to the user is transmitted to the user terminal 100, the application list is transmitted to the user terminal 100. The target application of the previous version installed was excluded.
On the other hand, in the present embodiment, the management server 200 transmits the target application of the old version to the user terminal 100 without excluding it from the application list of the target application. Then, in the user terminal 100, the target application of the old version is excluded from the application list. Thereby, the user terminal 100 presents the user with a list LT of target applications excluding target applications of the previous version.

[Functional Configuration of User Terminal 100 (SDK 3011) According to Fifth Embodiment]
FIG. 27 is a block diagram showing an example of a functional configuration to be executed based on the SDK 3011 of the user terminal 100 according to the present embodiment.
With reference to FIG. 27, the functional configuration of mutual customer feed processing executed by the user terminal 100 (SDK 3011) in the mutual customer referral system 500a will be described.
In this figure, the SDK 3011 includes an initialization processing unit 101, a list request unit 104, a display control unit 105, a customer sending information notification unit 106, a reward provision notification unit 107, a list acquisition unit 109, and a list generation unit. And 112. The initialization processing unit 101 further includes a unique identification information acquisition unit 102 and an installation notification unit 103.

The SDK 3011 according to this embodiment differs from the third embodiment in that the temporary installation notification unit 108 and the non-installed information acquisition unit 111 are not provided, and the list generation unit 112 is provided. Further, in FIG. 27, the same components as those in FIG. 19 are denoted by the same reference numerals, and the description thereof is omitted here.
The list acquisition unit 109 according to the present embodiment is configured to transmit, from the management server 200, an application list of at least one target application for which installation notification information corresponding to the user terminal 100 is not managed in the management server 200. get. In addition, the list acquisition unit 109 acquires a URL scheme corresponding to the target application included in the application list of the target application, as well as the application list of the target application.

  The list generation unit 112 generates a list LT of target applications excluding target applications of the old version installed in the own user terminal 100 among target applications included in the application list of target applications acquired by the list acquisition unit 109. Do. Specifically, the list generation unit 112 specifies the target application of the old version installed in the user terminal 100 among the target applications included in the application list using the URL scheme acquired by the list acquisition unit 109. Do. The list generation unit 112 regenerates the application list of the target applications excluding the target application of the previous version installed in the user terminal 100 specified using the URL scheme among the target applications included in the application list.

  Further, the configuration of the management server 200 of this embodiment is the same as that of the management server 200 of the first embodiment shown in FIG. 6, and the description thereof is omitted here.

[Details of operation of mutual customer processing according to the fifth embodiment]
Next, the operation of the mutual customer sending system 500a of the present embodiment will be described.
The basic operation of the mutual customer sending system 500a of this embodiment is the same as that of the first embodiment shown in FIGS. 14 and 15, and here, with reference to FIG. 28, the object of this embodiment The operation of the mutual customer delivery system 500a will be described focusing on the process of generating an application list of applications.

  The process shown in FIG. 28 indicates the process of the target application 10A installed in the user terminal 100. Further, it is assumed that an SDK 3011A similar to the above-described SDK 3011 is incorporated in the target application 10A.

In FIG. 28, since the processing of step SA11 to step SA17, the processing of step SA23, the processing of step SE11, and the processing of step SE15 are the same as those of the first embodiment shown in FIG. Do.
In step SA24a, the list request unit 104 transmits list request notification information for requesting an application list of at least one target application of a plurality of target applications to the management server 200 (REQ12a).
In step SE16a, the list notification unit 242 of the management server 200 generates an application list of the target application, and transmits the generated application list to the user terminal 100 (RES 12a). Here, the list notification unit 242 generates an application list of at least one target application whose installation information corresponding to the user terminal 100 is not managed. The list notification unit 242 may include the URL scheme corresponding to the target application in the application list. That is, the list notification unit 242 transmits the URL scheme corresponding to the target application included in the application list together with the application list to the user terminal 100, and the list acquisition unit 109 of the user terminal 100 acquires the application list and the URL scheme. get.

Next, the list generation unit 112 of the SDK 3011A confirms installation of the target application of the old version (step SA241). Specifically, the list generation unit 112 specifies the target application of the old version installed in the user terminal 100 among the target applications using the URL scheme included in the application list acquired by the list acquisition unit 109. Do. That is, the list generation unit 112 detects the target application of the old version installed in the user terminal 100 among the target applications included in the application list.
For example, the list generation unit 112 detects the target application of the old version installed in the user terminal 100 using the URL scheme included in the application list.

  Next, the list generation unit 112 deletes the target application of the old version from the application list of the target application (step SA242). That is, the list generation unit 112 generates an application list of target applications excluding target applications of the previous version installed in the user terminal 100 detected using the URL scheme among target applications included in the application list. .

  Next, the display control unit 105 of the SDK 3011A causes the display unit 120 to display a list LT of target applications based on the application list of the target applications generated by the list generation unit 112 (step SA25a).

  Further, the process after step SA26 (note that illustration is omitted from step SE17 and after step SA26) is the same as the process from step SA26, step SE17 to step SE19, and step SC11 shown in FIG. So, the explanation is omitted here.

[Summary of the fifth embodiment]
As described above, in the mutual customer sending system 500a of the present embodiment, the user terminal 100 (an example of the terminal device) is a terminal device that can communicate with the management server 200. Here, the management server 200 is installed on the user terminal 100 based on installation notification information indicating that the target application installed on the user terminal 100 among the plurality of target applications to be managed has been installed. Manage installation information of the target application. The user terminal 100 includes an installation notification unit 103, an installation notification unit 103, a list acquisition unit 109, a list generation unit 112, and a display control unit 105. The installation notification unit 103 transmits installation notification information of the target application installed in the own user terminal 100 to the management server 200. The list acquisition unit 109 acquires, from the management server 200, an application list of at least one target application for which installation information corresponding to the user terminal 100 is not managed in the management server 200. Among the target applications included in the application list acquired by the list acquisition unit 109, the list generation unit 112 selects the target application of the old version installed in the own user terminal 100 (an example of the target application before becoming a target of management) Regenerate the application list excluding. Then, the display control unit 105 causes the display unit 120 to display a list LT of target applications based on the application list generated by the list generation unit 112.

  Thus, for example, even when the target application of the old version not incorporating the SDK 3011 is installed in the user terminal 100, the user terminal 100 of the present embodiment does not include the target application of the old version. A list LT of target applications based on the application list of can be presented to the user. That is, as in the third and fourth embodiments, the user terminal 100 can present the user with a list LT of target applications that the user has not used, regardless of the versions of the target applications.

Further, in the present embodiment, the list acquisition unit 109 acquires, together with the application list, a URL scheme corresponding to the target application included in the application list. Then, the list generation unit 112 detects a target application of the old version installed in the own user terminal 100 among the target applications included in the application list using the URL scheme acquired by the list acquisition unit 109.
Thereby, the user terminal 100 according to the present embodiment can detect the target application of the old version by, for example, a simple means of determining whether the URL scheme can be opened in the user terminal 100.

[Display example of list of target applications]
Hereinafter, with reference to FIG. 29, a display example of the list LT of target applications generated by the user terminal 100 and displayed on the display unit 120 in the mutual customer sending system 500a of the present embodiment will be described. FIG. 29 is a diagram showing a display example of a list LT of target applications according to the present embodiment.
Here, it is assumed that the target application 10A (game A) serving as a customer sending source, the target application 10B (game C) of the old version, and the target application 10F (game G) are installed in the user terminal 100. Here, when the target application 10A (game A) and the target application 10F (game G) are activated in the user terminal 100, it is assumed that installation notification information has already been transmitted to the management server 200. Therefore, the management server 200 manages installation information indicating that the target application 10A (game A) and the target application 10F (game G) are installed in the user terminal 100. The target application 10D (game E) and the target application 10E (game F) are examples of target applications not installed in the user terminal 100. That is, the management server 200 does not manage the installation information of the target application 10B (game C), the target application 10D (game E), and the target application 10E (game F) corresponding to the user terminal 100.

  29 (a), (b) and (c) show at least one of the application lists acquired by the user terminal 100 from the management server 200, in which the installation information corresponding to the user terminal 100 is not managed in the management server 200. A display example of a list LT of target applications to be generated based on the application list when information indicating a target application is included and information indicating a target application for which installation information corresponding to the user terminal 100 is managed is not included Is shown.

  First, FIG. 29A shows a display example when the user terminal 100 generates a list LT of target applications indicated by the acquired application list. Here, the target application indicated by the application list is the target application 10B (game C), the target application 10D (game E), and the target application 10E (game C) for which the installation information corresponding to the user terminal 100 is not managed in the management server 200. It is a game F). In the target application list LT shown in FIG. 29A, information (L10) indicating the target application 10B (game C), information (L20) indicating the target application 10D (game E), and the target application 10E (game Information (L30) indicating F) is displayed as information indicating a target application not installed on the user terminal 100 (that is, a candidate of a target application to be a customer sending destination). Here, although the old version of the target application 10B (game C) is installed in the user terminal 100, the management server 200 does not manage installation information of the target application 10B (game C) corresponding to the user terminal 100. Information indicating the target application 10B (game C) is also displayed on the user terminal 100 as a non-installed target application.

  FIG. 29B illustrates a display example when the user terminal 100 generates a list LT of target applications excluding the target application of the old version from the target applications indicated by the acquired application list. In the list LT of target applications shown in FIG. 29B, the target application 10B (game C) indicated by the application list, the target application 10D (game E), and the target application 10E (game F) Information (L20) indicating the target application 10D (game E) and information (L30) indicating the target application 10E (game F) except for the target application 10B (game C) for which the version is installed It is displayed as information indicating an uninstalled target application (that is, a candidate of a target application to be a customer sending destination).

FIG. 29C shows a display example when the user terminal 100 generates a list LT of target applications that can distinguish target applications of the old version among target applications indicated by the acquired application list. For example, the list generation unit 112 of the user terminal 100 can distinguish the target application of the old version installed in the user terminal 100 detected using the URL scheme among the target applications indicated by the application list. A list LT of target applications may be generated. In the list LT of target applications shown in FIG. 29C, information (L10) indicating the target application 10B (game C), information (L20) indicating the target application 10D (game E), and the target application 10E (game Information (L30) indicating F) is displayed, and information (L20) indicating target application 10D (game E) and information (L30) indicating target application 10E (game F) are displayed on the user terminal 100, respectively. Information indicating that the application is not installed (here, “not installed”) is displayed as information indicating a target application not installed on the user terminal 100 (that is, a candidate of a target application to be a customer sending destination).
Therefore, the user terminal 100 generates a list LT of target applications that can be distinguished by the user among the target applications indicated by the acquired application list, and the target applications for which the old version is installed on the user terminal 100 are presented to the user can do.
Note that information (L10) indicating the target application 10B (game C) may display information indicating that the old version is installed.

Further, the application list acquired from the management server 200 further includes information indicating at least one target application whose installation information is managed, and a target application whose installation information is not managed and installation information is managed. It may include differentiation information that can be distinguished from the application.
29 (d), (e), and (f) show at least one of the application list acquired by the user terminal 100 from the management server 200 in which the installation information corresponding to the user terminal 100 is not managed in the management server 200. Information indicating the target application of the information, information indicating the at least one target application whose installation information is managed, and distinction information capable of distinguishing between the target application whose installation information is not managed and the target application whose installation information is managed Is included, a display example of a list LT of target applications to be generated based on the application list is shown.

FIG. 29D illustrates a display example when the user terminal 100 generates a list LT of target applications excluding the target application of the old version from the target applications indicated by the acquired application list. Here, among target application 10A (game A), target application 10B (game C), target application 10D (game E), target application 10E (game F), and target application 10F (game G) indicated by the application list. , The target application 10B (game C) in which the old version is installed is removed. Therefore, in the list LT of target applications shown in FIG. 29D, information (L20) indicating target applications 10D (game E), information (L30) indicating target applications 10E (game F), and target applications 10A ( Information (L40) indicating the game A) and information (L50) indicating the target application 10F (game G) are displayed. Further, information (L40) indicating the target application 10A (game A) and information (L50) indicating the target application 10F (game G) respectively indicate information installed in the user terminal 100 (here, "Installed" is displayed. That is, the information (L20) indicating the target application 10D (game E) and the information (L30) indicating the target application 10E (game F) are the target applications not installed in the user terminal 100 (that is, the target applications serving as customer destinations). It shows that it is the information which shows the candidate of. Here, the user terminal 100 generates information (here, “installed”) indicating that the user terminal 100 is installed on the basis of the distinction information included in the application list.
Thus, among the target applications indicated by the acquired application list, the user terminal 100 displays a list LT of target applications in which target applications whose installation information is managed can be distinguished from target applications whose installation information is not managed at least. Can be generated and presented to the user.

FIG. 29E illustrates a display example when the user terminal 100 generates a list LT of target applications without removing the target application of the old version from the target applications indicated by the acquired application list. In the target application list LT shown in FIG. 29 (e), information (L10) indicating the target application 10B (game C) is further displayed on the application list LT shown in FIG. 29 (d). It is different. Also, in the information (L10) indicating the target application 10B (game C), information indicating that the old version of the target application 10B (game C) is installed (here, “old version installed”) Is displayed.
Thus, among the target applications indicated by the acquired application list, the user terminal 100 displays a list LT of target applications in which target applications whose installation information is managed can be distinguished from target applications whose installation information is not managed at least. Can be generated and presented to the user. In addition, the user terminal 100 can present the user with a list LT of target applications so that the user can distinguish among target applications in which the old version installed in the user terminal 100 is installed.

In the list LT of target applications shown in FIG. 29E, it is not necessary to display information that can distinguish the target applications for which the old version is installed. For example, as shown in FIG. 29F, in the information (L10) indicating the target application 10B (game C), information (here, “installed”) indicating that the application is installed in the user terminal 100 is displayed It may be done.
Thus, among the target applications indicated by the acquired application list, the user terminal 100 displays a list LT of target applications in which target applications whose installation information is managed can be distinguished from target applications whose installation information is not managed at least. Can be generated and presented to the user.

  In the list LT of target applications shown in FIGS. 29 (d), (e), and (f), information indicating target applications installed in the user terminal 100 indicates that the user terminal 100 is installed. Instead of or in addition to displaying information (in this case, “installed”), information indicating a target application that is not installed on the user terminal 100 indicates information that is not installed on the user terminal 100 (for example, "Not installed" may be displayed.

Sixth Embodiment
Next, a sixth embodiment of the present invention will be described. In the third, fourth, and fifth embodiments, when the target application of the previous version in which the SDK 11 is not incorporated is installed in the user terminal 100, the target application of the installed previous version is excluded. The form which presents the list LT of object application to a user was explained. In the present embodiment, when there is a target application that has not been started among the target applications installed in the user terminal 100, a mode is presented to present to the user a list LT of target applications excluding the target application that has not been started explain.

  For example, even if the target application is downloaded from the store site and installed in the user terminal 100, the target application can not transmit installation notification information to the management server 200 unless it is activated (unexecuted). . Therefore, as in the case of the target application of the old version, the management server 200 recognizes that the target application which has not been started up is not installed in the user terminal 100. Therefore, for example, when presenting a target application that recommends installation to the user, the target application list to be presented to the user includes a target application that has been installed in the user terminal 100 but has not been started. There is.

  Therefore, in the present embodiment, among the target applications installed in the user terminal 100 using the same processing as in the case of excluding the target application of the old version described in the third, fourth, and fifth embodiments. A form will be described in which a list LT of target applications excluding target applications that have not been started is presented to the user.

[Overview of Mutual Customer Service System According to Sixth Embodiment]
FIG. 30 is an explanatory diagram for explaining the outline of the mutual customer delivery system 500a of this embodiment.
A network system 1a shown in FIG. 30 includes a management server 200a and a user terminal 100, as in the configuration shown in FIG. Here, in place of the target application 10B of the old version (for example, game C), the target application 10C (for example, game D) including the SDK 1011 corresponding to the mutual customer sending system 500a is installed in the user terminal 100. Is different from the configuration shown in FIG. In FIG. 30, parts corresponding to those in FIG. 18 are denoted by the same reference numerals.
The outline of the mutual customer delivery system 500a of this embodiment will be described with reference to FIG.

(1) When the target application 10A is installed in the user terminal 100 and started by the user X for the first time, the SDK 1011 incorporated in the target application 10A is an installation notification indicating that the target application 10A is installed in the user terminal 100 Send information (game A). Thus, the management server 200a manages installation information indicating that the target application 10A has been installed on the user terminal 100, based on the installation notification information acquired from the SDK 1011.

  On the other hand, since the target application 10C has been installed in the user terminal 100 but has never been started, the SDK 1011 incorporated in the target application 10C has not transmitted installation notification information to the management server 200. That is, since the management server 200 a has not acquired installation notification information indicating that the target application 10 C has been installed in the user terminal 100, the management server 200 a recognizes that the target application 10 C is not installed in the user terminal 100. .

(2) The SDK 1011 of the target application 10A acquires, from the management server 200a, non-installed information indicating a target application for which the management server 200a has not acquired installation notification information from the user terminal 100. The target application 10A corresponds to a customer sending source application having the same function as the customer sending source application 10 in the first and second embodiments.

(3) Of the target applications indicated by the uninstalled information acquired from the management server 200a, the target application (for example, the target application 10C) that has been installed in the user terminal 100 but has never been started is the SDK 1011 of the target application 10A. It detects whether or not it is installed in the user terminal 100 (installation detection). That is, it can be said that the non-installed information indicates a candidate of “target application which has been installed in the user terminal 100 but has not been activated” to be detected in the user terminal 100. The SDK 1011 detects, for example, whether or not the “target application installed in the user terminal 100 but has not been activated” is installed in the user terminal 100 using the URL scheme. Here, the SDK 1011 detects that the target application 10C is installed in the user terminal 100 as “target application installed in the user terminal 100 but has never been started” among target applications indicated by the non-installed information. Do.

(4) The SDK 1011 of the target application 10A transmits installation notification information indicating that the target application 10C (game D) is installed to the management server 200a. Thus, the management server 200a manages installation information indicating that the target application 10C is installed on the user terminal 100, based on the installation notification information (game D) acquired from the SDK 1011. Note that the management server 200a may manage the application including whether or not the target application installed in the user terminal 100 has been activated.

(5) The management server 200a transmits, to the user terminal 100, an application list (not including the game D) excluding the target application 10C when presenting the target application for which the user is recommended to install.
That is, among the plurality of target applications managed by the management server 200a, the installation information of the target application installed and started in the user terminal 100 and the target application installed in the user terminal 100 but not started yet Create an application list of at least one target application that does not manage any of the installation information of.
Then, the management server 200a transmits the generated application list to the user terminal 100. The user terminal 100 displays, on the display unit 120, a list LT of target applications excluding the target application 10C as target applications for which the user is recommended to install based on the above-described application list transmitted from the management server 200a.

  Thus, even if there is a target application that has been installed in the user terminal 100 but has not been activated, the mutual customer support system 500a according to the present embodiment excludes the object application that has not been activated. A list LT of target applications can be displayed on the display unit 120 and presented to the user.

  Note that “target application installed in the user terminal 100 but never started” and “target of the old version installed in the user terminal 100” described in the third, fourth, and fifth embodiments. “Application” is a target application that is different in the reason for not transmitting the installation notification information to the management server 200a, but is an object application that is not installed in the user terminal 100 but has not transmitted the installation notification information. There is no difference. Therefore, the target application installed in the user terminal 100 but not started and the target application of the old version are both included in the target application indicated by the uninstalled information. Then, among the target applications indicated by the non-installed information, the processing for detecting a target application that has been installed in the user terminal 100 but has never been started is the same as the processing for detecting a target application of the previous version For example, it can be processing to detect using a URL scheme.

  Therefore, also in the present embodiment, when the target application of the old version is installed in the user terminal 100, the target application of the old version can be excluded from the uninstalled information. Also, when the target application of the old version is installed in the user terminal 100 and there is also a target application installed in the user terminal 100 but has not been started, among the uninstalled information, the old version Both target applications and target applications that have not been started can be excluded.

Next, the configuration and processing of the present embodiment will be described in detail.
The configurations and processes of this embodiment can be applied to the configurations and processes described in the third, fourth, and fifth embodiments.
Hereinafter, configurations and processes of the present embodiment to which the configurations and processes described in the third, fourth, and fifth embodiments are applied will be described as first to third examples.

First Example of Configuration and Processing of Sixth Embodiment
For example, the configuration and processing of the third embodiment described with reference to FIGS. 19 to 23 can be applied as the configuration and processing of the present embodiment.

  The functional configuration shown in FIG. 19 may be applied as the functional configuration to be executed based on the SDK 1011 of the user terminal 100 of the present embodiment. The SDK 1011 includes an initialization processing unit 101, a list request unit 104, a display control unit 105, a customer referral information notification unit 106, a reward provision notification unit 107, a temporary installation notification unit 108, and a list acquisition unit 109. An uninstalled information acquisition unit 111 is provided. In the present embodiment, in the functional configuration of the SDK 1011 shown in FIG. 19, the temporary installation notification unit 108 detects a target application that has been installed in the user terminal 100 but has never been started. Then, the temporary installation notification unit 108 transmits temporary installation notification information indicating that the detected target application has been installed in the user terminal 100 to the management server 200a.

  Specifically, when the provisional installation notification unit 108 detects a target application installed in the user terminal 100 but has not been activated, for example, the provisional installation notification unit 108 is not installed, as in the process of detecting a target application of the old version. It detects using the URL scheme which the information acquisition part 111 acquired.

When the information indicating the target application installed in the user terminal 100 can be acquired by the function of the OS without using the URL scheme, the temporary installation notification unit 108 displays the information indicating the installed target application. Among the target applications indicated by the non-installed information acquired by the non-installed information acquisition unit 111, the target application that has been installed in the user terminal 100 but has not been activated may be detected by using
Also, unlike the target application of the previous version, the target application which has not been started up incorporates the SDK 1011. Therefore, the SDK 1011 has a function of detecting target applications installed in the user terminal 100, and the user terminal 100 is selected from among target applications indicated by the non-installed information acquired by the non-installed information acquisition unit 111. It may also detect target applications that have been installed but have not been launched.

  Further, in the present embodiment, in the configuration of the management server 200a shown in FIG. 20, when there is a target application that has been installed in the user terminal 100 but has not been activated, the provisional installation notification acquisition unit 247 is activated. The temporary installation notification information indicating that the target application having no is installed in the user terminal 100 is acquired from the target application 10A. For example, among the target applications indicated by the non-installation information transmitted by the non-installation information notification unit 248, the temporary installation notification acquisition unit 247 performs temporary installation notification of a target application that has been installed in the user terminal 100 but has never been activated. Information is acquired from the target application 10A. Then, the temporary installation notification acquisition unit 247 supplies the acquired temporary installation notification information to the installation information management unit 222.

  The installation information management unit 222 uses the installation information storage unit 236 to install installation information of a target application that has been installed in the user terminal 100 but has not been activated, based on the temporary installation notification information acquired by the temporary installation notification acquisition unit 247. Remember. The installation information stored in the installation information storage unit 236 is, for example, the installation information stored based on the provisional installation notification information as in the installation information of the target application of the old version shown in FIG. Ttype) is stored as "1". It should be noted that the notification type (Ttype) of the target application installed in this user terminal 100 but not started up can be distinguished from the target application of the previous version, notification types other than “0” and “1” (For example, "2") may be used.

Further, as the process according to the present embodiment, for example, the process shown in FIG. 23 may be applied.
For example, in the process of step SA173, the temporary installation notification unit 108 of the SDK 1011A of the target application 10A uses the URL scheme included in the non-installed information acquired by the non-installed information acquisition unit 111, among the uninstalled target applications A target application installed in the user terminal 100 but not started has been detected. Then, the temporary installation notification unit 108 notifies the management server 200a of the result of the installation confirmation (step SA174). That is, the provisional installation notification unit 108 indicates provisional installation notification information indicating a target application that has been installed in the user terminal 100 but has not been activated and is similar to provisional installation notification information indicating a target application of the old version. It transmits to the management server 200a. When there is no target application that has not been started up in the user terminal 100, information indicating that there is no target application that has not been started up may be notified as temporary installation notification information. .

  Thereby, the management server 200a can manage the installation information of the target application installed in the user terminal 100 but not started (step SE113a).

The processing in step SA24 and subsequent steps (note that illustration is omitted in step SE15 and subsequent steps SA25 and subsequent steps) is performed from step SA24 to step SA26 and step SE15 shown in FIG. 14 as described with reference to FIG. Since the process is the same as the process of SE19 and the process of step SC11, the description is omitted here.
For example, in step SE15 and step SE16, the list notification unit 242 of the management server 200a selects at least one target application for which installation information corresponding to the user terminal 100 is not managed in the installation information management unit 222 among a plurality of target applications. Extract an application list including information indicating. Then, the list notification unit 242 generates data of an application list page for displaying, on the user terminal 100, a list LT of target applications based on the extracted application list of target applications. When the list notification unit 242 can not also extract one target application, the list notification unit 242 may include, in the data, information for notifying the user of that. The application list of the target application is transmitted to the user terminal 100, and the SDK 1011A of the target application 10A generates data for displaying the list LT of the target applications on the user terminal 100 based on the acquired application list. May be

  Thus, the management server 200a can transmit, to the user terminal 100, an application list of target applications excluding target applications that have been installed in the user terminal 100 but have not been activated. Therefore, the user terminal 100 can present the user with a list LT of target applications excluding target applications installed in the user terminal 100 but not started.

  Note that among the target applications installed in the user terminal 100, any of the target application of the old version and the target application that has not been started may be similarly detected and excluded from the application list.

Second Example of Configuration and Processing of Sixth Embodiment
As the configuration and processing of the present embodiment, for example, the configuration and processing of the fourth embodiment described with reference to FIGS. 24 to 26 may be applied.

For example, in the configuration of the mutual customer feed system 500a of the present embodiment, the functional configuration executed based on the SDK 2011 of the user terminal 100 shown in FIG. 24 and the configuration of the management server 200b shown in FIG. 25 may be applied.
The SDK 2011 is different from the configuration of the SDK 1011 shown in FIG. 19 described in the first example described above in that the SDK 2011 does not include the uninstalled information acquisition unit 111. The management server 200b is different from the configuration of the management server 200a shown in FIG. 20 described in the first example in that the management server 200b does not include the uninstalled information notification unit 248.

  That is, the user terminal 100 does not acquire uninstalled information from the management server 200 b, but regards all the target applications installed in the user terminal 100 as candidates for target applications that have never been started, The provisional installation notification information of the target application having no may be transmitted to the management server 200b. At this time, the target application 10A may be excluded. Then, in the management server 200b, in comparison with the information managed by the installation information management unit 222, the target application that is not managed by the installation information management unit 222 may be identified as a target application that has never been started.

Further, the process shown in FIG. 26 may be applied as the process according to the present embodiment.
For example, in step SA173a, the temporary installation notification unit 108 of the SDK 2011A of the target application 10A may detect the target application installed in the user terminal 100 using the URL scheme. Here, the provisional installation notification unit 108 may detect a target application that has been started among the target applications installed in the user terminal 100 and may also detect a target application that has not been started. Then, in step SA174a, the temporary installation notification unit 108 may transmit temporary installation notification information indicating the detected target application to the management server 200b.

Thus, as in the first example described above, the management server 200a can manage installation information of a target application that has been installed in the user terminal 100 but has never been started. Also, the management server 200a can transmit, to the user terminal 100, an application list of target applications excluding target applications installed in the user terminal 100 but not started. Therefore, the user terminal 100 can present the user with a list LT of target applications excluding target applications installed in the user terminal 100 but not started.
Also in this second example, among the target applications installed in the user terminal 100, even if both the target application of the old version and the target application that has not been started are similarly detected and excluded from the application list Good.

Third Example of Configuration and Processing of Sixth Embodiment
As the configuration and processing of the present embodiment, for example, the configuration and processing of the fifth embodiment described with reference to FIGS. 27 and 28 may be applied.

  For example, in the configuration of the mutual customer feed system 500a of the present embodiment, a functional configuration to be executed based on the SDK 3011 of the user terminal 100 shown in FIG. 27 may be applied. The SDK 3011 does not include the temporary installation notification unit 108 and the non-installed information acquisition unit 111, and the configuration of the SDK 1011 illustrated in FIG. 19 described in the first example described above in that the list generation unit 112 is included. It is different. In the present embodiment, the list generation unit 112 excludes target applications that have been installed in the user terminal 100 but have not been activated, among target applications included in the application list of target applications acquired by the list acquisition unit 109. An application list may be generated.

  That is, in the present embodiment, the management server 200 may transmit the target application installed in the user terminal 100 but not started up to the user terminal 100 without excluding it from the application list of the target application. Then, the user terminal 100 generates (regenerates) an application list in which target applications installed in the user terminal 100 but not started have been excluded from the application list acquired from the management server 200. A list LT of target applications based on the list may be presented to the user.

Further, the process shown in FIG. 28 may be applied as the process according to the present embodiment.
For example, in step SA241, the list generation unit 112 of the SDK 3011A of the target application 10A may check a target application that has been installed in the user terminal 100 but has not been activated. Specifically, the list generation unit 112 uses the URL scheme included in the application list acquired by the list acquisition unit 109, and among the target applications, a target that has been installed in the user terminal 100 but has never been activated. The application may be identified. That is, the list generation unit 112 may detect, among the target applications included in the application list, a target application that has been installed in the user terminal 100 but has not been activated.

  Then, in step SA242, the list generation unit 112 may delete, from the application list of the target application, a target application that has been installed in the user terminal 100 but has not been activated. That is, among the target applications included in the application list, the list generation unit 112 detects an application of a target application that is detected using a URL scheme and is excluding the target application that has been installed in the user terminal 100 but has not been activated. The list may be regenerated.

  Further, in step SA25a, the display control unit 105 of the SDK 3011A may display the list LT of target applications on the display unit 120 based on the application list of target applications generated by the list generation unit 112.

Thereby, the user terminal 100 can present the user with a list LT of target applications excluding target applications installed in the user terminal 100 but not started.
Also in this third example, among the target applications installed in the user terminal 100, even if both the target application of the old version and the target application that has not been started are similarly detected and excluded from the application list Good.

  The display example shown in FIG. 29 may be applied as a display example of the list LT of target applications in the present embodiment. For example, in the display example of the list LT of target applications shown in FIG. 29, the “target applications of the old version” can be applied similarly by being “target applications that have been installed but have not been started”. .

[For the third to sixth embodiments]
The third to sixth embodiments described above can be described as follows, but are not limited to the following description.

(1) In the mutual customer delivery system 500a, the management server 200a (an example of a management device) includes an application management unit 221, an installation notification acquisition unit 241 (an example of a first information acquisition unit), and a temporary installation notification acquisition unit 247 (an example). An example of a third information acquisition unit), an installation information management unit 222, and a list notification unit 242 (an example of a second information notification unit).
The application management unit 221 manages information on a plurality of target applications to be managed. The installation notification acquisition unit 241 receives installation notification information (first information) transmitted from the user terminal 100 in response to execution of the target application 10A (an example of the first application) of the plurality of target applications by the user terminal 100. An example of) is acquired. The provisional installation notification acquiring unit 247 transmits, from the target application 10A, another application (for example, a target application 10B of an old version or a target application 10C) which is a target application other than the target application 10A among the plurality of target applications to the user terminal 100. The provisional installation notification information (an example of the third information) indicating that the software is installed is acquired. The installation information management unit 222 (an example of the installation information management unit) performs any of the operations on the user terminal 100 based on the installation notification information acquired by the installation notification acquisition unit 241 and the temporary installation notification information acquired by the temporary installation notification acquisition unit 247. Manage installation information indicating whether the target application has been installed. Then, the list notification unit 242 determines at least one of the plurality of target applications in which the installation information corresponding to the user terminal 100 is not managed by the installation information management unit 222 based on the installation information managed by the installation information management unit 222. An application list (second information) including information indicating a target application of is transmitted to the user terminal 100. Here, the installation information corresponding to the user terminal 100 refers to, for example, installation notification information transmitted from the user terminal 100 in response to the target application being executed by the user terminal 100.

  The management server 200a (an example of a management apparatus) includes at least an application management unit 221, an installation notification acquisition unit 241 (an example of a first information acquisition unit), and a temporary installation notification acquisition unit 247 (a third information acquisition unit). An example) and a list notification unit 242 (an example of a second information notification unit) may be provided. Then, the list notification unit 242 indicates information indicating at least one target application for which neither installation notification information (an example of the first information) nor provisional installation notification information (an example of the third information) has been acquired from the user terminal 100. The included application list (second information) may be transmitted to the user terminal 100.

  Thus, when the management server 200 a according to the present embodiment transmits to the user terminal 100 an application list indicating target applications for which the installation notification information corresponding to the user terminal 100 has not been acquired, the management server 200 a has not acquired the installation notification information. An application list of target applications excluding the target application installed in the user terminal 100 among the target applications can be transmitted to the user terminal 100. Therefore, according to the present embodiment, it is possible to present a list LT of appropriate target applications for which the user is recommended to install.

(2) Here, a plurality of target applications are provided so as to be installable in the user terminal 100 before being managed by the application management unit 221 of the management server 200a, and old after being provided by the management. Contains the target application of the version.
Then, other applications that are target applications installed in the user terminal 100 other than the target application 10A are installed in the user terminal 100 before being managed by the application management unit 221 among multiple target applications, for example. The target application may be an older version.
The target application (an example of another application) of this old version is a target application installed in the user terminal 100 among the plurality of target applications, and transmits installation notification information (an example of the first information) to the management server 200 Target application that does not have the The function of transmitting the installation notification information to the management server 200 is, for example, a function of the SDK 1011 (2011, 3011). That is, the target application of this old version is, for example, one in which the SDK 1011 (2011, 3011) is not incorporated.

  Thus, for example, even if the target application of the old version not incorporating the SDK 1011 is installed in the user terminal 100, the management server 200a of the present embodiment excludes the target application excluding the target application of the old version. Can be transmitted to the user terminal 100. Therefore, according to the present embodiment, it is possible to present the user with a list LT of target applications that have not been used by the user. That is, according to the present embodiment, it is possible to present a list LT of appropriate target applications for which the user is recommended to install.

(3) The above-mentioned other application is a target application installed in the user terminal 100 among a plurality of target applications, and the user terminal 100 transmits installation notification information (an example of the first information) to the management server 200a. The target application that has not been transmitted, that is, the target application that the installation notification acquisition unit 241 (an example of the first information acquisition unit) of the management server 200 a has not acquired may be used.

  Thus, for example, even if there is a target application that has been installed in the user terminal 100 but has not started, the management server 200a of the present embodiment is a target that has been installed but has not started. An application list of target applications excluding the application can be transmitted to the user terminal 100. Therefore, according to the present embodiment, the list LT of target applications excluding the installed target applications can be presented to the user. That is, according to the present embodiment, it is possible to present a list LT of appropriate target applications for which the user is recommended to install.

(4) Further, the management server 200a is not installed information indicating a target application of which installation information (an example of the first information) corresponding to the user terminal 100 is not managed in the installation information management unit 222 among a plurality of target applications. An uninstalled information notification unit 248 (an example of a fourth information notification unit) that transmits (an example of the fourth information) to the user terminal 100 is provided. It can be said that the non-installed information indicates a candidate of a target application of the old version to be detected in the user terminal 100 or a candidate of a target application that has been installed but has not been started.
Then, the temporary installation notification acquiring unit 247 (an example of the third information acquiring unit) is one of the other applications described above installed in the user terminal 100 among the target applications indicated by the uninstalled information transmitted by the uninstalled information notification unit 248. The provisional installation notification information (an example of the third information) indicating the application is acquired from the target application 10A (an example of the first application).

  Note that the installation notification acquisition unit 241 (an example of a first information acquisition unit) of the plurality of target applications in the non-installed information notification unit 248 receives the installation notification information (a first example) from the target application 10A (an example of the first application). The non-installed information (an example of the fourth information) indicating the target application for which an example of the information is not acquired may be transmitted to the user terminal 100.

  Further, the non-installed information notification unit 248 transmits, to the user terminal 100, non-installed information indicating a target application for which the installation notification information and the temporary installation notification information have not been acquired from the target application 10A among the plurality of target applications. It may be sent.

As a result, the management server 200 a notifies the candidate of the target application of the old version to be detected in the user terminal 100 or the candidate of the target application that has been installed but has not started up as uninstalled information. A target to be detected as a target application of the previous version or a target application that has been installed but has not started can be identified in 100. As a result, compared with the case of extracting from all target applications, it is possible to reduce the processing amount of extraction of the target application of the old version or the target application that has been installed but has not started. In addition, the target application 10A shortens the processing time for extracting the target application of this old version or a target application that has been installed but has not started up as compared with the case of extracting from all the target applications. Can.
In addition, the management server 200 a according to the present embodiment can manage a target application of the old version installed in the user terminal 100 or a target application that has been installed but has not been started. As a result, the management server 200 a according to the present embodiment can use the application list of the target application excluding the target application of the old version installed in the user terminal 100 or the target application installed but not started. It can be sent to 100. As a result, when presenting a target application for which installation is recommended to the user, a list LT of target applications excluding the target application of the previous version or the target application which has been installed but has not started up It can be presented to the user.

(5) Further, the non-installed information notification unit 248 (an example of the fourth information notification unit) of the management server 200a manages the information on the plurality of target applications managed by the application management unit 221 and the installation information management unit 222. The non-installed information (an example of the fourth information) is transmitted to the user terminal 100 based on the installation information. Here, the non-installed information indicates a target application of which installation information corresponding to the user terminal 100 is not managed in the installation information management unit 222 among a plurality of target applications.

  Thus, the non-installed information notification unit 248 refers to information managed by the application management unit 221 that manages information on a plurality of target applications to be managed, and extracts all the target applications and the installation information management unit 222. The target application for which the installation information corresponding to the user terminal 100 is not managed is indicated by comparing the target application for which the installation information corresponding to the user terminal 100 is managed with reference to the installation information to be managed. It becomes possible to identify non-installed information. It can be said that this non-installed information indicates a candidate of a target application of the old version to be detected in the user terminal 100 or a target application that has been installed but has not been started.

  It should be noted that the management server 200a is a target application (a game of a previous version different from the game C) or a target application (a game that has been installed but has never been started) from the target application 10A (an example of the first application). When the temporary installation notification information for the target application (different from D) is acquired, the installation information management unit 222 installs the target application that has transmitted the installation notification information or the temporary installation notification information, and the target application. The user terminal 100 may be managed in association with each other. Then, the non-installed information notification unit 248 sends, to the target application 10A, non-installed information indicating a target application that has not acquired any of installation notification information and provisional installation notification information from the target application 10A among the plurality of target applications. May be transmitted.

(6) Further, in the mutual customer sending system 500a, the user terminal 100 (an example of a terminal device) is a terminal device capable of communicating with the management server 200a. Here, the management server 200 a uses the target application installed in the user terminal 100 among the plurality of target applications to be managed, installation notification information indicating that the target application is installed in the user terminal 100 (the first Based on an example of information) and temporary installation notification information (an example of other installation notification information, an example of third information) indicating that another application that is a target application other than the target application is installed in the user terminal 100 , And manages installation information indicating which target application has been installed on the user terminal 100.
The user terminal 100 includes an installation notification unit 103, a temporary installation notification unit 108 (an example of another installation notification unit), a list acquisition unit 109 (an example of an acquisition unit), and a display control unit 105. The installation notification unit 103 transmits installation notification information of the target application installed in the user terminal 100 (an example of the own terminal device) to the management server 200a. The temporary installation notification unit 108 detects another application installed in the user terminal 100, and transmits the detected other application installation notification information (for example, temporary installation notification information) to the management server 200a. Here, the other application includes any of the target application of the previous version installed in the user terminal 100 or the target application that has been installed but has not been started. Further, the other installation notification information includes both temporary installation notification information of the target application of the old version and temporary installation notification information of the target application that has been installed but has never been started. Then, the list acquisition unit 109 is an application list including information indicating at least one target application whose installation information corresponding to the user terminal 100 is not managed in the management server 200a (an example of application notification information, an example of second information). Are acquired from the management server 200a. Then, the display control unit 105 causes the display unit 120 to display a list LT of target applications (an example of display information) based on the application list acquired by the list acquisition unit 109.

  In addition, the list acquisition unit 109 manages an application list including information indicating at least one target application that is not transmitted from the user terminal 100 in both of the installation notification information and the temporary installation notification information (an example of the other installation notification information). It can be understood as what is acquired from 200a.

  Thus, for example, when the target application of the old version is installed in the user terminal 100, or when there is a target application installed in the user terminal 100 but has not been activated, the user terminal 100 of the present embodiment. The application list of the target application excluding the target application of the previous version or the target application which has not been started can be acquired, and the list LT of the target applications based on the acquired application list can be presented to the user. Therefore, the user terminal 100 of the present embodiment can transmit, to the user terminal 100, an application list of target applications that are not installed in the user terminal 100 regardless of the version of the target application. As a result, when presenting a target application that recommends installation to the user, a list LT of target applications not installed in the user terminal 100 can be presented to the user in the user terminal 100. That is, according to the present embodiment, it is possible to present a list LT of appropriate target applications for which the user is recommended to install.

(7) Further, the user terminal 100 has not acquired, from the management server 200a, non-installed information indicating target applications for which installation information corresponding to the user terminal 100 (an example of the own terminal device) is not managed in the management server 200a. An installation information acquisition unit 111 is provided.
Then, the temporary installation notification unit 108 selects one of the target applications indicated in the non-installed information acquired by the non-installed information acquisition unit 111, for example, another application installed in the user terminal 100 (for example, However, it transmits provisional installation notification information of the target application (which has not been started) to the management server 200a.

  In addition, the user terminal 100 is not installed information which acquires not installed information which shows the target application which has not transmitted installation notification information from the user terminal 100 (an example of an own terminal apparatus) among several target applications from the management server 200a. The acquisition unit 111 may be provided.

  In addition, the non-installed information acquisition unit 111 is non-installed information indicating a target application that has not been transmitted from the user terminal 100 in the installation notification information and the temporary installation notification information (an example of other installation notification information) among a plurality of target applications. May be acquired from the management server 200a.

  Thereby, the target application 10A of the user terminal 100, for example, among the acquired non-installed information, the target application of the old version installed in the user terminal 100 or the target application which has been installed but has not been started Since the extraction is performed, it is possible to reduce the processing amount of extraction of the target application of the old version or the target application that has been installed but has not started up, as compared to the case of extraction from all the target applications. In addition, the user terminal 100 according to the present embodiment is compared with the case where the processing time for extracting the target application of the old version or the target application that has been installed but has not started up is extracted from all target applications. Can be shortened.

(8) The provisional installation notification unit 108 (an example of the other installation notification unit) uses the function of the user terminal 100 (an example of the own terminal device) to set the user terminal 100 among the target applications indicated in the non-installed information. Detect other applications installed in (for example, target application of previous version or target application that has been installed but has not started).

  Here, the function included in the user terminal 100 is, for example, a function of the OS of the user terminal 100, and detects a target application installed in the user terminal 100 using a URL scheme corresponding to the target application. It is a function. For example, the non-installed information acquisition unit 111 acquires, from the management server 200a, the URL scheme corresponding to the target application indicated in the non-installed information, which is included in the non-installed information. Then, the temporary installation notification unit 108 is installed on the user terminal 100 among the target applications indicated in the non-installation information using the URL scheme acquired by the non-installation information acquisition unit 111 by the function of the OS of the user terminal 100. Detect other applications that are

  Thus, the user terminal 100 can use, for example, another application (for example, a target application of the old version) installed in the user terminal 100 by a simple means of determining whether or not the URL scheme can be opened in the user terminal 100. Or, it is possible to detect a target application that has been installed but has not been started.

  The function of the user terminal 100 is not limited to the function of detecting a target application installed in the user terminal 100 using a URL scheme. For example, when the OS can acquire information indicating a target application installed in the user terminal 100 without using the URL scheme, the temporary installation notification unit 108 acquires information indicating the installed target application. Accordingly, among the target applications indicated by the uninstalled information acquired by the uninstalled information acquisition unit 111, another application installed in the user terminal 100 may be detected.

(9) Further, the temporary installation notification unit 108 (an example of the other installation notification unit) of the user terminal 100 does not acquire the non-installed information from the management server 200 b, but does not acquire the temporary installation notification information (an example of the other installation notification information). You may transmit to the management server 200b.
For example, the temporary installation notification unit 108 includes a target application installed in the user terminal 100 (an example of the own terminal device) and a target application of the old version (a target application installed in the own terminal device before being a management target). An example is detected. Then, the temporary installation notification unit 108 sets the temporary installation notification information of the detected target application as a candidate of another application (for example, a target application of the old version or a target application that has been installed but has never been started). Send to

  Thus, as in the third embodiment, for example, the management server 200b does not have installed information that becomes a candidate for a target application of an old version or a target application that has been installed but has not been activated for the user terminal 100. It is possible to extract the target application of the old version or the target application that has been installed but has not started up from among the applications installed in the user terminal 100 without transmission, and can be added as a management target.

(10) The application management unit 221 of the management server 200a (200b) prohibits the setting application that sets the prohibition of the publication based on the application list (an example of the second information) and the publication based on the application list of the setting application It manages inter-application filter information (an example of first posting prohibition information) in which the target application to be set is associated. Then, the list notification unit 242 (an example of the second information notification unit) of the management server 200a (200b) refers to the inter-application filter information managed by the application management unit 221, and the target application 10A (of the first application). When there is inter-application filter information in which the setting side application is set as an example), the remaining information excluding the information indicating the setting side application from the application list is transmitted to the user terminal 100.

  Further, the list notification unit 242 (an example of the second information notification unit) refers to the inter-application filter information (an example of the first posting prohibition information) managed by the application management unit 221, When there is inter-application filter information in which an application (an example of 1 application) is set as the setting side application, the remaining information obtained by removing the information indicating the set side application from the application list is transmitted to the user terminal 100 May be

  As a result, in the mutual customer delivery system 500a, when presenting a target application for which installation is recommended to the user, it is possible to set, in the management server 200a, the relationship between the target applications that the user does not want to recommend. For example, if there is a rating (age limitation) set in the target application, the target application 10A in which the rating is not set can not recommend the target application in which the rating is set. .

(11) Further, the management server 200a (200b) may include the reward processing unit 245. Then, the reward processing unit 245 determines the customer destination application 20 (one example of the second application) described in the first embodiment among the one or more target applications indicated by the application list (one example of the second information). A reward giving process may be performed in which a reward is given to the user who uses the user terminal 100 when the condition for giving a reward is satisfied. Here, the customer destination application 20 described in the first embodiment is, for example, a target application selected by the user terminal 100 from among one or a plurality of target applications indicated by the application list (an example of the second information). is there.

  In this way, in the mutual customer sending system 500a that rewards the target application of the customer sending source when the target application of the customer sending destination that has not been used by the user is installed, the target application that recommends installation for the user is presented. In this case, an application list excluding the target application of the previous version or the target application that has been installed but has not started can be transmitted to the user terminal 100.

(12) Further, the management server 200 a (200 b) acquires the customer information acquisition unit 243 that acquires customer information indicating the customer to the customer destination application 20 (an example of the second application) described in the first embodiment. And the customer information management unit 223 that manages the customer information acquired by the customer information acquisition unit 243. Here, for example, the customer-sending information acquisition unit 243 may acquire customer-sending information for the customer-sending destination application 20 from the target application 10A. Then, when the predetermined reward giving condition set in the customer sending destination application 20 is satisfied, the reward processing unit 245 manages the customer sending information corresponding to the customer sending destination application 20 by the customer sending information management unit 223. Reward grant processing may be performed on the condition that
As a result, when the target application is installed without using the present system, the mutual customer delivery system 500a can be prevented from being a target for awarding rewards because there is no record of customer delivery information.

  Here, the case where the predetermined reward giving condition is satisfied means the case where the customer destination application 20 (an example of the second application) is executed by the user terminal 100 or becomes executable. It is also good. When the predetermined reward giving condition is satisfied, the customer destination application 20 is executed or executable by the user terminal 100, and the predetermined outcome is achieved in the customer destination application 20. It may be the case of Thus, the mutual customer delivery system 500a can arbitrarily set the reward giving condition.

  In addition, the application management unit 221 of the management server 200a (200b) may manage information regarding a predetermined period set for a plurality of specific applications among a plurality of target applications. In this case, when the predetermined reward giving condition is satisfied, the customer destination application 20 (an example of the second application) is a specific application, and the customer destination application 20 is selected by the user terminal 100 within a predetermined period. It may be the case where it has been executed or becomes feasible. When the predetermined reward giving condition is satisfied, the customer sending destination application 20 is a specific application, and the customer sending destination application 20 is executed or executable by the user terminal 100 within a predetermined period. And may be a case where a predetermined result is achieved in the customer destination application 20. In this way, among the plurality of target applications, only a specific application that is performing a campaign can be targeted for rewarding.

(13) Further, the user terminal 100 includes the reward assignment notifying unit 107. The reward giving notification unit 107 indicates that the predetermined reward giving condition is satisfied when the predetermined reward giving condition is satisfied in the target application installed in the user terminal 100 (an example of the own terminal apparatus). The assignment notification information is transmitted to the management server 200a (200b). Here, when the management server 200a (200b) satisfies the predetermined reward giving condition in the target application among the one or more target applications indicated by the application list (an example of the second information, an example of the application notification information). Then, a reward giving process is performed to give a predetermined reward in the target application.

  Note that the target application among the one or more target applications indicated by the application list (an example of the application notification information) is, for example, a list LT of target applications displayed based on the application list in the user terminal 100 (display information Target application selected from among

  As described above, in the mutual customer sending system 500a, when the predetermined reward giving condition is satisfied, the user terminal 100 transmits the reward giving notification information to the management server 200a (200b). By installing and using the target application (for example, the customer destination application 20 in the first embodiment) selected from the above, a reward is given to the user (for example, user X) who has used the application be able to.

  The case where the predetermined reward giving condition is satisfied may be a case where it is determined that the predetermined result is achieved in the target application installed in the user terminal 100 (an example of the own terminal device). .

  In addition, a plurality of predetermined reward giving conditions are provided, and the reward giving notifying unit 107 respectively adds the reward giving notification information to the management server 200a (200b) based on satisfaction of each of the plurality of reward giving conditions. It may be sent to the user.

(14) Further, as described in the fifth embodiment, the user terminal 100 displays, for example, a list LT of target applications to be presented to the user based on the application list acquired from the management server 200 of the first embodiment. (For example, a screen displaying a list of information indicating a target application) may be generated.
For example, in the mutual customer sending system 500a, the user terminal 100 (an example of a terminal device) is a terminal device capable of communicating with the management server 200. Here, the management server 200 is installed in the user terminal 100 based on, for example, installation notification information indicating that the target application installed in the user terminal 100 among the plurality of target applications to be managed has been installed. Manage the installation information of the target application. Note that the installation notification information is an example of the first information, and is information transmitted from the user terminal 100 to the management server 200 in response to execution of the target application installed in the user terminal 100. It is not restricted to this.
The user terminal 100 includes an installation notification unit 103, an installation notification unit 103, a list acquisition unit 109 (an example of an acquisition unit), a list generation unit 112 (an example of a generation unit), and a display control unit 105. There is. The installation notification unit 103 transmits installation notification information of the target application installed in the user terminal 100 (an example of the own terminal device) to the management server 200. The list acquisition unit 109 manages an application list (an example of application notification information, an example of second information) including information indicating at least one target application whose installation information corresponding to the user terminal 100 is not managed in the management server 200. It is acquired from the server 200. The list generation unit 112 generates an application list (an example of presentation information) based on the application list acquired by the list acquisition unit 109. Then, the display control unit 105 causes the display unit 120 to display a list LT (an example of display information) of the target application based on the application list (an example of presentation information) generated by the list generation unit 112.
As a result, the user terminal 100 displays a list of target applications other than target applications for which the management server 200 manages installation information corresponding to the user terminal 100 (that is, target applications that have been executed by the user terminal 100). The LT can be generated and presented to the user.

Further, the list generation unit 112 (an example of the generation unit) of the user terminal 100 uses the function of the user terminal 100 to install the target application indicated by the application list acquired by the list acquisition unit 109 in the user terminal 100. It may be determined whether the target application is another target application (for example, a target application of an older version or a target application that has been installed but has not started).
Here, the function included in the user terminal 100 is, for example, a function of the OS of the user terminal 100, and detects a target application installed in the user terminal 100 using a URL scheme corresponding to the target application. It is a function. The function of the user terminal 100 is not limited to the function of detecting a target application installed in the user terminal 100 using the URL scheme, and the user terminal 100 does not use the URL scheme. Alternatively, information indicating a target application already installed in the user terminal 100 may be acquired. Other target applications installed on the user terminal 100 include target applications of the previous version or target applications that have been installed but have not started yet, and have already been installed on the user terminal 100 and have been started The target application of may be included.
Then, based on the determination result, the list generation unit 112 selects, from among the target applications indicated by the application list, the other target applications described above (for example, that the target application of the old version or the installed version is activated). An application list (an example of presentation information) excluding the target application) may be regenerated.
Thereby, the user terminal 100 can present the user with a list LT of target applications excluding the target applications installed in the user terminal 100. For example, even if the target application of the old version (that is, the target application for which the management server 200 does not manage the installation information) is installed in the user terminal 100, the user terminal 100 selects the target application of the old version. The list LT of excluded target applications can be presented to the user. In addition, even when there is a target application installed in the user terminal 100 but has never been started (that is, a target application for which the management server 200 does not manage installation information), the user terminal 100 performs this start A list LT of target applications excluding target applications that have never been done can be presented to the user.

In addition, the list generation unit 112 (an example of the generation unit) of the user terminal 100 is installed in the user terminal 100 from among the target applications indicated by the application list based on the result of determination using the functions of the user terminal 100. Application list (an example of presentation information) that allows the user to distinguish other target applications that are being used (for example, target applications of the previous version or target applications that have been installed but have not started) may be regenerated .
Accordingly, the user terminal 100 selects the target application installed in the user terminal 100 among the target applications (target applications whose installation information is managed by the management server 200) indicated by the application list acquired from the management server 200. A list LT of distinguishable target applications can be presented to the user. For example, even if the target application of the old version (that is, the target application for which the management server 200 does not manage the installation information) is installed in the user terminal 100, the user terminal 100 selects the target application of the old version. A list LT of distinguishable target applications can be presented to the user. Further, even if there is a target application installed in the user terminal 100 but never started (that is, a target application for which the management server 200 does not manage installation information), the target that has not been started up A list LT of target applications which can distinguish the applications can be presented to the user. Therefore, the user terminal 100 can distinguish and present the information indicating the target application not installed on the user terminal 100 (that is, the candidate of the target application to be the customer sending destination) to the user.

(15) Further, in the application list (an example of the second information, an example of the application notification information) acquired by the list acquiring unit 109 (an example of the acquiring unit) of the user terminal 100, the installation information is further managed in the management server 200 Information indicating at least one target application, and distinction information capable of distinguishing between the target application whose installation information is not managed and the target application whose installation information is managed may be included.
That is, in the application list (an example of the second information, an example of the application notification information) acquired by the list acquisition unit 109, the management server 200 manages installation information corresponding to the user terminal 100 (an example of the own terminal device) Information indicating at least one target application which is not included, information indicating at least one target application whose installation information is managed, and a target application whose installation information is not managed and a target application whose installation information is managed Possible differentiation information may be included.
Then, the list generation unit 112 (an example of the generation unit) determines, based on the identification information included in the application list acquired by the list acquisition unit 109, the target application whose installation information is managed and included in the acquired application list. An application list (an example of presentation information) that can be distinguished from at least a target application whose installation information is not managed may be regenerated.
As a result, the user terminal 100 receives at least one target application whose installation information is not managed (for example, a target application not installed on the user terminal 100) and at least one target application whose installation information is managed (for example, A list LT of target applications that can be distinguished from target applications installed and activated in the user terminal 100 can be presented to the user.

For example, among the target applications indicated by the application list, the list generation unit 112 may not start another target application installed in the user terminal 100 (for example, a target application of an older version or an installed version). When the application list excluding the target application is generated, the target application whose installation information is managed may be generated so as to be distinguishable at least from the target application whose installation information is not managed.
As a result, when the target application of the previous version is installed or there is a target application that has been installed but has not been started, the user terminal 100 is at least one of the target applications whose installation information is not managed. Target application excluding the target application of the previous version or target application which has been installed but has not been started up from among them (that is, target application which is not installed on the user terminal 100) and at least one of which the installation information is managed Present the user with a list LT of target applications which can be distinguished from target applications (for example, target applications installed and activated in the user terminal 100). Can. Therefore, the user terminal 100 can present, to the user, information indicating a target application not installed on the user terminal 100 (that is, a candidate for a target application to be a customer sending destination).

In addition, the list generation unit 112 may select another target application installed in the user terminal 100 among the target applications indicated by the application list (for example, the target application of the old version or has been installed but has not been activated) When generating the application list that can distinguish the target application, the target application whose installation information is managed may be generated so as to be distinguishable at least from the target application whose installation information is not managed.
As a result, when the target application of the previous version is installed or there is a target application that has been installed but has not been started, the user terminal 100 is at least one of the target applications whose installation information is not managed. At least one target application (for example, installed in the user terminal 100 and started) that distinguishes from the target application of the previous version or the target application that has been installed but has not been started, and whose installation information is managed It is possible to present the user with a list LT of target applications that can distinguish the target applications). Therefore, the user terminal 100 can present, to the user, information indicating a target application not installed on the user terminal 100 (that is, a candidate for a target application to be a customer sending destination).
It should be noted that a target application of an older version or a target application that has been installed but has not been started, and at least one target application whose installation information is managed (for example, a target application that has been installed in user terminal 100 and has been started) Since “P” and “P” are not target applications that have not yet been installed in the user terminal 100 (that is, candidates for target applications to be customers), they may not be presented separately.

The list notification unit 242 (an example of the second information notification unit) of the management server 200a (200b) includes at least one target application whose installation information corresponding to the user terminal 100 is not managed by the installation information management unit 222. Information, information including at least one target application whose installation information corresponding to the user terminal 100 is managed in the installation information management unit 222, target application whose installation information is not managed, and target application whose installation information is managed An application list (one example of second information, one example of application notification information) including distinction information that can be distinguished from the above may be transmitted to the user terminal 100.

  That is, in the application list (an example of the second information, an example of the application notification information) acquired by the list acquiring unit 109 (an example of the acquiring unit) of the user terminal 100, the user terminal 100 (self Information indicating at least one target application for which installation information corresponding to an example of the terminal device is not managed, information indicating at least one target application for which installation information is managed, and target application for which installation information is not managed A distinction information may be included that can distinguish between and the target application for which the installation information is managed.

  As described above, the user terminal 100 transmits the discrimination information capable of discriminating whether or not the management server 200a (200b) is managing the installation information corresponding to the user terminal 100 to the user terminal 100. A list LT of target applications can be presented to the user so that the user can distinguish (determine) target applications for which the management server 200a (200b) does not manage installation information among the target applications shown.

(16) In the mutual customer sending system 500a, the management server 200a (an example of a management device) includes an application management unit 221, an information acquisition unit, an installation information management unit 222 (installation information management unit), and a list notification unit. And 242 (an example of a second information notification unit).
In this configuration, the application management unit 221 manages information on a plurality of target applications to be managed.
The information acquisition unit acquires, from the user terminal 100, information indicating a target application installed in the user terminal 100 among the plurality of target applications. Here, the information acquisition unit is configured to acquire information indicating an application installed in the user terminal 100, detected in the user terminal 100, and the detection method in the user terminal 100 may be any method. . For example, the detection method in the user terminal 100 may be a method of detecting information indicating an application installed in the user terminal 100 by the function of the OS of the user terminal 100, or the installation record of the target application installed in the user terminal 100 If there is an execution record (for example, a record by a resident application that records a process in the user terminal 100, a record using a cookie, etc.), a method of detecting based on the record may be used. Furthermore, the information acquisition unit may be an installation notification acquisition unit 241 (an example of a first information acquisition unit) or a temporary installation notification acquisition unit 247 (an example of a third information acquisition unit). .
Further, the installation information management unit 222 uses the installation information indicating which target application has been installed in the user terminal 100 based on the information indicating the target application installed in the user terminal 100 acquired by the information acquisition unit described above. to manage. Then, the list notification unit 242 determines at least one of the plurality of target applications in which the installation information corresponding to the user terminal 100 is not managed by the installation information management unit 222 based on the installation information managed by the installation information management unit 222. Application list including information indicating a target application of (an example of the second information is transmitted to the user terminal 100.

  As described above, the management server 200 a transmits an application list indicating at least one target application that does not manage installation information corresponding to the user terminal 100 to the user terminal 100, so that the target is not installed in the user terminal 100. The application can be notified to the user terminal 100.

Seventh Embodiment
Next, a seventh embodiment of the present invention will be described. First, an outline of the mutual customer sending system 500b of this embodiment will be described.
In the mutual customer feed system 500 (500a) described above, the management server 200 (200a, 200b) manages the installed target application in association with the reward user ID (Reward UID) associated with the user terminal 100. Therefore, even if it is the same user, if the user terminal 100 is different, it will be judged that it is another user. For example, when the user changes the model of the user terminal 100, in the mutual customer sending system 500 (500a) described above, although the target application has been used in the user terminal 100 before the model change, In the user terminal 100, for example, it may be presented to the user as a target application to which a reward is given. As described above, in the mutual customer sending system 500 (500a) described above, installation is recommended to the user when the user terminal 100 is changed in model or when the same user uses a plurality of user terminals 100. A target application that is not a target may be presented to the user as a target application for which installation is recommended.

  Therefore, in the present embodiment, even when the user terminal 100 is changed in model or when the same user uses a plurality of user terminals 100, target applications that are not targets for which the user is not recommended to install are excluded. An embodiment of the mutual customer support system 500b that presents the user with a list LT of suitable target applications will be described.

[Overview of Mutual Customer Service System According to Seventh Embodiment]
FIG. 31 is an explanatory diagram for explaining the outline of the mutual customer support system 500b according to the seventh embodiment.
In this figure, a network system 1b according to this embodiment includes a management server 200c and a user terminal 100, as in the first to fifth embodiments. In addition, in this figure, the user terminal 100A shows the user terminal 100 before the model change of the user X, and installs target applications 10-1 to 10-3 (application 1 to application 3). The user terminal 100B indicates the user terminal 100 after the model change of the user X, and installs the target application 10-1 (application 1) and the target application 10-4 (application 4). A target application that is not installed in the user terminal 100A and the user terminal 100B will be described as a target application 10-5 (application 5) and a target application 10-6 (application 6). In addition, when not distinguishing in particular, description of "-1", "-2", etc. is abbreviate | omitted and demonstrated as the object application 10. FIG.
Further, in this figure, it is assumed that the management server 200c stores “application 1 (ApID = 001)” to “application 6 (ApID = 006)” as target application information of the mutual customer sending system 500b.
Here, with reference to FIG. 31, the outline of the mutual customer-sending system 500b of this embodiment will be described as an example in which the user X changes the model from the user terminal 100A to the user terminal 100B.

First, when the user terminal 100A before model change changes installation of each target application and starts up first, installation notification information corresponding to each target application is sent to the management server 200c as shown in (1) to (3) Send to. The installation notification information includes, for example, a reward user ID (Reward UID), an application ID (ApID), and an application user ID (ApUID).
The management server 200c acquires installation notification information corresponding to each target application, and stores the acquired information as installation information. Here, the installation information T1 corresponding to the user terminal 100A is stored in the management server 200c by (1) to (3).

  Next, it is assumed that the user X changes the model from the user terminal 100A to the user terminal 100B. When the user terminal 100B after model change has installed and started each target application, installation notification information corresponding to each target application is sent to the management server 200c as shown in (4) and (5). Send. Thus, the installation information T2 corresponding to the user terminal 100B is stored in the management server 200c.

For example, when the management server 200c acquires list request notification information from the target application 10-1 installed in the user terminal 100B, the management server 200c determines the application user ID included in the installation information T2 corresponding to the user terminal 100B. If the APUID) is not included in the installation information corresponding to the other user terminal 100, the installation information corresponding to the other user terminal 100 includes the application user ID (ApUID). It is determined that the user terminal 100 is the same user X. Here, since the application user ID (ApUID) “5288” included in the installation information T2 is included in the installation information T1 corresponding to the user terminal 100A, the management server 200c includes the user terminal 100A and the user terminal 100B. Determines the user terminal 100 of the same user X, and associates “09634565” and “24957234” of the reward user ID (Reward UID). Thus, the installation information T1 and the installation information T2 are associated with each other. Then, the management server 200 c generates an application list of target applications that are recommended to be installed for the user, for example, as shown in (6), on the basis of the associated installation information T1 and installation information T2 The application list of applications is transmitted to the user terminal 100B. In this example, among the target applications stored as target application information, “application 5 (ApID = 005)” and “application 6 (ApID = 006)” are not included in the installation information T1 or the installation information T2. The management server 200 c transmits an application list of target applications indicating “application 5 (ApID = 005)” and “application 6 (ApID = 006)” to the user terminal 100B.
As a result, the user terminal 100B displays a list LT of target applications.
As described above, in the present embodiment, the management server 200 c associates and manages reward user IDs (Reward UIDs) of different user terminals 100 based on the application user IDs (Ap UIDs).

Next, the mutual customer feed system 500b according to the present embodiment will be described in detail.
The configuration of the network system 1b according to the seventh embodiment of the present invention and the configuration of the user terminal 100 are the same as the configuration of the network system 1 in the first embodiment shown in FIG. 2 and the first shown in FIG. Since the configuration is the same as that of the user terminal 100 in the embodiment, the description thereof is omitted here. Moreover, since the functional configuration of the user terminal 100 (SDK 11) of the present embodiment is the same as that of the first embodiment shown in FIG. 5, the description thereof is omitted here.

Configuration of Management Server 200c According to Seventh Embodiment
Next, details of the configuration of the management server 200c according to the present embodiment will be described with reference to FIG.
FIG. 32 is a block diagram showing an example of the configuration of the management server 200c according to this embodiment. As described with reference to FIG. 4, the management server 200 c includes the communication unit 210, the management unit 220, the storage unit 230, and the control unit 240 c. In addition, in this figure, the same code | symbol is attached | subjected to the structure similar to FIG. 6, and description is abbreviate | omitted here.

Here, installation information stored in the installation information storage unit 236 will be described with reference to FIG.
FIG. 33 is a diagram showing an example of information stored in the installation information storage unit 236 according to the present embodiment, which is the same as the installation information shown in FIG.
In this figure, the installation information storage unit 236 stores installation information in which a reward user ID (Reward UID), an application ID (ApID), and an application user ID (ApUID) are associated. The installation information T1 corresponds to the user terminal 100A before the model change, and the installation information T2 corresponds to the user terminal 100B after the model change.

Referring back to FIG. 32, the control unit 240 c includes an installation notification acquisition unit 241, a list notification unit 242, a customer sending information acquisition unit 243, an installation guidance instruction unit 244, a reward processing unit 245, a clock unit 246, and the like. A terminal information extraction unit 249 is provided.
The control unit 240 c in the present embodiment is different from the first and second embodiments in that the other terminal information extraction unit 249 is provided.

Note that the installation information management unit 222 according to the present embodiment specifies the reward user ID (an example of unique identification information) for specifying the user terminal 100 in which the target application (an example of the first application) that has transmitted the installation notification information is installed. An application ID (an example of identification information) of an application is associated and managed, and the reward user ID and association information are associated and managed. Here, the association information is information for associating the user terminal 100 of the same user. Here, even with different user terminals 100 (user terminal 100A, user terminal 100B), for example, as the association information, the same application user ID is set in the same application of the same user, for example, , Use this app user ID. In the present embodiment, the installation information management unit 222 associates and manages the reward user ID and the application user ID in the target application.
Further, the installation notification information includes, for example, a reward user ID, an application ID of the target application, and an application user ID. Therefore, for example, as illustrated in FIG. 33, the installation information management unit 222 stores the reward user ID, the application ID, and the application user ID in the installation information storage unit 236 in association with one another. And the application user ID in association with each other.

  The other terminal information extraction unit 249 makes reference to the installation information management unit 222 to associate with the reward user ID that identifies the user terminal 100 in which the target application that has transmitted the installation notification information is installed. And extract another reward user ID associated with the reward user ID.

As described above, in the same application installed in both different user terminals 100 (user terminal 100A, user terminal 100B), different reward users are utilized by using the same application user ID being set. ID can be associated. Therefore, the other terminal information extraction unit 249 uses the application user ID as an example of user information in the target application as association information as a first extraction method.
Specifically, the other terminal information extraction unit 249 associates the application user ID in the target application associated with the reward user ID specifying the user terminal 100 in which the target application is installed with the reward user ID in addition to the above. Extract other reward user IDs. In addition, if there is a guarantee that the application user ID is unique among a plurality of target applications corresponding to the mutual customer delivery system 500b and the application user ID of a target application is not used in another target application, the association is performed. Only the application user ID may be used as the information, but if uniqueness is not guaranteed, a combination of the application ID of the target application and the application user ID may be used as the association information. That is, the other terminal information extraction unit 249 matches the set of the application ID and the application user ID corresponding to the target application installed in the user terminal 100 among the installation information stored in the installation information storage unit 236. An application user ID to be set or a combination of the application ID and the application user ID is extracted, and another reward user ID (reward user ID other than the own user terminal 100) associated with the extracted application user ID is extracted.
Thus, the other terminal information extraction unit 249 uses the application ID of the target application associated with the reward user ID specifying the user terminal 100 in which the target application is installed, or the application ID and the application user ID as the association information. Use a set of

By the way, there are cases where the same application is not used by different user terminals 100 (user terminal 100A, user terminal 100B). For example, it is a case where the target application (for example, target application 10-4) which was not utilized by the old terminal (user terminal 100A) is utilized by the new terminal (user terminal 100B). In this case, association using the application user ID of the target application can not be performed. Therefore, application user IDs of other target applications (for example, target application 10-1) installed in the same user terminal 100 (user terminal 100B) are used. That is, as the second extraction method, the other terminal information extraction unit 249 is another object associated with the same reward user ID as the application user ID of the target application (for example, the target application 10-4) as the association information. The application user ID of the application (for example, the target application 10-1) may be used. More specifically, the other-terminal information extraction unit 249 selects another target application associated with the same reward user ID as the application user ID of the target application among the installation information stored in the installation information storage unit 236. Extract the application user ID of. Furthermore, the other-terminal information extraction unit 249 extracts an application user ID that matches the application user ID of the other target application extracted from the installation information stored in the installation information storage unit 236, and extracts the application user ID extracted The other reward user ID (reward user ID other than the own user terminal 100) associated with the ID is extracted. Also in this example, not only the application ID but also a combination of the application ID and the application user ID may be used.
Thus, the other terminal information extraction unit 249 uses, as the association information, the application user ID of another target application associated with the same reward user ID as the application user ID of the target application. Alternatively, a set of application ID and application user ID of another target application associated with the same reward user ID as the combination of application ID and application user ID of the target application is used.
The other terminal information extraction unit 249 may further extract by the second extraction method when another reward user ID (reward user ID other than the own user terminal 100) can not be extracted by the first extraction method. You may Also, the first extraction method may be used. In the case of limiting to the first extraction method, the target application installed on the old terminal (user terminal 100A) is included in the list LT of target applications that have not been used by the user presented to the user. May be

  The list notification unit 242 according to the present embodiment is installed in the user terminal 100 in which the target application is installed, and in the other user terminals 100 specified by the other reward user ID extracted by the other terminal information extraction unit 249. An application list of at least one target application for which installation notification information has not been acquired from any of the target applications 10 is transmitted to the user terminal 100. That is, the list notification unit 242 is not only the target application installed in the user terminal 100 (user terminal 100B) after the model change but also the target application installed in the user terminal 100 (user terminal 100A) before the model change And the application list excluded from the target applications managed by the application management unit 221 is transmitted to the user terminal 100.

[Details of operation of mutual customer processing according to the seventh embodiment]
Next, the operation of the mutual customer delivery system 500b of this embodiment will be described.
The basic operation of the mutual customer sending system 500b of this embodiment is the same as that of the first embodiment shown in FIGS. 14 and 15, and here, with reference to FIG. 34, the object of this embodiment The operation of the mutual customer delivery system 500b will be described focusing on the process of generating the application list of applications. The example described here will be described on the assumption that it is in the same state as FIG. Also, in the example described here, the installation information stored in the installation information storage unit 236 is described on the premise that it is in the state shown in FIG.

  In addition, with reference to FIG. 34, the process by the side of the target application (for example, target application 10-1) currently installed in the user terminal 100 (user terminal 100B) is demonstrated. Further, in the processing shown in FIG. 34, the target application is described as including the SDK 11 in the first and second embodiments.

In FIG. 34, the process of step SA11 to step SA24 and the process of step SE11 are the same as those of the first embodiment shown in FIG.
In step SA24, when list request unit 104 transmits list request notification information to management server 200c (REQ12), other terminal information extraction unit 249 of management server 200c transmits the old terminal (user terminal 100A) in step SE115. Extract the target application installed in). Note that the list request notification information includes at least an application ID of a target application and a reward user ID corresponding to the user terminal 100B.

For example, when the management server 200c acquires list request notification information from the target application 10-1 installed in the user terminal 100B shown in FIG. 31, the other-terminal information extraction unit 249 follows the first extraction method described above. The target application installed in the user terminal 100A is extracted as follows.
The other terminal information extraction unit 249 acquires the reward user ID (“24957234”) and the application ID (“001”) included in the list request notification information. Next, a set of an application user ID (“5288”) and an application ID (“001”) corresponding to the application ID (“001”) associated with the reward user ID (“24957234”) is acquired. The other terminal information extraction unit 249 extracts installation information associated with another reward user ID including a set of the acquired application user ID (“5288”) and application ID (“001”).
The other terminal information extraction unit 249 identifies the reward user ID (“09634565”) associated with the extracted installation information. Note that the other terminal information extraction unit 249 stores the identified reward user ID (“09634565”) and the reward user ID (“24957234”) in the storage unit 230 as a set of reward user IDs associated with each other. Good.

  The other terminal information extraction unit 249 extracts a target application corresponding to the application ID associated with the identified reward user ID (“09634565”) as a target application installed on the old terminal (user terminal 100A). For example, the other terminal information extraction unit 249 extracts the target applications 10-1 to 10-3 (application 1 to application 3) illustrated in FIG.

Furthermore, for example, when the user X acquires list request notification information from the target application 10-4 illustrated in FIG. 31, the other terminal information extraction unit 249 combines the first extraction method and the second extraction method described above. The target application installed in the user terminal 100A is extracted as follows.
The other terminal information extraction unit 249 acquires the reward user ID (“24957234”) and the application ID (“004”) included in the list request notification information. Next, a set of an application user ID (“1922”) and an application ID (“004”) corresponding to the application ID (“004”) associated with the reward user ID (“24957234”) is acquired. The other terminal information extraction unit 249 extracts installation information associated with another reward user ID including the acquired set of the application user ID (“1922”) and the application ID (“004”). In this case, there is no other installation information including the application user ID (“1922”). Therefore, the other terminal information extraction unit 249 selects the application user ID ("5288") of the other target application (target application 10-1) from the installation information T2 associated with the reward user ID ("24957234"). Acquire a pair with the application ID ("001").

Next, the other terminal information extraction unit 249 extracts installation information associated with another reward user ID including a combination of the acquired application user ID (“5288”) and the application ID (“001”). . The other terminal information extraction unit 249 identifies the reward user ID (“09634565”) associated with the extracted installation information.
The other terminal information extraction unit 249 extracts a target application corresponding to the application ID associated with the identified reward user ID (“09634565”) as a target application installed on the old terminal (user terminal 100A). For example, the other terminal information extraction unit 249 extracts the target applications 10-1 to 10-3 (application 1 to application 3) illustrated in FIG.

  Next, the list notification unit 242 of the management server 200c performs a filtering process of the target application (step SE15b). The list notification unit 242 is one of the target application 10 installed in the user terminal 100 in which the target application is installed and the target application 10 installed in the other user terminal 100 specified by the other reward user ID extracted by the other terminal information extraction unit 249. An application list of at least one target application for which installation notification information has not been obtained from any of them is generated. That is, the list notification unit 242 corresponds to the installation information T1 associated with the reward user ID (“09634565”) corresponding to the user terminal 100A among the target application information managed by the application management unit 221, and the user terminal 100B. The application list of the target application excluding the installation information T2 associated with the reward user ID (“24957234”) is generated. For example, in the example illustrated in FIG. 31, the list notification unit 242 generates an application list of target applications indicating the target application 10-5 (application 5) and the target application 10-6 (application 6).

  The subsequent processing of step SE16 is the same as the processing of step SA25, the processing of step SA26, the processing of steps SE16 to SE19, and the processing of step SC11 shown in FIG.

Summary of Seventh Embodiment
(1) As described above, the management server 200 c (an example of the management apparatus) in the mutual customer sending system 500 b of the present embodiment includes the application management unit 221, the installation notification acquisition unit 241, and the installation information management unit 222. , The other terminal information extraction unit 249, and the list notification unit 242. The application management unit 221 manages information on a plurality of target applications to be managed. The installation notification acquisition unit 241 indicates that the target application is installed from the target application 10-1 (an example of the first application) installed in the user terminal 100 (an example of the terminal device) among the plurality of target applications. Get installation notification information. The installation information management unit 222 associates a reward user ID (an example of unique identification information) specifying the user terminal 100 in which the target application 10-1 that has transmitted the installation notification information is installed with the application ID of the target application 10-1. And manages the reward user ID and association information (for example, application user ID) in association with each other. The other terminal information extraction unit 249 refers to the installation information management unit 222 to associate information associated with the reward user ID identifying the user terminal 100 in which the target application 10-1 that has transmitted the installation notification information is installed. And extract another reward user ID associated with the reward user ID. The list notification unit 242 includes the target application 10 installed on the user terminal 100 in which the target application 10-1 is installed and the target application 10 installed on the other user terminal 100 specified by the other reward user ID extracted by the other terminal information extraction unit 249. The application list of at least one target application (for example, target application 10-5 (application 5), target application 10-6 (application 6)) that has not acquired installation notification information from any of Send to

  Thereby, for example, when the model of the user terminal 100 is changed, the management server 200c according to the present embodiment targets the application installed on the user terminal 100 (user terminal 100A) before the model change and the user after the model change The target application installed in the terminal 100 (user terminal 100B) can be associated and managed. Therefore, the management server 200c causes the user to present the user with a list LT of target applications that the user has not used, for example, when presenting the target applications that are recommended for installation to the user after changing the model of the user terminal 100. be able to. That is, when the management server 200 c changes the model of the user terminal 100 or when the same user uses a plurality of user terminals 100, the target already installed in another user terminal 100 of the same user It is possible to prevent the application from being presented to the user as an application list of a target application that recommends installation for the user.

(2) Further, in the present embodiment, the install information management unit 222 determines the user terminal 100 (an example of a terminal device) a reward user ID and an application ID (an example of identification information of a target application (an example of a first application) And the application user ID (an example of user information) in the target application are associated and managed. Then, the other terminal information extraction unit 249 uses the application user ID in the target application as the association information.
As a result, the management server 200c according to the present embodiment uses the application user ID, which is information managed by the management server 200c. Therefore, as compared with the case where new information is added as association information, the management server 200c can be performed by a simple means. Reward user IDs between different user terminals 100 can be associated.

(3) Also, in the present embodiment, the other terminal information extraction unit 249 is the user terminal 100 (an example of a terminal device) in which the target application (an example of the first application) is installed like the first extraction method described above. The application user ID in the target application associated with the reward user ID (an example of the unique identification information) specifying the other extracts the other reward user ID associated with the reward user ID.
Thereby, the management server 200c of this embodiment can associate the reward user ID between different user terminals 100 using the application user ID.

(4) Also, in the present embodiment, the other-terminal information extraction unit 249 uses the association information to be a reward user ID (an example of unique identification information) associated with the application user ID in the target application (an example of the first application). Use the application user ID in another target application associated with.
As a result, the management server 200c according to the present embodiment may extract another reward user ID associated with the reward user ID by using the application user ID in the target application as in the second extraction method described above. Even if it is not possible, it is possible to associate reward user IDs between different user terminals 100 using application user IDs in other target applications.

(5) Further, in the present embodiment, the other terminal information extraction unit 249 is a reward user ID for specifying the user terminal 100 (an example of the terminal device) in which the target application (an example of the first application) is installed as the association information. The application ID of the target application associated with (an example of the unique identification information) and the application user ID in the target application are used.
As a result, since both the application ID and the application user ID are used as the association information, the management server 200 c of the present embodiment erroneously generates an error, for example, when the same application user ID is used in different target applications. Thus, it can be prevented that the user is the same user.

(6) Further, in the present embodiment, the installation notification information includes a reward user ID (an example of unique identification information) for specifying the user terminal 100 (an example of a terminal device) and a target application (an example of a first application). Application ID (an example of identification information) is included. Then, the installation information management unit 222 associates and manages the reward user ID for identifying the user terminal 100 acquired by the installation notification acquisition unit 241 and the application ID of the target application.
Thereby, the management server 200c according to the present embodiment can manage the target application installed in the user terminal 100 based on the reward user ID and the application ID of the target application.

(7) Further, the management server 200 c according to the present embodiment associates the application user ID of the target application (an example of the first application) with the reward user ID (an example of unique identification information) specifying the user terminal 100 (user information An application user information acquisition unit that acquires (an example) is provided. Note that the installation notification acquisition unit 241 may function as an application user information acquisition unit. That is, the installation notification information may include the application user ID of the target application that has transmitted the installation notification information. As described above, the function of the application user information acquisition unit may be included in another function. Then, the installation information management unit 222 manages the application user ID in the target application acquired by the application user information acquisition unit in association with the reward user ID specifying the user terminal 100.
Thus, when the target application is installed on the user terminal 100, the management server 200c receives the application ID of the installed target application, the application user ID of the installed target application, and the reward associated with the user terminal 100. The user ID can be associated and managed. That is, the management server 200c can manage the application user ID of each target application installed in the user terminal 100 in association with the reward user ID.

(8) Further, the management server 200c of the present embodiment includes the reward processing unit 245. The reward processing unit 245 satisfies the predetermined reward giving condition in the target application 10-5 or 10-6 (an example of the second application) selected by the user terminal 100 from one or more target applications included in the application list. If it is determined that the predetermined application has been determined, the target application 10-1 or 10-4 (an example of the first application) executes a reward giving process in which a predetermined reward is given.
As a result, when it is determined that the predetermined reward giving condition is satisfied, the management server 200c according to the present embodiment can give the target application 10-1 or 10-4 a predetermined reward. Here, the management server 200c according to the present embodiment generates an application list of a target application to which a reward is to be given, and transmits the generated application list to the user terminal 100. That is, the management server 200c according to the present embodiment excludes target applications that are not targets of rewards when the user terminal 100 is changed in model or when the same user uses a plurality of user terminals 100. Are transmitted to the user terminal 100. Therefore, the management server 200c according to the present embodiment is a target application for which a reward is to be provided even when the user terminal 100 is changed in model or when the same user uses a plurality of user terminals 100. An appropriate application list can be presented to the user. Therefore, in the case where the management server 200c according to the present embodiment changes the model of the user terminal 100 or when the same user uses a plurality of user terminals 100, the target application that is not the target of the reward grant is the reward grant It can be suppressed that the user is presented as a target application to be a target.

Note that, in the present embodiment, the installation information storage unit 236 associates the reward user ID (Reward UID) with the application ID (ApID), the reward user ID (Reward UID), and the application user ID (Ap UID) in one data table. As shown in FIG. 35, it may be divided into two data tables. That is, the installation information storage unit 236 is a second data table that associates the first data table associating the reward user ID (RewardUID) with the application ID (ApID), the application user ID (ApUID) and the application user ID (ApUID) It may be divided into tables. In this case, data serving as a primary key to associate data tables with each other is associated with each data table.
In the example shown in FIG. 35, the installation information storage unit 236 stores a first data table and a second data table. The installation information storage unit 236 associates, for example, an installation ID (InstID) as a primary key, a reward user ID (RewardUID), an application ID (ApID), and a notification type (Ttype) as the first data table. Remember. Further, the installation information storage unit 236 stores, as a second data table, an installation ID (InstID) as a main key, an application ID (ApID), and an application user ID (ApUID).

  Further, in the above-described embodiment, although the case of using the application user ID as the association information has been described, the present invention is not limited to this. The management server 200 c may use, for example, a cooperation code (for example, an e-mail address or the like) input by the user as the association information. In this case, the other terminal information extraction unit 249 can associate a reward user ID between different user terminals 100 by associating a reward user ID with which the cooperation code input by the user matches.

Eighth Embodiment
Next, an eighth embodiment of the present invention will be described. First, an overview of the mutual customer delivery system 500c of the present embodiment will be described.
In the mutual customer feed system 500 (500 a) described above, one reward user ID is associated with one user terminal 100 and managed. Therefore, even if the same user terminal 100 is changed, it is determined that the user terminal 100 before the change and the user terminal 100 after the change are different user terminals 100.

Here, when a change occurs in the reward user ID, for example, when the change of the reward user ID is permitted to the user and is changed by the user, the case is changed by the convenience or processing of the mutual customer sending system 500c. Or when it is changed due to convenience or processing other than the mutual customer delivery system 500c.
For example, when there is different information associated with each user terminal 100 as a function of the OS of the user terminal 100 and information permitted to be used by each application (hereinafter referred to as ID information), This ID information can be used as a reward user ID. This ID information may be, for example, an advertising identifier.

  Here, when the user is permitted to change the ID information, when the user changes the ID information, the reward user ID is changed. As the reward user ID, a telephone number set in the user terminal 100 or an e-mail address used by the user in the user terminal 100 may be used. In that case, the used telephone number or e-mail address If etc. is changed, the reward user ID will be changed.

  When the reward user ID is changed, in the above-mentioned mutual customer sending system 500 (500a), although it is the same user terminal 100, for example, after the change of the reward user ID, it is used before the change of the reward user ID. The target application that was being executed may be presented to the user as a target application for which a reward is to be given. As described above, in the mutual customer sending system 500 (500a) described above, when the reward user ID is changed in the user terminal 100, the target application that is not the target for which the user is recommended to install is the target application for which the installation is recommended. May be presented to the user.

  Therefore, in the present embodiment, even when the reward user ID is changed in the same user terminal 100, the list LT of appropriate target applications excluding the target applications that are not targets for which the user is recommended to install is given to the user An embodiment of the mutual customer delivery system 500c to be presented will be described.

[Overview of Mutual Customer Service System According to Eighth Embodiment]
FIG. 36 is an explanatory diagram for explaining the outline of the mutual customer feed system 500c of this embodiment.
In this figure, the basic configuration of the network system 1c according to this embodiment is the same as the configurations of the first to seventh embodiments, and includes a management server 200d and a user terminal 100. This figure shows that the target applications 10-1 to 10-4 (applications 1 to 4) have been installed in the user terminal 100 before or after the change of the reward user ID. The target applications 10-1 to 10-3 (applications 1 to 3) illustrated in the area indicated by reference numeral 100M are installed and activated before the change of the reward user ID, and the installation notification information has been transmitted to the management server 200d. It shows that there is. On the other hand, the target application 10-4 (application 4) illustrated in the area indicated by reference numeral 100N is installed and activated after the change of the reward user ID, and indicates that the installation notification information is transmitted to the management server 200d. In addition, the target application 10-1 (application 1) illustrated in the area indicated by the code 100N is activated after the target application 10-1 (application 1) installed before the change of the reward user ID changes the reward user ID. It represents for convenience that the installation notification information has been sent to the management server 200d. The target applications 10-2 and 10-3 (application 2 and application 3) installed before the change of the reward user ID, for example, are not activated even after the change of the reward user ID, and manage installation notification information. It is assumed that it has not sent to the server 200d.

A target application that has not been installed in the user terminal 100 before and after the change of the reward user ID will be described as a target application 10-5 (application 5) and a target application 10-6 (application 6). In addition, when not distinguishing in particular, description of "-1", "-2", etc. is abbreviate | omitted and demonstrated as the object application 10. FIG.
Further, in this figure, it is assumed that the management server 200 d stores “application 1 (ApID = 001)” to “application 6 (ApID = 006)” as target application information of the mutual customer sending system 500 c.
Here, with reference to FIG. 36, the outline of the mutual customer-sending system 500c according to the present embodiment will be described by taking as an example the case where the user X changes the reward user ID in the user terminal 100.

  First, when each target application 10-1 to 10-3 is installed and started first before the change of the reward user ID, the user terminal 100 displays each target application 10 as shown in (1) to (3). Installation notification information corresponding to # 1.about.1-10-3 is transmitted to the management server 200d. The installation notification information transmitted in (1) to (3) includes, for example, a reward user ID (Reward UID) before change, an application ID (Ap ID), and an application user ID (Ap UID). ing.

  The management server 200 d acquires installation notification information corresponding to each of the target applications 10-1 to 10-3, and stores the acquired information as installation information. Here, the installation information T10 corresponding to the reward user ID before the change is stored in the management server 200d by (1) to (3).

Next, it is assumed that the user X changes the reward user ID (Reward UID) in the user terminal 100. Then, after changing the reward user ID (Reward UID), the user terminal 100 transmits installation notification information corresponding to the target application 10-1 installed before the change to the management server 200d as shown in (4). . For example, when the target application 10-1 is started for the first time after the change of the reward user ID (Reward UID), the user terminal 100 transmits installation notification information corresponding to the target application 10-1 to the management server 200d. The process of transmitting installation notification information after the target application installed before the change of the reward user ID changes the reward user ID will be described later with reference to FIG.
In addition, when the target application 10-4 is installed in the user terminal 100 after the change of the reward user ID (Reward UID), the user terminal 100 causes the target application 10-4 to be activated first as shown in (5). The installation notification information corresponding to the target application 10-4 is sent to the management server 200d.
The installation notification information transmitted in (4) and (5) includes, for example, a reward user ID (RewardUID) after change, an application ID (ApID), and an application user ID (ApUID). .

  The management server 200d acquires installation notification information corresponding to the target application 10-1 and installation notification information corresponding to the target application 10-4, and stores the acquired information as installation information. Here, the installation information T20 corresponding to the changed reward user ID (Reward UID) is stored in the management server 200d by (4) and (5).

  For example, when the management server 200d acquires the list request notification information transmitted from the target application 10-1 after the change of the reward user ID of the user terminal 100 of the user X, the installation information T20 corresponding to the changed reward user ID The application user ID (ApUID) included in is searched for whether it is included in the installation information corresponding to another reward user ID. Then, when the application user ID (ApUID) is included in the installation information corresponding to another reward user ID, the management server 200 d uses the installation information in the same user terminal 100 of the user X (described above). It is determined that the list request notification information is stored based on the installation notification information acquired from the user terminal 100 that transmitted the list request notification information.

  Here, “5288” of the application user ID (ApUID) included in the installation information T20 corresponds to the installation information T10 corresponding to the other reward user ID (Reward UID) (ie, the reward user ID (Reward UID) before the change). It is included in the installation information T10). Therefore, the management server 200d determines that the installation information T10 including the same application user ID (ApUID) “5288” and the installation information T20 are the installation information of the same user terminal 100 of the user X, and changes them. The "09634565" of the previous reward user ID (Reward UID) is associated with the "24957234" of the changed reward user ID (Reward UID).

Thus, the management server 200 d associates the installation information T10 with the installation information T20. Then, the management server 200d generates the application list of the target application that recommends the user to install based on the associated installation information T10 and installation information T20, for example, as shown in (6), the generated target application The application list of is transmitted to the user terminal 100. In this example, among the target applications stored as target application information, “application 5 (ApID = 005)” and “application 6 (ApID = 006)” are not included in the installation information T10 or the installation information T20. The management server 200 d transmits, to the user terminal 100, an application list of target applications indicating “application 5 (ApID = 005)” and “application 6 (ApID = 006)”.
As a result, the user terminal 100 displays a list LT of target applications.

As described above, in the present embodiment, the management server 200 d determines, based on the application user ID (ApUID), the pre-change reward user ID (RewardUID) and the post-change reward user ID (RewardUID) in the same user terminal 100. Are associated and managed as a reward user ID (Reward UID) of the same user terminal 100. Then, the management server 200d determines that the user terminal 100 corresponding to each of the pre-change reward user ID (Reward UID) and the post-change reward user ID (Reward UID) is the same user terminal 100, and the user terminal 100 An application list indicating at least one target application for which installation notification information has not been acquired from 100 is transmitted to the user terminal 100.
Thus, the user terminal 100 can present the user X with a list LT of appropriate target applications excluding the target applications that are not targets for which the user X is recommended to be installed (that is, target applications already installed on the user terminal 100). .

Next, the mutual customer feed system 500c according to the present embodiment will be described in detail.
The configuration of the network system 1c according to the present embodiment and the configuration of the user terminal 100 are the configuration of the network system 1 in the first embodiment shown in FIG. 2 and the configuration of the user terminal 100 in the first embodiment shown in FIG. Since the configuration is the same as that of the configuration, the description thereof is omitted here. Moreover, since the functional configuration of the user terminal 100 (SDK 11) of the present embodiment is the same as that of the first embodiment shown in FIG. 5, the description thereof is omitted here.

Note that, as described with reference to FIG. 36, the method according to the present embodiment, which associates and manages two types of reward user IDs (Reward UID) before change and after change based on the application user ID (ApUID), A method similar to the method of managing the reward user ID (RewardUID) before the model change and the reward user ID (RewardUID) after the model change in association with each other based on the application user ID (ApUID) described in the seventh embodiment. It is.
Therefore, the configuration of the mutual customer delivery system 500c according to the present embodiment may be the same as the configuration of the mutual customer delivery system 500b according to the seventh embodiment. That is, the configuration of the management server 200d provided in the mutual customer feed system 500c may be the same as the configuration of the management server 200c according to the seventh embodiment shown in FIG.

[Configuration of Mutual Customer Support System 500c According to Eighth Embodiment]
FIG. 37 is a block diagram showing an example of the configuration of a management server 200d according to this embodiment. The details of the configuration of the management server 200d according to the present embodiment will be described with reference to FIG.
The management server 200d includes a communication unit 210, a management unit 220, a storage unit 230, and a control unit 240d. In addition, in this figure, the same code | symbol is attached | subjected to the structure similar to FIG. 32, and description is abbreviate | omitted here. The configuration of the management server 200d shown in FIG. 37 is different from the configuration of the management server 200c shown in FIG. Here, as described above, the configuration of the management server 200d may be the same as the configuration of the management server 200c shown in FIG. Can be applied.

  For example, similar to the other-terminal-information extracting unit 249 illustrated in FIG. 32, the information extracting unit 249a according to this embodiment includes the reward user ID and the association information (for example, the target application) included in the installation information managed by the installation information managing unit 222. The reward user ID associated with the association information is extracted based on the user information in Thus, the information extraction unit 249a according to the present embodiment extracts a reward user ID before change in the user terminal 100 specified by the reward user ID after change.

  That is, in the seventh embodiment, the other terminal information extraction unit 249 extracts the reward user ID before the model change and the reward user ID after the model change by extracting the reward user ID associated with the association information. . On the other hand, in the present embodiment, the information extraction unit 249a extracts the reward user ID associated with the association information by using the same function as the other terminal information extraction unit 249 has, so that the same user terminal 100 can be obtained. The pre-change reward user ID and the post-change reward user ID (Reward UID) are extracted.

As the above-mentioned association information, user information (for example, application user ID) in the target application may be used as described in the seventh embodiment as the first extraction method.
Specifically, the information extraction unit 249a associates the application user ID in the target application associated with the reward user ID identifying the user terminal 100 in which the target application is installed with the reward user ID in addition to the reward user ID. Other reward user IDs may be extracted.
For example, among the target applications installed before the change of the reward user ID, the information extraction unit 249a is an application user of the target application (for example, the target application 10-1) that has transmitted the installation notification information even after the change of the reward user ID. You may use an ID. Then, the information extraction unit 249a is the same as the application user ID associated with the changed reward user ID is extracted by extracting another reward user ID associated with other than the changed reward user ID. The reward user ID before the change of the user terminal 100 may be extracted.

  The target application installed in the user terminal 100 may include a target application (for example, the target application 10-4) that is not installed before the change of the reward user ID. In this case, the reward user ID before the change can not be extracted using the application user ID of the target application (for example, the target application 10-4). Therefore, as the association information described above, as described in the seventh embodiment as the second extraction method, it is associated with the same reward user ID as the application user ID of the target application (for example, the target application 10-4) The application user ID of another target application (for example, target application 10-1) may be used.

  Note that only the application user ID in the target application may be used as the association information described above, or a combination of the application ID of the target application and the application user ID may be used.

  The information extraction unit 249a according to this embodiment further extracts the reward user ID before the model change and the reward user ID after the model change, as in the other-terminal information extraction unit 249 according to the seventh embodiment. It is also good.

  In addition, the list notification unit 242 of the present embodiment is configured to display an application list indicating at least one target application for which installation notification information has not been acquired from the user terminal 100 corresponding to the reward user ID extracted by the information extraction unit 249a. Send to For example, the list notification unit 242 changes the application list indicating at least one target application for which installation notification information has not been acquired from the user terminal 100 corresponding to the reward user ID before change or the reward user ID after change. It transmits to the user terminal 100 corresponding to the reward user ID. That is, among the plurality of target applications managed by the application management unit 221, the list notification unit 242 not only changes the target application installed after the change of the reward user ID in the user terminal 100 but also before changing the reward user ID. An application list of at least one target application excluding the installed target application is transmitted to the user terminal 100.

[Details of operation of mutual customer processing according to the eighth embodiment]
The basic operation of the mutual customer feed system 500c of this embodiment is the same as that of the first embodiment shown in FIGS. The operation will be described.

  In the operation of the process of generating the application list in the mutual customer sending system 500c of this embodiment, the other terminal information extraction unit 249 is the old terminal of the user X (the user terminal 100A before the model change) in the process of step SE115 shown in FIG. Instead of the process of extracting the target application installed in the), the information extraction unit 249a executes a process of extracting the target application installed before the change of the reward user ID in the user terminal 100 of the user X.

The specific process of step S115 performed by the information extraction unit 249a in the present embodiment is the same as the process performed by the other terminal information extraction unit 249 in the seventh embodiment, and association information (for example, an application user ID) is a process of extracting a reward user ID associated with the ID.
For example, the information extraction unit 249a extracts the reward user ID before the change of the user terminal 100 according to the first extraction method described above, and extracts the target application installed before the change of the reward user ID. The information extraction unit 249a may extract the reward user ID before the change of the user terminal 100 according to the second extraction method, or the user terminal combining the first extraction method and the second extraction method The reward user ID before the change of 100 may be extracted.

[Example of Transmission Processing of Installation Notification Information According to Eighth Embodiment]
Next, processing of transmitting installation notification information of a target application installed in the user terminal 100 before the change of the reward user ID in the user terminal 100 to the management server 200d after the change of the reward user ID will be described.

  The transmission process of the installation notification information is performed, for example, in the initialization process described with reference to FIG. 14 in the first embodiment. In the initialization process shown in FIG. 14, when the target application is installed on the user terminal 100 and started, the installation notification information of the target application is transmitted from the user terminal 100 to the management server 200 and becomes initialized. From the next start of the target application, the process of transmitting the installation notification information is not performed. Therefore, even if the reward user ID of the user terminal 100 is changed after that, the installation notification information can not be transmitted from the user terminal 100 after the change in the process shown in FIG.

  Therefore, in the present embodiment, when the reward user ID of the user terminal 100 is changed, the installation notification information is again transmitted from the user terminal 100 to the management server 200d even if the target application has already transmitted the installation notification before the change. Perform processing to send.

  FIG. 38 is a flowchart showing an example of the initialization process according to the present embodiment. This FIG. 38 shows another form of the initialization process (steps SA11 to SA17) shown in FIG. 14 and is similar to each process shown in FIG. 14 except the process related to the initialization process, It is omitted.

  In the initialization process shown in FIG. 38, it is assumed that different ID information associated with each user terminal 100 is stored in the terminal storage unit 140 as a function of the OS of the user terminal 100, and this ID information is rewarded. The case of using as a user ID will be described as an example. The ID information may be set by the OS and stored in the terminal storage unit 140, for example, or may be set by the user according to an instruction of the OS after activation of the OS and stored in the terminal storage unit 140. It is also good. Further, it is assumed that the change of the ID information is permitted to the user by the OS.

  Hereinafter, with reference to FIG. 38, when the reward user ID is changed, the operation of the process of transmitting the installation notification information again to the management server 200d in the initialization process will be described. In FIG. 38, the processes corresponding to the processes in FIG. 14 are denoted by the same reference numerals, and the description thereof will be appropriately omitted.

  The initialization processing unit 101 of the SDK 11A determines whether or not the initialization processing has been completed in the initialization processing (step SA12). When it is determined that the initialization process has not been completed (step SA12: NO), the unique identification information acquisition unit 102 of the SDK 11A refers to the terminal storage unit 140 and determines whether or not the reward user ID has been acquired. (Step SA13).

  When it is determined that the reward user ID has not been acquired (step SA13: NO), the unique identification information acquisition unit 102 generates and acquires the reward user ID corresponding to the user terminal 100. Here, the unique identification information acquisition unit 102 refers to the terminal storage unit 140, and acquires ID information associated with the user terminal 100 as a function of the OS as a reward user ID (step SA14a). Then, the unique identification information acquisition unit 102 stores the ID information acquired as the reward user ID in the inter-application shared area of the terminal storage unit 140 as a reward user ID (step SA15).

  On the other hand, when it is determined that the reward user ID has been obtained (step SA13: YES), the unique identification information acquisition unit 102 reads the reward user ID from the terminal storage unit 140, and proceeds to step SA16.

  Subsequently, the installation notification unit 103 of the SDK 11A transmits installation notification information indicating that the customer sending source application 10 (game A) is installed on the user terminal 100 to the management server 200d (step SA16). Here, the installation notification information includes a reward user ID (Reward UID) corresponding to the user terminal 100, an application ID (ApID) of the installed customer sending source application 10 (game A), and the customer sending source application 10 ( The application user ID (ApUID) of the user X registered in the game A) is included.

  Next, the installation notification acquisition unit 241 of the management server 200d acquires the installation notification information transmitted from the user terminal 100 (SDK 11A), and transmits the response information (notification result) indicating the acquisition to the user terminal 100 (the notification result). Send to SDK 11A). In addition, the installation information management unit 222 of the management server 200d receives the reward user ID (Reward UID) included in the installation notification information acquired by the installation notification acquisition unit 241 and the application ID (ApID) of the customer sending application 10 (game A). And the application user ID (ApUID) of the user X in the customer sending source application 10 (game A) are stored in the installation information storage unit 236 as installation information (step SE11).

  When acquiring the response information (notification result) transmitted from the management server 200d, the initialization processing unit 101 of the SDK 11A sets a flag indicating that initialization has been completed, and ends the initialization processing (step SA17).

  On the other hand, when it is determined in step SA12 that the initialization processing has been completed (step SA12: YES), the unique identification information acquisition unit 102 stores the ID information stored in the terminal storage unit 140 and the reward user ID (Reward UID). It is determined whether the ID information has been changed or not by comparing (step S121). When it is determined that the ID information is not changed because the ID information stored in the terminal storage unit 140 and the reward user ID (Reward UID) match (step S121: NO), the initialization processing unit 101 Finish the initialization process.

  On the other hand, when it is determined that the ID information is changed because the ID information stored in the terminal storage unit 140 and the reward user ID (RewardUID) do not match (step S121: YES), the unique identification information acquisition unit 102 Then, the post-change ID information is acquired as a reward user ID (step SA14a), and the acquired ID information is stored in the inter-application shared area of the terminal storage unit 140 as a post-change reward user ID (step SA15). Note that, when storing the changed reward user ID in the terminal storage unit 140, the unique identification information acquisition unit 102 may store the changed reward user ID instead of the pre-change reward user ID, The reward user ID after change may be stored so as to be distinguishable, leaving the reward user ID before change.

  Then, the installation notification unit 103 transmits installation notification information indicating that the customer sending source application 10 (game A) has been installed in the user terminal 100 to the management server 200 d (REQ 11, step SA 16). Here, the installation notification information includes a changed reward user ID (Reward UID) corresponding to the user terminal 100, an application ID (ApID) of the installed customer sending source application 10 (game A), and the customer sending origin. The application user ID (ApUID) of the user X registered in the application 10 (game A) is included.

  The management server 200 d acquires installation notification information transmitted from the user terminal 100 after the change of the reward user ID, and changes the reward user ID (Reward UID) included in the acquired installation notification information to the customer sending application 10 ( The application ID (ApID) of the game A) and the application user ID (ApUID) of the user X in the customer sending source application 10 (game A) are associated and installed as installation information (for example, installation information T20 shown in FIG. 36) It is stored in the information storage unit 236 (step SE11).

  Accordingly, when the reward user ID is changed, the user terminal 100 can transmit the installation notification information of the target application installed before the change and having transmitted the installation notification information after the change. Therefore, when the reward user ID is changed in the user terminal 100, the management server 200d uses the application user ID of the target application that has transmitted the installation notification information before and after the change. The reward user ID and the changed reward user ID can be managed in association with each other.

  When it is determined that the reward user ID has already been acquired in step SA13 when the target application installed in the user terminal 100 is activated for the first time, the unique identification information acquisition unit 102 is stored in the terminal storage unit 140. The ID information may be compared with the reward user ID (Reward UID) to perform processing based on the comparison result. For example, when the ID information stored in the terminal storage unit 140 and the reward user ID (RewardUID) do not match, the installation notification unit 103 manages the installation notification information as a management server using the ID information as a reward user ID (RewardUID). It may be sent to 200d.

  As a result, when the target application installed in the user terminal 100 starts up for the first time, the user terminal 100 has already acquired the reward user ID, and the ID information before the change is made although the ID information has been changed. Even in the case where the user ID is still stored in the terminal storage unit 140 as the reward user ID, installation notification information can be transmitted to the management server 200 d with the changed user ID information as the reward user ID. Also, when the target application is started for the first time, the target application installed before the change and having transmitted the installation notification information by not storing the changed ID information as the reward user ID in the terminal storage unit 140 The installation notification information of at least one of the target applications can be transmitted after the change.

  Note that when the target application installed in the user terminal 100 starts up, the initialization processing unit 101 may control to transmit installation notification information every time. In this case, the management server 200d may acquire and manage installation notification information before the change of the reward user ID and installation notification information after the change of the reward user ID from the user terminal 100.

Regarding the Seventh and Eighth Embodiments
The seventh and eighth embodiments described above can be described as follows, but are not limited to the following description.

(1) In the mutual customer feed system 500b of the seventh embodiment, the management server 200b (an example of a management device) includes an application management unit 221, an installation notification acquisition unit 241, an installation information management unit 222, and other terminal information extraction. A unit 249 and a list notification unit 242 are provided. Further, in the mutual customer feed system 500c of the eighth embodiment, the management server 200c (an example of a management device) includes an application management unit 221, an installation notification acquisition unit 241, an installation information management unit 222, and an information extraction unit 249a. , List notification unit 242. As described above, the function of the information extraction unit 249a can be the same as the function of the other terminal information extraction unit 249. Therefore, the configuration of the management server 200d of the eighth embodiment is the same as that of the seventh embodiment. The configuration may be similar to that of the management server 200c. In the following, the configuration of the management server 200d is described as an example that includes both the management server 200c and the management server 200d.
The application management unit 221 manages information on a plurality of target applications to be managed. The installation notification acquisition unit 241 (an example of the first information acquisition unit) is configured to execute the user terminal 100 in response to the target application 10-1 (an example of the first application) of the plurality of target applications being executed by the user terminal 100. The installation notification information (an example of the first information) transmitted from the above is associated with the reward user ID (an example of the unique identification information) associated with the user terminal 100, and acquired from the user terminal 100. The installation information management unit 222 (an example of the information management unit) associates and manages the reward user ID associated with the user terminal 100 acquired by the installation notification acquisition unit 241 and the association information. The information extraction unit 249a (an example of the extraction unit) extracts the reward user ID associated with the association information based on the reward user ID and the association information managed by the installation information management unit 222. The list notification unit 242 (an example of a second information notification unit) receives at least one target application (for example, a target application) that has not acquired installation notification information from the user terminal 100 corresponding to the reward user ID extracted by the information extraction unit 249a. 10-5 (application 5), an application list (an example of second information) including information indicating the target application 10-6 (application 6) is transmitted to the user terminal 100 in which the target application 10-1 is executed Do.

For example, the information extraction unit 249a (an example of an extraction unit) of the management server 200d extracts a plurality of reward user IDs (an example of unique identification information) associated with the association information. The list notification unit 242 (an example of the second information notification unit) acquires installation notification information (an example of the first information) from the user terminal 100 corresponding to each of the plurality of reward user IDs extracted by the information extraction unit 249a. An application list (an example of second information) including information indicating at least one target application (for example, target application 10-5 (application 5), target application 10-6 (application 6)) Is transmitted to the user terminal 100 for which the
Thus, the management server 200d (200c) according to the present embodiment can manage a plurality of reward user IDs in association with each other. The number of reward user IDs associated with the association information is not limited to plural but may be one.

Specifically, the information extraction unit 249a (an example of the extraction unit) of the management server 200d is a target application 10-1 (the first application) as a plurality of reward user IDs (an example of unique identification information) associated with the association information. Before the first unique identification information is associated with the first unique identification information, which is a reward user ID associated with the user terminal 100 for which the) is executed, and the user terminal 100 for which the target application 10-1 is executed. The associated second unique identification information may be extracted.
Then, the list notification unit 242 (an example of the second information notification unit) receives the installation notification information (the first information) from the user terminal 100 corresponding to the first unique identification information or the second unique identification information extracted by the information extraction unit 249a. An application list (an example of second information) including information indicating at least one target application (for example, target application 10-5 (application 5), target application 10-6 (application 6)) that has not acquired an example) , And may be transmitted to the user terminal 100 corresponding to the first unique identification information.

  Thus, for example, when the reward user ID of the user terminal 100 is changed, the management server 200d (200c) is a target application installed and activated (executed) on the user terminal 100 before the change of the reward user ID. The target application installed and activated (executed) on the user terminal 100 after the change of the reward user ID can be managed in association with each other. Therefore, when the management server 200d (200c), for example, changes the reward user ID of the user terminal 100 and then presents a target application for which installation is recommended to the user, a list of target applications that have not been used by the user The LT can be presented to the user. That is, when the reward user ID of the user terminal 100 is changed, the management server 200 d (200 c) causes the user to install the target application installed and activated (executed) in the user terminal 100 before the change of the reward user ID. It is possible to prevent the user from being presented as a list LT of target applications of target applications for which installation is recommended. Therefore, according to the present embodiment, it is possible to present a list LT of appropriate target applications for which the user is recommended to install.

(2) Further, the information extraction unit 249a (an example of the extraction unit) of the management server 200d is a target application 10-1 (the first application as a plurality of reward user IDs (an example of unique identification information) associated with the association information. Reward associated with another user terminal 100 different from the first unique identification information, which is the reward user ID associated with the user terminal 100 for which the) is executed, and the user terminal 100 corresponding to the first unique identification information The second unique identification information, which is a user ID, may be extracted.
Then, the list notification unit 242 (an example of the second information notification unit) selects one of the user terminal 100 corresponding to the first unique identification information extracted by the information extraction unit 249a and the user terminal 100 corresponding to the second unique identification information. Information indicating at least one target application (for example, target application 10-5 (application 5), target application 10-6 (application 6)) that has not acquired installation notification information (an example of the first information) from any of An application list (an example of second information) including the above may be transmitted to the user terminal 100 corresponding to the first unique identification information.

  Thereby, for example, when the model of the user terminal 100 is changed, the management server 200d (200c) is a target application installed and activated (executed) on the user terminal 100 (user terminal 100A) before the model change; The user terminal 100 after model change can be managed in association with the target application installed and executed (executed) in the user terminal 100 B. Therefore, the management server 200 d (200 c) When the target application to be recommended to be installed is presented to the user after the model change, it is possible to present the user with a list LT of target applications that the user has not used before, that is, the management server 200d (200c) , User terminal 100 In the case of changing the type, or in the case where a plurality of user terminals 100 are used by the same user, a target for which the user is recommended to install the target application already installed in the other user terminals 100 of the same user. It can be suppressed that the user is presented as an application list of applications.

(3) The installation information management unit 222 (an example of an information management unit) includes a reward user ID (an example of unique identification information) associated with the user terminal 100 and an application user ID in a target application (an example of a first application) Manage in association with (an example of user information). Then, the information extraction unit 249a (an example of the extraction unit) may use the application user ID in the target application as the association information.
As a result, the management server 200d (200c) uses the application user ID, which is information managed by the management server 200d (200c), so it is simpler than adding new information as association information. A plurality of reward user IDs can be associated by means.

For example, the information extraction unit 249 a (an example of the extraction unit) is associated with the reward user ID corresponding to the user terminal 100 in which the target application (an example of the first application) is installed The application user ID in the existing target application extracts another reward user ID associated with the reward user ID.
Thereby, the management server 200d (200c) can associate the reward user ID before and after the change in the same user terminal 100 or the reward user ID between different user terminals 100 using the application user ID. it can.

(4) Further, the information extraction unit 249a (an example of the extraction unit) is, as the association information, a reward user ID (unique to the application user ID (an example of the user information) in the target application (an example of the first application) An application user ID in another target application associated with (an example of identification information) may be used.

  As a result, the management server 200d (200c) can extract another reward user ID associated with the reward user ID using the application user ID in the target application as in the second extraction method described above. Even if not, the application user IDs in other target applications are used to associate reward user IDs before and after change in the same user terminal 100 or reward user IDs between different user terminals 100. be able to.

(5) In addition, the information extraction unit 249a (an example of the extraction unit) uses the reward user ID (specific identification information) associated with the user terminal 100 in which the target application (an example of the first application) is executed as association information. An application ID (an example of identification information for identifying a first application) of a target application associated with an example) and an application user ID (an example of user information) in the target application may be used.

  Thus, since both the application ID and the application user ID are used as association information, the management server 200d (200c), for example, has the same application user ID as the application user ID of the first user in a certain target application. When it is used as an application user ID in another target application of the second user different from the first user, it can be prevented from erroneously determining that the user is the same user.

(6) Further, the application user ID (an example of user information) in the target application (an example of the first application) is information for identifying a user who uses the target application executed by the user terminal 100. The management server 200 d acquires, for example, an application user ID (an example of user information) in a target application (an example of a first application) in association with a reward user ID (an example of unique identification information) associated with the user terminal 100. An application user information acquisition unit may be provided. Note that the installation notification acquisition unit 241 may function as an application user information acquisition unit. That is, the installation notification information may include the application user ID of the target application that has transmitted the installation notification information. As described above, the function of the application user information acquisition unit may be included in another function.
Then, the installation information management unit 222 may manage the application user ID in the target application acquired by the application user information acquisition unit in association with the reward user ID associated with the user terminal 100.

  Thereby, when the target application is executed by the user terminal 100, the management server 200d (200c) associates the application ID of the executed target application, the application user ID in the executed target application, and the user terminal 100. It is possible to manage the associated reward user ID in association with it. That is, the management server 200d (200c) can manage the application user ID of each target application executed by the user terminal 100 in association with the reward user ID.

  When using user information as association information, using application user ID is an example, and it is not restricted to this. For example, the user information used as association information may be any information that can identify the user in the target application, and may be a user name, a user's nickname or handle name (alias), a user image, or the like.

(7) Further, the installation notification acquisition unit 241 (an example of the first information acquisition unit) of the management server 200 d associates the application ID (an example of identification information) of the target application (an example of the first application) with the user terminal 100 It may be obtained in association with the specified reward user ID (an example of unique identification information). Then, the installation information management unit 222 (an example of the information management unit) manages the application ID of the target application acquired by the installation notification acquisition unit 241 in association with the reward user ID associated with the user terminal 100.
Thereby, the management server 200d (200c) can manage which target application has been executed by the user terminal 100 based on the reward user ID and the application ID of the target application.

(8) Further, the management server 200d includes the reward processing unit 245. The reward processing unit 245 has a predetermined reward giving condition in a target application 10-5 or 10-6 (an example of a second application) of one or a plurality of target applications indicated by the application list (an example of the second information). When satisfied, a reward giving process is performed to give a reward to a user (for example, user X) who uses the user terminal 100. Here, the target applications 10-5 and 10-6 (an example of the second application) are target applications selected by the user terminal 100 from among one or a plurality of target applications indicated by the application list, for example.
Accordingly, when it is determined that the predetermined reward giving condition is satisfied, the management server 200d (200c) can give the target application 10-1 or 10-4 a predetermined reward.

The ninth embodiment
Next, a ninth embodiment of the present invention will be described. In the first embodiment, the customer sending source application 10 in which the SDK 11 (SDK 11A) is incorporated in the target application installed in the user terminal 100 sends the customer destination application 20 not installed in the user terminal 100. The example of the customer-sending process to the customer has been described. In the present embodiment, an example of customer sending processing for sending a customer to the customer sending application 20 from a dedicated application specialized for the function of the customer sending source instead of the customer sending source application 10 will be described.

[Overview of Mutual Customer Service System According to Ninth Embodiment]
FIG. 39 is an explanatory diagram for explaining the outline of the mutual customer sending system 500d of this embodiment. A network system 1d according to the present embodiment includes a management server 200 and a user terminal 100, as in the first embodiment. In FIG. 39, parts corresponding to the parts in FIG. 4 are assigned the same reference numerals and descriptions thereof will be omitted.

  The mutual customer feed system 500d shown in FIG. 39 has replaced the customer feed source application 10 with a dedicated application (hereinafter also referred to as a "dedicated application 60") having a function of customer feed to the customer feed destination application 20. The points are different with respect to the mutual customer delivery system 500 shown in FIG. The dedicated application 60 is provided, for example, from the application store 400 to the user terminal 100 so as to be installable (downloadable). In this figure, the dedicated application 60 is installed in the user terminal 100, and an example is shown in which customer sending from the dedicated application 60 to the customer sending destination application 20 is performed.

  The dedicated application 60 includes, for example, the functions of the SDK 11A described in the first embodiment. As described above, since the dedicated application 60 installed in the user terminal 100 has the function of the SDK 11A, in the mutual customer sending system 500 d, the customer sending processing from the customer sending source application 10 to the customer sending destination application 20 is performed. Similarly, the customer sending process can be performed on the customer sending destination application 20 from the dedicated application 60.

  Here, since the customer sending source is the dedicated application 60, the reward in the customer sending destination application 20 (game B) instead of the reward in the customer sending source is given to the user X as an example. The management server 200 transmits the reward granting information to the application server 320 corresponding to the customer sending destination application 20 (game B) as shown in (11A).

  For example, if it is a normal time when the customer sending application 20 (game B) is not in a campaign, the management server 200 determines that the customer sending application 20 (game B) is installed on the user terminal 100, The reward granting information is transmitted to the application server 320 corresponding to the customer sending destination application 20 (game B). In addition, if the customer sending destination application 20 (game B) is in a campaign, the management server 200, for example, that the reward giving condition is satisfied in the customer sending destination application 20 (game B) installed on the user terminal 100 When the reward granting notification information indicating “A” is acquired, the reward granting information is transmitted to the application server 320 corresponding to the customer sending destination application 20 (game B).

  It should be noted that the customer destination application 20 (game B) is in a campaign, the customer destination application 20 is participating in the same campaign with the customer originator (here, the dedicated application 60) and the campaign It may be medium, or the customer destination application 20 may independently participate in the campaign and be in the campaign.

[Functional Configuration of User Terminal 100 (Dedicated Application 60) According to Ninth Embodiment]
FIG. 40 is a configuration diagram showing an example of a functional configuration of a customer-sending process performed by the terminal control unit 150 based on the dedicated application 60 in the user terminal 100 according to the present embodiment.
The dedicated application 60 includes an initialization processing unit 101, a list request unit 104, a display control unit 105, and a customer information information notification unit 106. Here, the dedicated application 60 only needs to have at least the functional configuration as the customer sending source (for example, the functional configuration of the SDK 11A) among the functional configurations of the SDK 11 shown in FIG. It is not necessary to provide the unique reward provision notification unit 107.
The dedicated application 60 may be configured to incorporate the SDK 11A.

  With this configuration, the dedicated application 60 transmits, to the management server 200, customer-sending information for the customer-sending application 20 selected from the list LT of the target applications, similarly to the customer-sending application 10 incorporating the SDK 11A. Processing can be performed.

  Also, the dedicated application 60 does not become an application of a customer destination. Therefore, the management server 200 may not manage whether or not the dedicated application 60 is installed in the user terminal 100. Therefore, since the dedicated application 60 does not have to transmit the installation notification information to the management server 200, the configuration may be such that the installation notification unit 103 shown in FIG. 40 is not provided.

[Operation example of mutual customer sending processing of the ninth embodiment]
Next, the operation of customer feed processing by the mutual customer feed system 500d according to the present embodiment will be described. The customer-sending process by the mutual customer-sending system 500d is the same process as the customer-sending process according to the first embodiment described with reference to FIG. be able to.

  Note that the customer feed process by the mutual customer feed system 500d may be partially different from the customer feed process according to the first embodiment. For example, as described above, since the dedicated application 60 is a customer sending source, the management server 200 may not manage whether or not the dedicated application 60 is installed.

  FIG. 41 is a flowchart showing an example of the operation of the customer sending process according to the present embodiment. The example shown in FIG. 41 is an example in which the dedicated application 60 executes the processing executed by the customer feed source application 10 shown in FIG. 14 instead of the customer feed source application 10, and the dedicated application 60 This is an example in which the management server 200 does not manage whether or not it is installed. In FIG. 41, parts corresponding to the respective processes shown in FIG. 14 are given the same reference numerals, and the description thereof will be omitted as appropriate.

  When the dedicated application 60 is installed in the user terminal 100 and activated, the initialization processing unit 101 of the dedicated application 60 executes an initialization process. The initialization process shown in this figure is a process of acquiring a reward user ID, and a process of transmitting installation notification information to the management server 200 is not performed. For example, in the initialization process, the unique identification information acquiring unit 102 of the dedicated application 60 refers to the terminal storage unit 140 and determines whether or not the reward user ID has been acquired (step SA13). Then, if the unique identification information acquisition unit 102 does not acquire the reward user ID, the unique identification information acquisition unit 102 generates and acquires the reward user ID (step SA14), and stores it in the inter-application shared area of the terminal storage unit 140 (step SA15). ), End the initialization process.

  That is, when any target application is installed before the dedicated application 60 is installed, the reward user ID acquired when the target application is installed is used in the mutual customer delivery system 500d. . On the other hand, if any target application is not installed before the dedicated application 60 is installed, the reward user ID used in the mutual customer sending system 500d is acquired when the dedicated application 60 is installed and started. Be done.

  The processing after the above-described initialization processing is the same as the processing described with reference to FIG. 14, and the customer-sending information sent to the customer-sending destination application 20 is transmitted from the dedicated application 60 to the management server 200 . Therefore, in the mutual customer sending system 500d according to the present embodiment, the management server 200 records the customer sending information for the customer sending destination application 20 as in the first embodiment by making the dedicated application 60 the customer sending source. It can be managed.

  In the present embodiment, since the customer feed source is the dedicated application 60, it is not necessary to specify the customer feed source, for example, when a reward for the customer feed source is not given. Therefore, in the present embodiment, the customer ID information may not include the application ID of the dedicated application 60 for identifying the customer origin, and at least the application ID (Ap ID of the customer destination application 20 (game B)). And a reward user ID (Reward UID).

  As described above, in the first embodiment, the mutual customer feed system 500d according to the present embodiment performs the customer feed process for the customer destination application 20 from the dedicated application 60 using the dedicated application 60 as a customer feed source. Similar to the mutual customer delivery system 500 described above, it is possible to send customers to the customer destination application 20. In addition, in the case of the customer sending process to the customer sending destination application 20 from the dedicated application 60, the customer sending destination application 20 can be a customer sending source, but the dedicated application 60 never becomes a customer sending destination. Therefore, with regard to the dedicated application 60, the processing is one-way customer sending processing to the customer sending destination application 20.

In addition, the structure which makes exclusive customer 60 by this embodiment a customer origin can be applied also to said 2nd-9th embodiment.
For example, in the second embodiment, based on a request from the dedicated application 60 installed in the user terminal 100, the management server 200 determines, based on a predetermined condition, a target application to be included in the application list to be transmitted to the user terminal 100. A process of selecting (filtering) may be performed.

  In the third to fifth embodiments, the target application 10A shown in FIG. 18 may be a dedicated application specialized to the function of the customer sending source. In the sixth embodiment, the target application 10A shown in FIG. 30 may be a dedicated application specialized for the function of the customer sending source. For example, like the dedicated application 60, the dedicated application described above may be configured to have at least only a functional configuration as a customer sending source. Therefore, for example, the dedicated application described above may have a configuration in which the reward provision notifying unit 107 unique as the functional configuration of the customer destination is removed from the functional configuration of the SDK 1011 illustrated in FIG. In addition, for example, the dedicated application described above may be configured by removing the reward provision notifying unit 107 which is unique as the functional configuration of the customer destination from the functional configuration of the SDK 2011 illustrated in FIG. Further, for example, the dedicated application described above may be configured by removing the reward provision notifying unit 107 unique as the functional configuration of the customer destination from the functional configuration of the SDK 3011 illustrated in FIG. The dedicated application described above may have a configuration in which the installation notification unit 103 is removed as in the case of the dedicated application 60.

In the seventh and eighth embodiments, the dedicated application 60 may be installed in the user terminal 100.
For example, in the seventh embodiment, based on a request from the dedicated application 60 installed in the user terminal 100B after model change, the management server 200c performs the user terminal 100B after model change and the user terminal 100A before model change. An application list indicating at least one target application for which the installation notification information has not been acquired may be transmitted to the user terminal 100B. In this case, the management server 200c is installed in both the user terminal 100B after model change and the user terminal 100A before model change, for example, according to the second extraction method described in the seventh embodiment described above. The reward user ID of the user terminal 100B after the model change may be associated with the reward user ID of the user terminal 100A before the model change by using the application user ID in the target application.
Further, in the eighth embodiment, when the reward user ID corresponding to the user terminal 100 is changed, the management server 200 d determines the reward user ID based on the request from the dedicated application 60 installed in the user terminal 100. An application list indicating at least one target application for which installation notification information has not been obtained either after the change or before the change of the reward user ID may be transmitted to the user terminal 100. In this case, the management server 200d transmits the installation notification information both after the change of the reward user ID and before the change of the reward user ID according to, for example, the second extraction method described in the eighth embodiment. The changed reward user ID may be associated with the pre-change reward user ID by using the application user ID in any of the target applications.

[Supplementary note]
One aspect of the present invention is a reward giving method in a user terminal in which a first application and a second application can be installed, wherein the user terminal performs a predetermined operation related to the second application in the user terminal Sending to the server a reward request including a second user identifier different from the first user identifier identifying the user in the first application, and based on the reward request, the second user identifier Receiving from the server a reward of the first application to a corresponding user identified by the first user identifier.

Further, one aspect of the present invention is a reward provision method in a user terminal in which a first application and a second application having a user identifier different from the first application can be installed, wherein the user terminal is Sending a reward request including a second user identifier identifying the user in the second application to the server when a predetermined operation related to the second application is performed; and the second request based on the reward request. Receiving from the server a grant of a reward in the first application to a user identified by a first user identifier identifying the user in the first application, corresponding to a user identifier. It is a reward giving method.
The second application may have a different system of user identifiers from the first application.

  Further, one aspect of the present invention is a reward provision method in a user terminal in which a first application and a second application having a user identifier different from the first application can be installed, wherein the user terminal is the user terminal Sending a reward request including a second user identifier identifying the user in the second application to the server when a predetermined operation related to the second application is performed; and the second request based on the reward request. Receiving from the server a grant of a reward in the first application to a user identified by a first user identifier identifying the user in the first application, corresponding to a user identifier. It is a reward giving method.

  Further, one aspect of the present invention is a reward giving method in a user terminal capable of installing a first application for news and a second application having a user identifier different from the first application, wherein the user terminal is the user terminal Sending a reward request including a second user identifier identifying the user in the management of the reward to the server, when the predetermined operation related to the second application is performed, and the second request based on the reward request. Receiving from the server a grant of a reward in the first application to a user identified by a first user identifier identifying the user in the first application, corresponding to a user identifier. It is a reward giving method.

  Further, according to one aspect of the present invention, in the reward giving method, the server stores identifier correspondence information in which the first user identifier and the second user identifier are associated, and the identifier correspondence information The reward may be received from the server on the basis of.

  Further, according to one aspect of the present invention, in the above-described reward giving method, when the information indicating the second application to be displayed in the first application is selected, the user terminal transmits the first user to the server. A notification that can identify an identifier may be sent to install the second application.

  Further, according to one aspect of the present invention, in the reward giving method, when the user terminal transmits the reward request to the server within a predetermined period, the reward may be received from the server.

  Moreover, one aspect of the present invention is a user terminal in which a first application and a second application can be installed, and when a predetermined operation related to the second application is performed, the user is identified in the first application Sending a reward request including a second user identifier different from the first user identifier to the server, and based on the reward request, identified by the first user identifier corresponding to the second user identifier It is a user terminal which receives grant of the remuneration in said 1st application to a user from said server.

  Further, according to one aspect of the present invention, in the case where a predetermined function related to the second application is performed in the user terminal on a computer that functions as a user terminal in which the first application and the second application can be installed, Transmitting to the server a reward request comprising a second user identifier different from a first user identifier identifying a user in one application, and corresponding to the second user identifier based on the reward request, Receiving a reward from the server for the user identified by the one user identifier from the server.

  Further, one aspect of the present invention is a reward granting method in a server capable of communicating with a user terminal in which the first application and the second application can be installed, wherein the server is the second application in the user terminal. Receiving a reward request including a second user identifier different from a first user identifier identifying the user in the first application, when the predetermined operation is performed; and, based on the reward request, Providing a reward in the first application to the user identified by the first user identifier, which corresponds to the user identifier in the above.

  Further, one aspect of the present invention is a server capable of communicating with a user terminal in which the first application and the second application can be installed, and in the case where the predetermined operation related to the second application is performed in the user terminal Receiving a reward request including a second user identifier different from a first user identifier identifying a user in the first application, the first application corresponding to the second user identifier based on the reward request A server for giving a reward in the first application to a user identified by a user identifier of

  Further, according to an aspect of the present invention, a predetermined function of the second application is performed in the user terminal in a computer that functions as a server capable of communicating with the user terminal in which the first application and the second application can be installed. Receiving a reward request including a second user identifier different from the first user identifier identifying the user in the first application, and corresponding to the second user identifier based on the reward request Providing a reward in the first application to the user identified by the first user identifier.

<Modification of First to Ninth Embodiment>

  Although the embodiments of the present invention have been described in detail with reference to the drawings, the specific configuration is not limited to the above-described embodiments, and includes design and the like within the scope of the present invention. For example, the respective functions described in the first to ninth embodiments described above can be arbitrarily combined. In the following description, the management servers 200, 200a, 200b, 200c, and 200d will be simply described as "management server 200" unless otherwise specified.

(1) In the above embodiment, the communication unit 210 (an example of a transmitting / receiving unit) of the management server 200 includes installation notification information (an example of first information), an application list (an example of second information, an example of application notification information), List request notification information, customer sending information (for example, customer sending source information or customer sending destination information), instruction information (an example of information for displaying an installable screen on the user terminal 100), or reward giving notification information directly An example of communication with the user terminal 100 has been described. Similarly, the terminal communication unit 130 (transmission / reception unit) of the user terminal 100 directly communicates the installation notification information, the application list, the list request notification information, the customer referral information, the instruction information, or the reward provision notification information with the management server 200. An example has been described.

  Here, the communication unit 210 (transmission / reception unit) of the management server 200 corresponds to the customer sending source application 10 (an example of the first application) or the customer sending destination application 20 (an example of the second application). After establishing the communication session via (an example of the server apparatus), the user terminal 100 may directly communicate with it. Similarly, the terminal communication unit 130 (transmission / reception unit) of the user terminal 100 corresponds to the customer sending application 10 (target application installed) or the customer sending application 20 (selected target application), and the application server 300 corresponding thereto. After establishing a communication session, the communication with the management server 200 may be directly performed.

When the user terminal 100 directly communicates with the management server 200, a communication session may be established as needed. That is, both the case of directly communicating with the management server 200 before establishing the communication session and the case of communicating directly with the management server 200 after establishing the communication session may be included.
For example, the installation notification information may directly communicate with the management server 200 before establishing a communication session, and may communicate directly with the management server 200 after establishing a communication session for other information. Good. By doing this, an application that does not have the application server 320 corresponding to the customer destination application 20 as the customer destination application 20 that is normally targeted for reward, that is, an application that operates in a standalone mode in the user terminal 100 It becomes possible to treat as. That is, when transmitting installation notification information indicating that a standalone application is installed, the user terminal 100 directly manages the communication server without establishing a communication session via the application server 300. It can communicate with the server 200.

  FIG. 17 is a flow chart for explaining the operation of communication session establishment processing. This communication session establishment process (communication session establishment process) is the case where the customer sending application 10 or the customer receiving application 20 is activated on the user terminal 100, and the SDKs 11A and 11B communicate with the management server 200 for the first time. For example, it is performed in the initialization processing described with reference to FIGS. 14 and 15. FIG. 17 shows a communication session establishment process performed in the initialization process shown in FIG. Note that this communication session establishment process can be performed similarly in the initialization process shown in FIG. In FIG. 17, parts corresponding to the respective processes in FIG. 14 are given the same reference numerals, and descriptions thereof will be omitted. The user terminal 100 and the application server 310 are assumed to have already established a communication session.

When the reward user ID has been acquired in the processing of steps SA12, SA13, SA14, and SA15, and the notification of installation notification information has been notified in the processing of steps SA16 and SA17, the initialization processing unit 101 of the SDK 11A acquires the one-time token. The requested one-time token acquisition request information is transmitted to the application server 310 (step SA21). When acquiring the one-time token acquisition request information from the user terminal 100 (SDK 11A), the application server 310 transmits one-time token generation request information based on the acquired one-time token acquisition request information to the management server 200 (step SF11). ). When the management server 200 acquires 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 SE12). When acquiring the one-time token from the management server 200, the application server 310 transmits the acquired one-time token to the user terminal 100 (SDK 11A) (step SF12). When acquiring the one-time token from the application server 310, the initialization processing unit 101 of the SDK 11A transmits session establishment request information including the acquired one-time token to the management server 200 (step SA22). When the management server 200 acquires session establishment request information from the user terminal 100 (SDK 11A), when the one-time token included in the acquired session establishment request information is correct information (sent to the user terminal 100 (SDK 11A) If it matches the one-time token), the communication session is established, and the communication by the mutual customer sending system 500 is permitted (step SE13). Thereafter, the process described with reference to FIG. 14 is performed. When 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 determines that a communication error occurs, and the communication by the mutual customer delivery system 500 is not permitted. Further, when the management server 200 can not acquire the session establishment request information from the user terminal 100 (SDK 11A), naturally, the communication by the mutual customer delivery system 500 is not permitted.
Thus, after establishing a communication session, by starting communication by the mutual customer referral system 500, security in the network system 1 including the mutual customer referral system 500 can be improved.

  Note that installation notification information (an example of first information), application list (an example of second information, an example of application notification information), list request notification information, customer referral information (for example, customer origin information or customer destination information) , Instruction information (an example of information for displaying the installable screen on the user terminal 100), or a part of the reward giving notification information, without directly communicating with the management server 200 from the user terminal 100; It may communicate with the user terminal 100 via the application server 300 (an example of a server apparatus) corresponding to the source application 10 (an example of a first application) or the customer sending application 20 (an example of a second application). That is, the communication unit 210 (transmission / reception unit) of the management server 200 transmits the installation notification information, the application list, the list request notification information, the customer sending information, the instruction information, or the reward giving notification information to the customer sending source application 10 or the customer sending destination application. The application server 300 may communicate with the user terminal 100 via the application server 300 corresponding to 20, or directly communicate with the user terminal 100.

Furthermore, the communication unit 210 (an example of the transmission / reception unit) of the management server 200 transmits the installation notification information, the application list, the list request notification information, the customer referral information, the instruction information, or the reward provision notification information You may communicate with the user terminal 100 via the application server 300 corresponding to the destination application 20. Similarly, the terminal communication unit 130 (transmission and reception unit) of the user terminal 100 transmits the customer sending application 10 (target application installed) or the application server 300 corresponding to the customer sending application 20 (selected target application). It may communicate with the management server 200.
Thus, in the mutual customer feed system 500, even when the user terminal 100 and the management server 200 communicate via the application server 300, the same customer feed processing and reward as in the first and second embodiments. Processing can be performed and similar effects can be obtained.

(2) In the above embodiment, an example in which the management server 200 is transmitted from the user terminal 100 (SDK 11) by including the application user ID (ApUID) in the installation notification information or the like has been described, but the present invention is not limited thereto. For example, the application server 300 may transmit the application user ID to the management server 200 in association with the reward user ID in the communication session establishment process. Specifically, at step SA21, when transmitting the one-time token acquisition request information to the application server 300, the initialization processing unit 101 of the SDK 11A notifies the application server 300 of the reward user ID. Furthermore, the application server 300 transmits the reward user ID, the application ID, and the application user ID to the management server 200. The installation information management unit 222 of the management server 200 sets, as an application user ID (ApUID) corresponding to installation information corresponding to the acquired reward user ID and application ID among the installation information stored in the installation information storage unit 236, The application user ID acquired from the application server 300 is stored. As described above, by transmitting the application user ID not from the user terminal 100 (SDK 11) but from the application server 300, it becomes unnecessary to manage the application user ID in the user terminal 100 (SDK 11).

  As described above, when the application server 300 transmits the application user ID to the management server 200 in association with the reward user ID in the communication session establishment process, the communication is performed only after the user information is registered in the installed target application. Session establishment processing can not be performed. However, the transmission of installation notification information indicating the installation of the target application installed in the user terminal 100 to the management server 200 does not have to be directly related to the user information being registered. Therefore, the user terminal 100 transmits installation notification information to the management server 200 regardless of whether user information is registered or not in the installed target application. Therefore, when the user terminal 100 transmits the installation notification information, it is transmitted before the communication session is established.

(3) In the above embodiment, an example in which the reward processing unit 245 executes the CP reward processing based on the fact that the reward granting notification information is acquired from the SDK 11B of the customer destination application 20 of the user terminal 100 has been described It is not limited to For example, the CP reward process may be executed based on the fact that the reward giving notification information has been acquired from the application server 320 corresponding to the customer sending destination application 20. In this case, the application ID of the customer sending destination application 20, the application user ID, the campaign ID, and the result point ID (RewardSpot ID) may be included in the reward assignment notification information (result point arrival notification).
For example, the reward processing unit 245 of the management server 200 acquires the reward assignment notification information (result point arrival notification) transmitted from the application server 320. Next, the reward processing unit 245 identifies the installation information corresponding to the application ID and the application user ID of the customer sending destination application 20 from the installation information stored in the installation information storage unit 236, and corresponds to the specified installation information. Reverse reward user ID. Then, the reward processing unit 245 corresponds to the customer referral information based on the fact that the record of the customer referral information for the customer user application 20 and the reward user ID subjected to the reverse lookup is managed in the customer referral information management unit 223. It sets outcome point ID (RewardSpotID) included in the acquired reward giving notification information in association with reward management ID, generates reward establishment information that sets the establishment status (RewardStatus) to flag “0” (not notified), and rewards It is stored in the establishment information storage unit 238. The subsequent processing is the same as in the above embodiment. As described above, transmitting the reward assignment notification information (result point arrival notification) from the application server 320 can reduce the processing load on the user terminal 100 (SDK 11B).

(4) In the above embodiment, when the target application is installed for the first time, the reward user ID can uniquely identify the installed user terminal 100 (unique identification in the mutual customer sending system 500) Although the example produced | generated as information) was demonstrated, it is not restricted to this. For example, a terminal identification number or a telephone number (for example, in the case of a smartphone) uniquely set in the user terminal 100 may be used as the reward user ID. However, without using personal information such as a terminal identification number or a telephone number, it is possible to improve security by generating and using a reward user ID as in this embodiment. Also, by adopting unique unique identification information in the mutual customer sending system 500 without using a terminal identification number, a telephone number, etc. as the reward user ID, a user terminal 100 owned by the user (an example of a terminal device) Even when changing by replacement, etc., the condition from the user terminal 100 before the change is maintained and the mutual customer-sending system 500 is used by transferring to the user terminal 100 after the change of the reward user ID through a predetermined procedure. It is possible to

  Further, the process of displaying the application list page in step SA25 of FIG. 14 and the process of transmitting the customer information when the target application to be downloaded is selected from the application list are replaced with the process performed by the SDK 11, Another application (for example, a browser) installed in the user terminal 100 not related to the processing of may be activated and executed. For example, by generating data of an application list page which is redirected from the management server 200 to the browser in the user terminal 100 and transmitting it to the user terminal 100, the browser is started in the user terminal 100, and the application list page It may be displayed. In addition, by transmitting the data of the application list page including the application ID (ApID) of the customer sending source application 10 (game A) included in the list request notification information, the customer destination application selected on the application list page Management server from the above-mentioned browser of customer sending information including application ID (ApID) of 20 (game B), application ID (ApID) of customer sending source application 10 (game A), and reward user ID (RewardUID) It may be sent to 200.

Also, in the CP reward process, as in the normal reward process, the CP customer process may be executed based on the customer destination application 20 being installed. In this case, the reward giving condition in the customer sending destination application 20 may be that the customer sending destination application 20 is installed in the user terminal 100.
In addition, if it is assumed that installation of the customer destination application 20 is the first outcome point for all the specific applications that carry out the campaign, the customer destination application 20 of the reward giving notification information corresponding to the achievement of the outcome point. You do not need to send from. In this case, the management server 200 performs a reward giving process similar to that of the normal reward, and transmits reward giving information including the campaign ID to the application server 310, whereby the CP corresponding to the normal reward from the application server 310. Rewards will be rewarded. Specifically, without performing the determination process of step SE22 in the flowchart of FIG. 15, the process of steps SE23 to 24 may be performed for either the CP reward or the normal reward.

(5) In the above embodiment, the game has been described as an example of the target application corresponding to the mutual customer feed system 500. However, the target application is not limited to the game, and any application other than the game may be used. .

  In addition, the storage unit 230 of the management server 200 may be included in a server device different from the management server 200. Then, the management unit 220 of the management server 200 or the control unit 240 communicates with the storage unit 230 provided in a server apparatus different from the management server 200 via the network NW, whereby each unit included in the storage unit 230 stores You may manage each information you

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

  In the above embodiment, the SDK 1011 (2011, 3011) has been described as having the list request unit 104 and the list acquisition unit 109 as different configurations. However, the list request unit 104 includes the list acquisition unit 109 The unit 104 may function as the list acquisition unit 109. Although the SDK 1011 (2011, 3011) includes the installation notification unit 103 and the temporary installation notification unit 108 as different configurations, the installation notification unit 103 includes the temporary installation notification unit 108, and the installation notification unit 103 The temporary installation notification unit 108 may be configured.

  In the third and fourth embodiments, the case where the non-installed information acquisition unit 111 of the SDK 1011A transmits non-installed information request notification information including the reward user ID to the management server 200a has been described. It is not limited to For example, the non-installed information acquisition unit 111 may transmit non-installed information request notification information including the application ID of the target application to the management server 200 without including the reward user ID. In this case, the non-installed information notification unit 248 of the management server 200 extracts all the target applications other than the application ID of the target application among the target application information stored in the target application information storage unit 231, and extracts the target The application ID (ApID) corresponding to the application and the URL scheme (ApURI) may be transmitted to the user terminal 100 as uninstalled information.

(6) A recording medium that can be read by a computer for the program for realizing the functions of the management unit 220, the control unit 240 (240a, 240b, 240c, 240d), the SDK 11 (1011, 2011, 3011) or the dedicated application 60 described above. The above-described processing may be performed by causing the computer system to read and execute the program recorded on the recording medium. Here, "to read and execute the program recorded on the recording medium into the computer system" includes installing the program on the computer system. The “computer system” mentioned here includes an OS and hardware such as peripheral devices. Also, the “computer system” may include a plurality of computer devices connected via a network including communication lines such as the Internet, WAN, LAN, and dedicated lines. The term "computer-readable recording medium" refers to a storage medium such as a flexible disk, a magneto-optical disk, a ROM, a portable medium such as a ROM or a CD-ROM, or a hard disk built 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 internally or externally accessible from the distribution server for distributing 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 executable in the terminal device. That is, the format stored in the distribution server does not matter 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, and the configuration may be such that the terminal device integrates after being downloaded at different timings, or the distribution server that distributes each of the divided programs may be different. Furthermore, "computer-readable recording medium" holds a program for a certain period of time, such as a volatile memory (RAM) in a computer system serving as a server or a client when the program is transmitted via a network. We shall include things. Further, the program may be for realizing a part of the functions described above. Furthermore, it may be a so-called difference file (difference program) that can realize the above-described functions in combination with a program already recorded in the computer system.

  In addition, some or all of the functions described above may be realized as an integrated circuit such as LSI (Large Scale Integration). Each function mentioned above may be processor-ized separately, and part or all may be integrated and processor-ized. Further, the method of circuit integration is not limited to LSI's, and implementation using dedicated circuitry or general purpose processors is also possible. In the case where an integrated circuit technology comes out to replace LSI's as a result of the advancement of semiconductor technology, integrated circuits based on such technology may also be used.

  1, 1a, 1b, 1c, 1d network system, 10 customer origin application, 10A, 10B, 10C, 10-1, 10-2, 10-3, 10-4, 10-5, 10-6 target application, 11, 11A, 11B, 1011, 1011A, 2011, 2011A, 3011, 3011A SDK, 20 customer destination applications, 30 stores, 60 dedicated applications, 100 user terminals, 101 initialization processing unit, 102 unique identification information acquisition unit, 103 Installation notification unit, 104 list request unit, 105 display control unit, 106 customer sending information notification unit, 107 compensation grant notification unit, 108 temporary installation notification unit, 109 list acquisition unit, 110 input unit, 111 not installed information acquisition unit, 120 Display unit, 130 terminal communication unit, 140 terminal storage unit, 50 terminal control unit, 200, 200a, 200b, 200c, 200d management server, 210 communication unit, 220 management unit, 221 application management unit, 222 installation information management unit, 223 customer information management unit, 230 storage unit, 231 target application Information storage unit 232 Normal reward information storage unit 233 Inter-application filter storage unit 234 Campaign information storage unit 235 Campaign participation application information storage unit 236 Installation information storage unit 237 Customer referral information storage unit 238 Reward satisfaction information storage Parts, 240, 240a, 240b, 240c, 240d Control part, 241 Installation notification acquisition part, 242 List notification part, 243 Customer sending information acquisition part, 244 Installation guidance instruction part, 245 Reward processing part, 246 Timekeeping part, 247 Temporary installation notification acquisition unit, 248 not installed information notification unit, 249 other terminal information extraction unit, 249a information extraction unit, 300 application server, 310 application server (game A), 320 application server (game B), 400 application store, 500 , 500a, 500b, 500c, 500d mutual customer delivery system

Claims (11)

A reward giving method in a user terminal in which a first application and a second application having different registration or management of the first application and the user identifier can be installed,
The user terminal is
Sending to the server a reward request including a second user identifier identifying a user in the second application when a predetermined operation related to the second application is performed in the user terminal;
Receiving, from the server, a reward in the first application to a user identified by a first user identifier identifying the user in the first application corresponding to the second user identifier based on the reward request Step and
And a rewarding method characterized by including. A reward giving method in a user terminal in which a first application and a second application having different registration or management of the first application and the user identifier can be installed,
The user terminal is
Sending to the server a reward request including a second user identifier that can identify the user terminal or user when a predetermined operation related to the second application is performed in the user terminal;
Receiving, from the server, a reward in the first application to a user identified by a first user identifier identifying the user in the first application corresponding to the second user identifier based on the reward request Step and
And a rewarding method characterized by including. A reward giving method in a user terminal in which a first application and a second application having different registration or management of the first application and the user identifier can be installed,
The user terminal is
Sending to the server a reward request including a second user identifier identifying the user in the management of the reward when a predetermined operation related to the second application is performed in the user terminal;
Receiving, from the server, a reward in the first application to a user identified by a first user identifier identifying the user in the first application corresponding to the second user identifier based on the reward request Step and
And a rewarding method characterized by including.   Claim: The server stores identifier correspondence information in which the first user identifier and the second user identifier are associated, and receives the reward from the server based on the identifier correspondence information. The reward giving method according to any one of claims 1 to 3.   When the user terminal selects information representing the second application displayed in the first application, the user terminal transmits a notification capable of identifying the first user identifier to the server, and the second application The reward giving method according to any one of claims 1 to 4, which is installed.   The reward granting method according to any one of claims 1 to 5, wherein, when the user terminal transmits the reward request to the server within a predetermined period, grant of the reward is received from the server. A user terminal capable of installing a first application and a second application that differs in registration or management of the first application and the user identifier,
When a predetermined operation related to the second application is performed, a reward request including a second user identifier identifying a user in the second application is transmitted to the server,
Receiving, from the server, a reward in the first application to a user identified by a first user identifier identifying the user in the first application corresponding to the second user identifier based on the reward request ,
User terminal. A computer that functions as a user terminal capable of installing a first application and a second application that differs in registration or management of the first application and the user identifier,
Sending to the server a reward request including a second user identifier identifying a user in the second application when a predetermined operation related to the second application is performed in the user terminal;
Receiving, from the server, a reward in the first application to a user identified by a first user identifier identifying the user in the first application corresponding to the second user identifier based on the reward request Step and
Reward grant program to carry out. A reward granting method in a server capable of communicating with a user terminal capable of installing a first application and a second application having different registration or management of the first application and the user identifier,
The server
Receiving a reward request including a second user identifier identifying a user in the second application when a predetermined operation related to the second application is performed in the user terminal;
Providing a reward in the first application to a user identified by a first user identifier identifying the user in the first application, corresponding to the second user identifier, based on the reward request;
And a rewarding method characterized by including. A server capable of communicating with a user terminal in which a first application and a second application having different registration or management of the first application and the user identifier can be installed,
When a predetermined operation related to the second application is performed in the user terminal, a reward request including a second user identifier identifying a user in the second application is received,
Providing a reward in the first application to a user identified by a first user identifier identifying the user in the first application corresponding to the second user identifier based on the reward request;
server. A computer functioning as a server capable of communicating with a user terminal capable of installing a first application and a second application having different registration or management of the first application and the user identifier
Receiving a reward request including a second user identifier identifying a user in the second application when a predetermined operation related to the second application is performed in the user terminal;
Providing a reward in the first application to a user identified by a first user identifier identifying the user in the first application, corresponding to the second user identifier, based on the reward request;
Reward grant program to carry out.

Images