JP6260857B2 - Management device, management method, and program - Google Patents

Description

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

  An application is installed on a user terminal such as a smartphone and the content of the application is enjoyed. Such an application is registered so that it can be downloaded to, for example, a store site that sells the application or a dedicated site for each application. Then, the user can download a desired application from these sites and install it on his user terminal.

  In addition, an advertisement (banner) of an application that has not yet been installed is displayed on a display screen that is displayed while using the application installed on the user terminal, and the store site described above when the advertisement (banner) is selected. If the selected application is downloaded and installed on the user's terminal after that, the advertisement (banner) that triggered the download is displayed to the original application provider (advertiser) In contrast, there is a reward advertising system in which a reward is given to the user's own use of the original application (see, for example, Patent Document 1).

Japanese Patent No. 5107455

  According to the reward advertisement system as described above, the provision of a reward serves as a motivation for sending customers between applications, and can lead to promotion of sales of applications. Therefore, a system for sending customers between more convenient applications is desired.

  The present invention has been made in view of such a situation, and provides a management device, a management method, and a program capable of improving the convenience of customers between applications.

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

  In order to solve the above-described problem, an aspect of the present invention provides an application management unit that manages information related to a first period set for a plurality of specific applications among a plurality of target applications to be managed. (221) and when one of the plurality of target applications is executed by the terminal device (100), the terminal device transmits the target application in response to the execution of the target application. A first information acquisition unit (241) that acquires the first information, and a request based on a first application executed by the terminal device among the plurality of target applications, thereby receiving the first information from the terminal device. Contains information indicating at least one target application for which information has not been acquired. The second information notification unit (242) that transmits the second information to the terminal device, and the second information transmitted from the second information notification unit in response to the transmission of the second information. When the first period is set for the second application among the target applications to be executed, the second application is executed or executable by the terminal device within the first period When the reward application process is performed based on the state, and the first period is not set for the second application, the second application is executed or executed by the terminal device A management device (200), comprising: a reward processing unit (245) that performs the reward granting process based on a possible state.

  Further, according to one aspect of the present invention, in the management device, when the reward processing unit has the first period set for the second application, the second application is the first application. A first reward giving process is performed as the reward giving process when the terminal device has been executed or is in an executable state within a period.

  Further, according to one aspect of the present invention, in the management device, when the reward processing unit has the first period set for the second application, the second application is the first application. Based on having been executed by the terminal device within a period or being in an executable state, and that the reward granting condition set in the second application has been satisfied, It is characterized by a reward giving process.

  Further, according to one aspect of the present invention, in the management device, when the reward processing unit does not set the first period for the second application, the second application is executed by the terminal device. A second reward granting process is performed as the reward granting process when executed or in an executable state.

  Further, according to one aspect of the present invention, in the management device, when the reward processing unit does not set the first period for the second application, the second application is executed by the terminal device. Performing the second reward granting process as the reward granting process based on being executed or in an executable state and satisfying the reward granting conditions set in the second application. Features.

  Further, according to one aspect of the present invention, in the management device, the reward processing unit satisfies the reward granting condition based on the satisfaction of the reward granting condition set in the second application. The reward granting process based on the obtained reward grant notification information is acquired when the reward grant notification information indicating the second grant executed by the terminal device or the server device corresponding to the second application is acquired. It is characterized by doing.

  Further, according to one aspect of the present invention, in the management device, even when the reward processing unit has the first period set for the second application, the second application is the first application. The second reward granting process is performed when it is executed outside the period or when it becomes executable.

  Further, according to one aspect of the present invention, in the management device, when the reward processing unit acquires the first information corresponding to the second application, the second application acquires the first information. It is characterized by determining that it was executed by the terminal device.

  In addition, according to an aspect of the present invention, in the management device, the reward processing unit has a timing at which the first information acquisition unit acquires the first information corresponding to the second application within the first period. According to whether or not there is, it is determined whether the second application is executed by the terminal device within the first period or outside the first period.

  Further, according to one aspect of the present invention, in the management device, the application management unit may set a setting-side application that sets prohibition of posting based on the second information, and a posting based on the second information in the setting-side application The first posting prohibition information associated with the prohibited application to be set is managed, and the second information notification unit refers to the first posting prohibition information managed by the application management unit, If there is the first posting prohibition information in which the first application is set as the set-side application, the remaining information obtained by removing information indicating the setting-side application from the second information is stored in the terminal device. It is characterized by transmitting to.

  Further, according to an aspect of the present invention, in the management device, the second information notification unit refers to the first posting prohibition information managed by the application management unit, and sets the first application. When there is first posting prohibition information set in the side application, the remaining information obtained by removing the information indicating the set side application from the second information is transmitted to the terminal device. And

  Further, according to one aspect of the present invention, in the management device, the application management unit manages second posting prohibition information in which a set-side application prohibited from posting based on the second information is registered, The second information notification unit refers to the second posting prohibition information managed by the application management unit, and sets the set-side application and the first application indicated by the second posting prohibition information. On the other hand, when the first period is not set, the second information excluding information indicating the set-side application is transmitted to the terminal device.

  Further, according to one aspect of the present invention, there is provided a first reward granted process performed by the management device as the reward grant process when the first period is set for the second application. A first reward information management unit (221) that manages information indicating a link destination of a posting location of information indicating one reward, each of the plurality of target applications, and when the first period is not set A second reward information management unit (221) for managing second reward information in association with information indicating the second reward granted by the second reward granting process performed as the reward granting process, The second information notifying unit includes information indicating a target application for which the first period is not set with the first application among the plurality of target applications. The second information associated with information indicating a reward is transmitted to the terminal device, while the first period is set with the first application among the plurality of target applications. The information indicating the target application is characterized in that the second information associated with the information indicating the link destination is transmitted to the terminal device.

  Further, according to one aspect of the present invention, the management device acquires a customer information acquisition unit (243) that acquires customer information indicating customer transmission to the second application, and the customer information acquisition unit acquires the customer information. A customer information management unit (223) for managing customer information, and when the reward processing unit is executed by the terminal device or is in an executable state, the reward processing unit The reward granting process is executed on condition that the customer information corresponding to the second application is managed by the customer information management unit.

  Further, according to one aspect of the present invention, the management device acquires a customer information that indicates customer transmission to the second application, and the customer information acquired by the customer information acquisition unit. A customer information management unit that manages the customer information, and when the reward processing unit satisfies the reward granting condition set in the second application, the customer information corresponding to the second application is The reward granting process is executed on the condition that it is managed by the customer information management unit.

  Further, according to one aspect of the present invention, in the management device, the customer information management unit associates the identification information of the second application with the unique identification information associated with the terminal device. It is managed as a record.

  Further, according to an aspect of the present invention, in the management device, the customer information management unit manages the identification information of the second application as a record of the customer information in association with the identification information of the first application. It is characterized by that.

  Further, according to one aspect of the present invention, in the management device, the customer information acquisition unit includes, as the customer information, unique identification information associated with the terminal device, identification information of the first application, and the Acquired in association with the identification information of the second application, and the customer information management unit acquires the unique identification information associated with the customer information, the identification information of the first application, and the identification information of the second application Are associated and managed as a record of the customer information.

  According to another aspect of the present invention, the management device can install the second application based on identification information of the second application associated with the customer information acquired by the customer information acquisition unit. A screen information notification unit (244) for transmitting information for displaying a screen on the terminal device to the terminal device is provided.

  Further, according to one aspect of the present invention, in the management device, the reward processing unit is configured to set another period that does not overlap with the first period for some or all of the plurality of specific applications. In the case where the reward granting process corresponding to the first period set in the second application has already been performed in the terminal device, the reward granting process corresponding to the different period is not performed. Features.

  Further, according to one aspect of the present invention, in the management device, the reward processing unit performs the first reward granting as the reward granting process when the first period is set for the second application. If at least one of the process and the second reward granting process performed as the reward granting process when the first period is not set has been performed in the terminal device, the other reward granting process It is characterized by not doing.

  According to another aspect of the present invention, an application management unit that manages information related to a first period set for a plurality of specific applications among a plurality of target applications to be managed; and the plurality of target applications When the target application is executed by the terminal device, the first information transmitted from the terminal device in response to the target application being executed by the terminal device is associated with the terminal device. The first information acquisition unit acquired from the terminal device and the first information acquired by the first information acquisition unit in association with the identified unique identification information and the identification information of the executed target application. First information that manages the unique identification information and the identification information of the target application in association with each other. A request based on a first application executed by the terminal device among the plurality of target applications with reference to a management unit, the application management unit, and the first information management unit; A second information notifying unit that transmits to the terminal device second information including information indicating at least one target application that has not acquired the first information; and the second information notifying unit transmits the second information. In response, the identification information of the second application among the target applications indicated by the second information transmitted from the second information notification unit, the identification information of the first application, and the terminal device The transmission from the first application to the second application is associated with the unique identification information. A customer information acquisition unit acquired from the terminal device as customer information indicating the second application, and the second application based on identification information of the second application associated with the customer information acquired by the customer information acquisition unit The first period is set for the second application selected by the terminal device and a screen information notifying unit that transmits information for causing the terminal device to display a screen on which the terminal device can be installed. The second application has been executed by the terminal device within the first period or has become executable, and the reward set in correspondence with the second application. The unique identification information associated with the terminal device and the identification information of the second application based on the fulfillment condition being satisfied Is acquired from the server application corresponding to the second application or the second application executed by the terminal device, based on the acquired reward grant notification information, Reward grant processing for transmitting reward grant information associated with user information of the first application associated with unique identification information to the first application executed by the terminal device or a server device corresponding to the first application. And when the first period is not set for the second application selected by the terminal device, the second application has been executed by the terminal device or is in an executable state. A reward processing unit for performing the reward granting process based on A management apparatus, characterized in that it comprises.

  One embodiment of the present invention is a management method in a management apparatus, the step of managing information related to a first period set for a plurality of specific applications among a plurality of target applications to be managed. And when one of the plurality of target applications is executed by the terminal device, the first information transmitted from the terminal device in response to the execution of the target application by the terminal device And obtaining at least one target application that has not acquired the first information from the terminal device by receiving a request based on a first application executed by the terminal device among the plurality of target applications. Transmitting second information including information to the terminal device When the first period is set for the second application among the target applications indicated by the transmitted second information in response to the transmission of the second information, Remuneration processing is performed based on the second application being executed by the terminal device within the first period or being in an executable state, and the first period is applied to the second application. Is not set, the reward application process is performed based on the fact that the second application is executed by the terminal device or is in an executable state. It is a management method.

  One embodiment of the present invention is a management method in a management apparatus, the step of managing information related to a first period set for a plurality of specific applications among a plurality of target applications to be managed. And when one of the plurality of target applications is executed by the terminal device, the first information transmitted from the terminal device in response to the execution of the target application by the terminal device A step of acquiring from the terminal device in association with the unique identification information associated with the terminal device and the identification information of the executed target application, and the unique identification associated with the acquired first information. Managing information and the identification information of the target application in association with each other Second information including at least one target application that has not acquired the first information from the terminal device by receiving a request based on a first application executed by the terminal device among the plurality of target applications; A step of transmitting information to the terminal device; and in response to transmitting the second information, identification information of a second application among the target applications indicated by the transmitted second information, the first Obtaining from the terminal device as customer information indicating customer-sending from the first application to the second application in association with the identification information of the application and the unique identification information associated with the terminal device; The second application associated with the acquired customer information. Transmitting to the terminal device information for causing the terminal device to display a screen on which the second application can be installed based on the identification information of the application, and for the second application selected by the terminal device When the first period is set, the second application has been executed by the terminal device within the first period or has become executable, and the second application Based on the fact that the reward granting conditions set in response to the above are satisfied, the reward grant notification information associated with the unique identification information associated with the terminal device and the identification information of the second application, The second application executed by the terminal device or a server device corresponding to the second application. When obtained, the reward grant information associated with the user information of the first application associated with the unique identification information is executed by the terminal device based on the acquired reward grant notification information. When the reward granting process to be transmitted to the server device corresponding to one application or the first application is performed and the first period is not set for the second application selected by the terminal device, And a step of performing the reward granting process based on the fact that the second application is executed by the terminal device or is in an executable state.

  According to another aspect of the present invention, a step of managing information related to a first period set for a plurality of specific applications among a plurality of target applications to be managed in the computer; When any target application of the applications is executed by the terminal device, obtaining the first information transmitted from the terminal device in response to the target application being executed by the terminal device; Second information including information indicating at least one target application that has not acquired the first information from the terminal device by receiving a request based on a first application executed by the terminal device among a plurality of target applications. Transmitting to the terminal device; and When the first period is set for the second application among the target applications indicated by the transmitted second information in response to transmitting the information, the second application When the reward granting process is performed based on being executed by the terminal device or in an executable state within the first period, and the first period is not set for the second application Is a program for executing the reward granting process based on the fact that the second application has been executed by the terminal device or has entered an executable state.

  According to another aspect of the present invention, a step of managing information related to a first period set for a plurality of specific applications among a plurality of target applications to be managed in the computer; When any target application of the applications is executed by the terminal device, the first information transmitted from the terminal device in response to the target application being executed by the terminal device corresponds to the terminal device. A step of acquiring from the terminal device in association with the attached unique identification information and the identification information of the executed target application, the unique identification information associated with the acquired first information, and the target application Managing the identification information in association with each other, and Second information including information indicating at least one target application that has not acquired the first information from the terminal device by receiving a request based on a first application executed by the terminal device of the application. In response to transmitting the second information to the device, the identification information of the second application among the target applications indicated by the transmitted second information, the identification information of the first application And acquiring from the terminal device as customer information indicating customer transmission from the first application to the second application in association with the unique identification information associated with the terminal device, and the acquired Identification information of the second application associated with customer information A step of transmitting information for causing the terminal device to display a screen on which the second application can be installed based on the second application selected by the terminal device; When a period is set, the second application is executed by the terminal device within the first period or is in an executable state, and is set corresponding to the second application The terminal device executes the reward grant notification information associated with the unique identification information associated with the terminal device and the identification information of the second application based on the fulfillment of the granted reward granting condition. The second application or the server device corresponding to the second application, Based on the acquired reward grant notification information, the reward application information associated with the user information of the first application associated with the unique identification information is the first application executed by the terminal device or the first application. When the reward application processing to be transmitted to the server device corresponding to the application is performed and the first period is not set for the second application selected by the terminal device, the second application is the terminal And a step of executing the reward granting process based on being executed by the apparatus or being in an executable state.

  As described above, according to the present invention, it is possible to improve the convenience of sending customers between applications.

It is explanatory drawing explaining the outline | summary of the mutual customer-delivery system of 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 explanatory drawing explaining an example of a structure and process of a mutual customer-delivery system of this embodiment. It is a block diagram which shows an example of the function structure performed based on SDK of the user terminal by this embodiment. It is a block diagram which shows an example of a structure of the management server by 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 information storage part. It is a figure which shows an example of the information memorize | stored in the reward formation information storage part. It is a 1st flowchart which shows an example of the operation | movement of a mutual customer transmission process by this embodiment. It is a 2nd flowchart which shows an example of the operation | movement of a mutual customer transmission process 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 flowchart explaining the operation | movement of the establishment process of a communication session. It is explanatory drawing explaining the outline | summary of the mutual customer-delivery system of 3rd Embodiment. It is a block diagram which shows an example of the 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 flowchart which shows an example of operation | movement of the mutual customer-delivery system by 3rd Embodiment. It is a block diagram which shows an example of the 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 flowchart which shows an example of operation | movement of the mutual customer-delivery system by 4th Embodiment. It is a block diagram which shows an example of the 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-delivery system by 5th Embodiment. It is a figure which shows the example of a display of the list of object applications by 5th Embodiment. It is explanatory drawing explaining the outline | summary of the mutual customer-delivery system of 6th Embodiment. It is explanatory drawing explaining the outline | summary of the mutual customer-delivery system of 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 flowchart which shows an example of operation | movement of the mutual customer sending system by 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 explanatory drawing explaining the outline | summary of the mutual customer-delivery system of 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 explanatory drawing explaining the outline | summary of the mutual customer-delivery system of 9th Embodiment. It is a block diagram which shows an example of the 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-delivery system by 9th Embodiment.

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

[Outline of mutual customer service system]
First, an outline of the mutual customer sending system according to the present embodiment will be described. This mutual customer transfer system is based on an application (hereinafter referred to as “send customer application”) that has not yet been installed on the user terminal from an original application already installed on the user terminal (hereinafter referred to as “customer application”). This is a system for sending customers between applications so that a customer application is also installed. However, the user information of the user registered for each application may be different. Therefore, the user information is not consistent between applications, and transmission from the customer source application to the customer destination application is performed at the same user terminal. It may not be easy to determine if a customer has been performed. Therefore, in the present embodiment, it is an object of the present invention to provide a mutual customer delivery system capable of mutual customer delivery even between applications that are the same user and managed by different user information. Even if they are different from each other, it is possible to easily perform mutual customers between applications.

  Here, the customer sending from the customer source application to the customer destination application means that the user who uses the customer source application sends the user to the customer destination application that has not been used yet. Sending customers to the destination app. In addition, mutual customer transmission indicates that each application can be a customer source and a customer destination, so that applications can send customers to each other. For example, when a customer is sent from a customer source application to a customer destination application, the customer destination application sends a customer to another customer destination application that is not yet installed on the user terminal. Can become a former app.

  In addition, in a mutual customer sending system in which a reward is granted when a customer destination application is installed, there is a possibility that the customer destination application may not be used only for the purpose of reward acquisition. Therefore, in the present invention, a reward is given when the installed customer destination application reaches a predetermined result point. Furthermore, if a plurality of different result points are provided, a reward can be obtained for each achieved result point. By using such achievement achievement-type reward, it becomes possible to increase the use of the customer destination application.

  In the present embodiment, the reward (reward) given when the customer destination application is installed based on the customer source application is divided into a normal period and a specific period (hereinafter referred to as “campaign period”). Different reward processing. A campaign is a measure (an event having a specific period) that is implemented in order to increase mutual customers for a specific period between a plurality of applications.

  Specifically, in the mutual customer delivery system of the present embodiment, a reward (reward) is given when a customer destination application is installed in a normal period (that is, a period other than the campaign period), and in the campaign period, Provided is a system that enables mutual sending of a plurality of applications in which rewards (rewards) are given when achievements in a customer destination application are achieved. Hereinafter, a reward that is performed during a normal period is referred to as “normal reward”, and a reward that is performed during a campaign period (campaign reward) is referred to as “CP reward”.

  CP rewards are mutual customers between specific applications participating in the campaign during the campaign period, whereas rewards are usually mutual between any applications that cover all of the applications that are compatible with the system. Become a customer.

  FIG. 1 is an explanatory diagram for explaining the 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 exemplified as applications corresponding to the mutual customer sending system of the present embodiment. “App A” is a customer-source application installed in the user terminal. “App B”, “App C”, and “App D” are applications that are not installed in the user terminal, and can be customer applications with respect to “App A” (customer application). is there. “App B” is in the campaign period with “App A”, and “App C” and “App D” are in the normal period that is not in 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 destination application for “application A” that is a customer source application. Here, labels L1, L2, and L3 displaying the application names and reward contents of “application B”, “application C”, and “application D” are arranged as operators that can be selected as a customer destination application. It is displayed. The label L1 displays the application name of “application B”, information indicating that it is during the campaign period, and the link destination of the site on which the reward content by CP reward is posted. The label L2 displays the application name of “application C” and the reward contents by the normal reward. On the label L3, the application name of “application D” and the reward contents by the normal reward are displayed.

  Here, in the case of a normal reward, the provision of points that can be used by the user in the customer source application is displayed as the reward content. On the other hand, in the case of CP rewards, for example, the achievement points that are the conditions for granting rewards in the game and the reward contents when the achievement points are achieved (points, items, etc.) are managed on the application side. Therefore, it is posted on the linked site. The achievement 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, or the 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 or can be executed (started) The reward is given for the “app A” as the customer's sender by a normal reward. On the other hand, when “App B” is selected as the customer destination application, “App B” is activated on the condition that “App B” is installed on the user terminal and becomes executable during the campaign period. After that, when the achievement point set in advance corresponding to the campaign is achieved (reward granting condition is satisfied), the reward is given by CP reward for the “app A” as the customer source. In addition, for example, a reward granting period that starts from the beginning or middle of the campaign period and ends after the end of the campaign period is set, and if the achievement point is achieved within this reward granting period, the reward by CP reward After the reward has been granted and the reward grant period has passed, no reward will be given by CP reward even if the achievement point is achieved. When a plurality of achievement points are set, reward is given by CP reward every time achievement points are achieved. In this way, the end point of the reward grant period is set after the end point of the campaign period, so that the user who installs at the end of the campaign period considers the period until the achievement point is achieved. ing.

  Moreover, even if the users of a plurality of applications installed on the user terminal are the same, the user information registered for each application (for example, the user ID that is identification information for uniquely identifying the user) may be different. Therefore, in the mutual customer sending system of the present embodiment, unique identification information that is information that can be uniquely identified for each user terminal, and can identify the user terminal (the user who uses the user terminal can be identified). ) Management is performed using unique identification information (hereinafter referred to as “reward user ID”). Thereby, even if the user ID is different between applications, the user terminal can be specified using the reward user ID, and mutual customers between applications can be easily provided.

  Further, in the mutual customer sending 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 if the user ID is different between applications, since the application user ID between applications is associated through the reward user ID, it is possible to easily identify the user of the client application and give a reward Is also possible. In the following description, identification information for uniquely identifying an application is referred to as an “application ID”.

  Further, when a customer is sent from the customer source application to the customer destination application, the customer destination application can become the customer source application. For example, when a customer is sent from “App A” to “App B”, “App B” uses “App C” or “App D” that has not yet been sent as a customer destination application. It can be a customer-source application that sends customers to “application C” or “application D”. At this time, if “App C” or “App D” is not in the campaign period with “App B”, it will be subject to normal reward, and if it is in the campaign period with “App B” Are subject to CP Rewards. Similarly, for example, when a customer is sent from “App A” to “App C”, “App C” to which the customer has been sent is “App B” that has not yet been sent. It can be a customer-source application that sends customers to “App D”.

In addition, as an example of the state of the application, a non-operating state (Not running), a normal operating state where some processing is being performed (Active), and a background state where some processing is being performed but not displayed on the screen (BackGround) and a suspended state (Suspended) where no processing is executed. Here, “activation of the 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). “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 at the same time, “starting the target application” means that the target application can be operated by the user, for example, displayed on the forefront of the screen. The transition to a state.
The application installation includes not only newly introducing an application program that has not been introduced into the user terminal, but also updating (updating) the application program so as to correspond to the mutual customer system. That is, it includes downloading and updating an update program for supporting the mutual customer system for the application installed in the user terminal.

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

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

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

Here, from the application (game) provider, it is desired to provide a service that motivates the purchase so that more users can purchase the application to be provided.
For example, an advertisement (banner) of an application that has not yet been installed is displayed on a display screen that is displayed while using an application that is installed on the user terminal 100 or a display screen that is transitioned by a user operation. ) Is directed to the store site described above, and when the selected application is downloaded and installed on the user terminal 100 to be executable or executed, the advertisement ( It is conceivable to provide a service in which a reward is given for the user's own use of the original application on which the banner) is displayed. In this case, since a reward (for example, an item or a game point that can be used in a game) that can be used in the original application is given to the user, it is a motivation to purchase a new application for the user who wants to obtain the reward. . As a result, it becomes possible to promote sales of the application.

  The management server 200 manages information related to the application corresponding to the mutual customer transfer system of the present embodiment and information related to normal reward or CP reward, and also manages customer information between applications by communicating with the user terminal 100. It is a management device that controls reward processing. Specifically, the management server 200 associates, for example, the application ID of the customer source application, the application ID of the customer destination application, and the reward user ID as customer information from the customer source application to the customer destination application. to manage.

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

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

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

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

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

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

  In this figure, the user terminal 100 includes an installed customer-source application 10 (game A) executed under the control of the terminal control unit 150, and a store 30 (store page on the store site) that is activated during the customer-transmission process. ) And a customer destination application 20 (game B) that is newly installed and executed.

  The customer-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 sends information necessary for playing the game A to the application server 310 (game A). Or from game A). Similarly, when the customer destination application 20 (game B) is installed in the user terminal 100, the customer destination application 20 (game B) assigns the user ID corresponding to the user X who plays the game B to the application server. 320 (game B) or information necessary during the game B play is acquired from the application server 320 (game B).

  In addition, software for mutual customer processing (hereinafter referred to as SDK (Software Development Kit) 11) is incorporated in the application corresponding to the mutual customer system of the present embodiment. The SDK 11 is composed of, for example, a collection of APIs (Application Programming Interfaces) for mediating between each application corresponding to the mutual customer sending system installed in the user terminal 100 and the management server 200. In this figure, the SDK 11A is incorporated in the customer application 10 (game A), and the SDK 11B is incorporated in the customer 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 source application 10 and the customer destination application 20, and a necessary function is executed according to each application. Note that the application corresponding to the mutual customer system can be either the customer source application 10 or the customer destination application 20, and thus the SKD 11 having both the SDK 11A and the SDK 11B is incorporated.

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

  Among the applications corresponding to the mutual customer system, there may be an application corresponding only to the customer destination application 20. In that case, only the SDK 11B may be incorporated, or the SDK 11A may be incorporated so that the SDK 11A does not function. In addition, in the case of an application that supports only the customer destination application 20, it is not necessary to provide an application server corresponding to the application. For example, an application that operates stand-alone on the user terminal 100 corresponds to the mutual customer sending system. Can be the target of an application.

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

  The configuration including the above-described SDK 11 (SDK 11A and SDK 11B in this figure) and the management server 200 is the main configuration of the mutual customer system according to the present embodiment (see reference numeral 500). To be described.

  The management server 200 executes a mutual customer process by communicating with the SDK 11 incorporated in an application corresponding to the mutual customer system 500 installed in the user terminal 100. In addition, the management server 200 transmits information regarding the reward to the application server 310 (game A) corresponding to the customer source application 10 (game A). Thereby, the reward is given to the user X in the customer source application 10 (game A) from the application server 310 (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 causes the storage unit 230 to store information on applications corresponding to the mutual customer sending system 500, information on applications participating in the campaign, customer information between applications, information on normal rewards and CP rewards, and the like. to manage. The storage unit 230 stores various types of 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 transmission process with the user terminal 100 or the application server 310 (game A) and 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”.

Next, an outline flow of the mutual customer sending process will be described.
Here, it is assumed that information on the target application corresponding to the mutual customer sending system 500 is managed in advance by the management server 200. In addition, the user terminal 100 has acquired the reward user ID of the user X, which is the unique identification information corresponding to the user terminal 100, and the acquired reward user ID is installed in the mutual customer sending system 500 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 that it can be referenced from the corresponding application.

(1) When the customer source application 10 (game A) is installed in the user terminal 100, the SDK 11A incorporated in the customer source application 10 (game A) is installed with the customer source application (game A). Installation notification information indicating this is transmitted to the management server 200 (REQ11). Here, the install notification information includes, for example, the application ID of the customer source application 10 (game A) and the reward user ID.

(2) When the management server 200 acquires the installation notification information transmitted from the user terminal 100 (SDK11A), the management server 200 transmits response information (notification result) indicating the acquisition to the user terminal 100 (SDK11A) ( RES11). In addition, the management server 200 manages the application ID of the customer-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 11 </ b> A) requests an application list (information indicating a target application that is a candidate for the customer destination application 20) of at least one target application of the target application corresponding to the mutual customer sending system 500. Request notification information is transmitted to the management server 200 (REQ12).

(4) When the management server 200 acquires the list request notification information from the user terminal 100 (SDK11A), the management server 200 does not acquire the installation notification information from the user terminal 100 among the plurality of target applications to be managed (that is, An application list of at least one target application (which has never been installed in the user terminal 100) is transmitted to the user terminal 100 (SDK11A) (RES12). At this time, the management server 200 transmits information related to the campaign in association with the specific application participating in the campaign.
When the user terminal 100 (SDK 11A) acquires 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 any target application 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) starts from the customer source application 10 (game A). The customer information indicating that the customer is sent to the selected target application (here, the customer destination application 20 (game B)) is transmitted to the management server 200 (REQ13). Here, the customer information includes, for example, an application ID of the customer application 10 (game A), an application ID of the customer application 20 (game B), and a reward user ID.

(6) When the management server 200 acquires customer information from the user terminal 100 (SDK 11A), based on the acquired customer information, instruction information for guiding the customer application 20 (game B) to an installable screen (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 (SDK11A) (RES13). Further, the management server 200 associates the application ID of the customer source application 10 (game A), the application ID of the customer destination application 20 (game B), and the reward user ID included in the acquired customer information. to manage.

(7) When the user terminal 100 acquires the above instruction information from the management server 200, the store 30 is an application that displays a store page of a store site where the customer destination application 20 (game B) can be installed (downloadable). Start up. The store 30 acquires a store page in which the customer destination application 20 (game B) can be installed from the app store 400 and displays it on the display unit 120. After the customer destination application 20 (game B) is downloaded and installed on 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 is subsequently started.

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

(9) When the management server 200 acquires the installation notification information transmitted from the user terminal 100 (SDK11B), the management server 200 transmits response information indicating the acquisition to the user terminal 100 (SDK11B) (RES14). In addition, the management server 200 determines that the customer destination application 20 (game B) uses the customer source application 10 (game A) in the user terminal 100 based on the acquired installation notification information and the managed customer information. ) Is determined to have been sent by the customer.

(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 source application 10 (game A). In this case, in the customer destination application 20 (game B), the user terminal 100 (SDK11B) is based on the fact that the reward granting conditions set in advance corresponding to the campaign are satisfied (the achievement point has been reached). Transmits reward grant notification information (information indicating achievement point arrival) indicating that the reward grant condition is satisfied to the management server 200 (REQ15). When there are a plurality of achievement points, the user terminal 100 (SDK 11B) sends the reward grant notification information (information indicating achievement point arrival) for the number of achievement points to the management server 200 based on the arrival at each achievement point. Send.

(11) When the management server 200 acquires the reward grant notification information from the user terminal 100 (SDK11B), the management server 200 is reward grant information based on the acquired reward grant notification information, and the achievement point in the customer destination application 20 (game B) The reward granting information indicating that it has reached is transmitted to the application server 310 (game A) corresponding to the customer source application 10 (game A) (CP reward processing). When there are a plurality of achievement points, the management server 200 transmits reward grant information based on the reward grant notification information for the number of reward points to the application server 310 (game A).
Here, the management server 200 transmits information indicating the achievement point arrival in the customer destination application 20 (game B) to the application server 310 (game A) corresponding to the customer source application 10 (game A). The content of the setting of the result point in the customer destination application 20 (game B) and the reward content given to the customer source application 10 (game A) when reaching each result point Is not involved. When displaying the list LT of the target application on the display screen of the user terminal 100, the link destination of the site where the reward content by CP reward is posted is displayed without displaying the reward content by CP reward on the display screen. This is because the management server 200 is not involved in the contents of the reward.

  When the customer destination application 20 (game B) is a target application that is not a specific application (or even if it is a specific application but outside the campaign period), the management server 200 displays the user terminal 100 (SDK11B). When the installation notification information indicating that the customer destination application 20 (game B) transmitted from is installed is acquired, reward granting information indicating that the achievement point by the normal reward is reached is sent to the application server 310 (game A). To the other side (normal reward processing).

  With this processing flow, the customer is sent from the customer application 10 (game A) to the customer application 20 (game B). Here, in the mutual customer sending system 500, each information exchanged between the SDK 11A and the SDK 11B and the management server 200 is related directly or via any information by the reward user ID corresponding to the user terminal 100. Has been. Thereby, even if the application user ID is different between the customer source application 10 (game A) and the customer destination application 20 (game B), the mutual customer sending system 500 can Reward processing can be easily performed.

  Next, the detail of each structure with SDK11 (SDK11A and SDK11B) with which the mutual customer sending system 500 is provided, and the management server 200 is demonstrated.

[Functional configuration of user terminal 100 (SDK11)]
FIG. 5 is a configuration diagram illustrating an example of a functional configuration of the mutual customer transmission process 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 process executed by the user terminal 100 (SDK 11) in the mutual customer 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 grant notification unit 107.
When the application into which the SDK 11 is installed is installed in 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 a process at the first activation. Further, the initialization processing unit 101 includes a unique identification information acquisition unit 102 and an installation notification unit 103.

The unique identification information acquisition unit 102 acquires unique user identification information that is uniquely set for each user terminal 100 and is a unique user identification information that can uniquely identify 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 ID of another user terminal 100. Generate and get. In addition, the unique identification information acquisition unit 102 stores the acquired reward user ID in the inter-application sharing area of the terminal storage unit 140 so that it can be referred to from any target application installed in the user terminal 100.
Here, the unique identification information acquisition unit 102 acquires a reward user ID when the installed target application is a target application first installed in the user terminal 100 among the plurality of target applications. That is, when the reward user ID is not stored in the inter-application sharing area of the terminal storage unit 140, the reward user ID is acquired. The obtained reward user ID is also used in the target application installed thereafter.

  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 install notification information 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 a case where the user downloads from the store site without installing the customer sending process by the mutual customer sending system 500 and the target application is installed, and a case where the user application is installed via the customer sending process by the mutual customer sending system 500 (simply In any case, the installation notification information is transmitted from the user terminal 100. When the installed target application 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 an application user ID in the installed target application of the user who installed the installed target application. Thereby, 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 instead of being included in the installation notification information.

  Here, the process in which the installation notification unit 103 transmits the installation notification information to the management server 200 is the same for both the SDK 11A of the customer source application 10 and the SDK 11B of the customer destination application 20. Executed when each installed application starts.

The list request unit 104 is a list request notification information requesting an application list of at least one target application (or a specific application) of a plurality of target applications based on a predetermined operation (first operation) in the customer source application 10. Is transmitted to the management server 200. Here, the predetermined operation described above is a user operation on the input unit 110, for example, for acquiring the application list of the target application (or specific application) from the management server 200 in the customer source application 10. The list request notification information includes, for example, the application ID (customer information) of the customer application 10 (target application (or specific application)) and the reward user ID corresponding to the user terminal 100. included.
In addition, the list request unit 104 acquires the application list transmitted from the management server 200 based on the transmitted list request notification information.
Note that the list request unit 104 may transmit to the management server 200 list request notification information for requesting an application list of a target application including a specific application for which a campaign is set with the customer source application 10. Alternatively, list request notification information for requesting an application list of a target application that does not include the specific application may be transmitted to the management server 200. In addition, the list request unit 104 may transmit, to the management server 200, list request notification information for requesting an application list for only a specific application for which a campaign is set with the customer source application 10.

  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 the target application list LT by overlapping or switching the display screen displayed on the display unit 120 by the customer source application 10.

The customer information notification unit 106 transmits customer information indicating that the customer has been sent to the target application (or a specific application) selected from the customer application 10 to the management server 200. Here, the target application (or specific application) selected from the customer source application 10 is a user operation (or a user operation (or specific application) included in the application list displayed on the display unit 120). It means any application selected based on the second operation).
The above-mentioned customer information includes, for example, an application ID (customer information) of the customer application 10, a selected target application (or a specific application), that is, an application ID of the customer application 20, and this user. A reward user ID corresponding to the terminal 100 is included.

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

  The reward grant notification unit 107 is a reward grant notification information indicating that the reward granting condition is satisfied based on the fact that the reward granting condition set in advance corresponding to the campaign is satisfied in the specific application during the campaign period. Is transmitted to the management server 200. Here, the above-described reward grant notification information includes, for example, an application ID (customer destination information) of a specific application (customer destination application 20) during the campaign period, and a reward user ID corresponding to the user terminal 100. Is included.

  Of the functional configurations based on the SDK 11 shown in FIG. 5, for example, the initialization processing unit 101 (unique identification information acquisition unit 102, installation notification unit 103), list request unit 104, display control unit 105, and customer The information notification unit 106 corresponds to the functional configuration of the SDK 11A corresponding to the customer source application 10 (that is, the functional configuration of the customer source). In addition, for example, the initialization processing unit 101 (unique identification information acquisition unit 102, installation notification unit 103) and the reward grant notification unit 107 include the functional configuration of the SDK 11B corresponding to the customer destination application 20 (that is, the customer destination). 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 configuration diagram illustrating an example of the configuration of the management server 200 according to the present embodiment. As described with reference to FIG. 4, the management server 200 includes a communication unit 210, a management unit 220, a storage unit 230, and a control unit 240. Here, the management unit 220, the storage unit, Each structure of 230 and the control part 240 is demonstrated in detail.

  The management unit 220 includes an application management unit 221, an installation information management unit 222, and a customer information management unit 223. The management unit 220 associates each piece of information to be managed and stores the information in the storage unit 230 for management.

  The application management unit 221 manages information (target application information) regarding a plurality of target applications corresponding to the mutual customer sending system 500. In addition, the application management unit 221 manages information related to 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 associates and manages information indicating a campaign (such as a campaign name) and information related to the campaign (such as information indicating a campaign period and a link destination of information posting location indicating reward).

Based on the installation notification information acquired from the user terminal 100, the installation information management unit 222 associates the reward user ID included in the installation notification information with the application ID of the installed target application and manages it as installation information.
Note that the installation information management unit 222 may manage 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 as installation information in association with each other.

The customer information management unit 223 receives the reward user ID, the application ID of the customer application 10, and the application ID of the customer application 20 included in the customer information transmitted from the user terminal 100 and acquired by the management server 200. It is associated and managed as a record of customer information.
Note that the customer information management unit 223 may further manage the customer information as a record of customer information associated with information indicating the campaign when the campaign is set in the customer application 10 and the customer application 20. .

The storage unit 230 stores various 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-app 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 information storage unit 237 and a reward establishment information storage unit 238. Various types of information may be stored in a format suitable for the use of the information, such as a database table format or a JSON (Java Script (registered trademark) Object Notation) format.

The target application information storage unit 231 stores target application information related to the target application corresponding to the mutual customer sending system 500. FIG. 7 is a diagram illustrating an example of target application information stored in the target application information storage unit 231. The target application information includes an application ID (ApID), a notification destination URL (NoticeURL), a store URL (ApStoreURL), an application name (ApNAME) indicating the name of the target application, and an explanation about the target application. An application description (ApDOC) that is information, an application icon image (ApICO) that is an icon image indicating the target application, and an application price (ApPRICE) are associated with each other.
The notification destination URL (NoticeURL) is the URL (Uniform Resource Locator) of the notification destination of the reward. For example, the URL of the application server 300 corresponding to the target application is set. The store URL (ApStoreURL) is a URL of a page of a sales site (application store 400) where the target application can be downloaded. The application price (ApPRICE) is the selling price of the target application. The target application information is used in a target application list LT displayed on the user terminal 100, for example.
The target application information is set in advance and stored in the target application information storage unit 231 before being available for download from the application store 400, and is managed by the application management unit 221.

The normal reward information storage unit 232 stores information related to normal reward (normal reward information) for each target application. FIG. 8 is a diagram illustrating an example of normal reward information stored in the normal reward information storage unit 232. The normal reward information indicates an item ID (ItemID) for 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 the name of the item. The reward item name (ItemName) is associated with the number of reward items (ItemNum) indicating the number of reward items given. In the minimum price (min_price), the price of the target application that is the target of normal reward is set. These normal reward information is used in a list LT of target applications displayed on the user terminal 100, for example.
The normal reward information is set when the target application information is stored in the target application information storage unit 231, stored in the normal reward information storage unit 232, and managed by the application management unit 221.

  The inter-application filter storage unit 233 stores filter information (inter-app filter information) between applications for limiting target applications that can be sent to each other. The processing for restricting target applications that can be sent to each other will be described in detail in the second embodiment.

  The campaign information storage unit 234 stores information (campaign information) related to a campaign of a specific application that participates in the campaign among the target applications. FIG. 9 is a diagram illustrating an example of campaign information stored in the campaign information storage unit 234. The campaign information includes campaign ID (CpID), campaign name (CpNAME), campaign start date / time (CpStartDATE), campaign end date / time (CpEndDATE), reward grant start date / time (RewardStartDATE), reward grant end date / time (RewardEndDATE) ).

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

In addition, in the CP reward, for example, a plurality of achievement points are set, and a user who starts using the customer destination application 20 during the campaign period defines how far the achievement point should be reached by starting reward granting. This is a reward grant period defined by the date and time (RewardStartDATE) and the reward grant end date and time (RewardEndDATE). For example, for a campaign period (an example of a first period), a reward granting period (an example of a second period) that starts from the start or middle of the campaign period and ends after the campaign period is set. As an example, the same date and time are set for the campaign start date and time and the reward grant start date and time, and the reward grant end date and time is set one week after the campaign end date and time. These pieces of campaign information are set in advance before the campaign start date and time, stored in the campaign information storage unit 234, and managed by the application management unit 221. In addition, similar information is set as the campaign information in the application server 300 and the management server 200 corresponding to each specific application that executes the campaign.
In addition, the structure which a reward provision period is not set separately from a campaign period may be sufficient, and the structure where a reward provision period is the same period as a campaign period may be sufficient.

  The campaign participation application information storage unit 235 stores information indicating the specific application that participates in the campaign set in the campaign information storage unit 234 (campaign participation application information). Here, since it is a campaign for mutual customers between applications, at least two applications are set in one campaign. FIG. 10 is a diagram illustrating an example of campaign participation application information stored in the campaign participation application information storage unit 235. The campaign participation application information is associated with a campaign ID (CpID), an application ID (ApID) of a specific application participating in the campaign with this campaign ID, and a campaign page URL (CpPageURL). 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 (CpPageURL) is information indicating a page (website page) on which information related to reward of CP reward given when the application is installed and used during the campaign period. This page also contains information about the application (description and price). For example, when a campaign is set for the customer source application 10 (game A) and the customer destination application 20 (game B), the page and application server in the application server 310 (game A) corresponding to each application Each URL with a page in 320 (game B) may be set as a campaign page URL. In addition, a campaign dedicated site may be provided separately, and the same URL for the campaign dedicated site may be set for both the customer source application 10 (game A) and the customer destination application 20 (game B). . Further, this campaign dedicated site may be provided in the management server 200.

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

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

  The installation information storage unit 236 stores installation information managed by the installation information management unit 222 based on installation notification information transmitted from the user terminal 100 and acquired by the management server 200. FIG. 11 is a diagram illustrating an example of installation information stored in the installation information storage unit 236. For example, a reward user ID (RewardUID), an application ID (ApID), and an application user ID (ApUID) included in the acquired installation notification information are associated with the installation information.

  Here, both in the case where the target application is simply installed without going through the customer sending process by the mutual customer sending system 500 and in the case where the target application is installed through the customer sending process by the mutual customer sending system 500, The installation notification information is transmitted, and the 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 provides double compensation. Can be prevented.

  The customer information storage unit 237 stores (records) customer information managed by the customer information management unit 223 based on customer information transmitted from the user terminal 100 and acquired by the management server 200. FIG. 12 is a diagram illustrating an example of customer information stored in the customer information storage unit 237. In the customer information, a reward management ID (RewardID), a reward user ID (RewardUID), a customer application ID (ApIDfrom), a customer application ID (ApIDto), and a campaign ID (CpID) are associated with each other. It has been. The reward management ID (RewardID) is a management ID that is issued in the order in which each customer information is acquired so that each customer information can be identified. The customer source application ID (ApIDfrom) is the application ID of the customer source application 10, and the customer destination application ID (ApIDto) is the application ID of the customer destination application 20. At this time, if both the customer source application 10 and the customer destination application 20 are in the campaign period of the same campaign, the campaign ID of the campaign is stored, and if it is not the campaign period, “null” is set as the campaign ID. The

  In addition, since the application list does not include a target application that has already been installed in the user terminal 100 or a target application that has been installed (a target application that has been uninstalled thereafter), a target to be newly installed The customer information to the application is stored in the customer information storage unit 237. Even when the customer information is stored in the customer information storage unit 237, the customer application 20 of the customer information is not necessarily downloaded and installed.

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

  In the case of a normal reward, this reward establishment information is stored in the installation information storage unit 236, for example, the installation information of the target application corresponding to the customer destination application ID of the customer information stored in the customer information storage unit 237. Sometimes, a new record (reward establishment information data for one piece) 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, when the reward grant notification information corresponding to the customer destination application ID of the customer information stored in the customer information storage unit 237 is acquired from the user terminal 100. 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 illustrating an example of the reward establishment information stored in the reward establishment information storage unit 238. In the reward establishment information, a reward management ID (RewardID), a result point ID (RewardSpotID), and an established state (RewardStatus) are associated. The reward management ID (RewardID) corresponds to the reward management ID included in the customer information stored in the customer information storage unit 237.

The achievement point ID (RewardSpotID) is identification information of the achievement point to which a reward is given in the customer destination application 20 set based on the reward granting condition.
In the case of CP reward, identification information indicating a result point (reward granting 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 result points, a plurality of records in which each of the plurality of result point IDs is associated with the same reward management ID are generated and stored in the reward establishment information storage unit 238.

In the case of normal reward, that is, when “null” is set in the campaign ID included in the customer information stored in the customer information storage unit 237, the result point (reward granting condition) is the customer destination application 20. “Null” is set as the result point ID.
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 result point ID, the result point (reward granting condition) is the same as in the case of normal reward. ) Is when the customer destination application 20 is installed and becomes executable, or when it is executed.

  In the established state (RewardStatus), flag information indicating whether or not the reward grant information is notified to the application server 310 (game A) corresponding to the customer source application 10 (game A) is set. That is, when a new record is generated in association with the reward management ID corresponding to the customer information stored in the customer information storage unit 237, the flag “0” ( Not notified) is set. Thereafter, when the notification of the reward grant information to the application server 310 (game A) is completed, the established state (RewardStatus) is updated to the flag “1” (notified). Note that when a response to the notification of reward grant 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 information acquisition unit 243, an installation guidance instruction unit 244, a reward processing unit 245, and a timing unit 246.

  The installation notification acquisition unit 241 displays 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, in the target application (the SDK 11 of the target application). ) As described above, the install notification information includes, for example, the reward user ID corresponding to the user terminal 100 and the application ID of the target application. 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 source application 10 (SDK 11A of the customer source application 10) installed in the user terminal 100, based on the acquired list request notification information, Referring to the target application information storage unit 231 and the installation information storage unit 236, at least one target application (or specific application) that has not acquired installation notification information from the user terminal 100 (that is, is not installed in the user terminal 100) ) Application list is transmitted to the user terminal 100.

In addition, 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 regarding a campaign corresponding to one or more specific applications included in the application list.
At this time, the list notification unit 242 includes information on the target application (application name, description, price, etc.), information on the reward contents of the normal reward, or information on the CP reward campaign (information indicating the campaign period and the reward corresponding to the campaign). The target application list LT based on the application list including the link destination of the posting location of the application generates application list page data 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. Information indicating the link destination of the selected page is transmitted to the user terminal 100.

  The customer information acquisition unit 243 is customer information from the customer source application 10 to the customer destination application 20, and includes a reward user ID, an application ID of the customer source application 10, and an application ID of the customer destination application 20. The customer information included is acquired from the user terminal 100. Then, the customer information acquisition unit 243 supplies the acquired customer information to the customer information management unit 223.

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

  The reward processing unit 245 executes a first reward grant process (CP reward process) related to CP reward and a second reward grant process (normal reward process) related to normal reward.

  When the installation notification acquisition unit 241 acquires installation notification information corresponding to the customer destination application 20, the reward processing unit 245 receives customer information from the customer source application 10 to the customer destination application 20 as a customer information storage unit 237. It is determined whether or not it is stored. Then, when the customer information is stored in the customer information storage unit 237 (that is, the customer information management unit 223 manages the customer information record for the customer application 20). If the customer destination application 20 is a target application sent from the customer source application 10 by the mutual customer sending system 500, 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 source application 10 so that the user is rewarded in the customer source application 10 in the CP reward process or the normal reward process. 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 going through the customer sending process by the mutual customer sending system 500. Therefore, on condition that the customer information record with respect to the customer destination application 20 is managed by the customer information management unit 223, the CP reward or the normal reward is simply given when the customer destination application 20 is installed. It becomes possible to prevent giving.

  It is assumed that a campaign is set between the customer destination application 20 and the customer source 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 the reward application unit 245 based on the satisfaction of the reward granting conditions set in advance corresponding to the campaign. When the reward grant notification information is acquired from the customer application 20, CP reward processing based on the acquired reward grant notification information is executed. On the other hand, it is assumed that no campaign is set between the customer destination application 20 selected on the user terminal 100 and the customer source application 10. In this case, the reward processing unit 245 executes normal reward processing when it is determined that the customer destination application 20 has been installed.

  Here, when the customer destination application 20 is a specific application for which a campaign is set with the customer source application 10, the reward processing unit 245 sets the installation notification acquisition unit 241 to the customer destination application 20. When the timing at which the corresponding installation notification information is acquired is within the campaign period, it is determined that the customer destination application 20 has been installed on the user terminal 100 within the campaign period. Note that the reward processing unit 245 determines that the customer destination application 20 is installed in the user terminal 100 outside the campaign period even if the customer destination application 20 has a campaign set with the customer source application 10. The normal reward process is executed instead of the CP reward process.

  In the normal reward process, the reward processing unit 245 sends the customer 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 grant information including the application user ID is transmitted to the application server 310 corresponding to the customer source application 10.

  In the CP reward process, the reward processing unit 245 stores the application user ID of the customer source application 10 associated with the reward user ID included in the reward grant notification information acquired from the customer destination application 20 in the installation information storage unit 236. Get by reference. And based on the acquired reward grant notification information, the reward grant information including the application user ID is transmitted to the application server 310 corresponding to the customer source application 10. In addition, the reward processing unit 245 may further include the campaign ID, the achievement point ID, and the like included in the acquired reward grant notification information in the reward grant information described above, and transmit it to the application server 310 corresponding to the customer source application 10. Good.

  In the case of the normal reward, the reward processing unit 245 stores the installation information of the target application corresponding to the customer destination application ID of the customer information stored in the customer information storage unit 237 in the installation information storage unit 236. Sometimes, a new record of 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” (unnotified) in the established state (RewardStatus) included in the reward established information.

  On the other hand, in the case of CP reward, when the reward processing unit 245 acquires, from the user terminal 100, reward grant notification information corresponding to the customer destination application ID of the customer information stored in the customer information storage unit 237, for example. Then, a new record of 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” (unnotified) in the established state (RewardStatus) included in the reward established information.

  For example, in the case of CP reward, the reward processing unit 245 displays the reward grant notification information corresponding to the customer destination application ID of the customer information stored in the customer information storage unit 237 as the campaign period corresponding to the customer information. If it is acquired from the user terminal 100, a new record of reward establishment information corresponding to the customer information is generated and stored in the reward establishment information storage unit 238. When the reward granting period is set for the campaign, the reward processing unit 245 displays the reward grant notification information corresponding to the customer destination application ID of the customer information stored in the customer information storage unit 237 as the reward. When the reward grant notification information is acquired from the customer destination application 20 within the grant period, a new record of reward establishment information corresponding to the customer information may be generated and stored in the reward establishment information storage unit 238. .

  Then, the reward processing unit 245 establishes the reward in response to the notification of reward grant information corresponding to the reward establishment information to the application server 310 (game A) in both the normal reward process and the CP reward process. The information establishment state (RewardStatus) is updated to flag “1” (notified).

  The timer 246 measures the time and acquires the current date and time. Note that the timer 246 may acquire the current date and time via the network NW from a date and time information providing server (not shown) that provides current date and time data. For example, the reward processing unit 245 determines whether or not the current date and time is within the campaign period or the reward granting period based on information indicating the current date and time counted by the timing unit 246. The various information storage units (231 to 238) stored and managed in the storage unit 230 indicate the data registration date and time when the record was generated and the date and time when a part of the generated record was updated. The data update date and time 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 timed by the time measuring unit 246 is recorded, and an application corresponding to the installation information is installed in the user terminal 100. It becomes the data indicating the date and time.

[Details of mutual customer processing]
Next, with reference to FIG. 14 and FIG. 15, the details of the operation of the mutual customer processing of the mutual customer system 500 according to the present embodiment will be described. 14 and 15 are flowcharts showing an example of the operation of the mutual customer processing according to the present embodiment. The processing shown in FIGS. 14 and 15 shows a detailed example of the outline processing flow described with reference to FIG.

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

  When the customer source application 10 (game A) is installed in the user terminal 100, the initialization processing unit 101 of the SDK 11A incorporated in the customer source application 10 (game A) executes only at the first activation. The application ID (ApID) of the customer source application 10, the application user ID (ApUID) of the user X registered in the customer source application 10, and the campaign ID (CpID) if a campaign is set Is acquired from the customer source application 10 (game A) (step SA11).

  Next, the initialization processing unit 101 of the SDK 11A executes the initialization processing 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 process has been completed (step SA12: YES), the initialization processing unit 101 ends without executing the subsequent initialization process, and proceeds to step SA17. On the other hand, when it is determined that the initialization process has not been 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). Whether or not the reward user ID has been acquired is determined by storing the reward user ID in the inter-application shared area of the terminal storage unit 140 so that it can be referred from any target application installed in the user terminal 100. It is judged by whether or not it is.

  When it is determined that the reward user ID has 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 obtains a reward user ID corresponding to the user terminal 100 (an ID unique in the mutual customer sending system 500). Generate and acquire (step SA14).

  Next, the unique identification information acquisition unit 102 stores the acquired reward user ID in the inter-application sharing 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 source application 10 (game A) has been installed in the user terminal 100 to the management server 200 (REQ11, step SA16). . Here, the installation notification information includes a reward user ID (RewardUID) corresponding to the user terminal 100, an application ID (ApID) of the installed customer application 10 (game A), and this customer 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 (SDK11A). 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 (SDK11A) (RES11). Further, the installation information management unit 222 of the management server 200 includes the reward user ID (RewardUID) included in the installation notification information acquired by the installation notification acquisition unit 241 and the application ID (ApID) of the customer source application 10 (game A). And the application user ID (ApUID) of the user X in the customer source application 10 (game A) are stored in the installation information storage unit 236 as installation information (step SE11).

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

Next, for the customer source application 10 (game A) running on the user terminal 100, the user X performs a predetermined operation on the input unit 110 for acquiring an application list of target applications that can be installed on the user terminal 100. Assume that an operation (first operation) is performed.
Based on a predetermined operation (first operation) in the customer source application 10, the list request unit 104 of the SDK 11A reads out the reward user ID from the inter-application shared area of the terminal storage unit 140 (step SA23), List request notification information for requesting an application list of at least one target application of the target application (information of target applications that are candidates for the customer destination application 20) is transmitted to the management server 200 (REQ12, step SA24).
Here, the list request notification information includes a reward user ID (RewardUID) corresponding to the user terminal 100, an application ID (ApID) of the customer source application 10 (game A), and a campaign ID (CpID). . If no campaign is set for the customer source application 10 (game A), “null” is set for the campaign ID (CpID). Further, even if the campaign ID (CpID) is not included in the list request notification information, the application ID of the customer source application 10 (game A) is referred to by referring to the campaign participating application information storage unit 235 and the campaign information storage unit 234 On the basis of ApID), the management server 200 acquires whether or not the customer source application 10 (game A) is carrying out a campaign, and if the campaign is being carried out, the corresponding campaign ID (CpID) is acquired 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 source application 10), the list notification unit 242 receives an installation notification from the user terminal 100 based on the acquired list request notification information. At least one target application that has not acquired information (that is, is not installed in the user terminal 100) is extracted. Specifically, the list notification unit 242 applies 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 as a target. By removing from the application ID of the target application managed in the application information storage unit 231 (filtering), at least one target application that is 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) and the campaign ID (CpID) of the customer source application 10 (game A) included in the list request notification information. Only a specific application for which a campaign is set with the customer application 10 (game A) may be extracted from the target applications. Note that there may be a case where a target application (specific application) that is not installed in the user terminal 100 does not exist and cannot be extracted.

  Note that the filtering process for filtering the target application included in the application list transmitted from the list notification unit 242 to the user terminal 100 in response to the acquisition of the list request notification information is the condition stored in the inter-application filter storage unit 233 ( Based on the filter information). This filtering process will be described in the second embodiment.

  Next, the list notification unit 242 generates application list page data for displaying the target application list LT based on the extracted application list of the target application on the user terminal 100 (step SE16), and the generated application list page Is transmitted to the user terminal 100 and redirected to the application list page (RES12, step SE17). If there is no target application (specific application) that is not installed in the user terminal 100, an application list page describing that the target application (specific application) does not exist is used instead of the target application list LT. 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 displays the application list page on the display unit 120 by the browser function (step SA25). .
Here, the display control unit 105 causes the application list page to be displayed by overlapping the display screen of the customer source application 10 (game A) that has been displayed on the display unit 120 until then. As a result, a list LT of target applications that can be selected as the customer destination application 20 is displayed on the application list page on the display unit 120 of the user terminal 100.

When any target application is selected by the user X from the target application list LT displayed on the display unit 120 of the user terminal 100, the customer information notifying unit 106 of the SDK 11A sends the customer application 10 (game A) sends customer information indicating that the customer has been sent to the selected target application (here, customer application 20 (game B)) to management server 200 (REQ13, step SA26). Here, in the customer information, the application ID (ApID) of the customer source application 10 (game A), the application ID (ApID) of the customer destination application 20 (game B), and the reward user ID (RewardUID) , And campaign ID (CpID). If no campaign is set for the customer source application 10 (game A) and the customer destination application 20 (game B), “null” is set for the campaign ID (CpID). The campaign ID (CpID) can be acquired in the management server 200 based on the application ID (ApID) of the customer source application 10 (game A) without acquiring the campaign ID (CpID) from the user terminal 100.
When the customer destination 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 source application 10 (game A). ) Display.

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

  Subsequently, the installation guide instruction unit 244 of the management server 200 determines the customer destination application 20 based on the application ID of the customer destination application 20 (game B) included in the customer information acquired by the customer information acquisition unit 243. Instruction information for guiding to an installable screen is transmitted to the user terminal 100. For example, the installation instructing instruction unit 244 transmits, to the user terminal 100, instruction information for starting the store 30, which is an application that displays a store page of a store site where the customer destination application 20 (game B) can be installed (downloadable). (Step SE19).

  When the user terminal 100 acquires the instruction information for starting the store 30 from the management server 200, the user terminal 100 starts the store 30 and displays the store page of the store site where the customer destination 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 so as to overlap the display screen of the customer source application 10 (game A) that has been displayed on the display unit 120 until then.

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

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

  First, the initialization processing unit 101 of the SDK 11B incorporated in the customer destination application 20 (game B) performs the processing executed only at the first activation, the application ID (ApID) of the customer destination application 20, and the customer The application 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 destination application 20 (game B) (step SB11). ).

  Next, the initialization processing unit 101 of the SDK 11B executes the initialization processing of the SDK 11B. The initialization processing unit 101 determines whether or not the initialization process has been completed (step SB12). If 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 proceeds to the installation notification process in step SB16.

  The installation notification unit 103 of the SDK 11B transmits installation notification information indicating that the customer destination application 20 (game B) has been installed in the user terminal 100 to the management server 200 (REQ14, step SB16). Here, the installation notification information includes a reward user ID (RewardUID) corresponding to the user terminal 100, an application ID (ApID) of the installed customer destination application 20 (game B), and this customer 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), similarly to 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 (SDK11B) (RES14). Further, the installation information management unit 222 of the management server 200 includes the reward user ID (RewardUID) included in the installation notification information acquired by the installation notification acquisition unit 241 and the application ID (ApID) of the customer destination application 20 (game B). And the application user ID (ApUID) of the user X in the customer destination application 20 (game B) are associated with each other and 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 (SDK11B) sets a flag indicating that initialization has been completed and ends the initialization process (step SB17) as in the process of step SA22.

  Next, when the installation notification acquisition unit 241 acquires the installation notification information corresponding to the customer destination application 20, the reward processing unit 245 transmits the customer destination application 20 (game B) from the customer source application 10 (game A). ) Is determined whether the customer information is stored in the customer information storage unit 237. Then, when the customer information is stored in the customer information storage unit 237 (that is, the customer information management unit 223 manages the customer information record for the customer application 20). If the customer destination application 20 is a target application sent from the customer source application 10 by the mutual customer sending system 500, the CP reward process or the normal reward process is executed. Here, in the process of step SE18, the target application sent from the customer sending application 10 by the customer sending application 500 by the mutual customer sending system 500 by recording 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 or not the installation notification acquisition unit 241 acquires the installation notification information corresponding to the customer destination application 20 (game B) within the campaign period (step SE22). .

  For example, when the customer destination application 20 (game B) is a specific application in which a campaign is set with the customer source application 10 (game A), the reward processing unit 245 displays 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 measured by the timer 246 when the installation notification information is acquired) is within the campaign period of the campaign.

  In step SE22, when it is determined that the timing at which the installation notification information is acquired is within the campaign period (step SE22: YES), the reward processing unit 245 rewards 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, if it is determined in step SE22 that the timing at which the installation notification information is acquired is not within the campaign period (step SE22: NO), the reward processing unit 245 executes normal reward processing. Even when the customer application 20 (game B) is a target application for which no campaign is set with the customer application 10 (game A), the installation notification information is acquired in step SE22. It is determined that the timing is not within the campaign period (step SE22: NO), and the reward processing unit 245 executes normal reward processing.

  First, the operation of the normal reward process will be described. In step SE22, when it is determined that the timing at which the installation notification information is acquired is not within the campaign period (step SE22: NO), the reward processing unit 245 causes the installation notification acquisition unit 241 to receive the installation notification information from the customer destination application 20. And the record of customer information for the customer destination application 20 is managed by the customer information management unit 223, and the result is associated with the reward management ID stored in the customer information. Reward establishment information having a spot ID (RewardSpotID) of “null” and an establishment state (RewardStatus) of 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 information corresponding to the reward management ID associated with the generated reward establishment information with reference to the customer information management unit 223. Then, the reward processing unit 245 sends the application user of the customer source application 10 (game A) to the application server 310 (game A) corresponding to the customer source application 10 (game A) included in the customer information. Reward grant information including ID (ApUID) (information indicating establishment of normal reward) is transmitted (step SE24). The application server 310 (game A) as a transmission destination is indicated by a notification destination URL (NoticeURL) 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 granting information as the flag “1” (notified).

  When the application server 310 (game A) receives from the management server 200 the reward granting information by normal reward (information indicating that the normal reward has been established) (step SF21), the application user ID (user X's application included in the reward granting information) A reward for a normal reward set in advance is given to the user ID) (step SF22).

  Next, the operation of the CP reward process will be described. In step SE22, when it is determined that the timing at which the installation notification information is acquired is within the campaign period (step SE22: YES), the reward processing unit 245 notifies the reward grant 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 of information.

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

  Assume that it is determined that the reward granting conditions set in advance corresponding to the campaign are satisfied (the point of achievement of CP reward has been reached) according to the progress of the game of the customer destination application 20 (game B) (step SD12). : YES).

  In this case, the customer destination application 20 (game B) notifies the SDK 11B of a result point ID (RewardSpotID) corresponding to the reached result point. Upon receiving the notification, the reward grant notification unit 107 of the SDK 11B reads the reward user ID from the inter-application shared area of the terminal storage unit 140 (step SB31), the read reward user ID (RewardUID), and the customer destination application 20 (game B). ) Of the reward grant notification information (result point arrival 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) to the management server 200. It transmits to (REQ15, step SB32). When there are a plurality of result points, the process returns to steps SD11 and SD12, and each time the result point is reached, the customer destination application 20 (game B) receives the result point ID (RewardSpotID) corresponding to the reached result point. ) To the SDK 11B. Then, the reward grant notification unit 107 of the SDK 11B transmits reward grant notification information (result spot arrival notice) to the management server 200.

  The reward processing unit 245 of the management server 200 acquires the reward grant notification information (result point arrival notification) transmitted from the user terminal 100 (SDK11B), and the customer information record for the customer destination application 20 is recorded. Based on what is managed in the information management unit 223, the achievement point ID (RewardSpotID) included in the acquired reward grant notification information is set in association with the reward management ID corresponding to the customer information, and the establishment state ( Reward establishment information with RewardStatus) as flag “0” (not notified) is generated and stored in the reward establishment information storage unit 238 (step SE25).

  Next, the reward processing unit 245 acquires customer information corresponding to the reward management ID associated with the generated reward establishment information with reference to the customer information management unit 223. Then, for the application server 310 (game A) corresponding to the customer source application 10 (game A) included in the customer information, the application user ID (ApUID) of the customer source application 10 (game A), the campaign Remuneration grant information (information indicating that CP reward has been established) including ID (CpID) and achievement 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 granting information as the flag “1” (notified).

  When there are a plurality of achievement points, the reward processing unit 245 acquires the reward corresponding to the customer information recorded in the customer information management unit 223 every time the reward grant notification information (result point arrival notification) is acquired. In association with the management ID, the reward establishment information with the flag “0” (not notified) of the establishment status (RewardStatus) is generated and stored in the reward establishment information storage unit 238. And the reward process part 245 uses the application server 310 corresponding to the customer origination application 10 (game A) for the reward provision information (information which shows CP reward establishment) based on each reward provision notification information (result point arrival notification). To (Game A). Then, the establishment status (RewardStatus) of the reward establishment information corresponding to the transmitted reward grant information is updated as flag “1” (notified).

  When the application server 310 (game A) receives the reward information by CP reward (information indicating establishment of CP reward) from the management server 200 (step SF31), the application user ID (user X's application included in the reward information) is received. 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 this embodiment, the management server 200 (an example of a management device) includes an application management unit 221, an installation notification acquisition unit 241, and a list notification unit 242. And a reward processing unit 245.
The application management unit 221 has a campaign having a campaign period (an example of a first period) set for a plurality of specific applications among a plurality of target applications (applications corresponding to the present system) to be managed ( Manage an example of an event. The installation notification acquisition unit 241 indicates that the target application installed on the user terminal 100 (an example of a terminal device) specified by a reward user ID (an example of unique identification information) among a plurality of target applications has been 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 a first application, the customer-source application 10) installed in the user terminal 100 among a plurality of target applications. An application list of at least one target application that has not been acquired is transmitted to the user terminal 100.
Here, the target application selected by the user terminal 100 from one or more target applications included in the application list notified by the list notification unit 242 (an example of the second application, the customer destination application 20) is the customer source application 10. It is assumed that a campaign is set 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) has been installed within the campaign period, and satisfies the reward granting conditions set in advance corresponding to the campaign. CP reward processing based on the acquired reward grant notification information (first reward) when acquiring the reward grant notification information indicating that the reward grant condition is satisfied from the customer destination application 20 An example of a grant process) is executed.
On the other hand, it is assumed that no campaign is set between the customer destination application 20 selected on the user terminal 100 and the customer source application 10. In this case, the reward processing unit 245 executes normal reward processing (an example of second reward granting processing) when it is determined that the customer destination application 20 has been installed.

In addition, the list notification unit 242 of the management server 200 is based on a request from a specific application (an example of a first application, the customer-source 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 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 destination application 20) selected on the user terminal 100 from one or more specific applications included in the application list is installed within the campaign period. Reward grant notification information indicating that the reward granting condition is satisfied is acquired from the customer destination application 20 based on the determination and the reward granting condition set in advance corresponding to the campaign is satisfied. In this case, CP reward processing based on the acquired reward grant notification information may be executed.

  Thereby, when the customer source application 10 is a specific application, the management server 200 displays an application list including at least a specific application for which a campaign is set with the customer source application 10 in the user terminal 100. Can be sent to. Note that the management server 200 may transmit to the user terminal 100 an application list of only specific applications for which a campaign is set with the customer source application 10. Then, the management server 200 performs CP reward processing when a customer to the customer destination application 20 is established from the customer source application 10 to which a campaign is set. In this CP reward process, unlike the normal reward process, a reward is granted based on the satisfaction of a reward provision condition set in advance corresponding to a campaign, so the customer destination application 20 is simply installed. In addition, the reward can be granted on condition that the customer destination application 20 is used.

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

  In the mutual customer sending system 500, when the target application once installed is uninstalled and then installed again, the installation information when the target application is first installed is managed in the management server 200. It is possible to specify that it has been installed. Therefore, in this system, when this target application is installed again, it can be prevented from being subject to 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 that can communicate 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. In addition, the management server 200 is customer information from one specific application to another specific application notified from the user terminal 100 specified by the reward user ID (an example of unique identification information) during the campaign period, The customer information that associates the customer source information indicating one specific application, the customer destination information indicating the other specific application, and the reward user ID (an example of unique identification information) corresponding to the user terminal 100 is managed. Further, the management server 200 is based on the fact that an application corresponding to the customer destination information based on the managed customer destination information is installed, and a reward granting condition set in advance corresponding to the event is satisfied. When the predetermined reward grant notification information is received, the reward grant information corresponding to the campaign is transmitted to the application corresponding to the customer 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 terminal device) is installed, and an application ID (an example of identification information) of the specific application and The installation notification information including the reward user ID of the user terminal 100 is transmitted 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 among a plurality of specific applications based on the first operation, and is operating with a specific application (customer application 10 List request notification information including the customer source information indicating the application ID and the reward user ID corresponding to the user terminal 100 is transmitted to the management server 200. The customer information notifying unit 106 is selected by the customer application information indicating the application ID of the specific application (an example of the customer application 10) that is operating based on the second operation during the campaign period. The customer information including the application ID of the specific application (an example of the customer application 20) and the customer information including 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 a reward grant notification unit 107. For example, as described above, the reward grant notification unit 107 transmits the application ID of the specific application that satisfies the reward granting condition based on the satisfaction of the reward granting condition set in advance corresponding to the campaign. 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. In addition, the user terminal 100 may be configured not to include the reward grant notification unit 107. In this case, the application server 300 is based on the fact that the reward grant condition set in advance corresponding to the campaign is satisfied, The reward grant notification information may be transmitted to the management server 200. The process in the case where the application server 300 transmits the reward grant notification information to the management server 200 will be described in (3) of the modification example described later.

As described above, in the mutual customer sending system 500 of the present embodiment, the management server 200 that manages campaigns set in a plurality of specific applications included in the target application corresponding to the mutual customer sending system 500, and the management server 200 The user terminal 100 can communicate with another user application 100 so that another specific application (an example of the customer destination application 20) is installed from one specific application (an example of the customer source application 10). Customers can be sent to a specific application (an example of the customer destination application 20). In the mutual customer sending system 500, user information registered in a plurality of applications installed in one user terminal 100 (an example of an application user ID) is used by using a reward user ID that can uniquely identify the user terminal 100. ) Are different, it is possible to easily carry out mutual customer processing and reward processing between applications. Further, in the mutual customer sending system 500, when a customer is established, a reward is given by a normal reward or a CP reward, which is a motivation for a user who wants to obtain a reward to purchase a new application. As a result, it becomes possible to promote sales of the application.
Therefore, according to this embodiment, the convenience of mutual customers between applications can be improved.

(3) The function of the installation notification unit 103, the function of the list request unit 104, the function of the customer information notification unit 106, and the function of the reward grant notification unit 107 are incorporated in each of the plurality of target applications. It is executed based on the SDK 11 (software). For example, the SDK 11A incorporated in the customer 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 information notification unit 106, and is incorporated in the customer destination application 20. The SDK 11 </ b> B thus executed executes the function of the installation notification unit 103 and the function of the reward grant notification unit 107. Note that the SDK 11A and the SDK 11B each have the same function, and execute a corresponding function depending on whether it is incorporated in the customer application 10 or the customer application 20.

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

(4) The reward processing unit 245 of the management server 200 determines that the customer destination application 20 (an example of a 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 the first period) is set with (an example of the first application), the customer destination application 20 is outside the campaign period. When it is determined that it has been installed, a normal reward process (an example of a second reward grant process) is executed.

  According to this, even if a customer destination application 20 has a campaign set with the customer source application 10, if the customer destination application 20 is installed outside the campaign period of the campaign, it can be a normal reward. . That is, when a campaign is set between the customer destination application 20 and the customer source application 10, if the customer destination application 20 is installed within the campaign period, the CP reward is set. If it is a period, it can be a normal reward.

(5) 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 acquisition unit 241 within the campaign period (first period) The customer destination application 20 is installed on the user terminal 100 (an example of a terminal device) during the campaign period.

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

  The reward processing unit 245 of the management server 200 receives the customer information when the customer information for the customer application 20 from the customer application 10 (an example of the first application) is within the campaign period. You may make it determine with the application 20 having been installed in the user terminal 100 within the campaign period. That is, if the customer 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 notified within the campaign period. Consider it installed.

(6) The reward user ID (an example of unique identification information) is stored in the user terminal 100. When the installed target application is a target application first installed in the user terminal 100 (an example of the own terminal device) among the plurality of target applications, the user terminal 100 acquires a reward user ID and acquires the reward A unique identification information acquisition unit 102 that stores a user ID in a terminal storage unit 140 (an example of a storage unit) so as to be referred to from any target application installed in the user terminal 100 is provided.

  Thus, according to the mutual customer sending 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 also common to the target application installed thereafter. Therefore, the reward user ID can be acquired and the system can be used without requiring the user to perform a special operation.

(7) Specifically, when the installed target application is installed in the user terminal 100, the unique identification information acquisition unit 102 receives the reward user ID (an example of unique identification information) in the terminal storage unit 140 (storage unit). In the example, the reward user ID is acquired when it is determined that the reward user ID is not stored in the terminal storage unit 140.
Thereby, the user terminal 100 can acquire the reward user ID when the target application is installed and activated 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 in the user terminal 100 (an example of the own terminal device), and the installed target application application The 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 associates and 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.

Thereby, when the target application is installed in 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. . Therefore, the management server 200 can specify the target application installed for each user terminal 100.
Even when the target application is installed regardless of this 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. Therefore, 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 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 installation notification information further including an application user ID of the installed target application of the user who installed the installed target application to the management server 200. Send. The management server 200 acquires the application user ID included in the installation notification information.
Depending on the target application, the timing for registering user information may differ depending on the target application, for example, when the user information is started for the first time, for example, when the tutorial is ended. Therefore, the management server 200 may acquire the application user ID (included in information other than the installation notification information 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 associates and 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. May be good.

  Thereby, when the target application is installed in the user terminal 100, the management server 200 recognizes the application ID of the installed target application, the application user ID in the installed target application, and the reward associated with the user terminal 100. The user ID can be managed in association with it. That is, the management server 200 can manage the application user ID for 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 related to the campaign, and stores the information in the campaign information storage unit 234 or the campaign participation application information storage unit 235 for management.
The list notification unit 242 of the management server 200 refers to the above-described information managed by the application management unit 221 and transmits information related to the campaign corresponding to one or more specific applications included in the application list.

  As a result, when the user terminal 100 displays the target application list LT based on the application list acquired from the management server 200 on the display unit 120, the user terminal 100 includes information on the campaign (the campaign information) for the specific application for which the campaign is set. Name, description, campaign period, etc.) can be displayed in association with each other.

(11) The application management unit 221 of the management server 200 manages information including a link destination of a posting place of information indicating a CP reward (an example of reward) as information on a campaign (an example of an event).
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 related to the campaign. Send information.

  Thereby, when the user terminal 100 displays the target application list LT based on the application list acquired from the management server 200 on the display unit 120, the CP reward of the campaign is indicated to the specific application for which the campaign is set. Information indicating the link destination of the information posting location can be displayed in association with each other. Note that the place where the information indicating the CP reward is posted is used as a link destination in order to give flexibility to the posting method so that various correspondences can be made according to the campaign content and time.

(12) Specifically, the application management unit 221 (an example of the first reward information management unit) of the management server 200 performs a CP reward (first reward of the first reward) set in advance corresponding to a campaign (an example of an event). Information indicating the link destination of the information posting location is stored in the campaign participation application information storage unit 235 for management. Moreover, the application management part 221 (an example of a 2nd reward information management part) shows the preset normal reward provided by each of a some target application and a normal reward process (an example of a 2nd reward provision process). The normal reward information associated with the information is stored in the normal reward information storage unit 232 for management.
The list notification unit of the management server 200 includes information indicating a normal reward for a target application for which no campaign is set with the customer-source application 10 (an example of the first application) among the plurality of target applications. An application list including information indicating a normal reward is transmitted to the user terminal 100 so as to be displayed in association with each other. On the other hand, the list notification unit displays the information indicating the above link destination in association with the target application for which a campaign is set with the customer source application 10 among the plurality of target applications. Then, an application list including information indicating the link destination is transmitted to the user terminal 100.

  Thus, when the user terminal 100 displays the target application list LT 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 for the target application for which no campaign is set. In addition, information indicating a link destination of a place where information indicating the CP reward (an example of reward) of the campaign can be displayed in association with the specific application in which the campaign is set.

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

  As a result, the mutual customer sending system 500 does not record customer customer information when the target application is installed regardless of this system, so that it can be excluded from normal rewards and CP rewards.

(14) The installation guidance instruction unit 244 of the management server 200 includes an application ID (an example of identification information) of the customer destination application 20 (an example of a second application) included in the customer information acquired by the customer information acquisition unit 243. The instruction information for guiding to the store page (screen) where the customer destination application 20 can be installed is transmitted to the user terminal 100.

  Thereby, when the target application sent from the customer source application 10 (an example of the first application) is selected, the user terminal 100 makes a special store page for the user that can install the selected target application. It can be displayed automatically without any operation.

(15) The 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 (an example of identification information) of the customer destination application 20 (an example of a second application). )It is included.
The reward grant notification unit 107 of the user terminal 100 (SDK11) transmits reward grant notification information including the above-described information to the management server 200.
The reward processing unit 245 of the management server 200, based on the reward grant notification information acquired from the customer destination application 20 installed in the user terminal 100, the customer source application 10 (of the first application) associated with the reward user ID. Remuneration grant information including an application user ID (an example of user information) is transmitted to the application server 310 (an example of a server device) corresponding to the customer source application 10.

  Thereby, the management server 200 can specify the user terminal 100 and the customer destination application 20 that have transmitted the acquired reward grant notification information, and a user (user) who uses the customer source application 10 on the user terminal 100 X) Remuneration grant information including the application user ID in the customer source application 10 of the user (user X) is transmitted to the application server 310 corresponding to the customer source application 10 so that a reward is granted to X). Can do.

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

  Thereby, the management server 200 refers to the campaign information storage unit 234 or the campaign participation application information storage unit 235 and specifies the campaign set in the customer destination application 20 that has transmitted the acquired reward grant notification information. Information relating to the campaign (for example, a reward grant period) can be specified. In particular, when a plurality of campaigns are set in the customer destination application 20, it is effective that this campaign ID is included in the reward grant 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) in a different period that does not overlap are set for a plurality of specific applications. At this time, the reward processing unit 245 of the management server 200 performs CP reward corresponding to the campaign (event) in 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 granting process) has been executed, the CP reward process (an example of the reward granting process) corresponding to the campaign of the above-described another period is not executed.

  As a result, in the mutual customer sending system 500, in the CP reward processing for the same customer destination application 20, the reward given by CP reward in another campaign is again given to the user who is given the reward by CP reward in a certain campaign. It can be prevented from being granted. In other words, the customer destination application 20 to which a reward is granted by CP reward is not a target of 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 arrival of the achievement point set in the campaign. When each of the plurality of achievement points is reached, a reward is given based on each arrival. However, even if a campaign B different from the campaign A is started in the subsequent period. Even if the achievement point set in the campaign B is reached, no reward is given.
Here, when the campaign period of the campaign B starts and the achievement point set in the campaign B is reached, the reward grant notification information is transmitted from the user terminal 100 to the management server 200. However, since customer information corresponding to campaign B is not transmitted from the user terminal 100 to the management server 200, the management server 200 does not manage customer information corresponding to the campaign B (customer information storage). There is no record corresponding to the part 237). As a result, since the reward establishment information corresponding to the campaign B is not managed in the reward establishment information storage unit 238, the management server 200 updates the reward establishment information even if the reward grant notification information for the campaign B is acquired. The reward grant notification information can be treated as invalid. Therefore, it is possible to control to prevent the CP reward from being given a double reward.

(18) The reward processing unit 245 of the management server 200 uses the CP reward process (an example of the first reward grant process) and the normal reward process (the second reward application process) of the customer destination application 20 (an example of the second application) in the user terminal 100. In the case where at least one of the examples of the reward granting process is executed, the other reward granting process is not executed.

  For example, in the management server 200, the establishment state included in the reward establishment information of the customer destination application 20 that has been subjected to the normal reward process or the CP reward process has already been updated to “1” (established). Therefore, even if the management server 200 acquires the reward grant notification information from the customer destination application 20 again, there is no reward establishment information that can be updated to “1” (established), and the reward grant notification information is not updated. Can be treated as invalid.

  As a result, the mutual customer sending system 500 can prevent the reward for normal rewards and the reward for CP rewards from being duplicated for the same customer application 20. That is, the customer destination application 20 to which a reward is given by normal reward is not subject to CP reward. In addition, the customer destination application 20 to which a reward is given by CP reward is not normally eligible for reward.

(19) In the above embodiment, for a campaign (an example of an event), a reward granting period (second) that starts from the beginning or middle of the campaign period (an example of the first period) and ends after the end of the campaign period Is set as an example. The reward grant notification unit 107 of the user terminal 100 (SDK11) transmits reward grant notification information to the management server 200. The reward processing unit 245 of the management server 200 acquires the reward grant notification information from the customer destination application 20 (an example of the second application) installed in the user terminal 100 within the reward grant period. A CP reward process (an example of a reward grant process) based on the reward grant notification information is executed.

  Thereby, even if the customer destination application 20 is installed in the user terminal 100 immediately before the end of the campaign period, the mutual customer sending system 500 reaches the achievement point where the reward of CP reward is given. The user can be given a period of time to try. In addition, the management server 200 can grant a CP reward (an example of a reward) when the reward grant notification information is acquired from the user terminal 100 within the reward grant period.

(20) Note that the reward grant notification unit 107 of the user terminal 100 (SDK11) receives the reward grant notification information when the timing at which the reward grant condition is satisfied is the reward grant period (an example of the second period). You may transmit with respect to the management server 200. FIG. Then, the reward processing unit 245 of the management server 200 acquires reward grant notification information from the customer destination application 20 (an example of a second application) when the timing at which the reward grant condition is satisfied is within the reward grant period. In addition, the CP reward process (an example of the reward grant process) based on the acquired reward grant notification information may be executed.

  In this case, the user terminal 100 transmits the reward grant notification information to the management server 200 only when the timing at which the reward grant condition is satisfied is the reward grant period. Therefore, the management server 200 is configured to acquire reward grant notification information from the user terminal 100 and receive a CP reward (an example of reward) when the reward granting condition is satisfied within the reward granting period. it can.

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

  Accordingly, the mutual customer sending system 500 can execute the corresponding CP reward process in response to the satisfaction of each of the plurality of reward granting conditions of the campaign set in the customer destination application 20. In other words, the user continues to use the customer destination application 20 in order to acquire as much as possible a plurality of rewards set in the campaign period (an example of the reward grant period). Therefore, the use of the customer destination application 20 can be increased.

(22) When the reward processing unit 245 of the management server 200 acquires reward grant notification information from the customer destination application 20 (an example of a second application) based on the fact that any of the plurality of reward granting conditions is satisfied In addition, when the acquired timing is within the reward grant period (an example of the second period), a CP reward process (an example of the reward grant process) based on the reward grant notification information is executed.

  That is, even when a plurality of reward granting conditions are set in the campaign, the management server 200 is rewarded at a timing when each of the plurality of reward granting conditions is satisfied (timing at which the management server 200 acquires the reward granting notification information). CP reward (an example of reward) can be granted only when it is within the grant period.

(23) Each of the plurality of reward granting conditions is, for example, a timing at which each of the plurality of achievement points set in advance in the processing by the customer destination application 20 (an example of the second application) is reached. The reward grant notification unit 107 of the user terminal 100 (SDK11), based on the satisfaction of each of the plurality of reward granting conditions, results point ID (results point information) indicating the reached result point among the plurality of result points. To the management server 200, respectively. And the reward process part 245 of the management server 200 is based on the satisfaction of each of several reward provision conditions, The achievement point ID which shows the achievement point which reached | attained among the several achievement points from the customer destination application 20 An application server that obtains reward grant notification information including (result spot information) and also provides reward grant information including the acquired result spot ID (result spot information) to the customer-source application 10 (an example of a first application) It transmits to 310 (an example of a server apparatus).

That is, the management server 200 gives the customer application 10 the result point ID indicating the result point reached in response to reaching each of the plurality of result points of the customer destination application 20 in the user terminal 100. It transmits to the corresponding application server 310.
Thereby, the mutual customer sending system 500 responds to the arrival of each of the plurality of achievement points of the campaign set in the customer destination application 20, and the CP reward (reward of reward) corresponding to each of the achievement points reached. An example) can be given.

(24) The reward grant notification unit 107 of the user terminal 100 (SDK11) includes arrival information indicating that one of the plurality of achievement points has been reached based on each of the plurality of reward granting conditions being satisfied. The reward grant notification information may be transmitted to the management server 200. Then, the reward processing unit 245 of the management server 200 reaches one of the plurality of achievement points from the customer destination application 20 (an example of the second application) based on the satisfaction of each of the plurality of reward granting conditions. In addition to acquiring the reward grant notification information including the arrival information indicating that it has been performed, the reward grant information corresponding to the number of times the reward grant notification information is acquired corresponds to the customer source application 10 (an example of the first application) May be transmitted to the application server 310 (an example of a server device).

  That is, the management server 200 does not include the achievement point ID in the reward granting information transmitted to the application server 310 corresponding to the customer source application 10 when reaching any one of the plurality of achievement points. Information indicating the number of acquisition times of information (that is, information indicating the number of achievement points and the number of achievement points) may be included. In this case, it is only necessary to negotiate in advance so that reward grant information including information indicating the number of times described above is exchanged between the application server 310 and the management server 200. Thus, even if the mutual customer sending system 500 includes information indicating the number of acquisition times of the reward grant notification information in the reward grant information instead of the result spot ID, the CP reward corresponding to each of the reached achievement points (an example of reward) Can be provided.

(25) The reward processing unit 245 of the management server 200 changes from the customer destination application 20 (an example of the second application) to any one of the plurality of achievement points based on the satisfaction of each of the plurality of reward granting conditions. An application server 310 (server device) that acquires reward grant notification information including arrival information indicating that it has arrived, and that corresponds to the customer source application 10 (an example of a first application) for reward grant information including the acquired arrival information For example).

  That is, the management server 200 does not include the achievement point ID in the reward granting information transmitted to the application server 310 corresponding to the customer source application 10 when reaching any one of the plurality of achievement points. The arrival information indicating that the achievement point has been reached (for example, flag information simply indicating that the achievement point has been reached) may be included. In this case, it is only necessary to arrange in advance that the reward grant information including the arrival information is simply exchanged between the application server 310 and the management server 200. And the application server 310 may count the frequency | count of acquisition of arrival information, and may provide the reward according to a count result. Therefore, the mutual customer sending system 500 is configured so that CP rewards (an example of rewards) corresponding to each of the reached achievement points are given even if the arrival information is simply included in the reward granting information instead of the achievement point ID. be able to.

  Thus, a plurality of reward granting conditions by CP reward can be provided. Here, the mutual customer sending system 500 does not need to know the setting contents of each reward granting condition, the total number of reward granting conditions, etc., and each time the reward granting condition is satisfied in the customer destination application 20 (in the result point) Each time it arrives, the result point ID, the information indicating the number of acquisition times of reward grant notification information, the arrival information, etc. are simply transmitted to the application server 310.

  In this embodiment, since the management server 200 manages information related to the target application corresponding to the mutual customer sending system 500, it is possible to prevent an application that does not correspond to this system from being a search target. Further, as a method for specifying an application installed in the user terminal 100, there is a method using a URL scheme. In this case, it is necessary to configure the URL scheme to be acquired from the management server 200. On the other hand, in this embodiment, installation information of the target application installed in the user terminal 100 is managed by the management server 200. Therefore, in this embodiment, the process at the time of producing | generating the application list used as the candidate selected as the customer's destination application 20 can be performed easily.

  Also, the process of downloading and installing from the application store 400 (an example of a store site) for purchasing the customer destination application 20 and the process of starting the customer destination application 20 after the installation is completed are left to the user's operation. It is unclear what operation will be performed during that time. For example, a user who is guided to the application store 400 that purchases the customer destination application 20 may download another application. Even in such a case, in the mutual customer sending system 500, since the customer sending information from the customer sending application 10 to the customer sending application 20 is managed, the reward process 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. Since the configuration of the mutual customer sending system 500 of the present embodiment is the same as that of the first embodiment, a characteristic process in the present embodiment will be described. In the first embodiment, with reference to FIG. 14, an application list excluding the target application installed in the process of step SE <b> 15 or an application list of a specific application in which a campaign is set with the customer source application 10. However, 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 a 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-app filter information) between applications for limiting target applications that can be sent to each other. The inter-app filter information for limiting the target applications that can be sent to each other is set as, for example, posting prohibition information that prohibits the target application selectable as the customer destination application 20 from being listed on the list LT.

  Note that this inter-app filter information is valid for normal rewards, even if a campaign is set between the target application and the customer-source application 10 for which no campaign is set with the customer-source application 10. This is information for filtering a specific application that is not in the campaign period.

  FIG. 16 is a diagram illustrating an example of the inter-app filter information stored in the inter-app filter storage unit 233. A filter ID (FilterID), a blocked application ID (ApIDfrom), and a blocked application ID (ApIDto) are associated with the inter-app filter information. The filter ID (FilterID) is a management ID issued in the order in which each piece of filter information is set so that each piece of inter-app filter information can be identified.

  In the blocked application ID (ApIDfrom), the application ID of the setting-side application that is set to prohibit the insertion in the target application list LT is set. On the other hand, in the blocked application ID (ApIDto), the application ID of the set-side application that is prohibited from being listed in the target application list LT of the setting-side application is set. That is, the inter-app filter storage unit 233 stores inter-app filter information that is a combination of a blocked application ID (application ID of the setting-side application) and a blocked application ID (application ID of the set-side application).

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

  Note that the blocked application ID (application ID of the setting side application) and the blocked application ID (application ID of the set side application) in the inter-app filter information shown in FIG. Also good. That is, the 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 set-side application). In the case of the customer, the target application set in the application ID to be blocked (the application ID of the setting side application) may be excluded from the application list that can be selected as the customer application 20.

  In addition, when it is desired to participate only in the CP reward without participating in the normal reward depending on the target application, the application ID of the target application is set to the blocked application ID (ApIDto), and the blocked application ID (ApIDfrom) is set to “ null ”. Thus, outside the campaign period, the target application is not listed in the target application list LT for customers from any target application. For example, in the case where an existing application is carrying out mutual customers by normal rewards before participating in the mutual customer sending system 500, and only CP rewards are intended to participate in the system. Can respond. Information regarding the target application for which only the CP reward is to be participated without participating in the normal reward is stored in association with the application ID (ApID) of the target application in the target application information storage unit 231 that stores the target application information regarding the target application. You may make it make it.

[Summary of Second Embodiment]
As described above, the application management unit 221 of the management server 200 includes the setting-side application that sets prohibition of listing in the target application list LT based on the application list, and the target application list LT of the setting-side application. The inter-app filter information (an example of the first post-prohibition information) that combines the set-side application that is prohibited from being posted on is stored in the inter-app filter storage unit 233 for management.
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 source application 10 (an example of the first application) as a set-side application. If there is a campaign (an example of an event) between the setting-side application indicated by the inter-application filter information and the customer-source application 10, the setting side The application list of the target application excluding the application is transmitted to the user terminal 100.

  Thereby, in the mutual customer sending system 500, it is possible to set the relationship of the target application that you do not want to send the customer in the normal reward to the management server 200. For example, if there is an application for which rating (age restriction) is set, a customer sending application 10 for which rating is not set to a customer destination application 20 for which rating is set Can be prevented.

  Further, the list notification unit 242 of the management server 200 refers to the inter-app filter information managed by the application management unit 221, and there is inter-app filter information that sets the customer source application 10 as the setting side application. If a campaign is not set between the set-side application indicated by the first posting prohibition information and the customer-source application 10, the application list of the target application excluding the set-side application Is transmitted to the user terminal 100.

  As a result, the target applications set in the setting application and the setting-side application of the inter-app filter information can mutually (bidirectionally) be prohibited (blocked) from being listed in the application list.

In addition, the application management unit 221 of the management server 200 includes the inter-application filter information (second posting prohibition information) in which only the set-side application that is prohibited from being listed in the target application list LT based on the application list is registered. Is stored in the inter-app filter storage unit 233 for management.
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-source application 10 (first application). When a campaign (an example of an event) is not set between the target application and the application list of the target application, the application list is transmitted to the user terminal 100.
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 in which information corresponding to the inter-app filter information is stored in the target application information storage unit 231, only the CP reward is allowed to participate.

  As a result, in the case of a target application for which only the campaign wants to participate in the mutual customer sending system 500, outside the campaign period, a customer from any target application is not listed in the target application list LT. Can do.

<Modification of the first and second embodiments>

  The embodiment of the present invention has been described in detail with reference to the drawings. However, the specific configuration is not limited to the above-described embodiment, and includes a design and the like within a scope not departing from the gist of the present invention. For example, the functions described in the first 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 at least one of installation notification information (an example of first information), an application list (an example of second information, for example, a plurality of target applications). Information indicating one target application), list request notification information, customer information (for example, customer source information or customer destination information), instruction information (an example of information for displaying an installable screen on the user terminal 100) ), Or an example in which reward grant notification information is directly communicated with the user terminal 100. Similarly, the terminal communication unit 130 (transmission / reception unit) of the user terminal 100 directly communicates the installation notification information, application list, list request notification information, customer information, instruction information, or reward grant notification information with the management server 200. An example was explained.

  Here, the communication unit 210 (transmission / reception unit) of the management server 200 includes the customer source application 10 (first application) or the customer destination application 20 (second application), and the application server 300 (server device) corresponding to each. The communication session may be established directly via the user terminal 100 and then directly communicated with the user terminal 100. Similarly, the terminal communication unit 130 (transmission / reception unit) of the user terminal 100 includes the customer application 10 (installed target application) or the customer application 20 (selected target application), and the application server 300 corresponding to each. You may communicate with the management server 200 directly after establishing a communication session via (server apparatus).

In addition, when communicating with the management server 200 directly from the user terminal 100, you may make it establish a communication session as needed. In other words, both the case of directly communicating with the management server 200 before establishing the communication session and the case of directly communicating with the management server 200 after establishing the communication session may be included.
For example, the installation notification information communicates directly with the management server 200 before establishing a communication session, and other information communicates directly with the management server 200 after establishing the communication session. Good. By doing in this way, the application that does not include the application server 320 corresponding to the customer destination application 20, that is, the application that operates stand-alone in the user terminal 100, as the customer destination application 20 that is the target of the normal reward, is the target application. Can be handled as That is, when transmitting installation notification information indicating that an application that operates in a stand-alone manner is installed, the user terminal 100 does not perform a process of establishing a communication session via the application server 300 (server device). It is possible to directly communicate with the management server 200.

  FIG. 17 is a flowchart for explaining the operation of the communication session establishment process. This communication session establishment process (communication session establishment process) is a case where the customer source application 10 or the customer destination application 20 is activated on the user terminal 100, and the SDK 11A and the SDK 11B communicate with the management server 200 for the first time. For example, the initialization process described with reference to FIGS. 14 and 15 is performed. FIG. 17 shows a communication session establishment process performed in the initialization process shown in FIG. The communication session establishment process can be performed in the same manner as the initialization process shown in FIG. In FIG. 17, parts corresponding to the respective processes in FIG. Note that it is assumed that a communication session has already been established between the user terminal 100 and the application server 310.

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

  Note that installation notification information (an example of first information), an application list (an example of second information, for example, information indicating at least one target application among a plurality of target applications), list request notification information, customer information (for example, , Customer source information or customer destination information), instruction information (an example of information for displaying an installable screen on the user terminal 100), or part of the reward grant notification information directly from the user terminal 100 Without communicating with the management server 200, communicate with the user terminal 100 via the application server 300 (server device) corresponding to the customer application 10 (first application) or the customer application 20 (second application). Also good. That is, the communication unit 210 (transmission / reception unit) of the management server 200 sends the installation notification information, application list, list request notification information, customer information, instruction information, or reward grant notification information to the customer source application 10 (first application). Or you may make it communicate with the user terminal 100 via the application server 300 (server apparatus) corresponding to the customer application 20 (2nd application), or communicate with the user terminal 100 directly.

Further, the communication unit 210 (transmission / reception unit) of the management server 200 sends the installation notification information, application list, list request notification information, customer information, instruction information, or reward grant notification information to the customer 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's destination application 20 (2nd application). Similarly, the terminal communication unit 130 (transmission / reception unit) of the user terminal 100 includes an application server 300 (server device) corresponding to the customer source application 10 (installed target application) or the customer destination application 20 (selected target application). ) To communicate with the management server 200.
Thus, even if the user terminal 100 and the management server 200 communicate with each other through the application server 300, the mutual customer sending system 500 is the same as the customer sending process and reward as in the first embodiment and the second embodiment. Processing can be performed, and similar effects can be obtained.

(2) In the above embodiment, an example in which the application user ID (ApUID) is included in the installation notification information and transmitted from the user terminal 100 (SDK 11) to the management server 200 has been described. However, the present invention is not limited to this. 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, in step SA21, the initialization processing unit 101 of the SDK 11A notifies the application server 300 of the reward user ID when transmitting the one-time token acquisition request information to the application server 300. Furthermore, the application server 300 transmits the reward user ID, application ID, and application user ID to the management server 200. The installation information management unit 222 of the management server 200 includes, as the application user ID (ApUID) corresponding to the 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. Thus, by transmitting the application user ID from the application server 300 instead of from the user terminal 100 (SDK11), it becomes unnecessary to manage the application user ID at the user terminal 100 (SDK11).

  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 cannot be performed. However, the transmission of the installation notification information indicating that the target application installed in the user terminal 100 is installed to the management server 200 does not have to be directly related to the registration of the user information. Therefore, the user terminal 100 transmits installation notification information to the management server 200 regardless of whether user information is registered 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, the reward processing unit 245 has explained an example in which the CP reward processing is executed based on the fact that the reward grant notification information is acquired from the SDK 11B of the customer destination application 20 of the user terminal 100. It is not limited to. For example, the CP reward process may be executed based on the acquisition of reward grant notification information from the application server 320 corresponding to the customer destination application 20. In this case, the reward grant notification information (result spot arrival notification) may include the application ID of the customer destination application 20, the application user ID, the campaign ID, and the result spot ID (RewardSpotID).
For example, the reward processing unit 245 of the management server 200 acquires reward grant notification information (result point arrival notification) transmitted from the application server 320. Next, the reward processing unit 245 identifies installation information corresponding to the application ID and application user ID of the customer destination application 20 from the installation information stored in the installation information storage unit 236, and corresponds to the identified installation information. Reverse reward user ID. Then, the reward processing unit 245 responds to the customer information based on the reverse reward user ID and the fact that the customer information record for the customer application 20 is managed in the customer information management unit 223. In association with the reward management ID, the achievement point ID (RewardSpotID) included in the acquired reward grant notification information is set, and the reward establishment information having the establishment status (RewardStatus) as the flag “0” (not notified) is generated, and the reward The establishment information storage unit 238 stores the information. The subsequent processing is the same as in the above embodiment. Thus, by transmitting the reward grant notification information (result point arrival notification) from the application server 320, the processing burden on the user terminal 100 (SDK11B) can be reduced.

(4) In the above embodiment, the reward user ID is unique identification information (unique identification unique in the mutual customer sending system 500) that can uniquely identify the installed user terminal 100 when the target application is first installed. Although the example generated as information) has been described, the present invention is not limited to this. For example, it is good also considering the terminal identification number and telephone number (for example, in the case of a smart phone) uniquely set to the user terminal 100 as a reward user ID. However, it is possible to improve the security by generating and using the reward user ID as in this embodiment without using personal information such as a terminal identification number or a telephone number. Further, by using unique identification information in the mutual customer sending system 500 without using a terminal identification number or a telephone number as a reward user ID, the user terminal 100 (terminal device) owned by the user is replaced by a new one. Even if it is changed, etc., the mutual user system 500 is used while maintaining the state from the user terminal 100 before the change by moving the reward user ID to the user terminal 100 after the change through a predetermined procedure. Is possible.

  Further, the process of displaying the application list page (target application list LT) in step SA25 and step SA26 in FIG. 14 and the process of transmitting customer information when a target application to be downloaded is selected from the application list are as follows: Instead of the process executed by the SDK 11, another application (for example, a browser) installed in the user terminal 100 that is not related to the process of the SDK 11 may be activated and executed. For example, by generating application list page data that is redirected to the browser at the user terminal 100 from the management server 200 and transmitting the data to the user terminal 100, the browser is activated at the user terminal 100, and the application list page is displayed. It may be displayed. Further, by sending the application list page data including the application ID (ApID) of the customer source application 10 (game A) included in the list request notification information, the customer destination application selected on the application list page is transmitted. The customer information including the application ID (ApID) of 20 (game B), the application ID (ApID) of the customer source application 10 (game A), and the reward user ID (RewardUID) is sent from the browser to the management server. 200 may be transmitted.

Further, the CP reward process may be executed based on the installation of the customer destination application 20 as in the normal reward process. In this case, the reward granting condition in the customer destination application 20 may be that the customer destination application 20 is installed in the user terminal 100.
In addition, if all the specific applications that execute the campaign have the customer application 20 installed as the first achievement point, the customer application 20 of the reward grant notification information corresponding to the achievement of the achievement point is provided. You do not have to send from. In this case, the management server 200 performs a reward granting process similar to a normal reward, and transmits reward reward information including a campaign ID to the application server 310, so that the CP corresponding to the normal reward is transmitted from the application server 310. Rewards will be rewarded. Specifically, the processing of steps SE23 to 24 may be performed for both CP reward and normal reward without performing the determination processing of step SE22 in the flowchart of FIG.

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

  Further, the storage unit 230 of the management server 200 may be provided in a server device different from the management server 200. Then, the management unit 220 or the control unit 240 of the management server 200 communicates with the storage unit 230 provided in a server device different from the management server 200 via the network NW, so that each unit included in the storage unit 230 stores. Each piece of information may be managed.

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

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

<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 descriptions.

(1) In the mutual customer sending system 500 of this 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 regarding a plurality of target applications to be managed. Here, the management target refers to a target managed as a target application corresponding to the mutual customer sending system 500, for example.
When one of the plurality of target applications is executed by the user terminal 100 (an example of a terminal device), the installation notification acquisition unit 241 (an example of the first information acquisition unit) The installation notification information (an example of the first information) transmitted from the user terminal 100 in response to being executed by the user terminal 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-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.
In response to the list notification unit 242 transmitting the application list, the reward processing unit 245 selects a target application (an example of a second application, a customer application) among the target applications indicated by the application list transmitted from the list notification unit 242. A reward granting process is performed based on the fact that the previous application 20) has been executed by the user terminal 100 or has become executable.

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. In addition, that the target application is ready to be executed by the user terminal 100 means that the target application is installed in the user terminal 100, for example.
Note that a configuration in which a part of the program that executes the target application in the user terminal 100 is installed in the user terminal 100 and a device other than the user terminal 100 has the remaining part of the program may be employed. For example, the program that executes the target application installed in the user terminal 100 may be only a program that is at least necessary for starting execution of the target application. And the remaining program is good also as a structure which the server apparatus (for example, application server 300) which can communicate with the user terminal 100, or another terminal apparatus (for example, other user terminal 100) has.
In addition, a configuration in which an apparatus other than the user terminal 100 has all the programs of the target application executed by the user terminal 100 may be employed. In other words, a program that executes the target application is not installed in the user terminal 100, but a server device that can communicate with the user terminal 100 (for example, the application server 300) or another terminal device (for example, another user terminal 100). It is good also as a structure to have. That is, that the target application is executed by the user terminal 100 includes a case where the target application is executed in a server device connected to the user terminal 100 via a 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, the fact that the target application is ready to be executed by the user terminal 100 means that, for example, registration (for example, user registration) that can be used for the server apparatus that is the main body that executes the target application is performed. This means that the target application can be executed via the communication network in accordance with an instruction from.

The first information described using the installation notification information as an example may be 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 installed. It may be information indicating something other than being installed. The information indicating things other than being installed may be, for example, information indicating activation, information indicating execution, simple flag information, and 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 first information acquired in response to the target application being executed by the user terminal 100.
Note that, in the operation of the mutual customer transmission process described with reference to FIG. 14 described above, the user terminal 100 receives the first information (the installation notification information in FIG. 14) when the target application is activated for the first time. ) Is transmitted to the management server 200, but is not limited to this. For example, the user terminal 100 may transmit first information (for example, installation notification information) to the management server 200 every time the target application is activated.

The second information described using the application list as an example includes any information indicating at least one target application for which installation notification information has not been acquired from the user terminal 100. There may be. For example, the second information may be data of an application list page that can be displayed on the user terminal 100, or information indicating a link destination of the application list page (for example, redirect instruction information). In this application list page, information indicating a plurality of target applications may be displayed in a vertical (vertical) direction (so-called list display) or in a horizontal (horizontal) direction. Alternatively, they may be displayed in a grid (lattice) in the vertical and horizontal directions (so-called grid display). Further, the second information may be data that simply includes information (for example, an application name, an application icon image, an application ID, etc.) indicating the target application so that the second information can be displayed on the user terminal 100.
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. May be included.

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 source application 10 executed by the user terminal 100. Can do.
Here, receiving a request based on the customer source application 10 executed by the user terminal 100 is, for example, an application of a target application that can be installed in the user terminal 100 in the customer source 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 the list request notification information to the management server 200 in response to, for example, activation of the customer source application 10 without any user operation. That is, receiving a request based on the customer source application 10 executed by the user terminal 100 acquires, for example, list request notification information transmitted from the user terminal 100 in response to the customer source application 10 being activated. It is good as well.

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

(2) For example, the reward processing unit 245 may perform the reward granting process when the customer destination application 20 (an example of the second application) is executed by the user terminal 100 or becomes executable. Good.

  As a result, the management server 200 receives the customer destination application 20 from the customer source application 10 when the customer destination application 20 has been executed by the user terminal 100 or has become executable (for example, installed). For example, it is determined that the customer has been sent to 20, and a reward can be given to the user X using the user terminal 100, for example.

(3) The reward processing unit 245, for example, the installation notification acquisition unit 241 (an example of the first information acquisition unit) 241 (an example of the first information acquisition unit) installation notification information (an example of the first information) corresponding to the customer destination application 20 (an example of the second application) ) May be determined that the customer destination application 20 has 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 installation and activation of the customer destination application 20 in the user terminal 100 (that is, in response to execution of the customer destination application 20). When the information is acquired, it may be determined that the customer destination application 20 has been executed by the user terminal 100. Note that the reward processing unit 245 may determine that the customer destination application 20 has been executed by the user terminal 100 when the first information is acquired in addition to the installation notification information.
In addition, the reward processing unit 245 displays information indicating that the customer destination application 20 is installed regardless of the first information, for example, a target application other than the customer source application 10 installed in the user terminal 100. Or when it is acquired by the function of the OS of the user terminal 100, it may be determined that the customer destination application 20 is ready to be executed by the user terminal 100.

  Accordingly, the management server 200 can determine that the customer destination application 20 has been executed by the user terminal 100 by acquiring the installation notification information of the customer destination application 20 transmitted from the user terminal 100. 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 install the installation information. And the reward processing unit 245 may acquire the result of the determination.

(4) The reward processing unit 245 is set in the customer destination application 20 that the customer destination application 20 (an example of the second application) has been executed by the user terminal 100 or has become executable. Reward grant processing may be performed based on satisfaction of the reward grant condition. For example, when the customer destination application 20 is installed in the user terminal 100 and the reward granting conditions set in the customer destination application 20 are satisfied, the reward processing unit 245 sends the customer destination application 10 to the customer destination application. The reward granting process may be performed on the assumption that the customer to 20 has been established.

  As described above, the management server 200 is rewarded based on the satisfaction of the reward granting conditions set in the customer destination application 20, so that the customer destination application 20 is simply installed. Alternatively, the reward can be given on condition that the customer destination application 20 is used, not just executed (for example, simply activated).

(5) The application management unit 221 manages information related to a campaign period (an example of a first period) set for some or all of a plurality of target applications. The list notification unit 242 (an example of the second information notification unit) is a target application (an example of a terminal device) executed by the user terminal 100 (an example of a terminal device) among the target applications (that is, specific applications) for which the campaign period is set. The target application (specific application) in which at least one of the campaign periods has not been acquired from the user terminal 100 by receiving a request based on an example of the first application, the customer source application 10) is shown. An application list including information (an example of second 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 selects a target application (an example of a second application, among the target applications indicated by the application list transmitted from the list notification unit 242). The reward application process is performed based on the fact that the customer destination application 20) is executed by the user terminal 100 during the campaign period or is in an executable state.

Thereby, the management server 200, when the campaign period is set in the customer source application 10 executed by the user terminal 100 (that is, when the customer source application 10 is a specific application), the customer source application By receiving the request based on 10, information indicating at least one target application that is not installed in the user terminal 100 among the target applications for which the campaign period is set can be transmitted to the user terminal 100. Note that the management server 200 transmits, to the user terminal 100, information indicating at least one target application that is not installed in the user terminal 100 among the target applications for which a campaign period is set with the customer source application 10. You may send it.
In addition, the management server 200 is in a state in which the customer destination application 20 out of information indicating at least one target application that is not installed in the user terminal 100 has been executed by the user terminal 100 during the campaign period or has become executable. Based on that, it can be determined that the customer has been established from the customer source application 10 to the customer destination application 20 within the campaign period, and for example, a reward can be given to the user X using the user terminal 100.

(6) For example, the reward processing unit 245 makes the customer application 20 (an example of the second application) executed by the user terminal 100 within the campaign period (an example of the first period) or in an executable state. As a result, the reward granting process may be performed.

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

  The reward processing unit 245 acquires the installation notification information (an example of the first information) corresponding to the customer destination application 20 (an example of the second application) by the installation notification acquisition unit 241 (an example of the first information acquisition unit). It is determined whether the customer destination application 20 is executed by the user terminal 100 within the campaign period or outside the campaign period, depending on whether or not the timing is within the campaign period (an example of the first period) Also good.

  For example, the reward processing unit 245 acquires the installation notification information (an example of the first information) corresponding to the customer destination application 20 (an example of the second application) by the installation notification acquisition unit 241 (an example of the first information acquisition unit). When the timing is within the campaign period (an example of the first period), it may be determined that the customer destination application 20 has been executed by the user terminal 100 within the campaign 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 based on 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 is in a state in which the customer terminal application 20 (an example of the second application) has been executed by the user terminal 100 within the campaign period (an example of the first period) or can be executed. In addition, the reward granting process may be performed based on the fact that the reward granting conditions set in the customer destination application 20 are satisfied.

  As described above, the management server 200 is rewarded based on the satisfaction of the reward granting conditions set in the customer destination application 20, so that the customer destination application 20 is simply installed. Alternatively, the reward can be given on condition that the customer destination application 20 is used, not just executed (for example, simply activated).

(8) For example, the application management unit 221 manages information related to 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. And When one of the plurality of target applications is executed by the user terminal 100 (an example of a terminal device), the installation notification acquisition unit 241 (an example of the first information acquisition unit) The installation notification information (an example of the first information) transmitted from the user terminal 100 in response to being executed by the user terminal 100 is acquired. In addition, the list notification unit 242 (an example of a second information notification unit) receives a request based on a target application (first application, customer-source application 10) executed by the user terminal 100 among a plurality of target applications. Then, 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 selects a target application (an example of a second application, among the target applications indicated by the application list transmitted from the list notification unit 242). When the campaign period is set for the customer application 20), the customer application 20 (an example of the second application) is executed by the user terminal 100 within the campaign period or is executable. The reward granting process is performed based on the situation.
On the other hand, the reward processing unit 245 applies the campaign period to the target application (an example of the second application, the customer destination application 20) selected from the target applications indicated by the application list transmitted from the list notification unit 242. Is not set, the reward granting process is performed based on the fact that the customer destination application 20 (an example of the second application) has been executed by the user terminal 100 or has become executable.

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

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

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

  In addition, the mutual customer sending system 500 may be configured to perform only reward grant processing (for example, CP reward processing) when the campaign period is set in the customer destination application 20, or when the campaign period is not set. It is good also as a structure which performs only reward provision processing (for example, normal reward process), and it is good also as a structure which performs both reward provision processing.

(9) When the campaign period (an example of the first period) is set for the customer destination application 20 (an example of the second application), the reward processing unit 245 Based on the fact that it has been executed by the user terminal 100 within the period or has become executable, and the reward granting conditions set in the customer destination application 20 have been satisfied, Reward processing (an example of first reward grant processing) is performed.

  On the other hand, if the campaign period (an example of the first period) is not set for the customer destination application 20 (an example of the second application), the reward processing unit 245 As a result of being executed by 100 or being in an executable state, normal reward processing (an example of second reward granting processing) is performed as the above-described reward granting processing.

  Thus, in the CP reward process when the campaign period is set for the customer destination application 20, the management server 200 has simply been executed or can be executed by the customer destination application 20. It is possible to give a reward on the condition that the customer destination application 20 is used, not just (for example, a state where the customer application 20 is simply activated or not installed but activated). On the other hand, in the case of the normal reward process in which the campaign period is not set for the customer destination application 20, the management server 200 is merely installed or executed (for example, simply activated). Can be rewarded.

(10) The reward processing unit 245 determines whether the customer destination application 20 is in the case where the campaign period (an example of the first period) is set in the customer destination application 20 (an example of the second application). When it is executed outside the campaign period or becomes executable, the second reward giving process is performed.

  According to this, even if a campaign period is set in the customer destination application 20, a normal reward can be made if the campaign is executed outside the campaign period or becomes executable. In other words, when the campaign period is set in the customer destination application 20, if the timing at which the customer application 20 is executed or becomes executable is within the campaign period, CP reward processing, If it is a period, normal reward processing can be performed.

  In the CP reward process, a reward may be given when the customer destination application 20 is executed by the user terminal 100 during the campaign period or becomes executable. In other words, when the campaign period (an example of the first period) is set for the customer destination application 20 (an example of the second application), the reward processing unit 245 determines that the customer destination application 20 If the terminal device is executed or is in an executable state, a CP reward process (an example of a first reward grant process) may be performed as the reward grant process described above.

Further, in the normal reward process, the customer destination application 20 has been executed by the user terminal 100 or has become executable, and the reward granting conditions set in the customer destination application 20 have been satisfied. You may give a reward based on it.
That is, when the campaign period (an example of the first period) is not set for the customer destination application 20 (an example of the second application), the reward processing unit 245 Based on the fact that it has been executed by 100 or has become executable, and the reward granting conditions set in the customer destination application 20 are satisfied, the normal reward process (second An example of the reward granting process).

(11) In the mutual customer sending 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 above-described management server 200 (an example of a management device). Here, the above-described management server 200 manages customer information indicating a customer from a target application serving as a customer source to a target application serving as a customer destination among a plurality of target applications. Based on this, it is managed that the target application of the customer destination has been installed. For example, the management server 200 transmits, as a customer information indicating a customer from a target application serving as a customer, to a target application serving as a customer, out of a plurality of target applications. Customer information and customer destination information indicating a target application as a customer destination are associated with each other 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 information notification unit 106.
The installation notification unit 103 includes, in one target application installed in the user terminal 100 (an example of the own terminal device), installation notification information (an example of first information) indicating that the target application has been installed. Send to. The list request unit 104 manages information indicating at least one target application among the plurality of target applications based on a first operation in one target application (for example, the customer source application 10, the first application). When making a request to the client 200, the customer source information (for example, the application ID of the customer sender application 10) indicating the one target application is transmitted to the management server 200. The customer information notifying unit 106 includes customer information indicating the target application selected based on the second operation from the 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 and the application ID of the second application) are transmitted to the management server 200. For example, the customer information notification unit 106 transmits customer destination information indicating the target application selected based on the second operation to the management server 200 as customer information.

As described above, in the mutual customer system 500 according to the present embodiment, the management server 200 that manages a plurality of specific applications included in the target application corresponding to the mutual customer system 500, and a user terminal that can communicate with the management server 200 100, the other target application (for example, the customer destination application 20) is installed in the user terminal 100 from the one target application (for example, the customer source application 10). Customers can be sent to the customer destination application 20).
Therefore, according to the present embodiment, it is possible to improve customer convenience between applications.

  Here, the customer sending information is information indicating customer sending from the customer sending application 10 to the customer destination application 20. Typically, the customer information is a 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. This is information indicating the customer destination application 20 (an example of the second application) among the target applications indicated by the transmitted application list, in accordance with the application list (an example of the second information) transmitted by the component example). For example, the application ID of the customer destination application 20 may be used as customer information. Further, the application ID of the customer destination application 20 (an example of customer destination information) may be used as the customer information in association with the application ID of the customer source application 10 (an example of customer source information). Further, in association with the reward user ID corresponding to the user terminal 100, the application ID of the customer destination application 20 may be used as customer information.

For example, the customer information notifying unit 106 transmits the customer information to the management server 200 in association with a reward user ID (an example of unique identification information) corresponding to the user terminal 100 (an example of the own terminal device). May be.
Thereby, the management server 200 can specify the user terminal 100 that has transmitted the customer information.

(12) In addition, the management server 200 may manage information related to a campaign period (an example of a first period) set for a specific application that is 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 some of the plurality of target applications.
The list request unit 104 (an example of a request unit) of the user terminal 100 (SDK11) is a first application in one specific application (for example, the customer source application 10) installed in the user terminal 100 (an example of the own terminal device). When requesting information indicating at least one specific application among the specific applications to the management server 200 based on the operation, the customer source information indicating the one specific application (for example, the customer application 10 Application ID) may be transmitted to the management server 200. The customer information notifying unit 106 is selected based on the second operation during the campaign period from the specific applications indicated by the information indicating the at least one specific application acquired from the management server 200. Customer destination information indicating a specific application (for example, an application ID of the customer destination application 20) may be transmitted to the management server 200.

  As described above, in the mutual customer sending system 500 according to the present embodiment, information related to the campaign period set for a specific application that is a part or all of the target application corresponding to the mutual customer sending system 500 is managed. By the management server 200 and the user terminal 100 communicable with the management server 200, the user terminal 100 can change from one specific application (an example of the customer source application 10) to another specific application (an example of the customer destination application 20). ) Can be installed, customers can be sent to another specific application (an example of the customer destination application 20).

(13) The SDK 11 (in which the functions of the installation notification unit 103, the function of the list request unit 104 (an example of a request unit), and the function of the customer information notification unit 106 are incorporated in each of a plurality of target applications. Based on an example of software). For example, the SDK 11A incorporated in the customer 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 information notification unit 106. The function of the reward grant notification unit 107 described above 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 destination application 20 may execute the function of the installation notification unit 103 and the function of the reward grant notification unit 107. Note that the SDK 11A and the SDK 11B each have the same function, and may execute a function corresponding to whether it is incorporated in the customer-source application 10 or the customer-destination application 20. .

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

(14) The reward grant notification unit 107 of the user terminal 100 (SDK 11) is set in the customer destination application 20 (an example of a target application or a specific application selected as a customer destination) indicated by the customer destination information. When the reward granting conditions are satisfied, the customer destination information indicating the customer destination application 20 (for example, the application ID of the customer destination application 20), and the reward user ID associated with the user terminal 100 (unique identification information) The above-described reward grant notification information is transmitted to the management server 200 in association with the management server 200.

  The reward grant 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 destination application 20 (an example of a second application). An example) may be associated. Then, the reward grant notification unit 107 of the user terminal 100 (SDK 11) displays the reward grant notification information in which the reward user ID associated with the user terminal 100 and the application user ID in the customer destination application 20 are associated with each other. May be sent to.

  The reward grant notification unit 107 may directly transmit the reward grant notification information described above to the management server 200, or the application server 300 (for example, the application server 320 corresponding to the customer destination application 20). It may be transmitted to the management server 200 indirectly via Further, the user terminal 100 may be configured not to include the reward grant notification unit 107. In this case, the application server 300 (for example, the application server 320 corresponding to the customer destination application 20) corresponds to the campaign in advance. When it is determined whether or not the set reward granting condition is satisfied and it is determined that the reward granting condition is satisfied, the reward granting notification information may be transmitted to the management server 200.

  Then, the reward processing unit 245 of the management server 200 confirms that the reward granting condition is satisfied based on the reward granting condition set in the customer destination application 20 (an example of the second application) being satisfied. When the reward grant notification information shown is acquired from the customer destination application 20 executed by the user terminal 100 or the application server 320 (an example of a server device) corresponding to the customer destination application 20, the acquired reward grant notification information Based on the reward granting process.

  Thus, when the reward granting conditions set for the customer destination application 20 are satisfied in the user terminal 100, the management server 200 can perform the reward granting process by acquiring the reward grant notification information. it can.

For example, the reward processing unit 245 of the management server 200, based on the fact that the reward granting condition set in the customer destination application 20 (an example of the second application) is satisfied, the application user ID ( Remuneration grant information associated with an example of user information of the first application is transmitted to the customer source application 10 executed by the user terminal 100 or the application server 310 corresponding to the customer source application 10 (an example of a server device). To do.
Here, the management server 200 includes an application user information acquisition unit that acquires user information of the target application. For example, the application user information acquisition unit acquires an application user ID (an example of user information of the first application) in the target application in association with a reward user ID (an example of 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 user ID of the target application that has transmitted the installation notification information may be included in the installation notification information. As described above, the function of the application user information acquisition unit may be included in another function.

  Thereby, when the reward granting conditions set in the customer destination application 20 are satisfied in the user terminal 100, the management server 200 provides the customer source application to the user (user X) who uses the user terminal 100. The reward in 10 can be given.

  In addition, although the example of the process in which the reward in the customer origination application 10 is provided to a user was demonstrated as a reward provision process, it replaces with the customer origination application 10 and the process in which the reward in the customer destination application 20 is provided to a user. It is good. In this case, the management server 200, for example, the customer application ID (ApIDto) included in the customer information stored in the customer information storage unit 237 and the 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 destination application 20 based on the notification destination URL (NoticeURL) included in the information. In addition, as a reward grant process, it is good also as a process in which both the reward in the customer origination application 10 and the reward in the customer destination application 20 are provided to a user, and the reward which can be shared and used in a some target application to a user It is good also as processing to be given.

  In addition, as a reward granting process, a reward that can be used in another application different from the target application, or a reward that can be used on a website (for example, a currency that can be used when buying and selling goods and services through communication via a communication network, (Points etc.) may be given to the user. In this case, for example, the management server 200 temporarily manages information related to a reward given to the user, and then a predetermined procedure is performed, thereby providing a reward that can be used by another application or a reward that can be used on a website. As described above, the managed reward information may be transmitted to a server device corresponding to another application or a server device corresponding to a website.

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

  Thereby, 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 the reward giving process because there is customer sending information. If the target application is installed regardless of this system, it is possible to prevent the reward granting process from being performed because there is no record of customer information.

  Further, the reward processing unit 245 of the management server 200 receives customer information corresponding to the customer destination application 20 in the customer information management unit 223 when the reward granting conditions set in the customer destination application 20 are satisfied. You may perform the above-mentioned reward provision process on the condition that it is managed.

  Thereby, the mutual customer transfer system 500, when the customer destination application 20 is executed by the user terminal 100 and the reward granting conditions set in the customer destination application 20 are satisfied by this system, Therefore, if the target application is installed without relying on this system, there is no record of customer information, so that it is not possible to perform the reward granting process.

For example, the customer information acquisition unit 243 uses the reward user ID (an example of unique identification information) associated with the user terminal 100 and the customer source application 10 (an example of the first application) as the customer information described above. Acquired in association with an ID (an example of identification information) and an application ID (an example of identification information) of the customer application 20 (an example of a second application). The customer information management unit 223 associates the reward user ID associated with the customer information, the application ID of the customer source application 10, and the application ID of the customer destination application 20 and manages them as a record of customer information. .
Thereby, since the management server 200 can specify the user terminal 100 and the customer-source application 10 where the customer is sent to the customer-destination application 20, the management server 200 can identify the user who uses the user terminal 100. A reward granting process in which a reward in the customer source application 10 is given can be performed.

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

The customer information management unit 223 uses an application ID (an example of identification information) of the customer application 20 (an example of a second application) as a reward user ID (an example of unique identification information) associated with the user terminal 100. ) And may be managed as a record of customer information.
Thereby, since the management server 200 can identify at least the user terminal 100 to which the customer is sent to the customer destination application 20, the user who uses the user terminal 100 may be a target for reward. it can. For example, in the case of giving a reward other than a reward in the customer source application 10, the application ID of the customer source application 10 may not be associated and managed as a record of customer information.

Further, the customer information management unit 223 uses the application ID (an example of identification information) of the customer application 20 (an example of the second application) and the application ID (identification of the customer application 10 (an example of the first application)). It may be managed as a record of customer information in association with an example of information.
Thereby, since the management server 200 can identify the customer source application 10 when the customer is sent to the customer destination application 20, for example, a reward to which a reward in the customer source application 10 is given A grant process can be performed. For example, when a reward in the customer source application 10 is given to all users or specific users who are not related to the user terminal 100 to which the customer has been sent, the reward user ID is recorded as customer information. It is not necessary to manage it in association.

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

  For example, the user terminal 100 (SDK 11) includes a unique identification information acquisition unit 102. When the one target application installed in the user terminal 100 is the first target application installed in the user terminal 100 among the plurality of target applications, the unique identification information acquisition unit 102 receives 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 that it can be referred to from other target applications installed in the user terminal 100.

  Thereby, according to the mutual customer sending 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 to the target application installed thereafter. To be available. Therefore, the reward user ID can be acquired and the system can be used without requiring the user to perform a special operation.

(17) Specifically, the unique identification information acquisition unit 102 determines whether or not a reward user ID (an example of unique identification information) is stored in the terminal storage unit 140 (an example of a storage unit). When 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 activated for the first time.

  As the unique identification information, in addition to the reward user ID uniquely generated by the mutual customer sending system 500a, UDID (Unique Device Identifier), IMEI (International Mobile Equipment Identity), An identification number such as IMSI (International Mobile Subscriber Identity) may be used. These identification numbers may be used after being hashed or encrypted. That is, any identification information that is generated or set inside or outside the mutual customer sending system 500 and is unique in the user terminal 100 may be used. Further, as the unique identification information, different information associated with each user terminal 100 as a function of the OS of the user terminal 100, which is permitted to be used by each application (for example, an advertisement identifier (Advertising Identifier)) may be used. Further, without acquiring the ID associated with each user terminal 100 as the unique identification information from the user terminal 100, for example, about 100 types such as screen resolution / width, time zone time difference, etc. These parameters may be acquired by the management server 200 and an ID generated using a predetermined algorithm may be used. 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 (SDK11) includes an application ID (an example of identification information) of the target application installed in the user terminal 100 and a reward corresponding to the user terminal 100 (an example of the own terminal device). In association with the user ID (an example of unique identification information), installation notification information (an example of first information) is transmitted to the management server 200.

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

  Thereby, when the target application is installed and activated on the user terminal 100 (that is, when the target application is executed on the user terminal 100), the management server 200 corresponds to the application ID of the target application and the user terminal 100. The attached reward user ID can be managed in association with each other. Therefore, the management server 200 can specify a target application installed for each user terminal 100 (for example, installed and started).

  Note that the installation notification information (an example of the first information) includes a reward application ID (an example of the unique identification information) associated with the user terminal 100 and the target application that has transmitted the installation notification information (an example of the first information). Both of the application IDs may be included, or one of them 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. Also good. Further, as described above, the first information described using the installation notification information as an example may be simple flag information, for example. 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) Further, the management server 200 of the present embodiment includes an application user information acquisition unit that acquires user information of the target application. For example, the application user information acquisition unit acquires an application user ID (an example of user information of the first application) in the target application in association with a reward user ID (an example of 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 user ID of the target application that has transmitted the installation notification information may be included 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 (SDK11) associates an application user ID (an example of user information in the target application) in the 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 that transmits to the management server 200 is provided. Note that the installation notification unit 103 may function as an application user information notification unit. That is, the application user ID of the target application that has transmitted the installation notification information may be included in the installation notification information. As described above, the function of the application user information notification unit may be included in another function.

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

  Thereby, when the target application is installed in the user terminal 100, the management server 200 recognizes the application ID of the installed target application, the application user ID in the installed target application, and the reward associated with the user terminal 100. The user ID can be managed in association with it. That is, the management server 200 can manage the application user ID for 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 the first reward information management unit) of the management server 200 sets a campaign period (an example of the first period) for the customer destination application 20 (an example of the second application). Information indicating the link destination of the posting location of information indicating CP reward (an example of the first reward) given by the CP reward process (an example of the first reward granting process) performed as the reward granting process when It is stored in the campaign participation application information storage unit 235 and managed. Moreover, the application management part 221 (an example of a 2nd reward information management part) shows the preset normal reward provided by each of a some target application and a normal reward process (an example of a 2nd reward provision process). The normal reward information associated with the information is stored in the normal reward information storage unit 232 for management.
The list notification unit of the management server 200 includes information indicating a normal reward for a target application for which no campaign is set with the customer-source application 10 (an example of the first application) among the plurality of target applications. An application list including information indicating a normal reward is transmitted to the user terminal 100 so as to be displayed in association with each other. On the other hand, the list notification unit displays the information indicating the above link destination in association with the target application for which a campaign is set with the customer source application 10 among the plurality of target applications. Then, an application list including information indicating the link destination is transmitted to the user terminal 100.

  Thus, when the user terminal 100 displays the target application list LT based on the application list acquired from the management server 200 on the display unit 120, the user terminal 100 is given a normal reward to the target application for which the campaign period is not set. Information related to rewards is displayed, and information indicating a link destination of information related to rewards provided by a CP reward (an example of reward) of the campaign is displayed in association with a specific application in which the campaign is set. Can do.

(21) The installation guidance instruction unit 244 (an example of the screen information notification unit) of the management server 200 is a customer destination application 20 (an example of a second application) associated with the customer information acquired by the customer information acquisition unit 243. Based on the application ID (an example of identification information), 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. Here, the information for causing the user terminal 100 to display a screen on which the customer destination application 20 can be installed is, for example, an application that displays a store page of a store site where the customer destination application 20 can be installed (downloadable). The instruction information for starting the store 30 is information including the URL (store URL) of the page of the sales site (application store 400) where the target application can be downloaded.

  Accordingly, when the customer destination application 20 sent from the customer source application 10 is selected, the user terminal 100 performs a special operation for the user on the store page where the selected customer destination application 20 can be installed. It can be displayed automatically without causing

(22) When another period that does not overlap with this campaign period is set for a 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 To do. In this case, the reward processing unit 245 of the management server 200 performs CP reward processing (an example of reward granting process) corresponding to the campaign period set in the customer destination application 20 (an example of the second application) in the user terminal 100. Is already performed, the CP reward process (an example of reward granting process) corresponding to the above-mentioned different period is not performed.

  As a result, in the mutual customer sending system 500, in the CP reward processing for the same customer destination application 20, the reward given by CP reward in another campaign is again given to the user who is given the reward by CP reward in a certain campaign. It can be prevented from being granted. In other words, the customer destination application 20 to which a reward is granted by CP reward is not a target of another CP reward.

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

  For example, in the management server 200, the establishment state included in the reward establishment information of the customer destination application 20 that has been subjected to the normal reward process or the CP reward process has already been updated to “1” (established). Therefore, even if the management server 200 acquires the reward grant notification information from the customer destination application 20 again, there is no reward establishment information that can be updated to “1” (established), and the reward grant notification information is not updated. Can be treated as invalid.

  As a result, the mutual customer sending system 500 can prevent the reward for normal rewards and the reward for CP rewards from being duplicated for the same customer application 20. That is, the customer destination application 20 to which a reward is given by normal reward is not subject to CP reward. In addition, the customer destination application 20 to which a reward is given by CP reward is not normally eligible for reward.

(24) The application management unit 221 of the management server 200 includes information regarding a campaign period (an example of a first period) set for a specific application that is a part or all of the plurality of target applications, Information about at least the end date of the reward granting period (an example of the second period) that includes part or all of the campaign period and ends after the end of the campaign period is managed.

  The reward processing unit 245 performs the reward granting process based on the fact that the reward granting conditions set in the customer destination application 20 are satisfied within the reward granting period.

  For example, the reward granting notification unit 107 of the user terminal 100 (SDK11) satisfies the reward granting condition when the reward granting condition set in the customer destination application 20 (an example of the second application) is satisfied. Remuneration grant notification information indicating this is transmitted to the management server 200.

  And the reward process part 245 of the management server 200 acquires the reward grant notification information which shows that the reward grant conditions were satisfied from the customer destination application 20 (an example of a 2nd application) within the reward grant period, Reward grant processing (for example, CP reward processing) based on the acquired reward grant notification information is performed.

  Thereby, even if the customer destination application 20 is installed in the user terminal 100 immediately before the end of the campaign period, the mutual customer sending system 500 reaches the achievement point where the reward of CP reward is given. The user can be given a period of time to try. In addition, the management server 200 can grant a reward when the reward grant notification information is acquired from the user terminal 100 within the reward grant period.

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

  Thereby, the mutual customer-delivery system 500 can perform the reward granting process according to each of the plurality of reward granting conditions corresponding to the customer destination application 20 being satisfied. In other words, the user continues to use the customer destination application 20 in order to acquire as much as possible a plurality of rewards set in the campaign period (an example of the reward grant period). Therefore, the use of the customer destination application 20 can be increased.

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

  Thereby, even when a plurality of reward granting conditions are set in the customer destination application 20, the management server 200 acquires the timing at which each of the plurality of reward granting conditions is satisfied (the management server 200 acquires the reward grant notification information). The reward can be granted only when the timing is within the reward grant period.

(27) Each of the plurality of reward granting conditions is a timing at which each of the plurality of achievement points set in the processing by the customer destination application 20 (an example of the second application) is reached. The reward grant notification unit 107 of the user terminal 100 (SDK11), based on the satisfaction of each of the plurality of reward granting conditions, results point ID (results point information) indicating the reached result point among the plurality of result points. To the management server 200, respectively. And the reward process part 245 of the management server 200 is based on the satisfaction of each of several reward provision conditions, The achievement point ID which shows the achievement point which reached | attained among the several achievement points from the customer destination application 20 While acquiring reward grant notification information associated with (success point information), the reward source information 10 associated with the acquired result spot ID (result spot information) is executed by the user terminal 100. (An example of a first application) or an application server 310 (an example of a server device) corresponding to the customer source application 10 is transmitted.

That is, the management server 200 gives the customer application 10 the result point ID indicating the result point reached in response to reaching each of the plurality of result points of the customer destination application 20 in the user terminal 100. It transmits to the corresponding application server 310.
As a result, the mutual customer sending system 500 receives a reward corresponding to each of the achieved achievement points in response to the arrival of each of the plurality of achievement points set in the customer destination application 20. Can be.

(28) The reward grant notification unit 107 of the user terminal 100 (SDK11) associates arrival information indicating that one of the plurality of achievement points has been reached based on each of the plurality of reward granting conditions being satisfied. The received reward grant notification information may be transmitted to the management server 200. Then, the reward processing unit 245 of the management server 200 reaches one of the plurality of achievement points from the customer destination application 20 (an example of the second application) based on the satisfaction of each of the plurality of reward granting conditions. The reward granting information corresponding to the number of times the reward grant notification information is acquired each time the reward grant notification information associated with the arrival information indicating that the arrival information has been acquired is executed by the user terminal 100. 10 (an example of a first application) or an application server 310 (an example of a server device) corresponding to the customer source application 10 may be transmitted.

  That is, the management server 200 grants a reward even if the achievement point ID is not associated with the reward granting information transmitted to the application server 310 corresponding to the customer source application 10 when reaching any one of the plurality of achievement points. Information indicating the number of times of notification information acquisition (that is, information indicating the number of achievement points and the number of achievement points) may be associated. In this case, it is only necessary to negotiate in advance so that reward grant information including information indicating the number of times described above is exchanged between the application server 310 and the management server 200. Thus, even if the mutual customer sending system 500 includes information indicating the number of acquisition times of reward grant notification information in the reward grant information instead of the result spot ID, a reward is given corresponding to each of the reached achievement points. Can be.

(29) The reward processing unit 245 of the management server 200 changes from the customer destination application 20 (an example of the second application) to any of a plurality of achievement points based on the satisfaction of each of the plurality of reward granting conditions. While acquiring the reward grant notification information associated with the arrival information indicating the arrival, the reward grant information associated with the acquired arrival information is sent to the customer source application 10 (first application) executed by the user terminal 100 Or an application server 310 (an example of a server device) corresponding to the customer-source application 10.

  That is, the management server 200 does not associate the achievement point ID with the reward granting information transmitted to the application server 310 corresponding to the customer source application 10 when reaching any one of the plurality of achievement points. Reaching information indicating that the result point has been reached (for example, flag information simply indicating that the result point has been reached) may be associated. In this case, it is only necessary to arrange in advance that the reward grant information including the arrival information is simply exchanged between the application server 310 and the management server 200. And the application server 310 may count the frequency | count of acquisition of arrival information, and may provide the reward according to a count result. Therefore, the mutual customer sending system 500 can give reward corresponding to each of the reached achievement points even if the reward granting information is simply associated with the arrival information instead of the achievement spot ID.

(30) The application management unit 221 of the management server 200 includes a setting-side application that sets prohibition of posting based on an application list (an example of second information), and a target that is prohibited from posting based on the application list of the setting-side application. Manages inter-app filter information (an example of first posting prohibition information) associated with a 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 refers to the customer source application 10 (an example of the first application). ) Is set in the application on the setting side, the remaining information obtained by removing the information indicating the application on the setting side from the application list is transmitted to the user terminal 100.

  Thereby, in the mutual customer sending system 500, it is possible to set the relationship of the target application that you do not want to send the customer in the normal reward to the management server 200. For example, if there is an application for which rating (age restriction) is set, a customer sending application 10 for which rating is not set to a customer destination application 20 for which rating is set Can be prevented.

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

  As a result, the target applications set in the setting application and the setting-side application of the inter-app filter information can mutually (bidirectionally) be prohibited (blocked) from being listed in the application list.

In addition, the application management unit 221 of the management server 200 includes inter-app filter information (an example of second posting prohibition information) in which a set-side application prohibited from posting based on an application list (an example of second information) 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 set-side application indicated by the inter-application filter information When the campaign period (an example of the first period) is not set for the customer application 10 (an example of the first application), the remaining information obtained by removing the information indicating the application to be set from the application list Is transmitted to the user terminal 100.

  As a result, in the case of a target application for which only the campaign wants to participate in the mutual customer sending system 500, outside the campaign period, a customer from any target application is not listed in the target application list LT. Can do.

(31) In the above embodiment, the management server 200 includes various information such as installation notification information, list request notification information, customer information, and reward grant notification information. However, although the example linked | related with the reward user ID corresponding to the user terminal 100 which transmitted these various information was demonstrated, it is not restricted 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 a reward user ID corresponding to the user terminal 100. Thus, various information transmitted in the established communication session may be associated with the reward user ID associated with the communication session without including the reward user ID in the various information.
The method of associating these various types of information with the reward user ID is an example, and the management server 200 associates these various types of information with the reward user ID that identifies the user terminal 100 that has transmitted the various types of information. For example, the method is not limited to the above method.

<Third Embodiment>
Next, a third embodiment of the present invention will be described. First, an outline of the mutual customer sending system 500a of the present embodiment will be described.
In general, the target application installed in the user terminal 100 is installed when the user himself / herself accesses the app store 400 without the mutual customer system 500 or when the user application 100 is installed via the mutual customer system 500. There is a case. By the way, some target applications are compatible with the system by upgrading from an old version in which the SDK 11 is not installed to a version in which the SDK 11 is installed. In the following description, a target application in which the SDK 11 is not incorporated will be referred to as an “old version target application”.
Since the old version of the target application does not have a communication function with the management server 200, even if the old version of the target application is installed in the user terminal 100, the management server 200 cannot be notified of the installation. . Therefore, the management server 200 described above recognizes that the old version is not installed. That is, it can be said that the old version of the target application is the target application before being managed by the management server 200. Therefore, in the mutual customer sending system 500 according to the first and second embodiments, when the target application recommended to be installed is presented to the user, the target application of the old version is included in the list LT of target applications presented to the user. May be included.

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

[Outline of Mutual Customer Transmission System According to Third Embodiment]
FIG. 18 is an explanatory diagram for explaining the outline of the mutual customer sending system 500a of the third embodiment.
In this figure, a network system 1a according to the present embodiment includes a management server 200a and a user terminal 100.
Here, the user terminal 100 installs the target application 10A (for example, game A) provided with the SDK 1011 corresponding to the mutual customer sending system 500a, and the old version of the target application 10B (for example, game C) that does not incorporate the SDK 1011. The outline | summary of the mutual customer-delivery system 500a of this embodiment is demonstrated with reference to FIG.

(1) When the target application 10A is installed in the user terminal 100 and is first activated by the user X, the SDK 1011 incorporated in the target application 10A indicates that the target application 10A is installed in the user terminal 100 Notification information (game A) is transmitted. Thereby, the management server 200a manages the installation information indicating that the target application 10A has been installed in 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 uninstalled information indicating the 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 application having the same function as the customer application 10 in the first and second embodiments.

(3) The SDK 1011 of the target application 10A is that the target application of the old version (for example, the target application 10B) installed in the user terminal 100 among the target applications indicated in the non-installed information acquired from the management server 200a is the user terminal It is detected whether or not it is installed in 100 (installation detection). That is, it can be said that the non-installed information indicates a candidate of an “old version target application” to be detected by the user terminal 100. The SDK 1011 detects whether or not the “old version of the target application” is installed in the user terminal 100 using, for example, a URL scheme. Details of the method using the URL scheme will be described later.

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

(5) When the management server 200a presents a target application recommended to be installed to the user, the management server 200a transmits an application list (not including the game C) excluding the target application 10B of the old version to the user terminal 100. .
That is, the management server 200a, among a plurality of managed target applications, install information of the target application installed and activated on the user terminal 100, and the above-described old version target application installed on the user terminal 100. An application list of at least one target application that does not manage any of the installation information is generated.
Then, the management server 200a transmits the generated application list to the user terminal 100. Based on the above-mentioned application list transmitted from the management server 200a, the user terminal 100 is a target application excluding the old version of the target application 10B installed in the user terminal 100 as a target application recommended for installation to the user. The list LT is displayed on the display unit 120.

  Thus, even if the old version of the target application is installed in the user terminal 100, the mutual customer sending system 500a according to the present embodiment displays the 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 sending 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 configuration shown in FIG. Since it is the same as the structure of the user terminal 100 in embodiment, the description is abbreviate | 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 temporarily installs the old version of the target application transmitted from the target application 10A that has detected that the old version of the target application 10B is installed on 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 illustrating 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, the functional configuration of the mutual customer process executed by the user terminal 100 (SDK 1011) in the mutual customer 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 information notification unit 106, a reward grant notification unit 107, a temporary installation notification unit 108, and a list acquisition. Unit 109 and an uninstalled information acquisition unit 111. Further, the initialization processing unit 101 includes a unique identification information acquisition unit 102 and an installation notification unit 103.
Note that the SDK 1011 in this embodiment is different from the first and second embodiments in that it includes a temporary installation notification unit 108, a list acquisition unit 109, and an uninstalled information acquisition unit 111. In FIG. 19, the same components as those in FIG. 5 are denoted by the same reference numerals, and description thereof is omitted here.

The non-installation information acquisition unit 111 includes non-installation information indicating a target application 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) among a plurality of target applications. Obtained from the management server 200a. That is, the non-installed information indicates a target application for which installation notification information has not been acquired from the target application 10A (an example of the first application) installed in the user terminal 100 among a plurality of target applications.
Note that when the installation information based on the temporary installation notification information is managed by the management server 200a, the non-installation information includes any of the installation notification information and the temporary installation notification information from the target application 10A among the plurality of target applications. Indicates a target application that has not been acquired.
The non-installed information acquired by the non-installed information acquiring 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 in association with the application ID (ApID) in the target application information storage unit 231 of the management server 200a, for example, as shown in FIG.

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

Further, as an example of specific processing, the temporary installation notification unit 108 uses the URL scheme acquired by the non-installed information acquisition unit 111 when detecting an old version target application installed in the user terminal 100. . The temporary installation notification unit 108 checks whether or not the URL scheme corresponding to the target application can be opened (used) by using a predetermined method. If it is confirmed that the method can be opened as a result of using the method, it is detected that an old version of the target application corresponding to the URL scheme is installed in the user terminal 100. Then, the temporary installation notification unit 108 transmits temporary installation notification information corresponding to one or a plurality of old version target applications detected as being installed in the user terminal 100 to the management server 200a.
As described above, the URL scheme calls an application or a specific function in the application, and is determined for each application. Therefore, the application installed in the user terminal 100 can be detected by using the URL scheme.

  When there is a target application whose 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 application included in the application list is at least one target application whose installation information corresponding to the user terminal 100 is not managed in the management server 200a, and may be a part or all of the target application. For example, only target applications that satisfy a predetermined condition may be included. Here, the application list is data of an application list page that displays a list LT of target applications recommended to be installed by the user on the user terminal 100. If there is no target application that recommends installation to the user (the target application could not be extracted), information notifying the user may be included in the data.

[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 configuration diagram illustrating an example of the configuration of the management server 200a according to the present embodiment. The management server 200a includes a communication unit 210, a management unit 220, a storage unit 230, and a control unit 240a. In this figure, the same components as those in FIG. 6 are denoted by the same reference numerals, and description thereof is omitted here.
20, the control unit 240a includes an installation notification acquisition unit 241, a list notification unit 242, a customer 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.
Note that the control unit 240a in this embodiment is different from the first and second embodiments in that it includes a temporary installation notification acquisition unit 247 and an uninstalled information notification unit 248.

  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. Unlike 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 illustrating 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 an application ID (ApID) of the target application, a notification destination URL (NoticeURL), a store URL (ApStoreURL), 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) that is description information about the target application, an app icon image (ApICO) that is an icon image indicating the target application, and an app price (ApPRICE) are associated with each other It has been.
This embodiment is different from the first and second embodiments in that the target application information includes a URL scheme (ApURI).

FIG. 22 is a diagram illustrating 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. In the installation information, a reward user ID (RewardUID), an application ID (ApID), an application user ID (ApUID), and a notification type (Ttype) are associated. The reward user ID (RewardUID), application ID (ApID), and application user ID (ApUID) are information included in the acquired installation notification information and temporary installation notification information. However, as described above, when the target application is an old version, the temporary installation notification information does not include the application user ID (ApUID). Therefore, the installation information corresponding to the target application of the old version ID (ApUID) is set to “null”.
This embodiment is different from the first and second embodiments in that the notification type (Ttype) is included in the target application information.

  Here, the notification type (Ttype) includes the installation information stored based on the installation notification information by the installation notification unit 103 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 for distinguishing whether an application installed in the user terminal 100 is a target application including the SDK 1011 or an old version target application not including 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”. The installation information stored based on the temporary installation notification information is shown. For example, in the installation information storage unit 236 shown in FIG. 22, a reward user ID (RewardUID) “0964565”, an application ID (ApID) “001”, and an application user ID (ApUID) “5288” are notified. 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, a reward user ID (RewardUID) “09634565”, an application ID (ApID) “002”, and an application user ID (ApUID) “null” are stored. The notification type (Ttype) “1” is associated 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 an old version target application that does not include 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 non-installed information to the SDK 1011. The non-installation information notification unit 248 transmits the non-installation 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. To 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 target application information stored in the target application information storage unit 231 and installation information stored in the installation information storage unit 236. .

  Specifically, the non-installed information notification unit 248 notifies the target application that is not included in the installation information stored in the installation information storage unit 236 from the target application information stored in the target application information storage unit 231. Extract regardless of type (Ttype). Then, the non-installed information notification unit 248 acquires, for example, the extracted application ID (ApID) of the 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 non-installed information including the URL scheme are transmitted to the target application 10A installed in the user terminal 100.

  When a previous version of the target application is installed in the user terminal 100, the temporary installation notification acquisition unit 247 acquires temporary installation notification information indicating that the previous version of the target application is installed from the target application 10A. . The temporary installation notification acquisition unit 247, 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 information of the target application of the old version installed in the user terminal 100, Obtained 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.

It should be noted that the list notification unit 242 of the present embodiment is one of the target applications when there is a target application for which the installation information corresponding to the user terminal 100 is not managed by the installation information management unit 222 among the plurality of target applications. A part or all (at least one target application) application list is transmitted to the user terminal 100. 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.
Note that the application management unit 221 according to the present embodiment manages information regarding a plurality of target applications to be managed. Further, the installation information management unit 222 according to the present embodiment manages the 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 Third Embodiment]
Next, the operation of the mutual customer sending system 500a of this embodiment will be described.
Note that the basic operation of the mutual customer service system 500a of this embodiment is the same as that of the first embodiment shown in FIGS. 14 and 15, and here, referring to FIG. The operation of the mutual customer sending system 500a will be described focusing on the process of generating the application list of applications. The process shown in FIG. 23 shows a detailed example of the outline process flow described with reference to FIG.

  Here, with reference to FIG. 23, the processing on the target application 10A side installed in the user terminal 100 will be described. Further, it is assumed that the target application 10A incorporates the same SDK 1011A as the above-described SDK 1011.

In FIG. 23, the processing from step SA11 to step SA17 is the same as that of the first embodiment shown in FIG.
In step SE11, the installation information management unit 222 of the management server 200a, the reward user ID (RewardUID) 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) in the installation information storage unit 236 as “0”.

  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 from the inter-application shared area of the terminal storage unit 140 in step SA170. The generated non-install 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 from the target application information stored in the target application information storage unit 231. Extract all non-installed target applications that are not in the installed information. Then, the non-installed information notification unit 248 acquires the application ID (ApID) and the URL scheme corresponding to all the extracted non-installed target applications from the target application information storage unit 231. The non-install information notification unit 248 generates non-install information corresponding to all the extracted target applications including the application ID (ApID) and 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). In addition, when the non-installed target application is not extracted, the non-installed information notification unit 248 may notify information indicating that there is no non-installed target application as the non-installed information.

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

Next, the temporary installation notification unit 108 of the SDK 1011A confirms the installation of the non-installed target application included in the acquired non-install information (step SA173). Specifically, the temporary installation notification unit 108 uses the URL scheme included in the non-installation information acquired by the non-installation information acquisition unit 111, and the target installed in the user terminal 100 among the non-installed target applications. Detect applications. The fact that the target application is detected using the URL scheme in spite of the target application whose installation information is not managed by the management server 200a indicates that the old version of the target application is installed in the user terminal 100. . That is, the temporary installation notification unit 108 detects an old version target application installed in the user terminal 100.
For example, the temporary installation notification unit 108 detects a previous version of the target application 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.
In addition, when the function which can detect the installed application other than URL scheme is provided, the temporary installation notification part 108 may utilize the function.

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

  Next, the temporary installation notification acquisition unit 247 of the management server 200a acquires the temporary installation notification information transmitted from the temporary installation notification unit 108 of the SDK 1011A (SE113). That is, the temporary installation notification acquisition unit 247, for example, among the target applications indicated by the non-install information transmitted by the non-install information notification unit 248, the temporary installation notification information of the target application of the old version installed in the user terminal 100. Is 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 (RewardUID), the application ID (ApID) of the target application 10A (game A), and the target application 10A (game) included in the temporary installation notification information acquired by the temporary installation notification acquisition unit 247. The application user ID (ApUID) of 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”, sets the notification type (Ttype) to “1”, and stores it in the installation information storage unit 236.
Further, the temporary installation notification acquisition unit 247 transmits response information indicating that 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 (not shown after step SE15 and after step SA25) is the same as the processing from step SA24 to step SA26, step SE15 to step SE19, and step SC11 shown in FIG. Therefore, the description is omitted here.
In this embodiment, in step SE15 and step SE16, the list notification unit 242 includes target applications whose installation information corresponding to the user terminal 100 is not managed by the installation information management unit 222 among the plurality of target applications. In this case, an application list of a part or all of the target application (at least one target application) is extracted. Then, the list notification unit 242 generates application list page data for displaying the target application list LT based on the extracted application list of the target application on the user terminal 100. Note that if the target application cannot be extracted, the list notification unit 242 may include information informing the user of the fact in the data. 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 target application list LT 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 service system 500a of this embodiment, the management server 200a (an example of a management device) includes an application management unit 221, an installation notification acquisition unit 241, and a 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 regarding a plurality of target applications to be managed. The installation notification acquisition unit 241 installs the target application 10A 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 the plurality of target applications. Installation notification information indicating that When a previous version of the target application 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 old version target application 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. I do not have it. The installation information management unit 222 manages the 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 provides the user terminal 100 with 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 the plurality of target applications. Send. The list notification unit 242 can be regarded as transmitting to the user terminal 100 an application list of at least one target application for which neither installation notification information nor temporary installation notification information has been acquired from the target application 10A. .

  Thereby, for example, even when an old version of the target application that does not incorporate the SDK 1011 is installed in the user terminal 100, the management server 200a of the present embodiment does not include the old version of the target application. Can be transmitted to the user terminal 100. That is, for example, when an old version of a target application is installed, the management server 200a according to the present embodiment erroneously presents the target application with the old version already installed in the application list of the target application. This can be prevented. Therefore, when presenting a target application that is recommended for installation to the user, the management server 200a of the present embodiment displays an application list of target applications that the user has not used, regardless of the version of the target application. Can be sent to. As a result, when presenting a target application that is recommended for installation to the user, the user terminal 100 can be made to present a list LT of target applications that the user has not used.

(2) In addition, the management server 200a of the present embodiment targets uninstalled information indicating a 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. An uninstalled information notification unit 248 that transmits to the application 10A (an example of the first application) is provided. It can be said that this non-installed information indicates a candidate of the target application of the old version to be detected by the user terminal 100.
Then, the temporary installation notification acquisition unit 247 includes the temporary installation notification information of the target application of the old version installed in the user terminal 100 among the target applications indicated by the non-installation information transmitted by the non-installation information notification unit 248. Obtained from the target application 10A. The non-installation information notification unit 248 transmits non-installation information indicating a target application for which neither installation notification information nor temporary installation notification information has been acquired from the target application 10A among the plurality of target applications to the target application 10A. Can be seen as something to do.
As a result, the management server 200a notifies the candidate of the old version target application to be detected in the user terminal 100 as uninstalled information, thereby clarifying the target of the old version target application to be detected in the user terminal 100. be able to. As a result, it is possible to reduce the processing amount of extraction of this old version of the target application compared to the case of extracting from all the target applications. Further, the target application 10A can shorten the processing time for extracting the old version of the target application compared to the case of extracting from all the target applications.
In addition, the management server 200a of the present embodiment can manage an old version target application installed in the user terminal 100. As a result, the management server 200a of the present embodiment can transmit to the user terminal 100 the application list of the target applications excluding the old version of the target application installed in the user terminal 100. As a result, when a target application that is recommended for installation is presented to the user, a list LT of target applications excluding the target application of the previous version can be presented to the user at the user terminal 100.

(3) The management server 200a of the present embodiment indicates a target application that has not acquired installation notification information from the target application 10A (an example of a first application) installed in the user terminal 100 among the 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 this non-installed information indicates a candidate of the target application of the old version to be detected by the user terminal 100.
Then, the temporary installation notification acquisition unit 247 includes the temporary installation notification information of the target application of the old version installed in the user terminal 100 among the target applications indicated by the non-installation information transmitted by the non-installation information notification unit 248. Obtained from the target application 10A.
As a result, the management server 200a notifies the candidate of the old version target application to be detected in the user terminal 100 as uninstalled information, thereby clarifying the target of the old version target application to be detected in the user terminal 100. be able to. As a result, it is possible to reduce the processing amount of extraction of this old version of the target application compared to the case of extracting from all the target applications. Further, the target application 10A can shorten the processing time for extracting the old version of the target application compared to the case of extracting from all the target applications.
In addition, the management server 200a of the present embodiment can manage an old version target application installed in the user terminal 100. As a result, the management server 200a of the present embodiment can transmit to the user terminal 100 the application list of the target applications excluding the old version of the target application installed in the user terminal 100. As a result, when a target application that is recommended for installation is presented to the user, a list LT of target applications excluding the target application of the previous version can be presented to the user at the user terminal 100.

(4) Moreover, in the management server 200a of this embodiment, the non-installation information notification unit 248 refers to information managed by the application management unit 221 and the installation information management unit 222, thereby indicating the non-installation information to the user terminal 100. To the target application 10A installed in Here, the non-installed information indicates a target application for which install information corresponding to the user terminal 100 is not managed in the install information management unit 222 among a plurality of target applications.
The management server 200a of the present embodiment acquires temporary installation notification information for an old version of the target application (an old version of the game 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 that has transmitted the installation notification information or temporary installation notification information and the user terminal 100 in which the target application is installed, and the non-installation information notification unit 248 Among the plurality of target applications, the non-installation information indicating the target application for which neither the installation notification information nor the temporary installation notification information has been acquired from the target application 10A is displayed as the target application. It may be transmitted to 10A.
As a result, the non-installed information notification unit 248 determines that all the target applications extracted by referring to the information managed by the application management unit 221 that manages information related to a plurality of target applications to be managed, and the installation information management unit 222 By comparing with the target application in which the installation information corresponding to the user terminal 100 extracted by referring to the information to be managed is managed, the target application in which the installation information corresponding to the user terminal 100 is not managed is indicated. Installation information can be specified. It can be said that this non-installed information indicates a candidate of the target application of the old version to be detected by the user terminal 100.

(5) Moreover, in the mutual customer service 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 a plurality of target applications to be managed is installed, and an old version target application (management target). The installation information of the target application installed in the user terminal 100 is managed based on the temporary installation notification information indicating that the target application) 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 an old version of the target application installed in the user terminal 100 and transmits the detected temporary installation notification information of the 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 whose 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 installation notification information nor temporary installation notification information has been transmitted. Then, the display control unit 105 causes the display unit 120 to display the target application list LT based on the application list of the target application acquired by the list acquisition unit 109. The list acquisition unit 109 may acquire the target application list LT indicating data to be displayed based on the application list from the management server 200a. Note that the list acquisition unit 109 can be regarded 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 own user terminal 100.

  Thereby, for example, when an old version of the target application that does not incorporate the SDK 1011 is installed in the user terminal 100, the user terminal 100 of the present embodiment uses the application list of the target application excluding the old version of the target application. And a list LT of target applications based on the acquired application list can be presented to the user. Therefore, the user terminal 100 according to the present embodiment can transmit to the user terminal 100 an application list of target applications that the user has not used, regardless of the version of the target application. As a result, when presenting a target application that is recommended for installation to the user, the user terminal 100 can be made to present a list LT of target applications that the user has not used.

(6) In addition, the user terminal 100 according to the present embodiment acquires, from the management server 200a, non-installed information acquisition that indicates a target application whose installation information corresponding to the user terminal 100 is not managed in the management server 200a. Part 111. The non-installation information acquisition unit 111 acquires non-installation information indicating a target application for which neither installation notification information nor temporary installation notification information has been transmitted from the own user terminal 100 among the plurality of target applications from the management server 200a. Can be seen as something to do.
Then, the temporary installation notification unit 108 manages temporary installation notification information of an old version of the target application installed in the own user terminal 100 among the target applications indicated by the non-install information acquired by the non-install information acquisition unit 111. It transmits to the server 200a.
Thereby, the target application 10A of the user terminal 100 according to the present embodiment extracts, for example, the old version of the target application installed in the user terminal 100 from the acquired non-installed information. As compared with the case of extracting from the above, it is possible to reduce the processing amount of extraction of the target application of the old version. In addition, the user terminal 100 according to the present embodiment can reduce the processing time for extracting the target application of the old version compared to the case of extracting from all the target applications.

(7) In addition, the user terminal 100 according to the present embodiment acquires, from the management server 200a, non-installed information indicating a target application that has not transmitted installation notification information from the own user terminal 100 among a plurality of target applications. An information acquisition unit 111 may be provided. Then, the temporary installation notification unit 108 manages temporary installation notification information of an old version of the target application installed in the own user terminal 100 among the target applications indicated by the non-install information acquired by the non-install information acquisition unit 111. It transmits to the server 200a.
Thereby, the target application 10A of the user terminal 100 according to the present embodiment extracts, for example, the old version of the target application installed in the user terminal 100 from the acquired non-installed information. As compared with the case of extracting from the above, it is possible to reduce the processing amount of extraction of the target application of the old version. In addition, the user terminal 100 according to the present embodiment can reduce the processing time for extracting the target application of the old version compared to the case of extracting from all the target applications.

(8) In the present embodiment, the non-installed information acquisition unit 111 acquires a URL scheme corresponding to the target application indicated in the non-installed information included in the non-installed information. Then, the temporary installation notification unit 108 uses the URL scheme acquired by the non-installation information acquisition unit 111, and among the target applications indicated by the non-install information, the old version of the target application installed in the own user terminal 100 Is detected.
Thereby, the user terminal 100 of this embodiment can detect the target application of an old version by the simple means of determining whether a URL scheme can be opened in the user terminal 100, for example.

(9) In the present embodiment, the application management unit 221 also sets the setting application on the side that sets prohibition of listing in the target application list LT based on the application list of the target application, and the target application of the setting application The inter-application filter information (first posting prohibition information) that combines the set-side application that is prohibited from posting on the list LT may be managed. 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 between the applications that set the target application 10A as the set-side application. When 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.
In this 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. If there is inter-app filter information, the application list of the target application excluding the set-side application may be transmitted to the user terminal 100.
In the present embodiment, the application management unit 221 also manages the inter-app filter information (second posting prohibition information) in which only the set-side application 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-app filter information managed by the application management unit 221 and transmits the application list of the target application excluding the set-side application to the user terminal 100.

  Accordingly, in the mutual customer sending system 500a, when the target application recommended to be installed is presented to the user, the relationship of the target application that is not recommended can be set in the management server 200a. For example, if there is a target application for which rating (age restriction) is set, the target application for which rating is set may not be recommended from the target application 10A for which rating is not set. .

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

(11) Further, the management server 200a of the present embodiment includes a customer information acquisition unit 243 and a customer information management unit 223, and the reward processing unit 245 satisfies a predetermined reward granting condition. When it is determined that the customer information has been sent, the reward granting process may be executed on condition that the customer information for the second application is managed by the customer information management unit 223. Here, the customer information acquisition unit 243 acquires customer information for the second application from the target application 10A, and the customer information management unit 223 manages the customer information acquired by the customer information acquisition unit 243. It may be.
As a result, the mutual customer sending system 500a can be configured not to be a target of reward granting because there is no customer customer information recorded when the target application is installed regardless of this system.
(12) The predetermined reward granting condition may be when it is determined that the customer destination application 20 (an example of the second application) is installed in the user terminal 100. Further, the predetermined reward granting condition may be when it is determined that the customer destination application 20 is installed in the user terminal 100 and it is determined that a predetermined result is achieved in the customer destination application 20.
As described above, the mutual customer sending system 500a can arbitrarily set the reward granting condition.
(13) 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 granting condition is that the second application is a specific application, the second application is determined to be installed in the user terminal 100 within a predetermined period, and a predetermined result is achieved in the second application. It may be when it is determined that it has been done.

  Thereby, only the specific application which is implementing the campaign among a plurality of target applications can be set as a reward grant target. Even when a specific application of an old version is installed in the user terminal 100 among the specific applications that are implementing the campaign, the old application The application list of specific applications that the user has not used can be transmitted to the user terminal 100 by excluding the version target application. As a result, a list of target applications (specific applications) executing a campaign that has not been used by the user can be presented to the user at the user terminal 100.

(14) Further, the user terminal 100 according to the present embodiment includes a reward grant notification unit 107. The reward grant notification unit 107, when it is determined that the predetermined reward grant condition is satisfied in the target application installed in the own user terminal 100, the reward grant notification information indicating that the predetermined reward grant condition is satisfied. Is transmitted to the management server 200a. Here, when the management server 200a determines that a predetermined reward granting condition in the target application selected by the user terminal 100 from one or a plurality of target applications included in the application list is satisfied, the management server 200a performs predetermined processing in the target application. The reward granting process in which the reward is granted is executed.
The predetermined reward granting condition may be when it is determined that a predetermined result is achieved in the target application installed in the user terminal 100.
In addition, a plurality of predetermined reward granting conditions are provided, and the reward granting notification unit 107 transmits reward granting notification information to the management server 200a based on the satisfaction of each of the plurality of reward granting conditions. May be.
Thereby, the user terminal 100 according to the present embodiment, for example, when the old version of the target application is installed, the target application that has not been used by the user who is the target of reward granting excluding the old version of the target application The application list can be obtained, and a list LT of target applications based on the application list can be presented to the user. Alternatively, it is possible to obtain an application list of target applications that have not been used by a user who is a target for reward excluding the target application of the previous version, and to present a list LT of target applications based on the application list to the user. . As a result, when the old version of the target application is included in the target application list LT and the old version of the target application is updated to the new version of the target application, the management server 200a sends the customer application 10 Can be prevented from being rewarded.
In addition, when it is determined that the predetermined reward granting condition is satisfied, the user terminal 100 according to the present embodiment provides reward grant notification information indicating that the predetermined reward granting condition is satisfied to the management server 200a. Can be sent.

<Fourth Embodiment>
Next, a fourth embodiment of the present invention will be described.
In the present embodiment, when an old version target application not incorporating SDK 11 is installed (updated), a list LT of target applications excluding the old version target application is presented to the user, Another embodiment different from the third embodiment will be described with respect to a method of excluding an old version 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 a target application recommended for installation to the user, the old version installed in the user terminal 100 from the application list. Was excluded from the list. For this reason, the non-installation information that is a candidate for the old version of the target application is transmitted to the user terminal 100 in advance, and the installation information of the old version of the target application 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 to the user terminal 100 in advance non-installation information that is a candidate for an old version target application. That is, the user terminal 100 regards all target applications and old version target applications installed in the user terminal 100 as candidates for the old version target application without acquiring the non-installed information from the management server 200b. The temporary 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, the target application that is not managed by the installation information management unit 222 is identified as an old version target application, as compared with the information managed by the installation information management unit 222.

[Functional configuration of user terminal 100 (SDK 2011) according to the fourth embodiment]
FIG. 24 is a configuration diagram illustrating 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 the mutual customer process executed by the user terminal 100 (SDK 2011) in the mutual customer 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 information notification unit 106, a reward grant notification unit 107, a temporary installation notification unit 108, and a list acquisition. Part 109. Further, the initialization processing unit 101 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 it does not include the non-installed information acquisition unit 111. In FIG. 24, the same components as those in FIG. 19 are denoted by the same reference numerals, and description thereof is omitted here.

  In the present embodiment, the temporary installation notification unit 108 detects the target application and the old version of the target application among the applications installed in the user terminal 100. Then, the temporary installation notification unit 108 regards the detected temporary installation notification information of the target application as a candidate for the old version of the target application, and transmits the temporary 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 configuration diagram illustrating an example of the configuration of the management server 200b according to the present embodiment. The management server 200b includes a communication unit 210, a management unit 220, a storage unit 230, and a control unit 240b. In this figure, the same components as those in FIG. 20 are denoted by the same reference numerals, and description thereof is omitted here.
The control unit 240b of the present embodiment includes an installation notification acquisition unit 241, a list notification unit 242, a customer 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. The control unit 240b of the present embodiment is different from the third embodiment in that the non-installed information notification unit 248 is not provided.

  The temporary installation notification acquisition unit 247 of the present embodiment installs temporary installation notification information excluding the target application managed by the application management unit 221 from the temporary installation notification information acquired from the temporary installation notification unit 108, for example. The information is supplied to the information management unit 222. In other words, the temporary installation notification acquisition unit 247 excludes the temporary installation from the temporary installation notification information acquired from the temporary installation notification unit 108, excluding the target application corresponding to the target application information stored in the target application information storage unit 231. 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 Processing According to Fourth Embodiment]
Next, the operation of the mutual customer sending system 500a of this embodiment will be described.
Note that the basic operation of the mutual customer system 500a of this embodiment is the same as that of the first embodiment shown in FIGS. 14 and 15, and here, referring to FIG. The operation of the mutual customer sending system 500a will be described focusing on the process of generating the application list of applications.

  The process shown in FIG. 26 shows the process on the target application 10A side installed in the user terminal 100.

In FIG. 26, the processing from step SA11 to step SA17 is the same as that of the first embodiment shown in FIG. It is assumed that SDK 2011A similar to the above-described SDK 2011 is incorporated in the target application 10A.
In step SE11, the installation information management unit 222 of the management server 200b, the reward user ID (RewardUID) included in the installation notification information acquired by the installation notification acquisition unit 241 and 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) in the installation information storage unit 236 as “0”.

  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 application installation in the user terminal 100 (step SA173a). In an example of specific processing, the temporary installation notification unit 108 detects a target application installed in the user terminal 100 and an old version target application using a URL scheme. For example, it is assumed that the user terminal 100 stores in advance URL scheme information in which the URL scheme of the target application and the application ID are associated with each other in the inter-application sharing area of the terminal storage unit 140. The temporary installation notification unit 108 uses a predetermined method to check whether the URL scheme corresponding to the target application existing in the URL scheme information associated with the application ID can be opened (used). When it is confirmed that the method can be opened as a result of using the method, it is determined that the target application corresponding to the URL scheme or the target application of the old version is installed in the user terminal 100. That is, it is detected that a target application whose installation is managed by the management server 200b and a previous version of a target application whose management is not managed by the management server 200b are mixed. Become. That is, the temporary installation notification unit 108 detects the detected target application and the old version of the target application as candidates for the old version of the target application, and generates temporary installation notification information.

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

Next, the temporary installation notification acquisition unit 247 of the management server 200b acquires the temporary installation notification information transmitted from the temporary installation notification unit 108 (SE113a).
The temporary installation notification information transmitted by the temporary installation notification unit 108 is a candidate for an old version of the target application, and the management that the installation is managed by the management server 200b and the installation is managed. The target application of the old version which is not managed by the server 200b is included. Therefore, the installation information management unit 222 removes the true old version of the target application from the temporary installation notification information acquired by the temporary installation notification acquisition unit 247, excluding the target application already stored in the installation information storage unit 236. Extract. In some cases, the true old version of the target application cannot be extracted. In this case, it is indicated that the user terminal 100 does not include an old version target application that is not managed by the management server 200b.
The installation information management unit 222 extracts the extracted version of the target application from the reward user ID (RewardUID) 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 X application user ID (ApUID) 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”, sets the notification type (Ttype) to “1”, and stores it in the installation information storage unit 236.
Further, the temporary installation notification acquisition unit 247 transmits response information indicating that the temporary installation notification information has been acquired to the user terminal 100 (SDK 2011A) (RES11C).

The subsequent processing of step SA175 is the same as that of the third embodiment shown in FIG.
Further, the processes after step SA24 (not shown after step SE15 and after step SA25) are the processes from step SA24 to step SA26, step SE15 to step SE19, and step SC11 shown in FIG. Since it is the same, description is abbreviate | omitted here.
In this embodiment, in step SE15 and step SE16, the list notification unit 242 obtains at least one target application 10B (from which neither installation notification information nor temporary installation notification information has been acquired from the target application 10A (game A). The application list of game C) is extracted. Then, the list notification unit 242 displays the data of the application list page for displaying the target application list LT based on the extracted application list of the target application as the target application list LT recommended for the user to install on the user terminal 100. Generate. If there is no target application that recommends installation to the user (the target application could not be extracted), the list notification unit 242 includes information for notifying the user of that fact in the data. Also good.

[Summary of Fourth Embodiment]
As described above, in the mutual customer sending system 500a of the present embodiment, the temporary installation notification unit 108 of the user terminal 100 includes the application installed on the own user terminal 100 and the target application of the old version (the management target and An example of a target application before becoming) is detected, and the temporary installation notification information of the detected target application is transmitted to the management server 200b as a candidate for the target application of the old version.
As a result, the management server 200b does not transmit the non-installation information that is a candidate for the old version of the target application to the user terminal 100, as in the third embodiment. It is possible to extract a target application of an old version that is not managed from and add it as a management target. Therefore, the target application installed in the user terminal 100 can be managed regardless of the version of the target application. Therefore, similarly to the third embodiment, the user terminal 100 of the present embodiment has never used the user regardless of the version of the target application when presenting the target application recommended for installation to the user. A list LT of target applications can be presented to the user.

  Further, when 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. Further, if the application ID of the application can be acquired, the temporary installation notification unit 108 may transmit temporary installation notification information including the detected application ID of the application to the management server 200b. In addition, 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 an application ID for registration. It may be.

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

[Functional configuration of user terminal 100 (SDK 3011) according to the fifth embodiment]
FIG. 27 is a configuration diagram illustrating an example of a functional configuration 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 the mutual customer process executed by the user terminal 100 (SDK 3011) in the mutual customer 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 information notification unit 106, a reward grant notification unit 107, a list acquisition unit 109, and a list generation unit. 112. Further, the initialization processing unit 101 includes a unique identification information acquisition unit 102 and an installation notification unit 103.

The SDK 3011 of this embodiment is different 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. In FIG. 27, the same components as those in FIG. 19 are denoted by the same reference numerals, and description thereof is omitted here.
It should be noted that the list acquisition unit 109 according to the present embodiment receives, from the management server 200, an application list of at least one target application that has not transmitted installation notification information whose installation information corresponding to the user terminal 100 is not managed by the management server 200. get. The list acquisition unit 109 acquires a URL scheme corresponding to the target application included in the application list of the target application together with the application list of the target application.

  The list generation unit 112 generates a list LT of target applications excluding the target application of the previous version installed in the user terminal 100 among the target applications included in the application list of the target application acquired by the list acquisition unit 109. To do. Specifically, the list generation unit 112 uses the URL scheme acquired by the list acquisition unit 109 to identify an old version target application installed in the user terminal 100 among the target applications included in the application list. To 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 Mutual Customer Processing Operation According to Fifth Embodiment]
Next, the operation of the mutual customer sending system 500a of this embodiment will be described.
Note that the basic operation of the mutual customer service system 500a of this embodiment is the same as that of the first embodiment shown in FIGS. 14 and 15, and here, referring to FIG. The operation of the mutual customer sending system 500a will be described focusing on the process of generating the application list of applications.

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

In FIG. 28, the processing from 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 in the first embodiment shown in FIG. To 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 the 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 (RES12a). Here, the list notification unit 242 generates an application list of at least one target application for which installation information corresponding to the user terminal 100 is not managed. The list notification unit 242 may include a 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 displays the application list and the URL scheme. get.

Next, the list generation unit 112 of the SDK 3011A confirms the installation of the target application of the old version (Step SA241). Specifically, the list generation unit 112 uses the URL scheme included in the application list acquired by the list acquisition unit 109 to identify an old version target application installed in the user terminal 100 among the target applications. To do. That is, the list generation unit 112 detects an old version of the target application installed in the user terminal 100 among the target applications included in the application list.
For example, the list generation unit 112 detects an old version target application installed in the user terminal 100 using a URL scheme included in the application list.

  Next, the list generation unit 112 deletes the old version of the target application 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 the target application of the previous version installed in the user terminal 100 detected using the URL scheme among the target applications included in the application list. .

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

  Further, the processes after step SA26 (not shown after step SE17 and after step SA26) are the same as the processes at step SA26, step SE17 to step SE19, and step SC11 shown in FIG. Therefore, explanation is omitted here.

[Summary of Fifth Embodiment]
As described above, in the mutual customer service system 500a 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. Here, the management server 200 is installed in the user terminal 100 based on installation notification information indicating that the target application installed in the user terminal 100 among the plurality of target applications to be managed is installed. Manage installation information for target applications. 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 whose installation information corresponding to the user terminal 100 is not managed in the management server 200. The list generation unit 112 includes an old version of a target application installed in the user terminal 100 among target applications included in the application list acquired by the list acquisition unit 109 (an example of a target application before being managed). Regenerate the application list excluding. Then, the display control unit 105 causes the display unit 120 to display the target application list LT based on the application list generated by the list generation unit 112.

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

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

[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 the target application list LT according to the present embodiment.
Here, it is assumed that the target application 10A (game A), the old version of the target application 10B (game C), and the target application 10F (game G), which are customers, are installed in the user terminal 100. Here, it is assumed that the target application 10 </ b> A (game A) and the target application 10 </ b> F (game G) have already transmitted the installation notification information to the management server 200 when activated on the user terminal 100. 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 that are not installed in the user terminal 100. That is, the management server 200 does not manage 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), at least one in which the installation information corresponding to the user terminal 100 is not managed in the management server 200 in the application list acquired by the user terminal 100 from the management server 200. Display example of list LT of target applications generated based on the application list when the information indicating the target application is included and the information indicating the target application for which the 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 applications indicated by the application list are the target application 10B (game C), target application 10D (game E), and target application 10E (installation information corresponding to the user terminal 100 in the management server 200). Game F). The target application list LT shown in FIG. 29A includes 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 that is not installed in the user terminal 100 (that is, a candidate for a target application to be a customer destination). Here, the old version of the target application 10B (game C) is installed in the user terminal 100, but 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 target application that has not been installed.

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

FIG. 29C shows a display example when the user terminal 100 generates a list LT of target applications that can distinguish an old version target application among the 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 previous version installed in the user terminal 100 detected using the URL scheme from the target applications indicated by the application list. A list LT of target applications may be generated. The target application list LT shown in FIG. 29C includes information (L10) indicating the target application 10B (game C), information (L20) indicating the target application 10D (game E), and target application 10E (game). F) is displayed (L30), and information (L20) indicating the target application 10D (game E) and information (L30) indicating the target application 10E (game F) are respectively displayed on the user terminal 100. Information indicating that it has not been installed (here, “not installed”) is displayed on the user terminal 100 as information indicating a target application that has not been installed (that is, a target application candidate to be a customer destination).
Therefore, the user terminal 100 generates a list LT of target applications in which the user can distinguish target applications whose previous versions are installed in the user terminal 100 among the target applications indicated by the acquired application list, and presents the list to the user. can do.
Note that information indicating that the old version is installed may be displayed in the information (L10) indicating the target application 10B (game C).

The application list acquired from the management server 200 further includes information indicating at least one target application for which installation information is managed, target applications for which installation information is not managed, and targets for which installation information is managed. Differentiating information that can be distinguished from the application may be included.
29D, 29E, and 29F, at least one in which the installation information corresponding to the user terminal 100 is not managed in the management server 200 in the application list acquired by the user terminal 100 from the management server 200. Information indicating the target application, information indicating at least one target application for which installation information is managed, and distinguishing information for distinguishing between a target application for which installation information is not managed and a target application for which installation information is managed Is displayed, a display example of a list LT of target applications generated based on the application list is shown.

FIG. 29D shows a display example when the user terminal 100 generates a list LT of target applications excluding target applications of the previous version from the target applications indicated by the acquired application list. Here, among the target application 10A (game A), the target application 10B (game C), the target application 10D (game E), the target application 10E (game F), and the target application 10F (game G) indicated by the application list. Thus, the target application 10B (game C) in which the old version is installed is excluded. Accordingly, the target application list LT shown in FIG. 29D includes information (L20) indicating the target application 10D (game E), information (L30) indicating the target application 10E (game F), and target application 10A ( Information (L40) indicating the game A) and information (L50) indicating the target application 10F (game G) are displayed. In addition, information (L50) indicating the target application 10A (game A) and information (L50) indicating the target application 10F (game G) are respectively information indicating that it is 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 not installed in the user terminal 100 (that is, the target application serving as a customer destination). Information). Here, the user terminal 100 generates information (here, “installed”) indicating that the user terminal 100 is installed on the user terminal 100 based on the distinction information included in the application list.
As a result, the user terminal 100 can list the target applications whose installation information is managed among target applications indicated by the acquired application list at least LT that can be distinguished from the target applications whose installation information is not managed LT. Can be generated and presented to the user.

FIG. 29E shows a display example when the user terminal 100 generates the target application list LT 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. 29E, information (L10) indicating the target application 10B (game C) is further displayed with respect to the application list LT shown in FIG. 29D. Different. In addition, information (L10) indicating the target application 10B (game C) includes information indicating that an old version of the target application 10B (game C) is installed (here, “old version installed”). Is displayed.
As a result, the user terminal 100 can list the target applications whose installation information is managed among target applications indicated by the acquired application list at least LT that can be distinguished from the target applications whose installation information is not managed LT. Can be generated and presented to the user. Further, the user terminal 100 can present a list LT of target applications to the user so that the user can distinguish the target applications installed with the old version installed on the user terminal 100.

Note that in the target application list LT shown in FIG. 29E, information that can distinguish the target application in which the old version is installed may not be displayed. For example, as shown in FIG. 29 (f), information (in this case, “installed”) indicating that it is installed in the user terminal 100 is displayed in the information (L 10) indicating the target application 10 B (game C). May be.
As a result, the user terminal 100 can list the target applications whose installation information is managed among target applications indicated by the acquired application list at least LT that can be distinguished from the target applications whose installation information is not managed LT. Can be generated and presented to the user.

  In the target application list LT shown in FIGS. 29D, 29E, and 29F, information indicating the target application installed in the user terminal 100 indicates that it is installed in the user terminal 100. In place of or in addition to the display of information (here, “installed”), information indicating that the target application is not installed on the user terminal 100 is added to information indicating that the information 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 an old version target application that does not incorporate the SDK 11 is installed in the user terminal 100, the installed old version target application is excluded. The form in which the target application list LT is presented to the user has been described. In the present embodiment, when there is a target application that has not been activated among target applications installed in the user terminal 100, a list LT of target applications excluding the target application that has not been activated is presented to the user. explain.

  For example, even if the target application is downloaded from the store site and installed in the user terminal 100, the target application cannot transmit installation notification information to the management server 200 unless it is activated (unless it is executed). . Therefore, the management server 200 recognizes that the target application that has not been activated is not installed in the user terminal 100, as in the case of the target application of the previous version. Therefore, for example, when presenting a target application that is recommended for installation to the user, the target application list LT to be presented to the user includes a target application that has been installed in the user terminal 100 but has never 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 previous version described in the third, fourth, and fifth embodiments. A mode in which a list LT of target applications excluding target applications that have never been started is presented to the user will be described.

[Outline of Mutual Customer Transmission System According to Sixth Embodiment]
FIG. 30 is an explanatory diagram for explaining the outline of the mutual customer sending system 500a of the present embodiment.
The network system 1a shown in FIG. 30 includes a management server 200a and a user terminal 100, similarly to the configuration shown in FIG. Here, instead of the old version of the target application 10B (for example, the game C), the target application 10C (for example, the game D) including the SDK 1011 corresponding to the mutual customer sending system 500a is installed in the user terminal 100. However, the configuration is different from that shown in FIG. In FIG. 30, the same reference numerals are given to portions corresponding to the respective portions in FIG.
With reference to this FIG. 30, the outline | summary of the mutual customer-delivery system 500a of this embodiment is demonstrated.

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

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

(2) The SDK 1011 of the target application 10A acquires from the management server 200a uninstalled information indicating the 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 application having the same function as the customer application 10 in the first and second embodiments.

(3) The SDK 1011 of the target application 10A is a target application (for example, the target application 10C) that has been installed in the user terminal 100 but has not started among the target applications indicated by the non-install information acquired from the management server 200a. Then, it is detected (installation detection) whether or not the user terminal 100 is installed. That is, it can be said that the non-installed information indicates candidates of “target applications installed in the user terminal 100 but never started” that should be detected in the user terminal 100. The SDK 1011 detects, for example, whether a “target application installed in the user terminal 100 but never started” is installed in the user terminal 100 using a URL scheme. Here, the SDK 1011 detects that the target application 10C is installed in the user terminal 100 as “a target application that has been installed in the user terminal 100 but never started” among the target applications indicated by the non-installation information. To 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. Thereby, the management server 200a manages the installation information indicating that the target application 10C is installed in 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 whether or not the target application installed in the user terminal 100 has been activated.

(5) The management server 200a transmits an application list (not including the game D) excluding the target application 10C to the user terminal 100 when presenting a target application recommended for installation to the user.
That is, the management server 200a includes, among a plurality of managed target applications, installation information of a target application that is installed and started on the user terminal 100, and a target application that is installed on the user terminal 100 but has not been started An application list of at least one target application that does not manage any of the installation information is generated.
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 recommended for installation to the user 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 never started, the mutual customer system 500a according to the present embodiment excludes the target application that has not been started. A list LT of target applications can be displayed on the display unit 120 and presented to the user.

  The “target application installed in the user terminal 100 but never started” and the “target of the previous version installed in the user terminal 100” described in the third, fourth, and fifth embodiments. The “application” is a target application that does not transmit the installation notification information to the management server 200a, but has not been transmitted to the management server 200a. There is no difference. For this reason, both the target application installed in the user terminal 100 but never started and the target application of the old version are included in the target application indicated by the non-installation information. And the process which detects the target application which is installed in the user terminal 100 but has not started among the target applications indicated by this non-installed information is similar to the process of detecting the target application of the old version. For example, the detection process can be performed using a URL scheme.

  Therefore, also in this embodiment, when the old version of the target application is installed in the user terminal 100, the old version of the target application can be excluded from the non-installed information. In addition, when an old version of the target application is installed in the user terminal 100 and there is a target application that has been installed in the user terminal 100 but never started, the old version of the target application is determined from the uninstalled information. Both the target application and the target application that has never been started can be excluded.

Next, the configuration and processing of this embodiment will be described in detail.
The configuration and processing described in the third, fourth, and fifth embodiments can be applied to the configuration and processing of the present embodiment.
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]
As the configuration and processing of this embodiment, for example, the configuration and processing of the third embodiment described with reference to FIGS. 19 to 23 can be applied.

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

  Specifically, when the temporary installation notification unit 108 detects a target application that has been installed in the user terminal 100 but has never been started, for example, as in the process of detecting a target application of an old version, it is not installed. Detection is performed using the URL scheme acquired by the information acquisition unit 111.

If 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 indicates the information indicating the installed target application. May be used to detect a target application that has been installed in the user terminal 100 but has not been started, from among the target applications indicated by the non-install information acquired by the non-install information acquisition unit 111.
Further, unlike the old version of the target application, the SDK 1011 is incorporated in the target application that has not been started. For this reason, the SDK 1011 has a function of detecting target applications installed in the user terminal 100, and the target application indicated by the non-installed information acquired by the non-installed information acquisition unit 111 is transmitted to the user terminal 100. A target application that has been installed but never started may be detected.

  Further, in the present embodiment, in the configuration of the management server 200a illustrated in FIG. 20, the temporary installation notification acquisition unit 247 is activated when there is a target application that has been installed in the user terminal 100 but has not been activated. Temporary installation notification information indicating that a target application having no name is installed in the user terminal 100 is acquired from the target application 10A. For example, the temporary installation notification acquisition unit 247, among the target applications indicated by the non-installation information transmitted by the non-installation information notification unit 248, the temporary installation notification of the target application that has been installed in the user terminal 100 but has not started. 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.

  Based on the temporary installation notification information acquired by the temporary installation notification acquisition unit 247, the installation information management unit 222 stores the installation information of the target application installed in the user terminal 100 but never started in the installation information storage unit 236. Remember. The installation information stored in the installation information storage unit 236 is, for example, the installation information stored based on the temporary installation notification information, like the installation information of the target application of the old version shown in FIG. Ttype) is stored as “1”. Note that the notification type (Ttype) of the target application installed in the user terminal 100 but never started is a notification type other than “0” and “1” so that it can be distinguished from the target application of the previous version. (For example, “2”).

Further, for example, the process shown in FIG. 23 may be applied as the process according to the present embodiment.
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-install information acquired by the non-install information acquisition unit 111, A target application installed in the user terminal 100 but never started is detected. Then, the temporary installation notification unit 108 notifies the management server 200a of the result of the installation confirmation (Step SA174). In other words, the temporary installation notification unit 108 installs the temporary installation notification information indicating the target application that has been installed in the user terminal 100 but has not been activated in the same manner as the temporary installation notification information indicating the old version of the target application. It transmits to the management server 200a. When there is no target application that has not been activated in the user terminal 100, information indicating that there is no target application that has not been activated may be notified as temporary installation notification information. .

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

The subsequent processing after step SA24 (not shown after step SE15 and after step SA25 is omitted), as described with reference to FIG. 23, from step SA24 to step SA26 and step SE15 to step shown in FIG. Since it is the same as the process of SE19 and the process of step SC11, description is abbreviate | omitted here.
For example, in step SE15 and step SE16, the list notification unit 242 of the management server 200a 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 among the plurality of target applications. An application list including information indicating is extracted. Then, the list notification unit 242 generates application list page data for displaying the target application list LT based on the extracted application list of the target application on the user terminal 100. Note that if the target application cannot be extracted, the list notification unit 242 may include information informing the user of the fact in the data. 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 target application list LT on the user terminal 100 based on the acquired application list. May be.

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

  Of the target applications installed in the user terminal 100, both the old version of the target application and the target application that has not been activated may be detected and excluded from the application list.

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

For example, 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.
The SDK 2011 is different from the configuration of the SDK 1011 shown in FIG. 19 described in the above first example in that the non-installed information acquisition unit 111 is not provided. Also, the management server 200b is different from the configuration of the management server 200a shown in FIG.

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

In addition, as the processing according to the present embodiment, the processing illustrated in FIG. 26 may be applied.
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 a URL scheme. Here, the temporary installation notifying unit 108 may detect a target application that has been started among target applications installed in the user terminal 100 and may detect a target application that has not been started. 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.

Thereby, similarly to the first example described above, the management server 200a can manage the installation information of the target application that has been installed in the user terminal 100 but has not started. Further, 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 never been started. Therefore, the user terminal 100 can present to the user a list LT of target applications excluding target applications that have been installed in the user terminal 100 but never started.
In the second example, among the target applications installed in the user terminal 100, both the target application of the old version and the target application that has not started can be detected and excluded from the application list. Good.

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

  For example, a functional configuration that is executed based on the SDK 3011 of the user terminal 100 shown in FIG. 27 may be applied to the configuration of the mutual customer sending system 500a of the present embodiment. The SDK 3011 has the configuration of the SDK 1011 illustrated in FIG. 19 described in the above first example in that the provisional installation notification unit 108 and the non-installed information acquisition unit 111 and the list generation unit 112 are provided. 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 started from 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 never started to the user terminal 100 without removing it from the application list of the target application. Then, in the user terminal 100, an application list that is installed in the user terminal 100 but has not started yet is generated (regenerated) by excluding the application list acquired from the management server 200, and generated. A list LT of target applications based on the list may be presented to the user.

Further, the processing shown in FIG. 28 may be applied as processing 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 confirm a target application that has been installed in the user terminal 100 but has not started. Specifically, the list generation unit 112 uses a URL scheme included in the application list acquired by the list acquisition unit 109, and is a target application that has been installed in the user terminal 100 but has not started yet. An application may be specified. That is, the list generation unit 112 may detect a target application that has been installed in the user terminal 100 but has not been started, among target applications included in the application list.

  In step SA242, the list generation unit 112 may delete the target application that has been installed in the user terminal 100 but has not started yet, from the application list of the target application. That is, the list generation unit 112 uses the target application included in the application list, except for the target application that is detected by using the URL scheme and that is installed in the user terminal 100 but has not started. You may regenerate the list.

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

Thereby, the user terminal 100 can present to the user a list LT of target applications excluding target applications that have been installed in the user terminal 100 but have never been started.
In the third example, among the target applications installed in the user terminal 100, both the target application of the old version and the target application that has not started can be detected and excluded from the application list. Good.

  Note that the display example shown in FIG. 29 may be applied as a display example of the target application list LT in the present embodiment. For example, in the display example of the target application list LT shown in FIG. 29, the “old target application” is set as “the target application that has been installed but never started”, and the same can be applied. .

[About the third to sixth embodiments]
Although it can describe as follows about the 3rd-6th embodiment demonstrated above, it is not restricted to the following description.

(1) In the mutual customer sending 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 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 regarding a plurality of target applications to be managed. The installation notification acquisition unit 241 includes 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) among the plurality of target applications by the user terminal 100. Example). The temporary installation notification acquisition unit 247 receives, from the target application 10A, another application (for example, the old version of the target application 10B or the target application 10C) that is a target application other than the target application 10A among the plurality of target applications. Temporary installation notification information (an example of third information) indicating installation is acquired. The installation information management unit 222 (an example of the installation information management unit) sends any information to 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. Manages installation information indicating whether the target application has been installed. Based on the installation information managed by the installation information management unit 222, the list notification unit 242 includes at least one of the plurality of target applications whose installation information corresponding to the user terminal 100 is not managed by the installation information management unit 222. An application list (second information) including information indicating the target application is transmitted to the user terminal 100. Here, the installation information corresponding to the user terminal 100 refers to installation notification information transmitted from the user terminal 100 in response to the target application being executed by the user terminal 100, for example.

  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). Then, the list notification unit 242 displays information indicating at least one target application for which neither installation notification information (an example of first information) nor temporary installation notification information (an example of third information) has been acquired from the user terminal 100. The application list (second information) that is included may be transmitted to the user terminal 100.

  Thereby, the management server 200a of this embodiment does not acquire the installation notification information when transmitting the application list indicating the target application for which the installation notification information corresponding to the user terminal 100 is not acquired to the user terminal 100. An application list of target applications excluding target applications 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 that are recommended for installation to the user.

(2) Here, the plurality of target applications are provided so that they can be installed on the user terminal 100 before being managed by the application management unit 221 of the management server 200a, and the old applications that are targeted for management after the provision are provided. The version of the target application is included.
In addition to the target application 10 </ b> A, another application that is a target application installed in the user terminal 100 is installed in the user terminal 100 before being managed by the application management unit 221 among a plurality of target applications, for example. The target application may be an older version.
This old version of the target application (an example of another application) is a target application installed in the user terminal 100 among a plurality of target applications, and transmits installation notification information (an example of first information) to the management server 200. It is a target application that does not have the function to perform. Note that the function of transmitting the installation notification information to the management server 200 is, for example, the function of the SDK 1011 (2011, 3011). That is, this old version of the target application is one in which, for example, SDK 1011 (2011, 3011) is not incorporated.

  Thereby, for example, even when an old version of the target application that does not incorporate the SDK 1011 is installed in the user terminal 100, the management server 200a of the present embodiment does not include the old version of the target application. Can be transmitted to the user terminal 100. Therefore, according to the present embodiment, a list LT of target applications that the user has not used 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 that are recommended for installation to the user.

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

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

(4) In addition, the management server 200a, among a plurality of target applications, non-installed information indicating target applications for which installation information (an example of first information) corresponding to the user terminal 100 is not managed by the installation information management unit 222 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 this non-installed information indicates a candidate of an old version target application to be detected by the user terminal 100 or a target application candidate that has been installed but never started.
Then, the temporary installation notification acquisition unit 247 (an example of the third information acquisition unit) is the above-described application installed in the user terminal 100 among the target applications indicated by the non-install information transmitted by the non-install information notification unit 248. Temporary installation notification information (an example of third information) indicating an application is acquired from the target application 10A (an example of a first application).

  The non-installation information notification unit 248 is configured such that, among the plurality of target applications, the installation notification acquisition unit 241 (an example of the first information acquisition unit) receives the installation notification information (the first application) 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 has not been acquired may be transmitted to the user terminal 100.

  In addition, the non-installation information notification unit 248 sends, to the user terminal 100, non-installation information indicating a target application for which neither installation notification information nor temporary installation notification information has been acquired from the target application 10A among a plurality of target applications. You may send it.

Thus, the management server 200a notifies the user terminal 100 of the old version target application candidates to be detected by the user terminal 100 or the target application candidates that have been installed but have not been started as non-installed information. In 100, it is possible to clarify a target to be detected as a target application of an old version or a target application that has been installed but never started. As a result, it is possible to reduce the amount of processing for extracting this old version of the target application or the target application that has been installed but never started, compared to the case of extracting from all the target applications. In addition, the target application 10A shortens the processing time for extracting the target application of the old version or the target application that has been installed but never started compared to the case of extracting from all the target applications. Can do.
In addition, the management server 200a of the present embodiment can manage an old version target application installed in the user terminal 100 or a target application that has been installed but never started. As a result, the management server 200a according to the present embodiment displays the application list of the target applications excluding the target application of the previous version installed in the user terminal 100 or the target application that has been installed but never started. 100 can be transmitted. As a result, when the target application recommended to be installed is presented to the user, a list LT of target applications excluding the target application of the previous version or the target application that has been installed but never started is displayed on the user terminal 100. 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 is managed by the information related to the plurality of target applications managed by the application management unit 221 and the installation information management unit 222. Based on the install information, non-install information (an example of fourth information) is transmitted to the user terminal 100. Here, the non-installed information indicates a target application for which install information corresponding to the user terminal 100 is not managed in the install information management unit 222 among a plurality of target applications.

  As a result, the non-installed information notification unit 248 determines that all the target applications extracted by referring to the information managed by the application management unit 221 that manages information related to a plurality of target applications to be managed, and the installation information management unit 222 A target application for which installation information corresponding to the user terminal 100 is not managed is shown by comparing with a target application for which installation information corresponding to the user terminal 100 extracted by referring to the installation information to be managed is managed. It is possible to specify non-installed information. This non-installed information can be said to indicate a candidate for an old version of a target application to be detected by the user terminal 100 or a target application that has been installed but never started.

  Note that the management server 200a is configured to start from the target application 10A (an example of the first application), an old version of the target application (an old version of the game different from the game C), or a target application that has been installed but has not started (game). 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 transmitted the installation notification information or the temporary installation notification information, and the target application. The user terminal 100 may be associated and managed. Then, the non-installation information notification unit 248 sends, to the target application 10A, non-installation information indicating the target application for which neither installation notification information nor temporary installation notification information has been acquired from the target application 10A among the plurality of target applications. May be transmitted.

(6) In the mutual customer sending system 500a, 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 installs information indicating that the target application has been installed in the user terminal 100 from the target applications installed in the user terminal 100 among the plurality of target applications to be managed (first). Information) and temporary installation notification information (an example of other installation notification information, an example of third information) indicating that another application, which is a target application other than the target application, is installed in the user terminal 100. Thus, installation information indicating which target application is installed in the user terminal 100 is managed.
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 other applications installed in the user terminal 100 and transmits other installation notification information (for example, temporary installation notification information) of the detected other applications to the management server 200a. Here, the other application includes both an old version of the target application installed in the user terminal 100 or a target application that has been installed but never started. The other installation notification information includes both temporary installation notification information of the target application of the previous version and temporary installation notification information of the target application that has been installed but never started. Then, the list acquisition unit 109 includes an application list (an example of application notification information and an example of second information) that includes information indicating at least one target application whose installation information corresponding to the user terminal 100 is not managed in the management server 200a. Is acquired from the management server 200a. Then, the display control unit 105 causes the display unit 120 to display a target application list LT (an example of display information) based on the application list acquired by the list acquisition unit 109.

  The list acquisition unit 109 manages an application list including information indicating at least one target application for which neither installation notification information nor temporary installation notification information (an example of other installation notification information) has been transmitted from the user terminal 100. It can be understood as what is acquired from 200a.

  Thereby, for example, when an old version target application is installed in the user terminal 100, or when there is a target application installed in the user terminal 100 but never started, the user terminal 100 of the present embodiment. Can acquire an application list of target applications excluding a target application of an old version or a target application that has never been started, and can present a list LT of target applications based on the acquired application list to the user. Therefore, the user terminal 100 of this embodiment can transmit the application list of the target application that is not installed in the user terminal 100 to the user terminal 100 regardless of the version of the target application. As a result, a list LT of target applications that are not installed in the user terminal 100 can be presented to the user at the user terminal 100 when the target application recommended for installation is presented to the user. That is, according to the present embodiment, it is possible to present a list LT of appropriate target applications that are recommended for installation to the user.

(7) In addition, the user terminal 100 has not acquired from the management server 200a uninstalled information indicating a target application 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 includes other applications installed in the user terminal 100 among the target applications indicated by the non-installation information acquired by the non-installation information acquisition unit 111 (for example, a target application of an old version or an installed version). Tentative installation notification information of the target application that has not been started up, but is transmitted to the management server 200a.

  The user terminal 100 acquires, from the management server 200a, non-installed information indicating a target application that has not transmitted installation notification information from the user terminal 100 (an example of the own terminal device) among a plurality of target applications. The acquisition unit 111 may be provided.

  The non-installation information acquisition unit 111 also indicates non-installation information indicating a target application for which neither installation notification information nor temporary installation notification information (an example of other installation notification information) is transmitted from the user terminal 100 among the plurality of target applications. May be acquired from the management server 200a.

  Thereby, the target application 10A of the user terminal 100 can, for example, select an old version target application installed in the user terminal 100 or a target application that has been installed but never started from the acquired non-installed information. Since extraction is performed, it is possible to reduce the amount of processing for extracting the target application of the old version or the target application that has been installed but never started, compared to the case of extracting from all the target applications. Further, the user terminal 100 according to the present embodiment compares the processing time for extracting this old version of the target application or the target application that has been installed but has not been activated from all target applications. Can be shortened.

(8) The temporary installation notification unit 108 (an example of another installation notification unit) uses the function of the user terminal 100 (an example of the own terminal device), and uses the user terminal 100 among the target applications indicated in the non-installed information. Other applications (for example, a target application of an old version or a target application that has been installed but never started) are detected.

  Here, the function of the user terminal 100 is, for example, the 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 the URL scheme corresponding to the target application indicated in the non-installed information included in the non-installed information from the management server 200a. Then, the temporary installation notification unit 108 uses the URL scheme acquired by the non-installed information acquisition unit 111 by the OS function of the user terminal 100 to install it in the user terminal 100 among the target applications indicated in the non-installed information. Detect other applications.

  As a result, the user terminal 100 can, for example, determine whether the URL scheme can be opened in the user terminal 100 by a simple means, such as another application installed in the user terminal 100 (for example, the target application of the old version). Or a target application that has been installed but never started.

  Note that the function of the user terminal 100 is not limited to the function of detecting the target application installed in the user terminal 100 using the URL scheme. For example, when the OS can acquire information indicating the target application installed in the user terminal 100 without using the URL scheme, the temporary installation notification unit 108 acquires information indicating the target application installed. Thus, other applications installed in the user terminal 100 may be detected among the target applications indicated by the non-install information acquired by the non-install information acquisition unit 111.

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

  As a result, the management server 200b stores the old version of the target application or the non-installed information that is a candidate of the target application that has been installed but has not been activated, as in the third embodiment, for example. Without transmission, it is possible to extract a target application of an old version or a target application that has been installed but never started from the applications installed in the user terminal 100 and add them as management targets.

(10) The application management unit 221 of the management server 200a (200b) prohibits the setting-side application that sets prohibition of posting based on the application list (an example of the second information) and the posting based on the application list of the setting-side application. The inter-app filter information (an example of the first posting prohibition information) that associates the set-side application to be managed is managed. 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 refers to the target application 10A (the first application). If there is inter-app filter information for which the example application is set to the set-side application, the remaining information obtained by removing 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-app filter information (an example of the first posting prohibition information) managed by the application management unit 221, and the target application 10 </ b> A (the first application information) If there is inter-app filter information in which one example of one application is set as the setting-side application, the remaining information obtained by removing information indicating the setting-side application from the application list is transmitted to the user terminal 100. May be.

  Accordingly, in the mutual customer sending system 500a, when the target application recommended to be installed is presented to the user, the relationship of the target application that is not recommended can be set in the management server 200a. For example, if there is a target application for which rating (age restriction) is set, the target application for which rating is set may not be recommended from the target application 10A for which rating is not set. .

(11) The management server 200a (200b) may include a reward processing unit 245. The reward processing unit 245 is predetermined in the customer destination application 20 (an example of the second application) described in the first embodiment among one or a plurality of target applications indicated by the application list (an example of the second information). If the reward granting conditions are satisfied, a reward granting process in which a reward is given to a user who uses the user terminal 100 may be performed. Here, the customer destination application 20 described in the first embodiment is, for example, a target application selected on the user terminal 100 from one or a plurality of target applications indicated by an application list (an example of second information). is there.

  As a result, the target application that is recommended for installation is presented to the user in the mutual customer sending system 500a that gives a reward to the target application of the customer when the target application of the customer who has not been used by the user is installed. In this case, the application list excluding the target application of the old version or the target application that has been installed but never started can be transmitted to the user terminal 100.

(12) Further, the management server 200a (200b) acquires the customer information indicating the customer sending to the customer destination application 20 (an example of the second application) described in the first embodiment. And a customer information management unit 223 that manages the customer information acquired by the customer information acquisition unit 243. Here, the customer information acquisition unit 243 may acquire customer information for the customer application 20 from the target application 10A, for example. The reward processing unit 245 manages customer information corresponding to the customer destination application 20 in the customer information management unit 223 when a predetermined reward granting condition set in the customer destination application 20 is satisfied. The reward granting process may be performed on the condition that
As a result, the mutual customer sending system 500a can be configured not to be rewarded because the customer application information is not recorded when the target application is installed regardless of this system.

  Here, the case where the predetermined reward granting condition is satisfied is a case where the customer destination application 20 (an example of the second application) has been executed by the user terminal 100 or has become executable. Also good. In addition, when the predetermined reward granting condition is satisfied, the customer destination application 20 is executed by the user terminal 100 or becomes executable, and a predetermined result is achieved in the customer destination application 20. It may be the case. As described above, the mutual customer sending system 500a can arbitrarily set the reward granting 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 granting 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 received by the user terminal 100 within a predetermined period. It may be a case where it has been executed or has become executable. In addition, when the predetermined reward granting condition is satisfied, the customer destination application 20 is a specific application, and the customer destination application 20 is executed or executable by the user terminal 100 within a predetermined period. And a case where a predetermined result is achieved in the customer destination application 20 may be used. In this way, among a plurality of target applications, only a specific application that is executing a campaign can be targeted for reward.

(13) In addition, the user terminal 100 includes a reward grant notification unit 107. The reward grant notification unit 107 is a reward indicating that the predetermined reward granting condition is satisfied when the predetermined reward granting condition is satisfied in the target application installed in the user terminal 100 (an example of the own terminal device). The grant notification information is transmitted to the management server 200a (200b). Here, when the management server 200a (200b) satisfies a predetermined reward granting condition in a target application among one or a plurality of target applications indicated by an application list (an example of second information, an example of application notification information) In addition, a reward granting process in which a predetermined reward is given in the target application is performed.

  The target application among one or a plurality of target applications indicated by the application list (an example of application notification information) is, for example, a list LT (display information) of target applications displayed on the user terminal 100 based on the application list. This is a target application selected from (Example).

  In this way, in the mutual customer sending system 500a, the user terminal 100 transmits reward grant notification information to the management server 200a (200b) when a predetermined reward granting condition is satisfied. For example, the application list 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, the user X) who has used the application be able to.

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

  Also, a plurality of predetermined reward granting conditions are provided, and the reward granting notification unit 107 sends the reward granting notification information to the management server 200a (200b) based on the satisfaction of each of the plurality of reward granting conditions. You may transmit to.

(14) Also, as described in the fifth embodiment, the user terminal 100 can, for example, list the target applications LT to be presented to the user based on the application list acquired from the management server 200 of the first embodiment LT. (For example, a screen displaying a list of information indicating the 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 that can communicate with the management server 200. Here, the management server 200 is installed in the user terminal 100 based on the installation notification information indicating that the target application installed in the user terminal 100 among the plurality of target applications to be managed is installed. Manage installation information for installed target applications. Note that the installation notification information is an example of 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 limited 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. Yes. 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 and an example of second information) that includes information indicating at least one target application whose installation information corresponding to the user terminal 100 is not managed in the management server 200. Obtain 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 target application list LT (an example of display information) based on the application list (an example of presentation information) generated by the list generation unit 112.
Thereby, the user terminal 100 lists the target applications excluding the target application for which the management server 200 manages the installation information corresponding to the user terminal 100 (that is, the target application that has been executed by the user terminal 100). The LT can be generated and presented to the user.

In addition, the list generation unit 112 (an example of a 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, an old version target application or a target application that has been installed but never started).
Here, the function of the user terminal 100 is, for example, the 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 the target application installed in the user terminal 100 using the URL scheme. The user terminal 100 does not use the URL scheme. Information indicating the target application installed in the user terminal 100 may be acquired. Other target applications installed in the user terminal 100 include other versions of the target application installed in the user terminal 100 and started in addition to the target application of the previous version or the target application that has been installed but never started. Target applications may be included.
Then, based on the determination result, the list generation unit 112 determines that the other target application described above (for example, the target application of the old version or the installed version has been started from the target applications indicated by the application list). An application list (an example of presentation information) excluding a target application that is not present may be regenerated.
Thereby, the user terminal 100 can present a list LT of target applications excluding the target applications installed in the user terminal 100 to the user. For example, even when an old version target application (that is, a target application for which the management server 200 does not manage installation information) is installed in the user terminal 100, the user terminal 100 stores the old version target application. A list LT of the excluded target applications can be presented to the user. Even when there is a target application that has been installed in the user terminal 100 but has not been started (that is, a target application for which the management server 200 does not manage installation information), the user terminal 100 does not start A list LT of target applications excluding target applications that have not been performed can be presented to the user.

In addition, the list generation unit 112 (an example of a 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 determination result using the function of the user terminal 100. An application list (an example of presentation information) in which the user can distinguish other target applications that have been installed (for example, target applications of an old version or target applications that have been installed but have not been started) may be generated again. .
Thereby, the user terminal 100 selects a target application installed in the user terminal 100 among 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 distinct target applications can be presented to the user. For example, even when an old version target application (that is, a target application for which the management server 200 does not manage installation information) is installed in the user terminal 100, the user terminal 100 stores the old version target application. A list LT of distinct target applications can be presented to the user. Further, even if there is a target application that has been installed in the user terminal 100 but has never been started (that is, a target application whose management server 200 does not manage installation information), this target that has never been started A list LT of target applications that can distinguish applications can be presented to the user. Therefore, the user terminal 100 can distinguish and present to the user information indicating a target application that is not installed in the user terminal 100 (that is, a target application candidate to be a customer destination).

(15) Further, in the application list (an example of the second information, an example of the application notification information) acquired by the list acquisition unit 109 (an example of the acquisition unit) of the user terminal 100, installation information is further managed in the management server 200. Information indicating at least one target application, and identification information that can distinguish between a target application for which installation information is not managed and a target application for which 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 that is not installed, information indicating at least one target application whose installation information is managed, and a target application whose installation information is 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 a generation unit) determines whether the target application for which the installation information included in the acquired application list is managed based on the distinction information included in the application list acquired by the list acquisition unit 109. Alternatively, at least an application list (an example of presentation information) that can be distinguished from a target application for which installation information is not managed may be generated again.
Thereby, the user terminal 100 has at least one target application whose installation information is not managed (for example, a target application that is not installed in 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 on the user terminal 100 can be presented to the user.

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

In addition, the list generation unit 112, among the target applications indicated by the application list, other target applications installed in the user terminal 100 (for example, an old version target application or installed but never started). 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 from at least the target application whose installation information is not managed.
As a result, the user terminal 100 has at least one target application whose installation information is not managed when an old version target application is installed or there is a target application that has been installed but never started. The target application of the old version or the target application that has been installed but never started is distinguished from among them, and at least one target application whose installation information is managed (for example, installed and started on the user terminal 100) A list LT of target applications that can distinguish target applications) can be presented to the user. Therefore, the user terminal 100 can present to the user information indicating a target application that is not installed in the user terminal 100 (that is, a target application candidate that is a customer destination).
It should be noted that the target application of the old version or the target application that has been installed but never started, and at least one target application whose installation information is managed (for example, the target application that has been installed and started on the user terminal 100) Is not a target application that is not yet installed in the user terminal 100 (that is, a candidate for a target application to be a customer destination), and thus 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 for which 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 for which installation information corresponding to the user terminal 100 is managed in the installation information management unit 222, a target application for which installation information is not managed, and a target application for which installation information is managed May be transmitted to the user terminal 100, including an application list (an example of the second information, an example of the application notification information).

  That is, the application list (an example of the second information, an example of the application notification information) acquired by the list acquisition unit 109 (an example of the acquisition unit) of the user terminal 100 is included in the management server 200a (200b). Information indicating at least one target application for which installation information corresponding to an example of a terminal device is not managed, information indicating at least one target application for which installation information is managed, and target applications for which installation information is not managed And distinction information that can distinguish the target application for which installation information is managed may be included.

  In this way, by transmitting to the user terminal 100 the distinction information that can distinguish whether or not the management server 200a (200b) manages the installation information corresponding to the user terminal 100, the user terminal 100 can be identified by the application list. Among the displayed target applications, the target application list LT 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 the installation information.

(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. 242 (an example of a second information notification unit).
In this configuration, the application management unit 221 manages information related to a plurality of target applications to be managed.
The information acquisition unit acquires information indicating the target application installed in the user terminal 100 among the plurality of target applications from the user terminal 100. 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 any detection method in the user terminal 100 may be used. . 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 an OS function of the user terminal 100, or an 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 processing in the user terminal 100, a record using Cookie, or the like), a detection method based on the record may be used. In addition, 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 displays installation information indicating which target application is 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. to manage. Based on the installation information managed by the installation information management unit 222, the list notification unit 242 includes at least one of the plurality of target applications whose installation information corresponding to the user terminal 100 is not managed by the installation information management unit 222. An application list including information indicating the target application (an example of the second information is transmitted to the user terminal 100).

  In this way, the management server 200a transmits to the user terminal 100 an application list indicating at least one target application that does not manage installation information corresponding to the user terminal 100, so that the target 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 above-described mutual customer sending system 500 (500a), the management server 200 (200a, 200b) manages the installed target application in association with the reward user ID (RewardUID) associated with the user terminal 100. Therefore, even if it is the same user, if the user terminal 100 differs, it will be judged that it is another user. For example, when the user changes the model of the user terminal 100, in the above-described mutual customer sending system 500 (500a), although the target application used on the user terminal 100 before the model change is used, the model after the model change is changed. In the user terminal 100, for example, it may be presented to the user as a target application to be rewarded. Thus, in the above-described mutual customer sending system 500 (500a), when the user terminal 100 is changed, or when the same user uses a plurality of user terminals 100, installation is recommended to the user. 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, the target application that is not a target to be recommended for installation is excluded. An embodiment of a mutual customer sending system 500b that presents the user with a list LT of appropriate target applications will be described.

[Outline of Mutual Customer Transmission System According to Seventh Embodiment]
FIG. 31 is an explanatory diagram illustrating an overview of the mutual customer sending system 500b according to the seventh embodiment.
In this figure, the 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 this figure, the user terminal 100A shows the user terminal 100 before the model change of the user X, and the target applications 10-1 to 10-3 (application 1 to application 3) are installed. User terminal 100B shows user terminal 100 after model change of user X, and installs target application 10-1 (application 1) and target application 10-4 (application 4). The target applications that are not installed in the user terminal 100A and the user terminal 100B will be described as the target application 10-5 (application 5) and the target application 10-6 (application 6). Unless otherwise distinguished, description of “−1”, “−2”, etc. will be omitted and the description will be made as the target application 10.
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, an outline of the mutual customer sending system 500b of the present 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 the model change is installed and activated for the first time, the 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 (RewardUID), 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 it 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 the model change is installed and activated for the first time, the installation notification information corresponding to each target application is sent to the management server 200c as shown in (4) and (5). Send. Thereby, 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 on the user terminal 100B, the management server 200c determines that the application user ID (included in the installation information T2 corresponding to the user terminal 100B) ApUID) is searched for whether it is included in the installation information corresponding to the other user terminal 100, and the application user ID (ApUID) is included in the installation information corresponding to the other user terminal 100. And the user terminal 100 of the same user X is determined. 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 determines that the user terminal 100A, the user terminal 100B, Are determined to be the user terminals 100 of the same user X, and the reward user ID (RewardUID) “096345565” and “249757234” are associated with each other. Thereby, the installation information T1 and the installation information T2 are associated with each other. Then, the management server 200c generates an application list of target applications recommended to be installed to the user based on the associated installation information T1 and installation information T2, for example, as shown in (6). An 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 200c transmits the application list of the target application indicating “application 5 (ApID = 005)” and “application 6 (ApID = 006)” to the user terminal 100B.
As a result, the user terminal 100B displays the target application list LT.
Thus, in this embodiment, the management server 200c associates and manages reward user IDs (RewardUID) of different user terminals 100 based on the application user ID (ApUID).

Next, the mutual customer sending 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 configuration shown in FIG. Since it is the same as the structure of the user terminal 100 in embodiment, the description is abbreviate | omitted here. The functional configuration of the user terminal 100 (SDK 11) of this embodiment is the same as that of the first embodiment shown in FIG.

[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 configuration diagram illustrating an example of the configuration of the management server 200c according to the present embodiment. As described with reference to FIG. 4, the management server 200 c includes a communication unit 210, a management unit 220, a storage unit 230, and a control unit 240 c. In this figure, the same components as those in FIG. 6 are denoted by the same reference numerals, and description thereof is omitted here.

Here, the 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 (RewardUID), an application ID (ApID), and an application user ID (ApUID) are associated with each other. 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 240c includes an installation notification acquisition unit 241, a list notification unit 242, a customer information acquisition unit 243, an installation guidance instruction unit 244, a reward processing unit 245, a timing unit 246, and others. A terminal information extraction unit 249.
In addition, the control part 240c in this embodiment differs in the point provided with the other terminal information extraction part 249 from 1st and 2nd embodiment.

Note that the installation information management unit 222 of this embodiment includes a reward user ID (an example of unique identification information) that identifies the user terminal 100 in which the target application (an example of the first application) that has transmitted the installation notification information is installed, and the target. The application ID (an example of identification information) of the application is managed in association with each other, and the reward user ID and the association information are managed in association with each other. Here, the association information is information for associating the user terminals 100 of the same user. Here, even if the user terminals 100 are different from each other (the user terminal 100A and the user terminal 100B), the same application user ID is set in the same application of the same user. This application user ID is used. In the present embodiment, the installation information management unit 222 manages the reward user ID and the application user ID in the target application in association with each other.
In addition, 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, the installation information management unit 222 stores the reward user ID, the application ID, and the application user ID in association with each other in the installation information storage unit 236 as shown in FIG. And the application user ID are managed in association with each other.

  The other terminal information extraction unit 249 makes an inquiry to the installation information management unit 222, through the association information associated with the reward user ID that identifies the user terminal 100 in which the target application that transmitted the installation notification information is installed. Then, another reward user ID associated with the reward user ID is extracted.

As described above, in the same application installed in both different user terminals 100 (the user terminal 100A and the user terminal 100B), different reward users are utilized by using the same application user ID set. An ID can be associated. Therefore, the other terminal information extraction unit 249 uses an application user ID as an example of user information in the target application as association information as the first extraction method.
Specifically, the other terminal information extraction unit 249 associates, in addition to the reward user ID, the application user ID in the target application associated with the reward user ID that identifies the user terminal 100 in which the target application is installed. The other rewarded user IDs are extracted. If there is a guarantee that the application user ID is unique among a plurality of target applications corresponding to the mutual customer sending system 500b and the application user ID of a certain target application is not used by another target application, the association is performed. Only the application user ID may be used as information, but when uniqueness is not guaranteed, a set of the application ID and application user ID of the target application may be used as 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 from the installation information stored in the installation information storage unit 236. The application user ID to be performed 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 user terminal 100) associated with the extracted application user ID is extracted.
Thus, the other terminal information extraction unit 249 uses, as association information, the application ID of the target application associated with the reward user ID that identifies the user terminal 100 in which the target application is installed, or the application ID and the application user ID. Use the pair.

By the way, different user terminals 100 (user terminal 100A, user terminal 100B) may not use the same application. For example, it is a case where the target application (for example, target application 10-4) which was not used in the old terminal (user terminal 100A) is used in the new terminal (user terminal 100B). In this case, the association using the application user ID of the target application is not possible. Therefore, the application user ID of another target application (for example, the target application 10-1) installed in the same user terminal 100 (user terminal 100B) is used. That is, the other terminal information extraction unit 249 uses, as the second extraction method, another target 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. You may make it utilize application user ID of an application (for example, object application 10-1). Specifically, the other terminal information extraction unit 249 selects other target applications associated with the same reward user ID as the application user ID of the target application from the installation information stored in the installation information storage unit 236. The application user ID is extracted. Further, 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 extracted application user. Other reward user IDs associated with the ID (reward user IDs other than the own user terminal 100) are extracted. Also in this example, not only the application ID but also a set of an application ID and an application user ID may be used.
As described above, the other terminal information extraction unit 249 uses the application user ID of another target application associated with the same reward user ID as the application user ID of the target application as the association information. Alternatively, a combination of an application ID and an application user ID of another target application associated with the same reward user ID as the combination of the application ID and the application user ID of the target application is used.
It should be noted that the other terminal information extraction unit 249 further extracts by the second extraction method when other reward user IDs (reward user IDs other than the own user terminal 100) cannot be extracted by the first extraction method. It may be. Moreover, you may make it stop by the 1st extraction method. In addition, when it stops by the 1st extraction method, the target application installed in the old terminal (user terminal 100A) is included in the list LT of target applications that the user presented to the user has not used. May be.

  Note that the list notification unit 242 of the present embodiment is installed in the user terminal 100 in which the target application is installed and 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 acquired from any of the target applications 10 is transmitted to the user terminal 100. In other words, the list notification unit 242 is not limited to the target application installed on the user terminal 100 after the model change (user terminal 100B), but also the target application installed on the user terminal 100 before the model change (user terminal 100A). The application list excluded from the target applications managed by the application management unit 221 is transmitted to the user terminal 100.

[Details of Mutual Customer Processing Operation According to Seventh Embodiment]
Next, the operation of the mutual customer sending system 500b of this embodiment will be described.
Note that the basic operation of the mutual customer 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. The operation of the mutual customer sending system 500b will be described focusing on the process of generating the application list of applications. In addition, the example demonstrated here is demonstrated on the assumption of the same state as FIG. Also, the example described here will be described on the assumption that the installation information stored in the installation information storage unit 236 is in the state shown in FIG.

  Here, with reference to FIG. 34, processing on the target application (for example, target application 10-1) side installed in the user terminal 100 (user terminal 100B) will be described. In the processing illustrated in FIG. 34, the target application will be described as including the SDK 11 in the first and second embodiments.

In FIG. 34, the processing from step SA11 to step SA24 and the processing of step SE11 are the same as those in the first embodiment shown in FIG.
In step SA24, when the list request unit 104 transmits list request notification information to the management server 200c (REQ12), in step SE115, the other terminal information extraction unit 249 of the management server 200c determines that the old terminal (user terminal 100A ) To extract the target application installed. The list request notification information includes at least an application ID of the 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 illustrated in FIG. 31, the other terminal information extraction unit 249 performs the above-described first extraction method. The target application installed in the user terminal 100A is extracted as follows.
The other terminal information extraction unit 249 acquires a reward user ID (“249757234”) and an 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 (“249757234”) is acquired. The other terminal information extraction unit 249 extracts installation information associated with another reward user ID including the set of the acquired application user ID (“5288”) and application ID (“001”).
The other terminal information extraction unit 249 identifies the reward user ID (“096354565”) associated with the extracted installation information. The other terminal information extraction unit 249 may store the specified reward user ID (“096345565”) and the reward user ID (“249757234”) 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 the target application corresponding to the application ID associated with the identified reward user ID (“096345565”) as the target application installed in 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.

Further, for example, when the user X acquires the list request notification information from the target application 10-4 shown 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 a reward user ID (“249757234”) and an 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 (“249757234”) is acquired. The other terminal information extraction unit 249 extracts installation information associated with another reward user ID including the set of the acquired application user ID (“1922”) and 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 uses 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 (“249757234”). A pair with the application ID (“001”) is acquired.

Next, the other terminal information extraction unit 249 extracts installation information associated with another reward user ID including the set of the acquired application user ID (“5288”) and application ID (“001”). . The other terminal information extraction unit 249 identifies the reward user ID (“096354565”) associated with the extracted installation information.
The other terminal information extraction unit 249 extracts the target application corresponding to the application ID associated with the identified reward user ID (“096345565”) as the target application installed in 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 for the target application (step SE15b). The list notification unit 242 includes the user application 100 installed with the target application and the target application 10 installed in the other user terminal 100 identified 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 them is generated. In other words, 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 ("249757234") to be generated 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 after step SE16 is the same as the processing at step SA25, the processing at step SA26, the processing at step SE16 to step SE19, and the processing at step SC11 shown in FIG.

[Summary of the seventh embodiment]
(1) As described above, in the mutual customer sending system 500b of this embodiment, the management server 200c (an example of a management device) includes an application management unit 221, an installation notification acquisition unit 241, and an installation information management unit 222. And an other terminal information extraction unit 249 and a list notification unit 242. The application management unit 221 manages information regarding 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) that identifies the user terminal 100 in which the target application 10-1 that transmitted the installation notification information is installed with the application ID of the target application 10-1. And managing the reward user ID and the association information (for example, application user ID) in association with each other. The other terminal information extraction unit 249 makes an inquiry to the installation information management unit 222, thereby associating information associated with the reward user ID that identifies the user terminal 100 in which the target application 10-1 that transmitted the installation notification information is installed. Then, another reward user ID associated with the reward user ID is extracted. The list notification unit 242 includes the target application 10 installed in the user terminal 100 in which the target application 10-1 is installed and 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 example, target application 10-5 (application 5), target application 10-6 (application 6)) for which installation notification information has not been acquired from any of the user terminals 100 is displayed. Send to.

  Thereby, the management server 200c of this embodiment, for example, when the model of the user terminal 100 is changed, the target application installed in 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, for example, when the target application recommended to be installed is presented to the user after the model of the user terminal 100 is changed, the management server 200c causes the user to present a list LT of target applications that the user has not used. be able to. That is, the management server 200c is a target that is already installed in another user terminal 100 of the same user when the model of the user terminal 100 is changed or when the same user uses a plurality of user terminals 100. It is possible to suppress the application from being presented to the user as an application list of target applications that are recommended for installation by the user.

(2) In this embodiment, the installation information management unit 222 also includes a reward user ID that identifies the user terminal 100 (an example of a terminal device) and an application ID (an example of identification information) of a target application (an example of a first application). ) And an application user ID (an example of user information) in the target application in association with each other. Then, the other terminal information extraction unit 249 uses the application user ID in the target application as the association information.
Thereby, since the management server 200c of this embodiment uses the application user ID which is information managed by the management server 200c, it is possible to use simpler means than when adding new information as association information. Reward user IDs between different user terminals 100 can be associated.

(3) Moreover, in this embodiment, the other terminal information extraction part 249 is the user terminal 100 (an example of a terminal device) by which the target application (an example of a 1st application) was installed like the 1st extraction method mentioned above. The application user ID in the target application associated with the reward user ID (an example of the unique identification information) that identifies the user ID is extracted in addition to the reward user ID.
Thereby, the management server 200c of this embodiment can associate the reward user ID between the different user terminals 100 using application user ID.

(4) Moreover, in this embodiment, the other terminal information extraction part 249 is a reward user ID (an example of specific identification information) linked | related with the application user ID in an object application (an example of a 1st application) as correlation information. The application user ID in the other target application associated with is used.
Thereby, the management server 200c of this embodiment can extract other reward user IDs 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 it is not possible, the reward user ID between different user terminals 100 can be associated using the application user ID in another target application.

(5) Also, in this embodiment, the other terminal information extraction unit 249 identifies a user terminal 100 (an example of a terminal device) in which a target application (an example of a first application) is installed as association information. The application ID of the target application associated with (an example of unique identification information) and the application user ID in the target application are used.
Accordingly, since both the application ID and the application user ID are used as the association information, the management server 200c according to the present embodiment, for example, erroneously uses the same application user ID in different target applications. Therefore, it can be determined that the users are the same.

(6) In the present embodiment, the installation notification information includes a reward user ID (an example of unique identification information) that identifies the user terminal 100 (an example of a terminal device) and a target application (an example of a first application). An application ID (an example of identification information) is included. Then, the installation information management unit 222 manages the reward user ID that identifies the user terminal 100 acquired by the installation notification acquisition unit 241 and the application ID of the target application in association with each other.
Thereby, the management server 200c of this 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) In addition, the management server 200c of the present embodiment associates an application user ID (an example of the first application) with the reward user ID (an example of the unique identification information) that identifies the user terminal 100. An application user information acquisition unit for acquiring (example). Note that the installation notification acquisition unit 241 may function as an application user information acquisition unit. That is, the application user ID of the target application that transmitted the installation notification information may be included in 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 that identifies the user terminal 100.
Thereby, when the target application is installed in the user terminal 100, the management server 200c, the application ID of the installed target application, the application user ID in the installed target application, and the reward associated with the user terminal 100 The user ID can be managed in association with it. That is, the management server 200c can manage the application user ID for each target application installed in the user terminal 100 in association with the reward user ID.

(8) In addition, the management server 200c of this embodiment includes a reward processing unit 245. The reward processing unit 245 satisfies a predetermined reward granting condition in the target applications 10-5 and 10-6 (an example of the second application) selected by the user terminal 100 from one or a plurality of target applications included in the application list. When it is determined that the target application 10-1 or 10-4 (an example of the first application) is given, a reward granting process in which a predetermined reward is given is executed.
Thereby, the management server 200c of this embodiment can provide a predetermined reward in the target applications 10-1 and 10-4 when it is determined that the predetermined reward provision condition is satisfied. Here, the management server 200c of the present embodiment generates an application list of a target application that is a target of reward granting, and transmits the generated application list to the user terminal 100. That is, the management server 200c of the present embodiment excludes the target application that is not the target of reward granting when the model of the user terminal 100 is changed or when the same user uses a plurality of user terminals 100. Is transmitted to the user terminal 100. For this reason, the management server 200c of the present embodiment allows the target application to be rewarded even when the model of the user terminal 100 is changed or when a plurality of user terminals 100 are used by the same user. An appropriate application list can be presented to the user. Therefore, when the model of the user terminal 100 is changed or when a plurality of user terminals 100 are used by the same user, the management server 200c according to the present embodiment is configured so that the target application that is not a target for reward grant is a reward grant. It can be suppressed that it is presented to the user as a target application.

In this embodiment, the installation information storage unit 236 associates the reward user ID (RewardUID) with the application ID (ApID), the reward user ID (RewardUID), and the application user ID (ApUID) in one data table. However, as shown in FIG. 35, it may be divided into two data tables. That is, the installation information storage unit 236 has a first data table that associates a reward user ID (RewardUID) with an application ID (ApID), and second data that associates an application user ID (ApUID) with an application user ID (ApUID). It may be divided into a table. In this case, data serving as a primary key for associating the data tables with each other is associated with each data table.
In the example illustrated 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 an installation ID (InstID) as a primary key, an application ID (ApID), and an application user ID (ApUID) in association with each other as a second data table.

  Moreover, although this embodiment mentioned above demonstrated the case where application user ID was utilized as correlation information, it is not limited to this. The management server 200c may use, for example, a cooperation code (for example, an e-mail address) input by the user as the association information. In this case, the other terminal information extraction unit 249 can associate the reward user IDs between the different user terminals 100 by associating the reward user IDs that match the cooperation codes input by the user.

<Eighth Embodiment>
Next, an eighth embodiment of the present invention will be described. First, an outline of the mutual customer sending system 500c of the present embodiment will be described.
In the mutual customer sending system 500 (500a) described above, one reward user ID is associated with one user terminal 100 and managed. Therefore, even if the user terminal 100 is the same, if the reward user ID 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 the reward user ID is changed, for example, when the user is allowed to change the reward user ID and is changed by the user, or when the reward user ID is changed by the convenience or processing of the mutual customer sending system 500c. Or the case where it is changed due to circumstances or processing other than the mutual customer sending system 500c.
For example, when there is information (hereinafter referred to as ID information) that is mutually different information associated with each user terminal 100 as an OS function of the user terminal 100 and is permitted to be used by each application, 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 is used. Etc. are changed, the reward user ID is changed.

  When the reward user ID is changed, in the above-described mutual customer sending system 500 (500a), for example, after the reward user ID is changed, it is used before the reward user ID is changed even though the user terminal 100 is the same. The target application that has been performed may be presented to the user as the target application that is the target of reward provision. As described above, in the above-described mutual customer sending system 500 (500a), when the reward user ID is changed in the user terminal 100, a target application that is not a target for which installation is recommended for the user is a target application that is recommended for installation. May be presented to the user.

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

[Outline of mutual customer sending system according to the eighth embodiment]
FIG. 36 is an explanatory diagram illustrating an overview of the mutual customer sending system 500c of the present embodiment.
In this figure, the basic configuration of the network system 1c according to the present 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 target applications 10-1 to 10-4 (application 1 to application 4) are installed in the user terminal 100 before or after the reward user ID is changed. The target applications 10-1 to 10-3 (application 1 to application 3) illustrated in the area indicated by reference numeral 100M are installed and activated before the reward user ID is changed, 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 reward user ID is changed, and indicates that the installation notification information is transmitted to the management server 200d. Further, the target application 10-1 (application 1) illustrated in the area indicated by reference numeral 100N is activated after the target application 10-1 (application 1) installed before the change of the reward user ID is changed. For convenience, the installation notification information is transmitted to the management server 200d. It should be noted that the target applications 10-2 and 10-3 (application 2 and application 3) installed before the change of the reward user ID have not been activated after the change of the reward user ID, for example, and manage the installation notification information It is assumed that it has not been transmitted to the server 200d.

The target application that has not been installed in the user terminal 100 before and after the reward user ID is changed will be described as the target application 10-5 (application 5) and the target application 10-6 (application 6). Unless otherwise distinguished, description of “−1”, “−2”, etc. will be omitted and the description will be made as the target application 10.
Further, in this figure, it is assumed that the management server 200d stores “application 1 (ApID = 001)” to “application 6 (ApID = 006)” as target application information of the mutual customer sending system 500c.
Here, with reference to FIG. 36, an example of a case where the user X changes the reward user ID in the user terminal 100 will be described as an overview of the mutual customer sending system 500c of the present embodiment.

  First, when each target application 10-1 to 10-3 is installed and activated for the first time before the reward user ID is changed, the user terminal 100, as shown in (1) to (3), each target application 10 Installation notification information corresponding to -1 to 10-3 is transmitted to the management server 200d. Note that the installation notification information transmitted in (1) to (3) includes, for example, a reward user ID (RewardUID) before change, an application ID (ApID), and an application user ID (ApUID). ing.

  The management server 200d acquires installation notification information corresponding to each of the target applications 10-1 to 10-3 and stores it as installation information. Here, 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 (RewardUID) on the user terminal 100. Then, after the reward user ID (RewardUID) is changed, the user terminal 100 transmits the 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 activated for the first time after changing the reward user ID (RewardUID), the user terminal 100 transmits installation notification information corresponding to the target application 10-1 to the management server 200d. A process in which the target application installed before changing the reward user ID transmits the installation notification information after changing the reward user ID will be described later with reference to FIG.
Further, when the target application 10-4 is installed in the user terminal 100 after the reward user ID (RewardUID) is changed, the user terminal 100 is configured to display (5) when the target application 10-4 is activated for the first time. The installation notification information corresponding to the target application 10-4 is transmitted to the management server 200d.
The installation notification information transmitted in (4) and (5) includes, for example, the changed reward user ID (RewardUID), application ID (ApID), and 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 them as installation information. Here, the installation information T20 corresponding to the changed reward user ID (RewardUID) 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 changing the reward user ID of the user terminal 100 of the user X, the installation information T20 corresponding to the changed reward user ID It is searched whether the application user ID (ApUID) included in is included in the installation information corresponding to other reward user IDs. When the application user ID (ApUID) is included in the installation information corresponding to another reward user ID, the management server 200d uses the same user terminal 100 (the above-described user terminal 100) of the user X as the installation information. It is determined that the 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 (RewardUID) (that is, the reward user ID (RewardUID) before the change). It is included in the installation information T10). Therefore, the management server 200d determines that the installation information T10 and the installation information T20 including the same application user ID (ApUID) “5288” are the installation information in the same user terminal 100 of the user X, and the change is made. The previous reward user ID (RewardUID) “096345565” is associated with the changed reward user ID (RewardUID) “249757234”.

Thereby, the management server 200d associates the installation information T10 with the installation information T20. Then, the management server 200d generates an application list of target applications recommended to be installed to the user based on the associated installation information T10 and installation information T20. For example, as illustrated in (6), the generated target application The application list is transmitted to the user terminal 100. In this example, among the target applications stored as the 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 200d 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 the target application list LT.

Thus, in this embodiment, the management server 200d, based on the application user ID (ApUID), the reward user ID (RewardUID) before change and the reward user ID (RewardUID) after change in the same user terminal 100, Are managed as the reward user ID (RewardUID) of the same user terminal 100. Then, the management server 200d determines that the user terminals 100 corresponding to the reward user ID (RewardUID) before the change and the reward user ID (RewardUID) after the change are the same user terminal 100, and the user terminal 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.
Thereby, the user terminal 100 can present to the user X a list LT of appropriate target applications excluding target applications that are not targets to be recommended for installation by the user X (that is, target applications already installed in the user terminal 100). .

Next, the mutual customer sending system 500c according to the present embodiment will be described in detail.
The configuration of the network system 1c and the configuration of the user terminal 100 according to the present embodiment 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 it is the same as that of a structure, the description is abbreviate | omitted here. The functional configuration of the user terminal 100 (SDK 11) of this embodiment is the same as that of the first embodiment shown in FIG.

Note that, as described with reference to FIG. 36, the method according to this embodiment for managing two types of reward user IDs (RewardUID) before and after the change in association with each other based on the application user ID (ApUID). A method similar to the method described in the seventh embodiment in which the reward user ID (RewardUID) before the model change and the reward user ID (RewardUID) after the model change are associated and managed based on the application user ID (ApUID) It is.
Therefore, the configuration of the mutual customer service system 500c according to the present embodiment may be the same as the configuration of the mutual customer service system 500b according to the seventh embodiment. That is, the configuration of the management server 200d included in the mutual customer sending 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 System 500c According to Eighth Embodiment]
FIG. 37 is a configuration diagram illustrating an example of the configuration of the management server 200d according to the present embodiment. 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 this figure, the same components as those in FIG. 32 are denoted by the same reference numerals, and description thereof is 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. 32 in that an information extraction unit 249a is provided instead of the other terminal information extraction unit 249. Here, since the configuration of the management server 200d may be the same as the configuration of the management server 200c shown in FIG. 32 as described above, the function of the other terminal information extraction unit 249 is included as the function of the information extraction unit 249a. Can be applied.

  For example, the information extraction unit 249a according to the present embodiment, like the other terminal information extraction unit 249 illustrated in FIG. 32, includes reward user IDs and association information (for example, target application) included in the installation information managed by the installation information management unit 222. Based on the user information), the reward user ID associated with the association information is extracted. Thereby, the information extraction part 249a of this embodiment extracts the reward user ID before a change in the user terminal 100 specified by the reward user ID after a 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 this embodiment, the information extraction unit 249a extracts the reward user ID associated with the association information by the same function as the function of the other terminal information extraction unit 249, so that the same user terminal 100 A reward user ID before change and a reward user ID (RewardUID) after change are extracted.

As the above-described association information, as described as the first extraction method in the seventh embodiment, user information (for example, application user ID) in the target application may be used.
Specifically, in the information extraction unit 249a, the application user ID in the target application associated with the reward user ID that identifies the user terminal 100 in which the target application is installed is associated in addition to the reward user ID. Other reward user IDs may be extracted.
For example, the information extraction unit 249a is the application user of the target application (for example, the target application 10-1) that has transmitted the installation notification information after the change of the reward user ID among the target applications installed before the change of the reward user ID. An ID may be used. And the information extraction part 249a is the same by extracting the other reward user ID linked | related with the application user ID linked | related with the reward user ID after a change other than the said reward user ID after a change. 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 reward user ID is changed. In this case, the reward user ID before the change cannot be extracted using the application user ID of the target application (for example, the target application 10-4). Therefore, as the above-described association information, as described as the second extraction method in the seventh embodiment, the association information is associated with the same reward user ID as the application user ID of the target application (for example, the target application 10-4). You may make it utilize the application user ID of the other target application (for example, target application 10-1).

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

  Note that the information extraction unit 249a according to the present embodiment further extracts the reward user ID before the model change and the reward user ID after the model change, similarly to the other terminal information extraction unit 249 according to the seventh embodiment. Also good.

  In addition, the list notification unit 242 of the present embodiment displays an application list indicating at least one 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. Send to. For example, the list notification unit 242 displays 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 before change or the reward user ID after change. It transmits with respect to the user terminal 100 corresponding to reward user ID. In other words, the list notification unit 242 not only selects the target application installed after the change of the reward user ID in the user terminal 100 among the plurality of target applications managed by the application management unit 221, but also before the change of the reward user ID. An application list of at least one target application excluded including the installed target application is transmitted to the user terminal 100.

[Details of Mutual Customer Processing Operation According to Eighth Embodiment]
The basic operation of the mutual customer service system 500c of this embodiment is the same as that of the first embodiment shown in FIGS. 14 and 15, and here, the process of generating the application list of the target application of this embodiment The operation will be described.

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

Note that the specific process of step S115 executed by the information extraction unit 249a in the present embodiment is the same as the process executed by the other terminal information extraction unit 249 in the seventh embodiment, and associated information (for example, an application user) ID) is a process for extracting a reward user ID associated with 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. Note that 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 by combining the first extraction method and the second extraction method. 100 reward user IDs before change may be extracted.

[Example of Installation Notification Information Transmission Processing According to Eighth Embodiment]
Next, in the present embodiment, a process for transmitting the installation notification information of the target application installed 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 installation notification information transmission process is performed, for example, in the initialization process described with reference to FIG. 14 in the first embodiment. In the initialization process illustrated in FIG. 14, when the target application is installed on the user terminal 100 and activated, the installation notification information of the target application is transmitted from the user terminal 100 to the management server 200 to be initialized. The process for transmitting the installation notification information is not performed from the next activation of the target application. Therefore, even if the reward user ID of the user terminal 100 is subsequently changed, the installation notification information cannot 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 received the installation notification before the change. Process to send.

  FIG. 38 is a flowchart illustrating an example of the initialization process according to the present embodiment. FIG. 38 shows another form of the initialization process (steps SA11 to SA17) shown in FIG. 14, and is the same as each process shown in FIG. 14 except for the process related to the initialization process. Omitted.

  In the initialization processing shown in FIG. 38, it is assumed that different ID information associated with each user terminal 100 as a function of the OS of the user terminal 100 is stored in the terminal storage unit 140, and this ID information is rewarded. A case where it is used 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 from the OS after the OS is started and stored in the terminal storage unit 140. Also good. In addition, it is assumed that the user is allowed to change the ID information by the OS.

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

  The initialization processing unit 101 of the SDK 11A determines whether or not 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 to determine 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 a 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 sharing area of the terminal storage unit 140 as the reward user ID (step SA15).

  On the other hand, when it is determined that the reward user ID has been acquired (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 source application 10 (game A) has been installed in the user terminal 100 to the management server 200d (step SA16). Here, the installation notification information includes a reward user ID (RewardUID) corresponding to the user terminal 100, an application ID (ApID) of the installed customer application 10 (game A), and this customer 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 sends response information (notification result) indicating that the acquisition has been received to the user terminal 100 ( To the SDK 11A). The installation information management unit 222 of the management server 200d also includes a reward user ID (RewardUID) included in the installation notification information acquired by the installation notification acquisition unit 241 and an application ID (ApID) of the customer source application 10 (game A). And the application user ID (ApUID) of the user X in the customer source application 10 (game A) are stored in the installation information storage unit 236 as installation information (step SE11).

  When the initialization processing unit 101 of the SDK 11A acquires the response information (notification result) transmitted from the management server 200d, the initialization processing unit 101 sets a flag indicating initialization and ends the initialization process (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 and the reward user ID (RewardUID) stored in the terminal storage unit 140. To determine whether or not the ID information has been changed (step S121). When it is determined that the ID information stored in the terminal storage unit 140 matches the reward user ID (RewardUID) and the ID information has not been changed (step S121: NO), the initialization processing unit 101 End the initialization process.

  On the other hand, when it is determined that the ID information stored in the terminal storage unit 140 does not match the reward user ID (RewardUID) and the ID information is changed (step S121: YES), the unique identification information acquisition unit 102 Then, the changed ID information is acquired as the 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 the changed reward user ID (step SA15). In addition, 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 changed reward user ID, You may memorize | store so that the reward user ID after a change can be distinguished, leaving the reward user ID before a change.

  Then, the installation notification unit 103 transmits installation notification information indicating that the customer source application 10 (game A) is installed in the user terminal 100 to the management server 200d (REQ11, step SA16). Here, the installation notification information includes the changed reward user ID (RewardUID) corresponding to the user terminal 100, the application ID (ApID) of the installed customer application 10 (game A), and the customer source. The application user ID (ApUID) of the user X registered in the application 10 (game A) is included.

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

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

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

  Thereby, when the target application installed in the user terminal 100 is started for the first time, the user terminal 100 has acquired the reward user ID and the ID information before the change even though the ID information is changed. Is still stored in the terminal storage unit 140 as a reward user ID, the installation notification information with the changed ID information as the reward user ID can be transmitted to the management server 200d. In addition, when the target application is started for the first time, by not storing the changed ID information as the reward user ID in the terminal storage unit 140, the target application that has been installed before the change and the installation notification information has been transmitted The installation notification information of at least one target application can be transmitted after the change.

  Note that the initialization processing unit 101 may perform control so that installation notification information is transmitted each time the target application installed in the user terminal 100 is activated. In this case, the management server 200d may acquire and manage the installation notification information before the change of the reward user ID and the installation notification information after the change of the reward user ID from the user terminal 100, respectively.

<About the seventh and eighth embodiments>
The seventh and eighth embodiments described above can be described as follows, but are not limited to the following descriptions.

(1) In the mutual customer sending 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. Unit 249 and list notification unit 242. In the mutual customer sending 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. A list notification unit 242. As described above, since the function of the information extraction unit 249a can be the same as the function of the other terminal information extraction unit 249, the configuration of the management server 200d of the eighth embodiment is the same as that of the seventh embodiment. It is good also as a structure similar to the structure of the management server 200c. Hereinafter, the configuration of the management server 200d will be described as an example that includes both the management server 200c and the management server 200d.
The application management unit 221 manages information regarding a plurality of target applications to be managed. The installation notification acquisition unit 241 (an example of the first information acquisition unit) receives the user terminal 100 in response to the execution of the target application 10-1 (an example of the first application) among the plurality of target applications. Is acquired from the user terminal 100 by associating the installation notification information (an example of the first information) transmitted from and the reward user ID (an example of the unique identification information) associated with the user terminal 100. The installation information management unit 222 (an example of an information management unit) manages the reward user ID associated with the user terminal 100 acquired by the installation notification acquisition unit 241 and the association information in association with each other. The information extraction unit 249a (an example of an extraction unit) extracts a reward user ID associated with the association information based on the reward user ID and association information managed by the installation information management unit 222. The list notification unit 242 (an example of a second information notification unit) is 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. An application list (an example of second information) including information indicating 10-5 (application 5) and target application 10-6 (application 6)) is transmitted to the user terminal 100 on which the target application 10-1 is executed. To do.

For example, the information extraction unit 249a (an example of the 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 not included in the target application 10-1. Is transmitted to the user terminal 100 on which is executed.
Thereby, the management server 200d (200c) of the present embodiment can manage a plurality of reward user IDs in association with each other. Note that the number of reward user IDs associated with the association information is not limited to a plurality, and may be one.

Specifically, the information extraction unit 249a (an example of the extraction unit) of the management server 200d uses the target application 10-1 (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 user terminal 100 on 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 (first information of 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, the target application 10-5 (application 5) and the target application 10-6 (application 6)) that has not acquired one example) , It may be transmitted to the user terminal 100 corresponding to the first unique identification information.

  Thereby, for example, when the reward user ID of the user terminal 100 is changed, the management server 200d (200c) is installed on the user terminal 100 and started (executed) the target application before the reward user ID is changed. The target application installed and activated (executed) on the user terminal 100 after changing the reward user ID can be managed in association with each other. Therefore, for example, when the management server 200d (200c) presents target applications recommended to be installed to the user after changing the reward user ID of the user terminal 100, a list of target applications that the user has not used. 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 200d (200c) gives the target application installed and executed (executed) to the user before the change of the reward user ID to the user. On the other hand, it is possible to prevent the user from being presented as the target application list LT of the target applications recommended for installation. Therefore, according to the present embodiment, it is possible to present a list LT of appropriate target applications that are recommended for installation to the user.

(2) Further, the information extraction unit 249a (an example of the extraction unit) of the management server 200d uses the target application 10-1 (first application) as a plurality of reward user IDs (an example of unique identification information) associated with the association information. The first unique identification information, which is the reward user ID associated with the user terminal 100 for which the user ID is executed, and the reward associated with another user terminal 100 different from the user terminal 100 corresponding to the first unique identification information. You may extract the 2nd specific identification information which is user ID.
The list notification unit 242 (an example of the second information notification unit) includes 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 first information) from any of the above May be transmitted to the user terminal 100 corresponding to the first unique identification information.

  Thereby, the management server 200d (200c), for example, when the model of the user terminal 100 is changed, the target application installed and activated (executed) on the user terminal 100 (user terminal 100A) before the model change, and The management server 200d (200c) can manage the user terminal 100, for example, by associating and managing the user terminal 100 after the model change (target application installed and executed (executed) on the user terminal 100B). When the target application that is recommended for installation is presented to the user after the model change, the user can be presented with a list LT of target applications that the user has not used, ie, the management server 200d (200c). , The user terminal 100 When the type is changed or when a plurality of user terminals 100 are used by the same user, a target application that is already installed in another user terminal 100 of the same user is recommended to be installed to the user It can be suppressed that the application list of applications is presented to the user.

(3) The installation information management unit 222 (an example of the 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 the target application (an example of the first application). (An example of user information) is associated and managed. And the information extraction part 249a (an example of an extraction part) may utilize application user ID in a target application as association information.
Thereby, since the management server 200d (200c) uses the application user ID which is information managed by the management server 200d (200c), it is simpler than when new information is added as association information. A plurality of reward user IDs can be associated by means.

For example, the information extraction unit 249a (an example of the extraction unit) is associated with a reward user ID corresponding to the user terminal 100 in which the target application (an example of the first application) is installed as in the first extraction method described above. Other reward user IDs associated with the application user ID in the target application are extracted in addition to the reward user ID.
Thereby, management server 200d (200c) associates the reward user ID before and after change in the same user terminal 100, or the reward user ID between different user terminals 100 using application user ID. it can.

(4) Further, the information extraction unit 249a (an example of the extraction unit) has, as association information, a reward user ID (unique) associated with an application user ID (an example of user information) in the target application (an example of the first application). You may utilize application user ID in the other object application linked | related with (an example of identification information).

  Thereby, the management server 200d (200c) can extract other reward user IDs 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, using the application user ID in another target application, 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 is associated. be able to.

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

  Accordingly, since both the application ID and the application user ID are used as the association information, the management server 200d (200c) has, for example, 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 a second user different from the first user, it can be prevented that the user is mistakenly determined to be the same user.

(6) 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. For example, the management server 200d acquires an application user ID (an example of user information) in the target application (an example of the first application) in association with a reward user ID (an example of unique identification information) associated with the user terminal 100. You may provide an application user information acquisition part. Note that the installation notification acquisition unit 241 may function as an application user information acquisition unit. That is, the application user ID of the target application that transmitted the installation notification information may be included in 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 of the executed target application with the user terminal 100. And associated reward user IDs can be managed. That is, the management server 200d (200c) can manage the application user ID for each target application executed by the user terminal 100 in association with the reward user ID.

  Note that when user information is used as association information, the application user ID is used as an example, and the present invention is not limited to this. For example, the user information used as the association information may be information that can identify the user in the target application, and may be a user name, a user nickname or handle name (alias), a user image, or the like.

(7) Also, the installation notification acquisition unit 241 (an example of the first information acquisition unit) of the management server 200d 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 given reward user ID (an example of unique identification information). Then, the installation information management unit 222 (an example of an 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.
Accordingly, the management server 200d (200c) can manage which target application is executed by the user terminal 100 based on the reward user ID and the application ID of the target application.

(8) The management server 200d also includes a reward processing unit 245. The reward processing unit 245 has a predetermined reward granting condition in the target applications 10-5 and 10-6 (an example of the second application) out 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 in which a reward is given 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 one or a plurality of target applications indicated by the application list, for example.
Thereby, the management server 200d (200c) can grant a predetermined reward in the target applications 10-1 and 10-4 when it is determined that the predetermined reward granting condition is satisfied.

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

[Overview of Mutual Customer 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. The 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, portions corresponding to those in FIG. 4 are assigned the same reference numerals, and descriptions thereof are omitted.

  In the mutual customer sending system 500d shown in FIG. 39, the customer sending application 10 is replaced with a dedicated application (hereinafter also referred to as “dedicated application 60”) having a function of sending customers to the customer sending application 20. This is different from the mutual customer sending system 500 shown in FIG. The dedicated application 60 is provided so that it can be installed (downloaded) from the application store 400 to the user terminal 100, for example. This figure shows an example in which a dedicated application 60 is installed in the user terminal 100 and a customer is sent from the dedicated application 60 to the customer destination application 20.

  The dedicated application 60 includes, for example, the function 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 500d, the customer sending process from the customer sending application 10 to the customer destination application 20 is performed. Similarly, it is possible to perform a customer sending process from the dedicated application 60 to the customer destination application 20.

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

  For example, if the customer destination application 20 (game B) is in a normal period when it is not in a campaign, the management server 200 determines that the customer destination application 20 (game B) is installed in the user terminal 100. Remuneration grant information is transmitted to the application server 320 corresponding to the customer destination application 20 (game B). Further, if the customer destination application 20 (game B) is in a campaign, the management server 200 confirms that the reward granting condition is satisfied in the customer destination application 20 (game B) installed in the user terminal 100, for example. When the reward granting notification information indicating that is received, the reward granting information is transmitted to the application server 320 corresponding to the customer destination application 20 (game B).

  It should be noted that the customer destination application 20 (game B) is in a campaign that the customer destination application 20 participates in the same campaign with the customer source (here, the dedicated application 60). The customer application 20 may be participating in the campaign alone and in the campaign.

[Functional Configuration of User Terminal 100 (Dedicated Application 60) of Ninth Embodiment]
FIG. 40 is a configuration diagram illustrating an example of a functional configuration of a customer sending process executed 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 notification unit 106. Here, the dedicated application 60 only needs to have at least a functional configuration as a customer source (for example, a functional configuration of the SDK 11A) among the functional configurations of the SDK 11 shown in FIG. The unique reward grant notification unit 107 may not be provided.
Note that the dedicated application 60 may have a configuration in which the SDK 11A is incorporated.

  With this configuration, the dedicated application 60 transmits customer information for the customer destination application 20 selected from the target application list LT to the management server 200, as with the customer source application 10 in which the SDK 11A is incorporated. Can be processed.

  Further, the dedicated application 60 does not become a customer destination application. Therefore, the management server 200 does not have to manage whether or not the dedicated application 60 is installed in the user terminal 100. Therefore, the dedicated application 60 does not need to transmit the installation notification information to the management server 200, and may be configured not to include the installation notification unit 103 illustrated in FIG.

[Operation Example of Mutual Customer Processing of Ninth Embodiment]
Next, the operation of the customer sending process by the mutual customer sending system 500d according to the present embodiment will be described. The customer sending process by the mutual customer sending system 500d is the same as the customer sending process according to the first embodiment described with reference to FIG. be able to.

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

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

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

  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 sending system 500d. . On the other hand, if no target application is 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 activated. Is done.

  Processes after the initialization process described above are the same as those described with reference to FIG. 14, and customer information to be sent to the customer 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 customer information for the customer destination application 20 in the same manner as in the first embodiment when the dedicated application 60 becomes a customer sender. Can be managed.

  In the present embodiment, since the customer source is the dedicated application 60, for example, when no reward is given to the customer source, the customer source need not be specified. Therefore, in this embodiment, the customer ID does not need to include the application ID of the dedicated application 60 for identifying the customer, and at least the application ID (ApID of the customer application 20 (game B)). ) And a reward user ID (RewardUID).

  As described above, the mutual customer sending system 500d of the present embodiment performs the customer sending process from the dedicated application 60 to the customer destination application 20 using the dedicated application 60 as a customer sending source. Similarly to the mutual customer sending system 500 described, the customer can be sent to the customer destination application 20. In the case of a customer sending process from the dedicated application 60 to the customer destination application 20, the customer destination application 20 can be a customer sending source, but the dedicated application 60 does not become a customer destination. Accordingly, the dedicated application 60 is a one-way customer sending process to the customer destination application 20.

Note that the configuration using the dedicated application 60 according to the present embodiment as a customer source can also be applied to the second to ninth embodiments.
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 a target application included in the application list to be transmitted to the user terminal 100 based on a predetermined condition. The process of selecting (filtering process) may be performed.

  Further, in the third to fifth embodiments, the target application 10A shown in FIG. 18 may be a dedicated application specialized for the function of the customer source. In the sixth embodiment, the target application 10A shown in FIG. 30 may be a dedicated application specialized in the function of the customer source. For example, the above-described dedicated application may have a configuration including at least a functional configuration as a customer sending source similarly to the dedicated application 60. Therefore, for example, the above-described dedicated application may have a configuration in which the reward grant notification unit 107 that is unique as the functional configuration of the customer is excluded from the functional configuration of the SDK 1011 illustrated in FIG. In addition, the above-described dedicated application may have a configuration in which, for example, the reward grant notification unit 107 that is unique as the functional configuration of the customer destination is excluded from the functional configuration of the SDK 2011 illustrated in FIG. In addition, the dedicated application described above may have a configuration in which the reward grant notification unit 107 that is unique as the functional configuration of the customer is excluded from the functional configuration of the SDK 3011 illustrated in FIG. Note that the above-described dedicated application may have a configuration in which the installation notification unit 103 is excluded as in 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 the model change, the management server 200c performs the user terminal 100B after the model change and the user terminal 100A before the model change. And an application list indicating at least one target application from which 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 the model change and the user terminal 100A before the model change according to, for example, the second extraction method described in the seventh embodiment. Using the application user ID in the target application, 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.
In the eighth embodiment, when the reward user ID corresponding to the user terminal 100 is changed, the management server 200d determines the reward user ID based on a request from the dedicated application 60 installed in the user terminal 100. You may transmit to the user terminal 100 the application list which shows the at least 1 object application which has not acquired installation notification information from any after change and before change of reward user ID. In this case, the management server 200d transmits the installation notification information both after the reward user ID is changed and before the reward user ID is changed, for example, according to the second extraction method described in the eighth embodiment. The reward user ID after the change and the reward user ID before the change may be associated using the application user ID in any of the target applications.

<Modification of the first to ninth embodiments>

  The embodiment of the present invention has been described in detail with reference to the drawings. However, the specific configuration is not limited to the above-described embodiment, and includes a design and the like within a scope not departing from the gist of the present invention. For example, the functions described in the first to ninth embodiments can be arbitrarily combined. In the following description, the management servers 200, 200a, 200b, 200c, and 200d are simply described as “management server 200” unless otherwise distinguished.

(1) In the above embodiment, the communication unit 210 (an example of the transmission / reception 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 information (for example, customer source information or customer destination information), instruction information (an example of information for displaying an installable screen on the user terminal 100), or reward grant notification information directly The example which communicates with the user terminal 100 was demonstrated. Similarly, the terminal communication unit 130 (transmission / reception unit) of the user terminal 100 directly communicates the installation notification information, application list, list request notification information, customer information, instruction information, or reward grant notification information with the management server 200. An example was explained.

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

In addition, when communicating with the management server 200 directly from the user terminal 100, you may make it establish a communication session as needed. In other words, both the case of directly communicating with the management server 200 before establishing the communication session and the case of directly communicating with the management server 200 after establishing the communication session may be included.
For example, the installation notification information communicates directly with the management server 200 before establishing a communication session, and other information communicates directly with the management server 200 after establishing the communication session. Good. By doing in this way, the application that does not include the application server 320 corresponding to the customer destination application 20, that is, the application that operates stand-alone in the user terminal 100, as the customer destination application 20 that is the target of the normal reward, is the target application. Can be handled as That is, when transmitting installation notification information indicating that an application that operates in a stand-alone manner is installed, the user terminal 100 directly manages without performing a process of establishing a communication session via the application server 300. Communication with the server 200 is possible.

  FIG. 17 is a flowchart for explaining the operation of the communication session establishment process. This communication session establishment process (communication session establishment process) is a case where the customer source application 10 or the customer destination application 20 is activated on the user terminal 100, and the SDK 11A and the SDK 11B communicate with the management server 200 for the first time. For example, the initialization process described with reference to FIGS. 14 and 15 is performed. FIG. 17 shows a communication session establishment process performed in the initialization process shown in FIG. The communication session establishment process can be performed in the same manner as the initialization process shown in FIG. In FIG. 17, parts corresponding to the respective processes in FIG. Note that it is assumed that a communication session has already been established between the user terminal 100 and the application server 310.

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

  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 information (for example, customer source information or customer destination information) The instruction information (an example of information for causing the user terminal 100 to display an installable screen) or a part of the reward grant notification information does not directly communicate with the management server 200 from the user terminal 100. You may communicate with the user terminal 100 via the application server 300 (an example of a server apparatus) corresponding to the former application 10 (an example of a 1st application) or the customer destination application 20 (an example of a 2nd application). That is, the communication unit 210 (transmission / reception unit) of the management server 200 transmits the installation notification information, application list, list request notification information, customer information, instruction information, or reward grant notification information to the customer source application 10 or customer destination application. 20 may communicate with the user terminal 100 via the application server 300 corresponding to 20, or directly communicate with the user terminal 100.

Further, the communication unit 210 (an example of the transmission / reception unit) of the management server 200 sends the installation notification information, the application list, the list request notification information, the customer information, the instruction information, or the reward grant notification information to the customer source application 10 or the customer. You may communicate with the user terminal 100 via the application server 300 corresponding to the previous application 20. Similarly, the terminal communication unit 130 (transmission / reception unit) of the user terminal 100 passes through the application server 300 corresponding to the customer source application 10 (installed target application) or the customer destination application 20 (selected target application). You may communicate with the management server 200.
Thus, even if the user terminal 100 and the management server 200 communicate with each other through the application server 300, the mutual customer sending system 500 is the same as the customer sending process and reward as in the first embodiment and the second embodiment. Processing can be performed, and similar effects can be obtained.

(2) In the above embodiment, an example in which the application user ID (ApUID) is included in the installation notification information and transmitted from the user terminal 100 (SDK 11) to the management server 200 has been described. However, the present invention is not limited to this. 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, in step SA21, the initialization processing unit 101 of the SDK 11A notifies the application server 300 of the reward user ID when transmitting the one-time token acquisition request information to the application server 300. Furthermore, the application server 300 transmits the reward user ID, application ID, and application user ID to the management server 200. The installation information management unit 222 of the management server 200 includes, as the application user ID (ApUID) corresponding to the 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. Thus, by transmitting the application user ID from the application server 300 instead of from the user terminal 100 (SDK11), it becomes unnecessary to manage the application user ID at the user terminal 100 (SDK11).

  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 cannot be performed. However, the transmission of the installation notification information indicating that the target application installed in the user terminal 100 is installed to the management server 200 does not have to be directly related to the registration of the user information. Therefore, the user terminal 100 transmits installation notification information to the management server 200 regardless of whether user information is registered 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, the reward processing unit 245 has explained an example in which the CP reward processing is executed based on the fact that the reward grant notification information is acquired from the SDK 11B of the customer destination application 20 of the user terminal 100. It is not limited to. For example, the CP reward process may be executed based on the acquisition of reward grant notification information from the application server 320 corresponding to the customer destination application 20. In this case, the reward grant notification information (result spot arrival notification) may include the application ID of the customer destination application 20, the application user ID, the campaign ID, and the result spot ID (RewardSpotID).
For example, the reward processing unit 245 of the management server 200 acquires reward grant notification information (result point arrival notification) transmitted from the application server 320. Next, the reward processing unit 245 identifies installation information corresponding to the application ID and application user ID of the customer destination application 20 from the installation information stored in the installation information storage unit 236, and corresponds to the identified installation information. Reverse reward user ID. Then, the reward processing unit 245 responds to the customer information based on the reverse reward user ID and the fact that the customer information record for the customer application 20 is managed in the customer information management unit 223. In association with the reward management ID, the achievement point ID (RewardSpotID) included in the acquired reward grant notification information is set, and the reward establishment information having the establishment status (RewardStatus) as the flag “0” (not notified) is generated, and the reward The establishment information storage unit 238 stores the information. The subsequent processing is the same as in the above embodiment. Thus, by transmitting the reward grant notification information (result point arrival notification) from the application server 320, the processing burden on the user terminal 100 (SDK11B) can be reduced.

(4) In the above embodiment, the reward user ID is unique identification information (unique identification unique in the mutual customer sending system 500) that can uniquely identify the installed user terminal 100 when the target application is first installed. Although the example generated as information) has been described, the present invention is not limited to this. For example, it is good also considering the terminal identification number and telephone number (for example, in the case of a smart phone) uniquely set to the user terminal 100 as a reward user ID. However, it is possible to improve the security by generating and using the reward user ID as in this embodiment without using personal information such as a terminal identification number or a telephone number. Further, by using unique identification information in the mutual customer sending system 500 without using a terminal identification number or a telephone number as a reward user ID, the user terminal 100 owned by the user (an example of a terminal device) Even if the user is changed by replacement, etc., the mutual user system 500 is used by maintaining the state from the user terminal 100 before the change by moving the reward user ID to the user terminal 100 after the change through a predetermined procedure. It becomes possible to do.

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

Further, the CP reward process may be executed based on the installation of the customer destination application 20 as in the normal reward process. In this case, the reward granting condition in the customer destination application 20 may be that the customer destination application 20 is installed in the user terminal 100.
In addition, if all the specific applications that execute the campaign have the customer application 20 installed as the first achievement point, the customer application 20 of the reward grant notification information corresponding to the achievement of the achievement point is provided. You do not have to send from. In this case, the management server 200 performs a reward granting process similar to a normal reward, and transmits reward reward information including a campaign ID to the application server 310, so that the CP corresponding to the normal reward is transmitted from the application server 310. Rewards will be rewarded. Specifically, the processing of steps SE23 to 24 may be performed for both CP reward and normal reward without performing the determination processing of step SE22 in the flowchart of FIG.

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

  Further, the storage unit 230 of the management server 200 may be provided in a server device different from the management server 200. Then, the management unit 220 or the control unit 240 of the management server 200 communicates with the storage unit 230 provided in a server device different from the management server 200 via the network NW, so that each unit included in the storage unit 230 stores. Each piece of information may be managed.

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

  In the above embodiment, the SDK 1011 (2011, 3011) has been described as including 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, and the list request unit 109 The unit 104 may function as the list acquisition unit 109. Further, the SDK 1011 (2011, 3011) has been described with respect to the case where the installation notification unit 103 and the temporary installation notification unit 108 are provided as different configurations. However, the installation notification unit 103 includes the temporary installation notification unit 108, and the installation notification unit 103 includes The temporary installation notification unit 108 may be configured.

  In the third and fourth embodiments, the case where the non-installation information acquisition unit 111 of the SDK 1011A transmits the non-installation 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 not-install 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 target applications other than the application ID of the target application from the target application information stored in the target application information storage unit 231, and extracts the target The application ID (ApID) and URL scheme (ApURI) corresponding to the application may be transmitted to the user terminal 100 as non-installed information.

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

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

  1, 1a, 1b, 1c, 1d network system, 10 customer 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 application, 30 store, 60 Dedicated application, 100 User terminal, 101 Initialization processing unit, 102 Unique identification information acquisition unit, 103 Installation notification section, 104 list request section, 105 display control section, 106 customer information notification section, 107 reward grant notification section, 108 temporary installation notification section, 109 list acquisition section, 110 input section, 111 uninstalled information acquisition section, 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-app filter storage unit, 234 Campaign information storage unit, 235 Campaign participation application information storage unit, 236 Installation information storage unit, 237 Customer information storage unit, 238 Reward establishment information storage 240, 240a, 240b, 240c, 240d control unit, 241 installation notification acquisition unit, 242 list notification unit, 243 customer information acquisition unit, 244 installation guidance instruction unit, 245 reward processing unit, 246 timing unit, 247 Temporary installation notification acquisition unit, 248 Uninstalled 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 system

Claims (9)

An application management unit that manages information related to the first period set for a plurality of specific applications among a plurality of target applications to be managed;
When any one of the plurality of target applications is executed by the terminal device, the first information transmitted from the terminal device is acquired in response to the target application being executed by the terminal device. A first information acquisition unit;
Second information including at least one target application that has not acquired the first information from the terminal device by receiving a request based on a first application executed by the terminal device among the plurality of target applications; A second information notification unit for transmitting information to the terminal device;
In response to the transmission of the second information, the first period is set for the second application among the target applications indicated by the second information transmitted from the second information notification unit. In the case, the reward application processing is performed based on the second application being executed by the terminal device within the first period or being in an executable state, and the second application is processed with respect to the second application. If the first period is not set, a reward processing unit that performs the reward granting process based on the second application being executed by the terminal device or being in an executable state;
A management apparatus comprising: The reward processing unit
If the first period is set for the second application, the second application has been executed by the terminal device within the first period or has become executable. The management apparatus according to claim 1, wherein a first reward giving process is performed as the reward giving process. The reward processing unit
If the first period is set for the second application, the second application has been executed by the terminal device within the first period or has become executable. The management device according to claim 1, wherein a first reward granting process is performed as the reward granting process on the basis that a reward granting condition set in the second application is satisfied. The reward processing unit
When the first application period is not set for the second application, the reward application process is performed when the second application is executed by the terminal device or is in an executable state. The management apparatus according to any one of claims 1 to 3, wherein a second reward granting process is performed. The reward processing unit
If the first period is not set for the second application, the second application has been executed by the terminal device or has become executable, and the second application The management device according to any one of claims 1 to 3, wherein a second reward granting process is performed as the reward granting process on the basis that a set reward granting condition is satisfied. The reward processing unit
Based on the fact that the reward granting condition set in the second application has been satisfied, reward grant notification information indicating that the reward granting condition has been satisfied, the second application executed by the terminal device or The management device according to claim 3 or 5, wherein, when acquired from a server device corresponding to the second application, the reward granting process based on the acquired reward grant notification information is performed. The reward processing unit
Even when the first period is set for the second application, when the second application is executed outside the first period or becomes executable, the second application The management apparatus according to claim 4, wherein the reward granting process is performed. A management method in a management device,
Managing information related to a first period set for a plurality of specific applications among a plurality of target applications to be managed;
When any one of the plurality of target applications is executed by the terminal device, the first information transmitted from the terminal device is acquired in response to the target application being executed by the terminal device. Steps,
Second information including at least one target application that has not acquired the first information from the terminal device by receiving a request based on a first application executed by the terminal device among the plurality of target applications; Transmitting information to the terminal device;
In response to transmitting the second information, when the first period is set for the second application among the target applications indicated by the transmitted second information, the second information A reward granting process is performed based on the application being executed by the terminal device within the first period or being in an executable state, and the first period is set for the second application. If not, performing the reward granting process based on the second application being executed by the terminal device or being in an executable state;
The management method characterized by including. On the computer,
Managing information related to a first period set for a plurality of specific applications among a plurality of target applications to be managed;
When any one of the plurality of target applications is executed by the terminal device, the first information transmitted from the terminal device is acquired in response to the target application being executed by the terminal device. Steps,
Second information including at least one target application that has not acquired the first information from the terminal device by receiving a request based on a first application executed by the terminal device among the plurality of target applications; Transmitting information to the terminal device;
In response to transmitting the second information, when the first period is set for the second application among the target applications indicated by the transmitted second information, the second information A reward granting process is performed based on the application being executed by the terminal device within the first period or being in an executable state, and the first period is set for the second application. If not, performing the reward granting process based on the second application being executed by the terminal device or being in an executable state;
A program for running

Images