JP2015036955A - Terminal device, control method, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a customer guidance to an application (that is, an application before provision) scheduled to be released which is not yet released.SOLUTION: A terminal device can communicate with a management device which manages information regarding an application before provision which is the application before provision among a plurality of object applications and manages identification information of a selection application selected in the terminal device among the applications before provision in association with unique identification information specifying the terminal device as a record of customer guidance information. The terminal device includes: a list acquisition part for acquiring an application list of at least one application before provision from the management device; and customer guidance information notification part for transmitting customer guidance information including the identification information of the selection application selected from at least one application before provision included in the acquired application list to the management device in association with the unique identification information for specifying own terminal device.

Description

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

  Unlike applications provided for SNS (Social Networking Service) members (for example, games, etc.), the application is used for an independently operated application that can be downloaded from a store site that sells the application. It is necessary to attract users from scratch. Therefore, every time a new application is sold (released), it is necessary to carry out promotional activities such as advertising for attracting customers.

  For example, for the purpose of attracting customers to a new application, there is a method of displaying an advertisement of an application that has not yet been installed on a display screen that is displayed while using an application that has been installed on a user terminal (for example, Patent Documents). 1).

Japanese Patent No. 5107455

  If the method as described above is used, for example, by displaying an advertisement of an application that the user wants to use on the user terminal, it is possible to connect the customer to the application. However, it has sometimes been difficult to enable customers to be released to an application that is yet to be released (ie, an application before the start of provision).

  The present invention has been made in view of such circumstances, and an object of the present invention is to make it possible to send customers to an application to be released that has not yet been released (that is, an application before the start of provision).

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

  In order to solve the above-described problem, according to one aspect of the present invention, information on a pre-providing application that is an application before starting provision is managed among a plurality of target applications to be managed, and the pre-providing application The management device (200a) that manages the identification information of the selected application selected in the terminal device (100) from among the information and the unique identification information that identifies the terminal device as a record of customer information for the pre-providing application A list acquisition unit (104) that acquires at least one application list of the application before starting provision from the management device, and is included in the application list acquired by the list acquisition unit At least one of the provided openings A customer information notifying unit (106) that transmits the customer information including the identification information of the selected application selected from the previous applications to the management device in association with the unique identification information that identifies the terminal device. And a terminal device.

  Further, according to one aspect of the present invention, the terminal device includes a presentation unit (105) that presents a presentation list based on an application list of the pre-providing application acquired by the list acquisition unit, and the list acquisition unit The application list is acquired from the management device, and each of the pre-providing applications included in the application list has been selected in the terminal device based on the record of the customer information managed by the management device. Information indicating whether or not there is obtained from the management device, and when the presentation unit presents the presentation list, based on the information indicating whether or not the selection acquired by the list acquisition unit, The pre-providing application that has been selected in the terminal device and the pre-providing application that has not been selected It characterized in that it presented to distinguish between Shon.

  According to another aspect of the present invention, the terminal device presents an application information acquisition unit (41) that acquires information on the selected application from the management device, and information on the selected application acquired by the application information acquisition unit. And an information presentation unit (42).

  Further, according to one aspect of the present invention, in the terminal device, the information on the selected application is information indicating that the selection application has started to be provided.

  Further, according to an aspect of the present invention, the management apparatus is configured so that the terminal apparatus associates list request notification information for requesting an application list of at least one application before starting provision with the unique identification information for identifying the terminal apparatus. A list request unit (104) that transmits to the application, and the list acquisition unit transmits the list request notification information transmitted from the management device in response to the list request unit transmitting the list request notification information. The application list is acquired.

  Further, according to one aspect of the present invention, in the terminal device, the list request unit transmits the list request notification information to the management device from a target application running on the terminal device, and acquires the list. The application acquires the application list of the application before the provision start in the target application that transmitted the list request notification information, and the customer information notification unit identifies the target application that acquired the application list of the application before the provision start Unique identification that identifies the terminal device with the customer information including information and identification information of the selected application selected from at least one pre-provision application included in the application list in the target application Associated with information And transmitting relative serial management device.

  According to another aspect of the present invention, when the terminal device determines whether or not the unique identification information is stored in a storage unit, and determines that the unique identification information is not stored in the storage unit. A unique identification information acquisition unit (102) that acquires the unique identification information and stores the acquired unique identification information in the storage unit (140) so that it can be referred to by any target application installed in the terminal device. It is characterized by providing.

  Moreover, one aspect of the present invention is installation notification information indicating that the terminal device has been installed in the target application installed in the terminal device, and the installation notification information including identification information of the target application And an installation notification unit (103) that transmits the information to the management apparatus in association with the unique identification information that identifies the terminal apparatus.

  Further, according to one aspect of the present invention, in the terminal device, the installation notification unit includes user information on the installed target application of a user who installed the installed target application, and identification information of the target application. The installation notification information that is included is transmitted to the management apparatus in association with unique identification information that identifies the terminal apparatus.

  Further, according to one aspect of the present invention, in the terminal device, the management device manages a reception period indicating a period in which the terminal device receives a selection for the application before starting provision, and the customer information notification unit The customer information is transmitted to the management device within the reception period.

  Further, according to one aspect of the present invention, the terminal device transmits the application list or the customer information to the management device via a server device corresponding to a target application or the selected application installed in the terminal device. A transmission / reception unit (130) that communicates with or directly communicates with the management apparatus is provided.

  Further, according to one aspect of the present invention, in the terminal device, the transmission / reception unit directly establishes a communication session with the installed target application or the selection application via a corresponding server device. It is characterized by communicating with the management device.

  In addition, according to one aspect of the present invention, information on a pre-providing application that is an application before the start of provisioning among a plurality of target applications to be managed is managed, and selected from the pre-provisioning application at the terminal device A terminal device control method capable of communicating with a management device that associates identification information of a selected application and unique identification information for identifying the terminal device, and manages it as a record of customer information for the pre-providing application. Acquiring an application list of at least one application before starting provision from the management device; and selecting the selected application selected from at least one application before starting provision included in the acquired application list The customer guiding information including another information, a control method which comprises the steps of: transmitting to said management apparatus in association with the unique identification information for identifying the own terminal device.

  In addition, according to one aspect of the present invention, information on a pre-providing application that is an application before the start of provisioning among a plurality of target applications to be managed is managed, and selected from the pre-provisioning application at the terminal device A computer provided in a terminal device capable of communicating with a management device that associates identification information of the selected application and unique identification information that identifies the terminal device, and manages it as a record of customer information for the application before starting provision, Acquiring an application list of at least one application before starting provision from the management device; and selecting the selected application selected from at least one application before starting provision included in the acquired application list The customer guiding information for including the identification information, a program for executing the steps of: transmitting to said unique identification information in association with the management device identifying the own terminal device.

  In addition, according to one aspect of the present invention, information on a pre-providing application that is an application before the start of provisioning among a plurality of target applications to be managed is managed, and selected from the pre-provisioning application at the terminal device In an application installed in a terminal device that can communicate with a management device that associates the identification information of the selected application with the unique identification information that identifies the terminal device and manages it as a record of customer information for the application before the provision start A program of software to be embedded, wherein the computer acquires an application list of at least one pre-providing application from the management device; and at least included in the acquired application list Transmitting the customer information including the identification information of the selected application selected from the one application before the provision start to the management apparatus in association with the unique identification information for identifying the terminal apparatus; , Is a program for executing.

  As described above, according to the present invention, it is possible to send customers to an application to be released that has not yet been released (that is, an application before the start of provision).

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 explanatory drawing explaining an example of a structure and process of the mutual customer-delivery system by 3rd Embodiment. It is an example of the display screen of the application list by 3rd Embodiment. It is a block diagram which shows an example of the function structure of the process performed based on the resident application of a user terminal. 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 a release schedule application information storage part. It is a figure which shows an example of the customer information memorize | stored in the customer information storage part by 3rd Embodiment. It is a 1st flowchart which shows an example of operation | movement of the mutual customer-delivery process by 3rd Embodiment. It is a 2nd flowchart which shows an example of operation | movement of the mutual customer-delivery process by 3rd Embodiment. It is a 3rd flowchart which shows an example of operation | movement of the mutual customer transmission process by 3rd Embodiment. It is explanatory drawing explaining an example of a structure and process of a mutual customer-delivery system by 4th Embodiment. It is a block diagram which shows an example of a function structure of the customer-transmission process performed based on the exclusive application of a user terminal. It is a 1st flowchart which shows an example of operation | movement of the mutual customer transmission process by 4th Embodiment. It is a 2nd flowchart which shows an example of operation | movement of the mutual customer-delivery process by 4th Embodiment. It is a flowchart explaining the operation | movement of the establishment process of a communication session.

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

[Outline of mutual customer service system]
First, an outline of the mutual customer sending system according to the present embodiment will be described. This mutual customer-delivery system is based on an application that has not been installed on the user terminal (hereinafter referred to as “send-source application”) from an original application that is already installed and used on the user terminal (hereinafter also referred to as “customer-source 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, an object is to provide a mutual customer delivery system capable of mutual customer delivery even between applications managed by the same user or different user information. Even if the information is different, it is configured so that mutual customers between applications can be easily performed.
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 (application list) LT of 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 “application C” or “application D” is selected as the customer destination application, when the selected “application C” or “application D” is installed, the “application A” that is the customer source Usually, a reward is performed. On the other hand, when “App B” is selected as the customer destination application, after “App B” is activated on the condition that “App B” is installed in the user terminal during the campaign period, the campaign When the achievement point set in advance corresponding to is achieved (reward granting condition is satisfied), CP reward is performed for “application A” as a customer source. For example, a reward granting period is set that starts at the beginning or middle of the campaign period and ends after the end of the campaign period. If the achievement point is achieved within this reward granting period, a CP reward is issued. After the reward grant period, CP reward will not be given even if the achievement point is achieved. When a plurality of achievement points are set, CP reward is performed 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.

  Further, even when users of a plurality of applications installed on the user terminal are the same user, user information registered for each application (for example, a user ID that is identification information for uniquely identifying a user) is different. There is. 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”.

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 guided to the above-mentioned store site, and when the selected application is downloaded and installed in the user terminal 100, the original application in which the advertisement (banner) that triggered the download is displayed. It is conceivable to provide a service in which a reward is granted for the use of the user. 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 random access memory (RAM), a read only memory (ROM), a flash ROM, and a hard disk drive (HDD), or a combination thereof. A control program (for example, an OS (Operating System) for causing the terminal control unit 150 to perform a basic operation), an installed application program, various information, and the like are stored.

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

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

[Configuration and processing of mutual 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) is installed in the user terminal 100 used by the user X, and the customer-destination application is based on the operation of the user X in the installed customer-source application 10 (game A). An example in which a reward (reward) is given to the user X in the customer source application 10 (game A) when 20 (game B) is installed in the user terminal 100 and usage is started 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. Further, in the case of an application that supports only the customer destination application 20, if it is limited to only normal rewards, there is no need to provide an application server corresponding to the application. The application can be the target of an application corresponding to the mutual customer system.

  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. Further, 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 installation notification information includes at least 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 11A) requests a list requesting an application list (a list of target applications that are candidates for the customer destination application 20) of at least one target application of the target application corresponding to the mutual customer sending system 500. The 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 the acquired application list LT on the display unit 120.

(5) When any target application is selected by the user X from the application list displayed on the display unit 120, the user terminal 100 (SDK 11A) is selected from the customer-source application 10 (game A). The customer information indicating that the customer has been sent to the target application (here, the customer destination application 20 (game B)) is transmitted to the management server 200 (REQ13). Here, the customer information includes at least the application ID of the customer application 10 (game A), the application ID of the customer application 20 (game B), and the 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 at least 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 the application list LT is displayed on the display screen of the user terminal 100, the link destination of the site where the reward content by the CP reward is posted is displayed without displaying the reward content by the CP reward on the display screen. This is because the management server 200 is not involved in the reward contents.

  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 a 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. It is executed when each application is installed.

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 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. .
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 the application list acquired by the list request unit 104. For example, the display control unit 105 displays the application list 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).
Further, the above-mentioned customer information includes the application ID of the customer source application 10 (customer source information), the selected target application (or specific application), that is, the application ID of the customer destination application 20, and the user terminal 100. The reward user ID corresponding to is included.

  For example, when a specific application during the campaign period is selected from the application list based on the second operation described above during the campaign period, the customer information notifying unit 106 selects the application of the customer source application 10. Customer information including the ID (customer information), the selected specific application), that is, the application ID of the customer application 20, and the reward user ID corresponding to the user terminal 100 is transmitted to the management server 200.

  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 reward grant notification information described above includes the application ID (customer destination information) of the specific application (customer destination application 20) during the campaign period and the reward user ID corresponding to the user terminal 100. It is.

[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. Such target application information is used in the application list LT of the target application 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 the application list LT of the target application 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. In the installation information, a reward user ID (RewardUID), an application ID (ApID), and an application user ID (ApUID) included in the acquired installation notification information are associated.

  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, 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). The customer information 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.

  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 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 application list including the link destination of the posting location) 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 data of an application list page in which the application list described in an 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 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 SA15.

  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 on 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, a predetermined operation on the input unit 110 for the user X to acquire a list of target applications that can be installed in the user terminal 100 with respect to the customer source application 10 (game A) running on the user terminal 100. It is assumed that (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 (list 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.

  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 list request notification is a condition (filter information) stored in the inter-application filter storage unit 233. It can also be performed based on. This filtering process will be described in the second embodiment.

  Next, the list notification unit 242 generates application list page data that the application list of the extracted target application can display on the user terminal 100 (step SE16), and includes information indicating the link destination of the generated application list page. The redirect instruction information is transmitted to the user terminal 100 and redirected to the application list page (RES12, step SE17). When there is no target application (specific application) that is not installed in the user terminal 100, an application list page is generated in which the target application (specific application) does not exist instead of the application list.

When the user terminal 100 (SDK 11A) acquires redirect instruction information including information indicating the link destination of 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. Thereby, the application list LT of the 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 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). The customer information indicating that the customer has been sent to the selected target application (here, the customer destination application 20 (game B)) is transmitted to the 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 a terminal device) is installed, and includes an application ID (an example of identification information) of the specific application, 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 a terminal device) among a plurality of target applications, the user terminal 100 acquires a reward user ID and acquires the reward user A unique identification information acquisition unit 102 that stores an ID in a terminal storage unit 140 (an example of a storage unit) so that the ID can be referenced from any target application installed in the user terminal 100 is provided.

  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 also common to the target application to be installed thereafter. In order to make it possible to use the system, the reward user ID can be acquired without causing 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 a terminal device), and the application ID of the installed target application And installation notification information including 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 application list acquired from the management server 200 on the display unit 120, information regarding the campaign (such as the name and description of the campaign, the campaign period, etc.) is included in the specific application for which the campaign is set. ) 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.

  Accordingly, when the user terminal 100 displays the application list acquired from the management server 200 on the display unit 120, the link destination of the information posting location indicating the CP reward of the campaign is displayed for the specific application for which the campaign is set. 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.

  As a result, when the user terminal 100 displays the application list acquired from the management server 200 on the display unit 120, the user terminal 100 displays information indicating normal reward for the target application for which no campaign is set, and the campaign is set. The specific application can be displayed in association with information indicating the link destination of the information posting location indicating the CP reward (an example of reward) of the campaign.

(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 different 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. That is, the customer destination application 20 for which the CP reward has been performed is not a target for 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 has been 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 for which the normal reward has been performed is not subject to the CP reward. Further, the customer destination application 20 for which the CP reward has been performed is not a target of the normal 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, characteristic processing 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 restricting the target applications that can be sent to each other is set as, for example, posting prohibition information that prohibits posting in an application list that can be selected as the customer destination application 20.

  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 application ID (ApIDfrom) to be blocked, the application ID of the setting side application that sets prohibition of publication in the application list is set. On the other hand, the blocked application ID (ApIDto) is set with the application ID of the set-side application that is prohibited from being listed in the application list of the setting-side application. 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, the target application is not listed in the application list (list of target applications corresponding to the mutual customer sending system 500) for customers from any target application outside the campaign period. 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 posting in the application list, and the target application that is prohibited from posting the setting-side application in the application list. The inter-app filter information (an example of the first posting prohibition information) that is combined with the setting-side application 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 uses the inter-application filter information (an example of second posting prohibition information) in which only the set-side application that is prohibited from being listed in the application list is registered. It is stored in the storage unit 233 and managed.
Then, the list notification unit 242 of the management server 200 refers to the inter-application filter information managed by the application management unit 221 and the set-side application indicated by the inter-application filter information is the customer-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.

  Thereby, in the case of a target application that only wants to participate in the mutual customer sending system 500, it is possible to prevent a customer from any target application from appearing in the application list outside the campaign period.

<Third Embodiment>
Next, a third embodiment of the present invention will be described. In the first and second embodiments, the mutual customer process for sending a user from the customer source application 10 installed in the user terminal 100 to the customer destination application 20 not installed in the user terminal 100 is performed. An example in which the customer application 20 is a target application released at the time of customer transmission has been described. In the present embodiment, an example in which the customer destination application is a target application scheduled to be released and has not been released at the time of customer transmission will be described. Here, the target application scheduled to be released refers to a target application that is scheduled to be provided to the user and has not yet been released, that is, a target application before the start of provision.

  When sending a customer to a target application to be released, this target application is not released at the time of customer delivery, and therefore cannot be guided to an installation destination (download destination). In addition, in the case of a target application scheduled to be released, the target application may be under development and a reward granting method may not be determined. Therefore, in this embodiment, customer information to be sent to a target application scheduled to be released is managed, and when the target application is installed in the user terminal 100 after release, it is based on the managed customer information. So that rewards are granted.

[Configuration and Processing of Mutual Customer Transmission System According to Third Embodiment]
FIG. 17 is an explanatory diagram illustrating an example of the configuration and processing of the mutual customer sending system 500a in the network system 1a of the present embodiment. In FIG. 17, parts corresponding to those in FIG. 4 are assigned the same reference numerals and explanations thereof are omitted.

  In the example illustrated in FIG. 17, the customer source application 10 (game A) is installed in the user terminal 100 used by the user X, and based on the operation of the user X in the installed customer source application 10 (game A). The target application to be released is selected. The selected target application to be released will be described as a customer destination application 50 (game N). In the example shown in FIG. 17, when the selected customer destination application 50 (game N) is installed in the user terminal 100 after release, the user X in the customer destination application 50 (game N) Reward (reward).

  Here, since the released customer application 50 (game N) is a released target application, it can be the customer application 20 described in the first and second embodiments, and the user terminal 100. It can also be a customer-source application 10 after being installed on.

  Note that when the target application to be released is selected by the user X, the user X may be registered for the selected target application to be released. For example, the user X can select the target application to be registered from the target applications scheduled to be released in the customer source application 10 and register it in advance.

  The main configuration of the mutual customer sending system 500a of the present embodiment is a configuration provided with an SDK 11 (SDK 11A and SDK 11N in this figure) and a management server 200a. The SDK 11A is incorporated in the customer source application 10 (game A), and the SDK 11N is incorporated in the customer application 50 (game N). The SDK 11N has the same configuration as the SDK 11B shown in FIG. Note that the application corresponding to the mutual customer system 500a can be either the customer source application 10 or the customer destination application 50, as in the first and second embodiments. Therefore, both the SDK 11A and the SDK 11N are configured. The SDK 11 having the above is incorporated. The configuration of the SDK 11 is the same as the configuration shown in FIG.

  The management server 200a communicates with the SDK 11 incorporated in an application corresponding to the mutual customer system 500 installed in the user terminal 100, thereby executing the mutual customer process according to the present embodiment. In the present embodiment, the management server 200a manages the customer information from the customer source application 10 (game A) installed in the user terminal 100 to the customer destination application 50 (game N) scheduled to be released, and also releases the release information. When the customer destination application 50 (game N) is installed in the user terminal 100 later, information about the reward is transmitted to the application server 350 (game N) corresponding to the customer destination application 50 (game N). Thereby, in the application server 350 (game N), a reward is given to the user X in the customer destination application 50 (game N).

  Hereinafter, an outline flow of the mutual customer sending process according to the present embodiment will be described. Here, description of processing similar to the processing described using FIG. 4 is omitted as appropriate. The processes (1) and (2) are the same as those described with reference to FIG.

(3A) It differs from the process of (3) shown in FIG. 4 in that instead of requesting an application list of a target application that is not installed in the user terminal 100, an application list of a target application to be released is requested.
The user terminal 100 (SDK 11A) receives list request notification information for requesting an application list (list of target applications that are candidates for the customer destination application 50) of at least one target application scheduled to be released corresponding to the mutual customer sending system 500a. It transmits to the management server 200a (REQ12A).

(4A) Upon acquiring the list request notification information from the user terminal 100 (SDK11A), the management server 200a transmits an application list of at least one target application scheduled to be released to the user terminal 100 (SDK11A) (RES12A). When the user terminal 100 (SDK 11A) acquires the application list from the management server 200a, the user terminal 100 (SDK 11A) displays the acquired application list on the display unit 120. For example, the application list displayed on the display unit 120 includes information related to a reward given by selecting a target application to be released included in the application list.

(5A) When any target application scheduled to be released is selected from the application list displayed on the display unit 120 by the user X, the user terminal 100 (SDK 11A) Then, customer information indicating that the customer has been sent to the customer destination application 50 (game N)) is transmitted from the customer source application 10 (game A) to the management server 200a (REQ13A). Here, the customer information includes at least the application ID of the customer application 50 (game N) and the reward user ID.

(5B) When the customer destination application 50 (game N) is released, the management server 200a transmits release information indicating that it has been released to the user terminal 100. For example, the resident application 40 that is an application that is resident and operates in the user terminal 100 acquires the above-described release information from the management server 200a by push notification. Then, the user terminal 100 displays the acquired release information on the display unit 120. For example, the user terminal 100 displays the above-described release information in an alert dialog pop-up displayed on the display screen displayed on the display unit 120 or a predetermined notification area (an area where notification information in various applications is displayed) in the display screen. Is displayed. For example, the release information includes information indicating a link destination of a page on which an introduction screen of the customer destination application 50 (game N) is displayed.

(5C) When the user X operates the release information displayed on the user terminal 100 (for example, taps information indicating a link destination), the browser 45 that is a browser application installed in the user terminal 100 is activated. Then, an introduction screen of the released customer destination application 50 (game N), which is the link destination page described above, is displayed on the user terminal 100.
In addition, on the introduction screen of the customer destination application 50 (game N), display information indicating that a reward cannot be obtained unless it is installed within a predetermined period, and the customer destination application 50 (game N) can be installed (downloaded). A link button to the app store 400 is displayed.

(6A) On the introduction screen displayed on the user terminal 100, when the user X operates (for example, tap operation) on the link button to the app store 400, the customer destination application 50 (game N) can be installed (download) The store 30 that is an application for displaying the store page of the app store 400 is activated. The store 30 acquires a store page from which the customer destination application 50 (game N) can be installed from the app store 400 and displays the store page on the display unit 120.

The subsequent processes (7), (8), and (9) are the same as the processes described with reference to FIG.
(7) After the customer destination application 50 (game N) is downloaded and installed in the user terminal 100 by the operation of the user X, the customer destination application 50 (game N) installed by the operation of the user X is subsequently activated. Is done.
(8) The user terminal 100 (SDK11N) transmits installation notification information indicating that the customer destination application 50 (game N) is installed to the management server 200a (REQ14).
(9) When the management server 200a acquires the installation notification information transmitted from the user terminal 100 (SDK11N), the management server 200a transmits response information indicating the acquisition to the user terminal 100 (SDK11N) (RES14).

  Further, the management server 200a determines that the customer destination application 50 (game N) releases the customer destination application 50 (game N) on the basis of the acquired installation notification information and the managed customer information. Before, it determines with the customer terminal 100 (game A) having been sent by the user terminal 100.

(11A) The management server 200a installs the customer destination application 50 (game N) sent from the customer source application 10 (game A) before release into the user terminal 100, so that the customer destination application 50 In (Game N), reward grant information indicating that a reward is granted to the user X is transmitted to the application server 350 (Game N) corresponding to the customer destination application 50 (Game N).

  Through such a processing flow, the customer is sent from the customer source application 10 (game A) to the customer destination application 50 (game N) which is the target application scheduled to be released. Here, the management server 200a manages customer information including the application ID of the customer application 50 (game N) to be released and the reward user ID. Thereby, not only the application user ID of the user X in the customer destination application 50 (game N) is not set, but also the installation destination of the customer destination application 50 (game N) and the reward giving method are not determined. Even so, the reward process can be performed after the release of the customer application 50 (game N) based on the customer information. Therefore, the motivation for the user X to use the target application can be enhanced before the release of the target application.

  FIG. 18 is an example of an application list display screen displayed on the user terminal 100 according to the present embodiment. In the application list display screen shown in this figure, the target application to be released (the target application to be released that can be selected), the target application that has been selected among the target applications that are to be released, and the target application that has been paid Tabs TB21, TB22, and TB23 having a function as an operator for switching and displaying each application list are displayed side by side.

  Here, a state is shown in which a tab TB21 (a tab displayed as “to be released”) on which an application list LT2 of selectable target applications to be released is displayed is selected. When the tab TB22 (tab displayed as “selected”) is selected (for example, a tap operation), an application list of the selected target applications among the target applications scheduled to be released is displayed. Further, when the tab TB23 (a tab displayed as “reward acquired”) is selected (for example, a tap operation), a reward acquired target for which a user has acquired a reward given when a customer is established The application list for the application is displayed.

  In the application list LT2, labels L21 and L22 on which information related to the target application to be released are displayed are displayed side by side as selectable operators. For example, the label L21 includes “application name” (here, “game N”) of the target application to be released and information indicating “selectable period” that is a selectable period (here, “○ month × Day to Δ days ”) and information (here,“ item A ”) indicating“ reward ”given when the customer is established. Further, the label L22 includes “application name” (here, “game Q”) of the target application scheduled to be released and information indicating “selectable period” which is a selectable period (here, “○ month × Day to Δ day ”) and information (here,“ item B ”) indicating“ reward ”given when the customer is established are displayed. Here, the time when the customer is established is, for example, when the selected target application to be released is installed and activated in the user terminal 100 after the release.

  In the application list LT2, the above-mentioned label corresponding to the number of target applications scheduled to be released is displayed, and when there is no selectable target application to be released, a message (for example, a message to that effect) , "No applications can be selected").

  Note that the selectable target application to be released may be, for example, a target application that can be registered in advance before release. The selectable period may be a period in which registration is received in advance for the target application scheduled to be released. Moreover, the reward given when a customer is established may be a reward given on the condition that it is installed and activated as a registration privilege.

Thus, since the user terminal 100 (SDK 11A) displays the application list LT2 of selectable target applications to be released, the user terminal 100 (SDK11A) can easily select the target application to be released to the user. . Moreover, since the information of the reward given by selecting before a release is displayed on the application list LT2, the grant of a reward can be motivated by the user who selects the target application to be released.
Further, the user terminal 100 (SDK 11A) can distinguish and display a selectable target application to be released, a selected target application, and a target application that has been rewarded. Thereby, the user can easily confirm the selection status and the reward acquisition status for the target application scheduled to be released.

[Functional configuration of user terminal 100 (SDK 11) of the third embodiment]
In the user terminal 100 according to the present embodiment, the functional configuration of the mutual customer transmission process executed by the terminal control unit 150 based on the SDK 11 is the same as the configuration shown in FIG. To do.

The list request unit 104 according to the present embodiment transmits list request notification information for requesting an application list of at least one target application scheduled to be released to the management server 200a based on a predetermined operation in the customer source application 10. . Here, the list request notification information includes information associated with a reward user ID that identifies the user terminal 100 that has transmitted the list request notification information.
Further, the list request unit 104 has a function of a list acquisition unit, and receives an application list of at least one target application scheduled to be released transmitted from the management server 200a in response to the transmission of the list request notification information. get.

  It should be noted that the list request unit 104 selects one or both of an application list of at least one target application (or a specific application) of a plurality of target applications and an application list of at least one target application scheduled to be released. The requested list request notification information may be transmitted to the management server 200a. Then, the list requesting unit 104 obtains an application list of one or both of an application list of at least one target application (or a specific application) of the plurality of target applications and an application list of at least one target application scheduled to be released. You may get it.

  Further, the list request unit 104 acquires an application list from the management server 200a, and manages information indicating whether or not each target application to be released included in the application list has been selected in the user terminal 100. Obtained from the server 200a. Here, whether or not each of the target applications scheduled to be released has been selected in the user terminal 100 is determined by whether the application ID of the target application scheduled to be released is associated with a reward user ID that identifies the user terminal 100 It is determined based on whether or not information recording is managed in the management server 200a. In addition, the list request | requirement part 104 may acquire the information which can distinguish the target application which has acquired the reward after the release among the target applications scheduled to be released.

  The display control unit 105 causes the display unit 120 to display the application list of at least one target application to be released acquired by the list request unit 104. For example, when the display control unit 105 displays the application list of the target application to be released on the display unit 120, the display control unit 105 uses the information obtained by the list request unit 104 and indicating whether or not the above selection has been made. In the terminal 100, the target application that has been selected for release and the target application that has not been selected for release are displayed separately. Note that the display control unit 105 may distinguish and display target applications for which rewards have been acquired after release from among the target applications scheduled to be released.

  For example, the display control unit 105 displays an application list page that displays an application list in which an unselected release target application, a selected release target application, and a rewarded target application are displayed. When the list request unit 104 acquires the link destination information from the management server 200a, the acquired application list page is displayed on the display unit 120 by executing the browser function (see, for example, FIG. 18).

  The customer information notification unit 106 transmits customer information indicating that the customer has been sent to the target application (customer application 50) to be released to the management server 200a. For example, the customer information notifying unit 106 includes the application ID of the customer destination application 50 selected from at least one target application to be released included in the application list acquired by the list request unit 104, and the user terminal 100. The customer information including the reward user ID for identifying the user is transmitted to the management server 200a.

The customer information notifying unit 106 may transmit customer information indicating that the customer is sent from the customer source application 10 to the customer destination application 50 to the management server 200a.
For example, the list request unit 104 transmits list request notification information from the target application running on the user terminal 100 to the management server 200a. Here, the target application operating on the user terminal 100 is, for example, the customer source application 10. Then, the list request unit 104 acquires the application list of the target application scheduled to be released in the customer source application 10 that has transmitted the list request notification information. Further, the customer information notifying unit 106 acquires the application ID of the customer source application 10 that acquired the application list of the target application scheduled to be released, and at least one release schedule included in the application list in the customer source application 10. The customer information including the application ID of the customer destination application 50 selected from the target application and the reward user ID that identifies the user terminal 100 is transmitted to the management server 200a.

[Functional configuration of resident application 40]
Next, with reference to FIG. 19, a functional configuration of processing executed by the terminal control unit 150 based on the resident application 40 in the user terminal 100 will be described. FIG. 19 is a configuration diagram illustrating an example of a functional configuration of processing executed based on the resident application 40. The resident application 40 is a resident application that is activated and executed regardless of the execution state of the target application when the OS is activated in the user terminal 100. The resident application 40 includes an application information acquisition unit 41 and an information presentation unit 42.

  The application information acquisition unit 41 acquires information related to the application from the management server 200a. For example, when the customer application 50 (game N) is released, the application information acquisition unit 41 acquires release information indicating that the customer application 50 (game N) has been released from the management server 200a as information related to the application. For example, the application information acquisition unit 41 acquires the release information described above from the management server 200a by push notification.

  The information presentation unit 42 causes the display unit 120 to display information regarding the customer destination application 50 acquired by the application information acquisition unit 41. For example, the information presentation unit 42 releases the above-described release in an alert dialog pop-up displayed on the display screen displayed on the display unit 120 or a predetermined notification area (an area where notification information in various applications is displayed) in the display screen. Display information.

[Configuration of Management Server 200a of Third Embodiment]
Next, the configuration of the management server 200a 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. In FIG. 20, the same reference numerals are given to the components corresponding to the respective parts shown in FIG. 6, and description thereof will be omitted.

  The management server 200a according to the present embodiment includes a communication unit 210, a management unit 220, a storage unit 230a, and a control unit 240a. In the storage unit 230a, the data configuration of information stored in the target application information storage unit 231a and the customer information storage unit 237a is different from the data configuration of information stored in the target application information storage unit 231 and the customer information storage unit 237. And the point provided with the release schedule application information storage part 239 differs from the structure of the memory | storage part 230 of the management server 200 shown in FIG. Further, the control unit 240a is different from the configuration of the control unit 240 of the management server 200 shown in FIG. 6 in that an application information notification unit 247 is provided. Since the configuration of the other management server 200a is the same as the configuration of the management server 200 shown in FIG. 6, the characteristic processing and the above-described different configuration in this embodiment will be described.

The application management unit 221 stores and manages information related to a plurality of target applications to be managed and a target application to be released that is an application before the target application is started to be stored in the target application information storage unit 231a. That is, the target application information storage unit 231a stores information on the target application scheduled to be released as target application information in addition to the information on the released target application.
FIG. 21 is a diagram illustrating an example of target application information stored in the target application information storage unit 231a. In the target application information, a release information URL (ReleaseInfURL) and a release flag (FlagRelease) are further associated with the target application information shown in FIG.

  The release information URL (ReleaseInfURL) is a URL indicating the link destination of the information posting page related to the target application to be released. The URL of this posting page is, for example, the URL of a web page provided on the website of the developer or seller of the target application scheduled to be released. This posted page includes information displayed on an introduction screen for display on the user terminal 100 after the release of the target application to be released (after the start of provision). For example, this posting page includes a link button to the app store 400 on which the target application scheduled to be released can be installed (downloadable), display information that a reward cannot be obtained unless the application is installed within a predetermined period, and the like. include. The posted page may include information (for example, release date and more detailed description of the application) provided to the user before the release of the target application scheduled to be released (before the start of provision).

The release flag (FlagRelease) is flag information indicating whether or not the target application has been released. For example, a flag “0” indicates a target application that has not been released (that is, a target application scheduled to be released), and a flag “1” indicates a target application that has been released.
For example, when a target application scheduled to be released is registered in the target application information storage unit 231a, the flag “0” is set, and when the target application is released, the flag “1” is updated. When the target application is registered in the target application information storage unit 231a at the same time as the release, the flag “1” is set from the beginning at the time of registration.

  In the case of a target application scheduled to be released with the flag “0” set, the notification destination URL (NoticeURL) or the store URL (ApStoreURL) may be set to “null”. The URL of the notification destination of the reward and the URL of the page of the sales site (application store 400) may be set for each.

  The target application information storage unit 231a may store information related to the target application scheduled to be released separately from information related to the target application being released. In this case, the target application information storage unit 231a includes, for example, an application ID (ApID) of the target application scheduled to be released, an application name (ApNAME) indicating the name of the target application, You may memorize | store the information which linked | related the application description (ApDOC) which is the description information regarding a target application, the application icon image (ApICO) which is an icon image which shows the said target application, and an application price (ApPRICE). Then, when the target application scheduled to be released is released, it may be registered in the information regarding the released target application.

  In addition, the application management unit 221 receives, as information about a reward for each target application scheduled to be released, a reception period indicating a period (that is, a selectable period) in which the user terminal 100 receives selection for the target application scheduled to be released, or at least ends. The remuneration grant period in which the date and time is defined is stored in the release scheduled application information storage unit 239 for management. That is, the release scheduled application information storage unit 239 stores information related to the reward for each target application scheduled to be released.

FIG. 22 is a diagram illustrating an example of information stored in the release-scheduled application information storage unit 239. This information includes application ID (ApID), reception start date and time (RcpStartDATE), reception end date and time (RcpEndDATE), reward grant start date and time (RewardStartDATE), reward grant end date and time (RewardEndDATE), and the contents of the reward It is associated with the information shown. Information indicating the contents of the reward includes an item ID (ItemID) for identifying an item to be given as a reward in the target application scheduled to be released, a reward item name (ItemName) indicating the name of the item, and a reward for the item The number of reward items (ItemNum) indicating the number to be granted is included.
The application ID (ApID) is the application ID of the target application scheduled to be released. The reception start date / time (RcpStartDATE) and the reception end date / time (RcpEndDATE) are respectively the start date / time and end date / time of the period for receiving selection for the target application to be released (ie, selectable period) in the user terminal 100. Each is shown. In addition, each of the reward grant start date (RewardStartDATE) and reward grant end date (RewardEndDATE) is the user who selected the target application to be released (for example, the user who registered in advance), and the target application was released Later, it shows the start date and time and end date and time of the reward granting period that stipulates if the reward will be granted if it is installed before.

  The start date / time of the reward grant period is normally the release date / time of the target application (date / time when installation is possible). Therefore, the reward grant time limit may be set only by at least the reward grant end date (RewardEndDATE) of the reward grant start date (RewardStartDATE) and the reward grant end date (RewardEndDATE). For example, the reward grant end date and time is set one week or one month after the release date and time of the target application. Moreover, it is good also as a structure which does not provide a reward provision time limit.

  The customer information management unit 223 recognizes the application ID of the customer destination application 50 and the user terminal 100 selected in the user terminal 100 from at least one target application to be released included in the application list. In association with the ID, it is managed as a record of customer information indicating that a user who uses the user terminal 100 has been sent to the customer destination application 50. That is, the customer information storage unit 237a stores, in addition to the customer information to the released target application, the record of the customer information to the target application scheduled to be released.

  FIG. 23 is a diagram illustrating an example of customer information stored in the customer information storage unit 237a. In the customer information, an information type flag (FlagInf) is further associated with the customer information shown in FIG. The information type flag (FlagInf) is flag information indicating whether the information is customer information indicating a customer to be released to the target application or customer information indicating a customer to be released to the target application. It is. For example, the flag “0” is set in the information type flag (FlagInf) in the case of customer information indicating the customer to be released to the target application, and the customer to the target application scheduled to be released is set. In the case of the customer information shown, the flag “1” is set.

  Here, in the case of customer information indicating customer delivery to the target application scheduled to be released, since the customer is not a customer during the campaign period, “null” is set as the campaign ID (CpID). In addition, when a customer to a target application scheduled to be released is established, if the target application (that is, the customer destination application 50) is rewarded, it is not necessary to specify the customer source application 10, “Null” is set in the customer application ID (ApIDfrom). That is, the customer information storage unit 237a stores, for example, customer information associated with the word user ID and the application ID of the customer application 50 as customer information to the target application to be released.

  The customer information storage unit 237a associates a reward user ID, an application ID of the customer source application 10, and an application ID of the customer destination application 50 as customer information to the target application to be released. The customer information may be stored.

Returning to FIG. 20, the configuration of the control unit 240a will be described.
The list notification unit 242 transmits an application list of at least one target application scheduled to be released to the user terminal 100. For example, the list notification unit 242 transmits an application list to the user terminal 100 based on a request from a target application installed in the user terminal 100 among a plurality of target applications.
Specifically, the list notification unit 242 receives an application list of at least one target application to be released, which is transmitted from the customer source application 10 (SDK 11A of the customer source application 10) installed in the user terminal 100. When the requested list request notification information is acquired, the application list of at least one target application scheduled to be released is transmitted to the user terminal 100 with reference to the target application information storage unit 231a based on the acquired list request notification information. To do.

  Note that the list notification unit 242 refers to the customer information storage unit 237a, and indicates the release target application included in the customer information acquired and stored from the user terminal 100 that transmits the application list ( That is, information indicating a target application scheduled to be released that has been selected in the user terminal 100 may be transmitted to the user terminal 100. Further, the list notification unit 242 refers to the customer information storage unit 237a and the reward establishment information storage unit 238, and sends information indicating the target application included in the customer information for which the reward grant information has been notified to the user terminal 100. You may send it.

  At this time, the list notification unit 242 is an application including information (application name, description, price, etc.) related to the target application scheduled to be released, information indicating a period in which the target application scheduled to be released can be selected, or information indicating the content of the reward Data of an application list page (for example, see FIG. 18) that can be displayed on the user terminal 100 is generated and transmitted to the user terminal 100. For example, the list notification unit 242 generates application list page data in which the application list described in the HTML (HyperText Markup Language) format that can be displayed by the browser function that can be executed by the SDK 11 is displayed. Information indicating the link destination is transmitted to the user terminal 100.

  The list notification unit 242 transmits an application list to the user terminal 100 in response to a request from the user terminal 100, and each of the target applications to be released included in the application list has been selected in the user terminal 100. Is transmitted to the user terminal 100. Here, the list notification unit 242 records the customer information in which the application ID of the target application to be released included in the application list is associated with the reward user ID that identifies the user terminal 100, by the customer information management unit 223. Whether or not each of the target applications scheduled to be released has been selected in the user terminal 100 is determined based on whether or not they are managed.

  That is, when transmitting the application list to the user terminal 100, the list notification unit 242 is an unselected release target application or a selected release target application in the user terminal 100. Send so that it can be distinguished. The list notification unit 242 refers to the reward establishment information storage unit 238, and among the selected target applications scheduled to be released, the target application for which reward grant information has been notified after release (that is, the user X has acquired the reward) May be transmitted so that they can be distinguished.

  Specifically, for example, when generating the data of the application list page that can be displayed on the user terminal 100 described above, the list notification unit 242 and the target application that has been selected to be released and the target that has been selected to be released. Data of an application list page (see, for example, FIG. 18) that displays the application and the target application for which reward has been acquired is generated and transmitted to the user terminal 100.

  The customer information acquisition unit 243 acquires customer information including the application ID of the customer destination application 50 selected on the user terminal 100 and the reward user ID that identifies the user terminal 100 from the user terminal 100 (SDK11A). . The customer information acquisition unit 243 receives customer information including the application ID of the customer source application 10, the application ID of the customer destination application 50, and the reward user ID that identifies the user terminal 100 from the requested target application. You may get it. Then, the customer information acquisition unit 243 supplies the acquired customer information to the customer information management unit 223.

The customer information management unit 223 associates the application ID of the customer application 50 included in the customer information acquired by the customer information acquisition unit 243 with the reward user ID that identifies the user terminal 100, Manage as a record of information.
For example, the customer information management unit 223 includes the application ID of the customer application 50 included in the customer information acquired by the customer information acquisition unit 243 within the reception period stored in the scheduled release application information storage unit 239. It associates with the reward user ID which specifies the user terminal 100, and manages as a record of customer information. Here, the customer information management unit 223 sets the information type flag (FlagInf) to a flag because the customer information acquired by the customer information acquisition unit 243 is customer information indicating customers to the target application to be released. Set “1”.
The customer information management unit 223, when the customer information acquired by the customer information acquisition unit 243 is customer information indicating customer transmission to the target application that has been released, is an information type flag (FlagInf). Set the flag “0” to.

  The customer information management unit 223 identifies the application ID of the customer source application 10, the application ID of the customer application 50, and the user terminal 100 that are included in the customer information acquired by the customer information acquisition unit 243. The reward user ID may be associated and managed as a record of customer information.

Based on the customer information managed by the customer information management unit 223, the application information notification unit 247 identifies information related to the customer application 50 using the reward user ID associated with the application ID of the customer application 50. To the user terminal 100 to be transmitted. For example, when the customer destination application 50 is released based on the information managed by the application management unit 221 and the customer information managed by the customer information management unit 223, the application information notification unit 247 Information indicating that 50 has been released is transmitted to the user terminal 100 identified by the reward user ID associated with the application ID of the customer destination application 50.
Here, the information indicating that the customer destination application 50 has been released includes instruction information for guiding the customer destination application 50 to a screen on which the customer destination application 50 can be installed. Thereby, the user terminal 100 can notify the user X that the customer destination application 50 has been released and can be installed. Thereby, the user X does not need to remember the release date of the customer destination application 50 registered in advance, and can install the customer destination application 50 on the user terminal 100 on the release date.

  Based on the installation notification information corresponding to the customer destination application 50 acquired by the installation notification acquisition unit 241 and the record of the customer information managed by the customer information management unit 223, the reward processing unit 245 When it is determined that 50 is installed in the user terminal 100, a reward process is performed in which a reward is given to a user who uses the user terminal 100. For example, the reward processing unit 245 executes a reward process in which a reward is given to a user who uses the user terminal 100 in the installed customer destination application 50.

  Specifically, the reward processing unit 245, when it is determined that the customer destination application 50 is installed in the user terminal 100, the application of the customer destination application 50 associated with the reward user ID that identifies the user terminal 100. The reward grant information including the user ID is transmitted to the application server 350 corresponding to the customer destination application 50. Thereby, in the application server 350, the reward in the customer destination application 50 is provided with respect to the user X.

  Further, the reward processing unit 245 refers to the information stored in the scheduled release application information storage unit 239, and displays installation notification information indicating that the customer destination application 50 has been installed in the user terminal 100 as a customer destination. When the installation notification acquisition unit 241 acquires the application 50 within the reward grant period (within the reward grant period), the above-described reward process is executed. That is, when the installation notification information indicating that the customer destination application 50 has been installed in the user terminal 100 is acquired outside the reward grant period of the customer destination application 50, the reward processing unit 245 performs the above-described reward processing. Do not execute.

[Details of Operation of Mutual Customer Processing of Third Embodiment]
Next, with reference to FIG. 24, FIG. 25, and FIG. 26, the details of the operation of the mutual customer processing of the mutual customer system 500a according to the present embodiment will be described. 24, 25, and 26 are flowcharts showing an example of the operation of the mutual customer sending process according to the present embodiment. The processing shown in FIGS. 24, 25, and 26 shows a detailed example of the schematic flow of the processing described with reference to FIG.

  First, referring to FIG. 24, the user terminal 100 selects from the process (process (1) of FIG. 17) executed by the SDK 11A after the customer-source application 10 (game A) is installed in the user terminal 100. A detailed example up to a process (process (5A) in FIG. 17) in which the management server 200a acquires and manages customer information for the customer application 50 (game N) that is the target application to be released will be described. In FIG. 24, the same reference numerals are given to portions corresponding to the processing shown in FIG. 14, and description thereof will be omitted as appropriate.

  Similar to the processing described with reference to FIG. 14, when the customer source application 10 (game A) is installed in the user terminal 100, initialization of the SDK 11A incorporated in the customer source application 10 (game A) is performed. The processing unit 101 executes an initialization process.

  Next, based on a predetermined 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), and at least one release schedule List request notification information for requesting the application list of the target application (list of target applications that are candidates for the destination application 50) is transmitted to the management server 200a (REQ12A, step SA310).

  Here, the list request notification information includes a reward user ID (RewardUID) corresponding to the user terminal 100 and an application ID (ApID) of the customer source application 10 (game A). The list request notification information may include a campaign ID (CpID). In this case, “null” may be set as the campaign ID (CpID).

  When the list notification unit 242 of the management server 200a acquires the list request notification information transmitted from the user terminal 100 (SDK 11A of the customer source application 10), the target application information (for example, the target application information storage unit 231a) Referring to FIG. 21), the target application to be released is extracted. Then, the list notification unit 242 transmits the extracted application list of the target application to be released to the user terminal 100 specified by the reward user ID included in the list request notification information. For example, the list notification unit 242 generates application list page data including the application list (step SE310), and transmits redirection instruction information including information indicating a link destination of the generated application list page to the user terminal 100. Then, it is redirected to the application list page (RES12A, step SE312).

  Here, the list notification unit 242 refers to the release scheduled application information storage unit 239 to determine whether or not the release scheduled target application included in the application list is within the selectable period. Data of an application list page associated with information to be displayed may be generated, or data of an application list page including an application list of only target applications scheduled to be released within a selectable period may be generated.

  If there is no target application scheduled to be released, an application list page describing that there is no target application scheduled to be released is generated instead of the application list. For example, if there is no target application scheduled to be released within the selectable period, an application list page describing that there is no selectable target application to be released is generated instead of the application list.

When the user terminal 100 (SDK 11A) acquires redirect instruction information including information indicating the link destination of the application list page from the management server 200a, the display control unit 105 of the SDK 11A uses the browser function to display an application list of target applications to be released. The page is displayed on the display unit 120 (step SA312).
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, the application list LT2 of the target applications to be released that can be selected as the customer destination application 50 is displayed on the application list page on the display unit 120 of the user terminal 100 (see, for example, FIG. 18).

  When any target application is selected by the user X from the application list LT2 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). The customer information indicating that the customer has been sent to the selected target application to be released (here, the customer destination application 50 (game N)) is transmitted to the management server 200a (REQ13A, step SA314). .

  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 50 (game N), and the reward user ID (RewardUID) Is included. The customer ID may include a campaign ID (CpID). In this case, “null” may be set as the campaign ID (CpID).

  When the customer destination application 50 (game N) is selected, the display control unit 105 of the SDK 11A closes the application list page displayed on the display unit 120 in step SA312, and the customer source application 10 (game A). ) Display.

  The customer information acquisition unit 243 of the management server 200a acquires customer information from the user terminal 100 (SDK 11A). Then, the customer information management unit 223 obtains the application ID (ApID) of the customer application 50 (game N) and the reward user ID (RewardUID) included in the customer information acquired by the customer information acquisition unit 243. The customer information is stored in the customer information storage unit 237a as a record of customer information (step SE314). At this time, the customer information management unit 223 sets the flag “1” in the information type flag (FlagInf).

Next, referring to FIG. 25, the details of the process of notifying the release information after the customer destination application 50 (game N) is released (from the process (5B) to the process (6A) in FIG. 17). An example will be described.
The application information notification unit 247 of the management server 200a refers to the customer information indicating the customer to be released to the target application managed by the customer information management unit 223, and the customer who has released the target application. Information is extracted (step SE320).

  Specifically, the application information notifying unit 247 includes the customer destination application 50 (with flag “1” set in the information type flag (FlagInf) in the customer information recorded by the customer information management unit 223). Customer information indicating the customer to game N) is extracted. Next, the application information notification unit 247 is included in the extracted customer information indicating the customer to the customer application 50 (game N) and the target application information stored in the target application information storage unit 231a. Based on the release flag (FlagRelease), it is determined whether or not the customer destination application 50 (game N) has been released. When the customer destination application 50 (game N) has been released, the application information notification unit 247 plans to release customer information indicating customer transmission to the customer destination application 50 (game N). Extracted as customer information for which the target application has been released.

  Next, the application information notification unit 247 determines whether or not the customer destination application 50 (game N) has been installed in the user terminal 100 (step SE322). Specifically, the application information notification unit 247 refers to the installation information stored in the installation information storage unit 236, and displays installation notification information indicating that the customer destination application 50 (game N) has been installed. By determining whether or not the installation notification acquisition unit 241 has acquired from the user terminal 100, it is determined whether or not the customer destination application 50 (game N) has been installed in the user terminal 100.

In step SE322, when it is determined that the customer destination application 50 (game N) is not installed in the user terminal 100 (step SE322: NO), the application information notification unit 247 sends the customer destination application 50 (game N). Release information indicating that has been released to the user terminal 100 (step SE324). That is, the application information notification unit 247 transmits release information of the customer destination application 50 (game N) to the user terminal 100. Here, the release information includes, for example, the URL of the information posting page (the introduction screen of the customer destination application 50 (game N)) regarding the customer destination application 50 (game N). The URL of the information posting page regarding the customer destination application 50 (game N) is associated with the application ID of the customer destination application 50 (game N) in the target application information stored in the target application information storage unit 231a. This URL is set in the release information URL (ReleaseInfURL).
On the other hand, in step SE322, when it is determined that the customer destination application 50 (game N) has been installed in the user terminal 100 (step SE322: YES), the application information notification unit 247 does not execute the process of step SE324. . That is, in this case, the application information notification unit 247 does not transmit the release information of the customer destination application 50 (game N) to the user terminal 100.
Note that the management server 200a may repeatedly execute the processing from step SE320 to step SE324 at an interval of once a day, for example. As a result, the management server 200a determines whether or not the customer destination application 50 (game N) has been released every day, and if it has been released, releases the release information to the user on the release date. It can be transmitted to the terminal 100. Note that the interval at which the processing from step SE320 to step SE324 is executed is an example, and is not limited to the interval once a day.
In addition, after transmitting release information of the customer destination application 50 (game N) to the user terminal 100 in the process of step SE324, the management server 200a, for example, from the user terminal 100 to the customer destination application 50 even after three days have passed. If installation notification information indicating that (Game N) has been installed has not been acquired, the release information of the customer destination application 50 (Game N) may be sent again to the user terminal 100 as a reminder. Good. Furthermore, when the reward grant deadline is set, the management server 200a may repeat this reminder for a period until the reward grant deadline arrives. Note that the number of elapsed days (elapsed time) as a condition for transmitting release information as a reminder is an example, and the number of elapsed days as a condition is not limited to three days.

  Next, the application information acquisition unit 41 of the resident application 40 being executed in the user terminal 100 acquires the release information transmitted from the management server 200a. Then, the information presentation unit 42 of the resident application 40 causes the display unit 120 to display the release information of the customer destination application 50 acquired by the application information acquisition unit 41 (step SA320). For example, the information presentation unit 42 releases the acquired release dialog in an alert dialog pop-up displayed on the display screen displayed on the display unit 120 or a predetermined notification area (an area where notification information in various applications is displayed) in the display screen. Display information.

  When the user X performs an operation (for example, a tap operation) on the release information displayed on the display unit 120, the browser 45 installed in the user terminal 100 is activated, and the activated browser 45 is included in the release information. A page linked to the URL, that is, an introduction screen of the released customer application 50 (game N) is displayed (step SA322). Here, on the introduction screen of the customer destination application 50 (game N), display information indicating that a reward cannot be obtained unless it is installed within a predetermined period, and the customer destination application 50 (game N) can be installed ( A link button to a downloadable app store 400 is displayed. That is, in the release information, the released customer address is used as instruction information for guiding to the store page (game N download page) of the app store 400 where the customer app 50 (game N) can be installed (downloadable). A URL for displaying the introduction screen of the application 50 (game N) is included.

  When the user X operates (for example, tap operation) on the link button to the app store 400 on the introduction screen displayed by the browser 45 (step SA324), the store 30 is activated, and the activated store 30 is sent to the customer. A store page (download page of game N) of the application store 400 in which the previous application 50 (game N) can be installed is displayed (step SA326).

  Accordingly, the user X installs the customer destination application 50 (game N) in the user terminal 100 from the store page (game N download page) of the app store 400 where the customer destination application 50 (game N) can be installed. can do.

  Note that the application information notification unit 247 determines whether or not it is within the reward grant period, and when it is within the reward grant period, the release information indicating that the customer destination application 50 (game N) has been released is displayed. You may transmit with respect to the user terminal 100. FIG.

  Next, referring to FIG. 26, the processing after the customer destination application 50 (game N) is installed and activated on the user terminal 100 after the release (from the processing (8) in FIG. 17 to the processing (11A)). A detailed example will be described. In FIG. 26, the same reference numerals are given to portions corresponding to the processing shown in FIG. 15, and description thereof will be omitted as appropriate.

  First, when the customer destination application 50 (game N) is installed in the user terminal 100, the user terminal 100 (SDK11N) is changed to the user terminal 100 (SDK11A) when the customer source application 10 (game A) is installed. The same processing as the initial startup processing and initialization processing shown in FIG.

  When the installation notification acquisition unit 241 of the management server 200a acquires the installation notification information corresponding to the customer destination application 50 (game N) from the user terminal 100 (SDK11N), the reward processing unit 245 of the management server 200a It is determined whether customer information for 50 is stored in customer information storage unit 237a. When the customer information is stored in the customer information storage unit 237a (that is, the customer information management unit 223 manages the customer information record for the customer application 50). The customer application 50 is determined to be the target application sent by the mutual customer sending system 500a, and the reward process is executed.

Here, in the process of step SE314, the customer destination application 50 is the target application sent by the mutual customer sending system 500a before the release by recording customer information stored in the customer information storage unit 237a. It is determined that there is.
In the reward processing unit 245, the installation notification acquisition unit 241 acquires installation notification information from the customer destination application 50, and the customer information record for the customer destination application 50 is managed by the customer information management unit 223. And the reward point ID (RewardSpotID) is set to “null” and the established state (RewardStatus) is set to the flag “0” (unnotified) in association with the reward management ID stored in the customer information. Formation information is generated and stored in the reward formation information storage unit 238 (step SE332).

Next, the reward processing unit 245 acquires the customer information corresponding to the reward management ID associated with the generated reward establishment information with reference to the customer information record stored in the customer information storage unit 237a. To do. Then, the reward processing unit 245 applies the application user of the customer destination application 50 (game N) to the application server 350 (game N) corresponding to the customer destination application 50 (game N) included in the customer information. Remuneration grant information including ID (ApUID) is transmitted (step SE334). Here, for example, the application user ID (ApUID) of the customer destination application 50 (game N) is determined by the management server 200a by the user terminal 100 (SDK11A) based on installation notification information indicating that the customer destination application 50 has been installed. Is obtained from
In addition, the transmission destination (application server 350) of reward granting information is a notification destination URL (ApID) associated with the application ID (ApID) of the customer destination application 50 (game N) stored in the target application information storage unit 231a. NoticeURL).

  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 350 (game N) receives the reward grant information as reward establishment information from the management server 200a (step SF332), the app user ID (app user ID of the user X) included in the reward grant information is received. A predetermined reward is given (step SF334). This reward is set in advance by the provider of the target application, for example, as a reward given by a customer before release for the target application to be released.

[Summary of Third Embodiment]
(1) As described above, in the mutual customer service system 500a of the present embodiment, the management server 200a (an example of a management device) includes an application management unit 221, a list notification unit 242, and a customer information management unit 223. And an installation notification acquisition unit 241 and a reward processing unit 245.
The application management unit 221 manages information related to a target application to be released (an example of an application before the start of provision), which is an application before the start of provision, among a plurality of target applications to be managed. The list notification unit 242 transmits an application list of at least one target application scheduled to be released to the user terminal 100 (an example of a terminal device). The customer information management unit 223 includes an application ID (identification information) of the customer application 50 (an example of a selected application) selected in the user terminal 100 from at least one target application to be released included in the application list. Of the customer information indicating that the user using the user terminal 100 has been sent to the customer application 50 by associating a reward user ID (an example of unique identification information) that identifies the user terminal 100 Manage as a record.
The installation notification acquisition unit 241 is installation notification information indicating that the target application installed in the user terminal 100 among a plurality of target applications is installed, and includes an installation ID including the application ID of the installed target application Information is acquired from the target application in association with the unique identification information that identifies the terminal device.
The reward processing unit 245 installs the customer destination application 50 in the user terminal 100 based on the installation notification information acquired by the installation notification acquisition unit 241 and the customer information recorded by the customer information management unit 223. When it is determined that the reward is given, a reward process (an example of a reward grant process) in which a reward is given to a user who uses the user terminal 100 is executed.

In this way, the management server 200a manages customer information for a target application selected on the user terminal 100 from at least one target application scheduled to be released, and the target application is installed in the user terminal 100 after the release. Then, a reward process is performed in which a reward is given to a user (user X) who uses the user terminal 100 based on the managed customer information. At this time, the management server 200a identifies the user (user X) who uses the user terminal 100 based on the reward user ID included in the customer information.
Thereby, the management server 200a enables the user to send the customer to the target application to be released that has not yet been released. When the customer is established after the release, the management server 200a gives a reward to the user who has been sent. be able to. Therefore, the motivation for the user to use the target application can be enhanced before the target application is released.
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 / encrypted. That is, any identification information that is generated or set inside or outside the mutual customer sending system 500a and is unique in the user terminal 100 may be used.

(2) Further, in the mutual customer sending system 500a of the present embodiment, the user terminal 100 (an example of a terminal device) can communicate with a management server 200a (an example of a management device). Here, the management server 200a manages information on a target application to be released (an example of an application before the start of provision), which is an application before the start of provision, among a plurality of target applications to be managed. Further, the management server 200a identifies the application ID (an example of identification information) of the customer destination application 50 (an example of the selected application) selected from the target applications scheduled to be released and the user terminal 100. It is associated with a user ID (an example of unique identification information) and managed as a record of customer information for a target application scheduled to be released.
The user terminal 100 includes a list request unit 104 having a function of a list acquisition unit, and a customer information notification unit 106. The list request unit 104 (an example of a list acquisition unit) acquires an application list of at least one target application scheduled to be released from the management server 200a. The customer information notifying unit 106 receives customer information including the application ID of the customer destination application 50 selected from at least one target application to be released included in the application list acquired by the list request unit 104. The terminal 100 (an example of a terminal device) is transmitted to the management server 200a in association with a reward user ID that identifies the terminal 100.

In this way, the user terminal 100 acquires the application list of at least one target application scheduled to be released from the management server 200a, and the transmission selected from the at least one target application scheduled to be released included in the acquired application list. The customer information for the customer application 50 is transmitted to the management server 200a. At this time, the user terminal 100 transmits, to the management server 200a, customer information including a reward user ID for the management server 200a to identify a user to whom a reward is granted when the customer is established.
As a result, the user terminal 100 can send a customer to a target application to be released that has not yet been released.
The management server 200a provides a reward grant that rewards a user who uses the user terminal 100 when the customer destination application 50 corresponding to the managed customer information is installed in the user terminal 100. Processing may be executed.

  The function of the list request unit 104 and the function of the customer information notification unit 106 are executed based on the SDK 11 (software) incorporated in each of a plurality of target applications. For example, the SDK 11A incorporated in the customer source application 10 executes the function of the list request unit 104 and the function of the customer information notification unit 106.

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

(3) The user terminal 100 (SDK 11) includes a unique identification information acquisition unit 102. 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), and stores the reward user ID in the terminal storage unit 140. If it is determined that the reward user ID is not obtained, the reward storage user ID is obtained, and the obtained reward user ID can be referred to from any target application installed in the user terminal 100 (an example of a terminal device). Remember me.

  In other words, the reward user ID is acquired on the condition that the target application first installed in the user terminal 100 among a plurality of target applications is started, and can be referred to from any target application installed in the user terminal 100. As such, it is stored in the user terminal 100.

  Thus, according to the mutual customer sending system 500a, 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 to be installed thereafter. In order to make it possible to use the system, the reward user ID can be acquired without causing the user to perform a special operation.

(4) The user terminal 100 (SDK 11) includes an installation notification unit 103. The installation notification unit 103 is installation notification information indicating that the target application installed in the user terminal 100 (an example of a terminal device) has been installed, and includes an application ID (an example of identification information) of the target application. The installation notification information is transmitted to the management server 200a in association with a reward user ID (an example of unique identification information) that identifies the user terminal 100.

  Accordingly, when the customer destination application 50 is installed, the user terminal 100 can notify the management server 200a that the customer destination application 50 has been installed in the user terminal 100. Therefore, the management server 200a refers to the customer information based on the application ID of the target application installed in the user terminal 100 and the reward user ID that identifies the user terminal 100 included in the installation notification information. It is possible to determine whether or not the installed target application is the customer destination application 50. That is, the management server 200a can determine whether or not the customer destination application 50 is installed in the user terminal 100.

(5) The installation notification information may further include an application user ID (an example of user information) of the target application that has transmitted the installation notification information. For example, the installation notification unit 103 of the user terminal 100 includes an application user ID in the installed target application of the user who installed the installed target application, and an installation notification including the application ID (an example of identification information) of the target application. The information is transmitted to the management server 200a in association with a reward user ID (an example of unique identification information) that identifies the user terminal 100 (an example of a terminal device).

  Note that the user terminal 100 (SDK 11) may include the application user ID in information other than the installation notification information and transmit it to the management server 200a.

  Thereby, when the customer destination application 50 is installed, the user terminal 100 recognizes the application user ID of the user (user X) who uses the customer destination application 50 in the user terminal 100, and the reward user who identifies the user terminal 100 The management server 200a can be notified so that it can be associated with the ID.

(6) The reward processing unit 245 of the management server 200a, based on the installation notification information acquired by the installation notification acquisition unit 241 and the record of customer information managed by the customer information management unit 223, When it is determined that (an example of the selected application) is installed in the user terminal 100, a reward process (reward grant) in which a reward is given to a user who uses the user terminal 100 in the installed customer destination application 50 An example of processing is executed.

  That is, when the customer destination application 50 is installed after the release on the user terminal 100 of the user (user X) who has been sent to the customer destination application 50 to be released that has not yet been released, the management server 200 a The reward process is executed so that a reward in the customer destination application 50 is given to the user (user X). Therefore, according to this embodiment, the grant of the reward in the target application scheduled to be released can be motivated to use the target application.

(7) For example, when it is determined that the customer destination application 50 (an example of a selected application) has been installed in the user terminal 100, the reward processing unit 245 of the management server 200a recognizes the reward user ID ( Reward grant information including the application user ID (an example of user information) of the customer destination application 50 associated with the example of the unique identification information) is sent to the application server 350 (an example of a server device) corresponding to the customer destination application 50. Send.
Here, the installation notification acquisition unit 241 functions as an application user information acquisition unit. That is, the management server 200a includes an application user information acquisition unit that acquires the application user ID of the customer destination application 50 installed in the user terminal 100 in association with the reward user ID that identifies the user terminal 100.

  The management server 200a may acquire the application user ID from the user terminal 100 by including it in information other than the installation notification information. The management server 200a may acquire the application user ID in the customer destination application 50 from the application server 350 corresponding to the customer destination application 50.

  Thus, when the customer destination application 50 is installed in the user terminal 100, the management server 200a associates the application user ID in the installed customer destination application 50 with the reward user ID that identifies the user terminal 100. Can be managed. In addition, when the customer destination application 50 indicated by the application ID included in the managed customer information is installed in the user terminal 100, the management server 200a uses the customer destination application 50 on the user terminal 100. The reward application information including the application user ID in the customer application 50 associated with the reward user ID included in the customer information is given to the customer application 50 so that a reward is given to the (user X). Can be transmitted to the application server 350 corresponding to.

  The management server 200a replaces the reward grant information including the application user ID in the customer destination application 50 with the application server 350 corresponding to the customer destination application 50, and the customer destination application 50 installed in the user terminal 100. (SDK11N) may be transmitted. Thereby, in the customer's destination application 50 installed in the user terminal 100, a reward based on the reward grant information may be granted. Further, the reward grant information is transmitted to the application server 350 corresponding to the customer destination application 50 via the customer destination application 50 installed in the user terminal 100, and the reward based on the reward grant information is granted in the application server 350. May be.

(8) The list request unit 104 of the user terminal 100 (SDK11) sends list request notification information for requesting an application list of at least one target application scheduled to be released (an example of an application before starting provision) to the user terminal 100 (terminal device). In association with a reward user ID (an example of unique identification information) that identifies the management server 200a. Then, the list request unit 104 (an example of a list acquisition unit) acquires the application list of the target application to be released transmitted from the management server 200a in response to the transmission of the above list request notification information.

  Thereby, the user terminal 100 can acquire the application list of the target application scheduled to be released from the management server 200a. Therefore, the user terminal 100 can acquire the latest information of the target application scheduled to be released at a necessary timing.

(9) The user terminal 100 (SDK11) includes a display control unit 105 (an example of a presentation unit). The display control unit 105 displays a list of target applications to be released (application list and presentation) based on an application list of target applications to be released (an example of pre-provision application) acquired by the list request unit 104 (an example of a list acquisition unit). An example of a list) is displayed on the display unit 120 and presented to the user.

  Thereby, the user can confirm information (for example, the contents of the game and the contents of the reward) regarding the target application scheduled to be released, and can make a selection with a simple operation.

  For example, the list request unit 104 of the user terminal 100 (SDK 11) acquires the application list from the management server 200a, and based on the record of customer information managed by the management server 200a, the release schedule target included in the application list Information indicating whether each of the applications (an example of an application before starting provision) has been selected in the user terminal 100 is acquired from the management server 200a. When the display control unit 105 of the user terminal 100 displays a list of target applications to be released (an application list or an example of a presentation list) on the display unit 120 and presents it to the user, the list request unit 104 acquires the above-described information. Based on the information indicating whether or not it has been selected, the user terminal 100 (an example of a terminal device) displays the selected target application to be released and the target application that has not been selected to be displayed separately. Present. Here, the information indicating whether or not the above-described selection has been performed is, for example, the information on the selected release target application and the unselected release target application displayed in the list of release target applications. Display information corresponding to each (for example, tabs TB21 and TB22 shown in FIG. 18).

Thereby, the user terminal 100 can distinguish and display the selected release target application and the unselected release target application. Therefore, the user can easily confirm the target application scheduled to be released and the target application selected to be released.
Note that the user terminal 100 may generate a list of target applications scheduled to be released (an example of an application list or a presentation list) by acquiring an application list from the management server 200a and display the list on the display unit 120. At this time, the user terminal 100 acquires from the management server 200a information indicating whether each of the target applications to be released included in the application list has been selected in the user terminal 100, thereby selecting the release schedule that has been selected. A list of target applications scheduled to be released (an example of an application list and a presentation list) may be generated in which the target applications and target applications that are not yet selected are displayed separately.

(10) In response to a request from the user terminal 100 (an example of a terminal device), the list notification unit 242 of the management server 200a transmits the application list to the user terminal 100, and the release schedule included in the application list A record of customer information in which an application ID (an example of identification information) of a target application (an example of an application before starting provision) is associated with a reward user ID (an example of unique identification information) that identifies the user terminal 100 Based on whether or not the management unit 223 manages, information indicating whether or not each of the target applications to be released included in the application list has been selected in the user terminal 100 is given to the user terminal 100 Send.

  As described above, the management server 200a transmits the application list of the target applications scheduled to be released to the user terminal 100 in response to a request from the user terminal 100. 100 can be transmitted.

  In addition, the management server 200a further displays information indicating whether or not the reward acquired target application has been acquired by the user among the selected target applications. You may transmit with respect to the terminal 100. FIG. Then, the user terminal 100 may display the selected release target application and the unselected release target application separately, and may further display the reward-acquired target application.

(11) The management server 200a associates with a reward user ID (an example of unique identification information) that identifies the user terminal 100, and selects a customer destination application 50 (selected application) selected on the user terminal 100 (an example of a terminal device). A customer information acquisition unit 243 that acquires customer information including an application ID (an example of identification information) from the user terminal 100 is provided. The customer information management unit 223 associates the application ID of the customer destination application 50 included in the customer information acquired by the customer information acquisition unit 243 with the reward user ID that identifies the user terminal 100, and Manage as a record.

  Thereby, the management server 200a manages the record of the customer information in which the application ID of the customer destination application 50 and the reward user ID that identifies the user terminal 100 are associated with each other based on the customer information acquired from the user terminal 100. can do.

(12) The list request unit 104 of the user terminal 100 (SDK11) transmits list request notification information to the management server 200a from a target application operating on the user terminal 100 (an example of a terminal device). Here, the target application operating on the user terminal 100 is, for example, the customer source application 10.
Further, the list request unit 104 functions as a list acquisition unit, and acquires an application list of a target application to be released (an example of an application before starting provision) in the customer source application 10 that has transmitted the list request notification information.
The customer information notifying unit 106 includes the application ID of the customer source application 10 (an example of the target application) that acquired the application list of the target application to be released, and at least one included in the application list in the customer source application 10. Reward user ID (an example of unique identification information) that identifies the user terminal 100 with customer information including the application ID of a customer application 50 (an example of a selected application) selected from the target applications scheduled to be released And transmitted to the management server 200a.

  Thereby, the user terminal 100 can transmit customer information for the customer destination application 50 from the customer source application 10 installed in the user terminal 100 to the management server 200a.

(13) The list notification unit 242 of the management server 200a sends the application list to the user terminal based on a request from the customer source application 10 (an example of the target application) installed in the user terminal 100 among the plurality of target applications. 100 is transmitted. The customer information acquisition unit 243 is associated with a reward user ID (an example of unique identification information) that identifies the user terminal 100, and an application ID (an example of identification information) of the customer application 10 (an example of a requested target application). And the customer ID information including the application ID of the customer destination application 50 (an example of the selected application) is acquired from the customer source application 10. The customer information management unit 223 recognizes the user ID of the application ID of the customer source application 10 and the application ID of the customer destination application 50 included in the customer information acquired by the customer information acquisition unit 243. It is associated with the user ID and managed as a record of customer information.

  Thereby, the management server 200a can acquire and manage customer information for the customer destination application 50 from the customer source application 10 installed in the user terminal 100 from the user terminal 100.

(14) The application management unit 221 of the management server 200a manages a reception period (that is, a selectable period) indicating a period for receiving a selection for a target application to be released (an example of an application before starting provision) in the user terminal 100. ing.
The customer information notifying unit 106 of the user terminal 100 (SDK 11) transmits customer information to the management server 200a within the reception period.
The customer information management unit 223 of the management server 200a uses the application ID (identification information) of the customer application 50 (an example of the selected application) included in the customer information acquired by the customer information acquisition unit 243 within the above reception period. Is associated with a reward user ID (an example of unique identification information) that identifies the user terminal 100 and managed as a record of customer information.

  That is, in the mutual customer sending system 500a, a selectable period (for example, a period in which registration is possible in advance) is set for each target application scheduled to be released. As a result, the user terminal 100 permits the user to select the target application to be released only during the selectable period, and sends the customer information for the selected customer destination application 50 to the management server 200a. Can be sent. In addition, since the management server 200a manages the recording of customer information acquired only within this selectable period, only the customers within this selectable period can be targeted for reward.

(15) The application management unit 221 of the management server 200a may manage a reward grant time limit in which at least the end date / time is defined. Then, the reward processing unit 245 of the management server 200a acquires the installation notification information indicating that the customer destination application 50 (an example of the selected application) has been installed in the user terminal 100 within the reward grant time limit. If so, a reward process (an example of a reward grant process) is executed.

  In this way, since the time limit for granting the reward is set, the motivation for the user to install and use the customer destination application 50 can be further enhanced.

Note that the installation information management unit 222 includes installation date information based on the timing at which the installation notification information is acquired, the application ID (an example of identification information) of the application installed in the user terminal 100 and the user terminal included in the installation notification information. The reward user ID (an example of unique identification information) that identifies 100 may be directly or indirectly associated and managed. In this case, the reward processing unit 245 determines that the installation notification acquisition unit 241 has acquired installation notification information indicating that the customer destination application 50 has been installed in the user terminal 100, and the installation information management unit 222. The reward process is executed when the installation date and time information of the acquired installation notification information that is managed by is within the reward grant period.
For example, the reward processing unit 245 determines that the installation notification acquisition unit 241 has acquired installation notification information indicating that the customer destination application 50 has been installed in the user terminal 100, and the application user ID in the customer destination application 50 When the installation notification acquisition unit 241 acquires (an example of user information) and the installation date and time information of the acquired installation notification information managed by the installation information management unit 222 is within the reward grant period, The reward grant information including the application user ID in the customer application 50 is transmitted to the application server 350 corresponding to the customer application 50.

(16) The management server 200a includes an application information notification unit 247. Based on the customer information managed by the customer information management unit 223, the application information notification unit 247 displays information related to the customer destination application 50 (an example of the selected application) with the application ID (identification information) of the customer destination application 50. It is transmitted to the user terminal 100 specified by the reward user ID (one example of unique identification information) associated with one example).

That is, the management server 200a transmits information related to the customer destination application 50 to the user terminal 100 in which the customer destination application 50 is selected.
Thereby, the management server 200a can notify the information regarding the customer destination application 50 to the user who has selected the customer destination application 50.

(17) For example, based on the information managed by the application management unit 221 and the customer information managed by the customer information management unit 223, the application information notifying unit 247 determines whether the customer destination application 50 (an example of a selected application) When released (provided to start), a release user indicating that the customer destination application 50 has been released (started to provide) is associated with an application ID (an example of identification information) of the customer destination application 50. It transmits with respect to the user terminal 100 specified by ID (an example of unique identification information).

  Here, the application information notification unit 247 updates the release flag (FlagRelease) of any target application from the flag “0” to the flag “1” in the target application information stored in the target application information storage unit 231a. If it is determined that the updated target application has been released. Next, the application information notification unit 247 refers to the target application information stored in the target application information storage unit 231a, and the target application to be released whose flag “1” is set in the information type flag (FlagInf). The customer information in which the application ID of the released target application is set in the customer application ID (ApIDto) is extracted from the customer information for the customer. Subsequently, the application information notification unit 247 transmits the release information of the released target application to the user terminal 100 specified by the reward user ID included in the extracted customer information.

  When the target application information storage unit 231a stores information related to the target application scheduled to be released separately from information related to the released target application, the target application stored as information related to the target application scheduled to be released is stored. When registered as information related to the released target application, the application information notification unit 247 may determine that the target application has been released.

  Thereby, the management server 200a can notify the user who has selected the customer destination application 50 that the release date of the selected customer destination application 50 has arrived. Therefore, the management server 200a can prompt the user to install the customer destination application 50.

(18) The user terminal 100 includes an application information acquisition unit 41 and an information presentation unit 42. The application information acquisition unit 41 acquires information about the customer destination application 50 (an example of a selected application) from the management server 200a. The information presenting unit 42 displays information on the customer destination application 50 acquired by the application information acquiring unit 41 on the display unit 120 and presents it to the user. Note that the functions of the application information acquisition unit 41 and the information presentation unit 42 described above are executed based on the resident application 40 installed in the user terminal 100, for example.

  Thereby, the user terminal 100 can acquire and notify the information regarding the customer destination application 50 selected from at least one target application to be released included in the application list from the management server 200a.

(19) For example, the information related to the customer destination application 50 (an example of the selected application) is release information indicating that the customer destination application 50 has been released (started providing).

  Thereby, the user terminal 100 can notify the user who has selected the customer destination application 50 that the release date of the selected customer destination application 50 has arrived. Therefore, the user terminal 100 can prompt the user to install the customer destination application 50.

(20) The application management unit 221 of the management server 200a may manage information indicating the provision start date and time of the target application scheduled to be released as information related to the target application scheduled to be released (an example of an application before starting provision).
For example, the application information notification unit 247 is configured to send the customer destination application 50 (an example of the selected application) based on information indicating the provision start date and time managed by the application management unit 221 and customer information managed by the customer information management unit 223. ) Is transmitted to the user terminal 100 identified by the reward user ID (an example of unique identification information) associated with the application ID (an example of identification information) of the customer destination application 50. May be.

  Thereby, the management server 200a can notify the release date and time of the selected customer destination application 50 to the user who has selected the customer destination application 50. For example, in the user terminal 100, as the release date of the customer destination application 50 approaches, the number of days or time until the release date can be displayed in a countdown manner, or release information can be notified at predetermined time intervals or time intervals.

For example, the application management unit 221 may store and manage a preset release date or release date (that is, provision start date) in the target application information storage unit 231a instead of the release flag.
The application information notification unit 247 then sends the customer destination application 50 (an example of the selected application) based on the information indicating the provision start date and time managed by the application management unit 221 and the customer information managed by the customer information management unit 223. ) Is associated with the application ID (an example of identification information) of the customer destination application 50, when it is determined that the provision start date and time has been reached. You may transmit with respect to the user terminal 100 specified by reward user ID (an example of unique identification information).

(21) Information indicating that the customer destination application 50 (an example of the selected application) has been released (starts providing) includes instruction information for guiding the customer destination application 50 to a screen on which the customer destination application 50 can be installed. This instruction information is, for example, the URL of a page for posting information related to the customer destination application 50, and includes a customer destination application that includes a link button to the app store 400 on which the customer destination application 50 can be installed (downloadable). This is the URL of the page on which 50 introduction screens are displayed.

  Thereby, the user terminal 100 can easily display a store page on which the customer destination application 50 can be installed (downloadable) without causing the user to perform complicated operations. Therefore, the mutual customer sending system 500a can prevent the user from motivating to install the customer destination application 50 due to difficulty in operation.

(22) In the third embodiment, the mutual customer sending system 500a executes a process specialized for the customer sending process to the target application scheduled to be released, and is described in the first and second embodiments. When the reward process and the CP reward process are not executed, a configuration excluding a part of the configuration of the user terminal 100 or the management server 200a included in the mutual customer sending system 500a may be adopted.
For example, since the user terminal 100 (SDK11) does not need to transmit the reward grant notification information described in the first embodiment, the reward grant notification unit 107 may be omitted. The management server 200a may be configured without the normal reward information storage unit 232, the campaign information storage unit 234, or the campaign participation application information storage unit 235.
Moreover, in the said 3rd Embodiment, although the reward process provided with a reward on condition that the customer destination application 50 was installed in the user terminal 100 and started was demonstrated as an example, it demonstrates by 2nd Embodiment. As in the CP reward process, a reward may be awarded when a preset reward provision condition is satisfied. In this case, the user terminal 100 (SDK 11) may include a reward grant notification unit 107. For example, a reward granting condition is set in advance for the target application scheduled to be released, and the reward granting notification unit 107 of the user terminal 100 (SDK11) is rewarded based on the satisfaction of the preset reward granting condition. Reward grant notification information indicating that the grant conditions are satisfied may be transmitted to the management server 200. That is, the reward processing unit 245 selects the customer destination application 50 (an example of the selected application) based on the installation notification information acquired by the installation notification acquisition unit 241 and the customer information recorded by the customer information management unit 223. ) Is installed in the user terminal 100, and the reward grant notification information indicating that the reward granting condition is satisfied from the customer destination application 50 based on that the preset reward granting condition is satisfied. When the user terminal 100 is acquired, a reward based on the acquired reward grant notification information may be given to the user who uses the user terminal 100. Furthermore, the reward processing unit 245 indicates that the installation notification acquisition unit 241 has acquired the installation notification information indicating that the customer destination application 50 (an example of the selected application) has been installed in the user terminal 100 within the reward grant period. It is good also as the above-mentioned reward provision conditions.

  Further, by applying the processing in the second embodiment to the present embodiment, the target application scheduled to be released that is listed in the application list may be selected based on a predetermined condition.

<Fourth Embodiment>
Next, a fourth embodiment of the present invention will be described. In the third embodiment, the example of the customer sending process in which the customer sending application 10 installed in the user terminal 100 is sent to the customer sending application 50 that is the target application scheduled to be released has been described. In the present embodiment, an example of a customer sending process for sending a customer to a customer destination application 50 from a dedicated application specialized for a customer sending function to a target application to be released instead of the customer sending application 10 will be described. .

[Configuration and Processing of Mutual Customer Transmission System According to Fourth Embodiment]
FIG. 27 is an explanatory diagram illustrating an example of the configuration and processing of the mutual customer sending system 500b in the network system 1b of the present embodiment. In FIG. 27, portions corresponding to those in FIG. 17 are denoted by the same reference numerals, and description thereof is omitted.

  A mutual customer sending system 500b shown in FIG. 27 is different from the mutual customer sending system 500a shown in FIG. The dedicated application 60 is a dedicated application having a function of sending customers to a target application scheduled to be released. The dedicated application 60 is provided so as to be installable (downloadable) from the application store 400 to the user terminal 100, for example. Here, an example is shown in which a dedicated application 60 is installed in the user terminal 100 and a customer is sent from the dedicated application 60 to a customer destination application 50 that is a target application to be released.

  The dedicated application 60 includes the function of the SDK 11A described in the third embodiment. As described above, the dedicated application 60 installed in the user terminal 100 has the function of the SDK 11A of the customer destination application described in the third embodiment. Similarly to the mutual customer sending system 500a of the embodiment, a customer sending process for sending customers to the target application scheduled to be released can be performed.

  In the example illustrated in FIG. 27, the browser 45 is installed in the user terminal 100, but the function of the browser 45 may be included in the dedicated application 60. Further, the function of the resident application 40 may be included in the dedicated application 60.

[Functional Configuration of User Terminal 100 of Fourth Embodiment]
FIG. 28 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, since the dedicated application 60 only needs to have a function as a customer source in the functional configuration of the SDK 11 shown in FIG. 5, the reward grant notification unit 107 having a functional configuration unique to the customer destination application is provided. It is not necessary to prepare. Accordingly, the SDK 11A may be incorporated in the dedicated application 60.

  With this configuration, the dedicated application 60 sends customer information for the customer destination application 50 selected from the target applications scheduled to be released to the management server 200a in the same manner as the customer source application 10 in which the SDK 11A is incorporated. Can be sent.

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

[Operation Example of Mutual Customer Processing of Fourth Embodiment]
Next, the operation of the customer sending process by the mutual customer sending system 500b according to the present embodiment will be described. In the customer sending process by the mutual customer sending system 500b, the customer application 10 performs the process of the customer sending application 10, whereby the customer sending process according to the third embodiment described with reference to FIGS. 24, 25 and 26 is performed. A process similar to the process can be performed. It should be noted that the customer sending process by the mutual customer sending system 500b may be performed by the dedicated application 60 to perform a process partially different from the customer sending process according to the third embodiment. For example, as described above, the management server 200a may not manage whether the dedicated application 60 is installed.

  FIG. 29 is an example in which the dedicated application 60 executes the process executed by the customer source application 10 shown in FIG. 24 instead of the customer source application 10, and whether the dedicated application 60 is installed in the user terminal 100. It is a flowchart which shows an example of operation | movement of a customer-transmission process when the management server 200a does not manage whether it is no. In FIG. 29, portions corresponding to the respective processes shown in FIG. 24 are denoted by the same reference numerals, and description thereof is 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. In this initialization process, a process of acquiring a reward user ID is performed, and a process of transmitting installation notification information 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 to determine whether or not the reward user ID has been acquired (step SA13) and has not been acquired. In this case, a reward user ID is generated and acquired (step SA14), and stored in the inter-application shared area of the terminal storage unit 140 (step SA15).

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 500b. . On the other hand, if no target application is installed before the dedicated application 60 is installed, the rewarded user ID used in the mutual customer sending system 500b is acquired when the dedicated application 60 is installed and activated. Is done.
The processes after the initialization process described above are the same as those described with reference to FIG. As described above, in the mutual customer sending system 500b according to the present embodiment, customer information to be sent to the customer destination application 50 is transmitted from the dedicated application 60 to the management server 200a. In addition, the management server 200a can manage the recording of customer information for the target application to be released.

Further, the dedicated application 60 may have the function of the browser 45. For example, in the processing after the customer destination application 50 is released, even if the dedicated application 60 executes the processing in which the browser 45 shown in FIG. 25 displays the introduction screen of the customer destination application 50 instead of the browser 45. Good.
FIG. 30 shows an example of processing in which release information is notified after the customer destination application 50 (game N) is released, and the dedicated application 60 displays an introduction screen of the customer destination application 50. Show. In FIG. 30, the same reference numerals are given to portions corresponding to the processes shown in FIG.

  The process in which the management server 200a transmits the release information to the user terminal 100 (the processes in steps SE320, SE322, and SE324) is the same as the process described with reference to FIG. The resident application 40 being executed in the user terminal 100 acquires the release information transmitted from the management server 200a, and displays the acquired release information of the customer destination application 50 on the display unit 120 (step SA320).

  When the user X operates (for example, tap operation) on the release information displayed on the display unit 120, the dedicated application 60 installed in the user terminal 100 is activated (step SA330). For example, the release information includes instruction information (for example, URL scheme) for starting a specific function (for example, browser function) of the dedicated application 60, and the dedicated application 60 is started based on the instruction information. .

  The dedicated application 60 displays the link destination page of the URL included in the release information, that is, the introduction screen of the released customer application 50 (game N) by the browser function of itself (step SA332). Here, on the introduction screen of the customer destination application 50 (game N), display information indicating that a reward cannot be obtained unless it is installed within a predetermined period, and the customer destination application 50 (game N) can be installed ( A link button to a downloadable app store 400 is displayed.

  When the user X operates (for example, tap operation) on the link button to the application store 400 on the introduction screen displayed by the dedicated application 60 (step SA334), the store 30 is activated, and the activated store 30 is transmitted. A store page (download page of game N) of application store 400 in which customer application 50 (game N) can be installed is displayed (step SA336).

[Summary of Fourth Embodiment]
As described above, in the mutual customer service system 500b of this embodiment, the configuration of the management server 200a (an example of a management device) is the same as the configuration of the management server 200a (an example of a management device) of the third embodiment. It is.
The user terminal 100 (an example of a terminal device) according to the present embodiment only needs to have at least a function as a customer source application in the functional configuration of the SDK 11 described in the third embodiment. For example, the user terminal 100 includes a list request unit 104 having a function of a list acquisition unit, and a customer information notification unit 106. The list request unit 104 (an example of a list acquisition unit) acquires an application list of at least one target application scheduled to be released from the management server 200a. The customer information notifying unit 106 receives customer information including the application ID of the customer destination application 50 selected from at least one target application to be released included in the application list acquired by the list request unit 104. The terminal 100 (an example of a terminal device) is transmitted to the management server 200a in association with a reward user ID that identifies the terminal 100.
Here, the function of the list request unit 104 and the function of the customer information notification unit 106 are executed based on the dedicated application 60 installed in the user terminal 100.

Thereby, similarly to the user terminal 100 of 3rd Embodiment, the user terminal 100 can send a customer with respect to the target application of the release plan which has not been released yet.
Further, in the mutual customer service system 500b of the present embodiment, similar to the mutual customer service system 500a of the third embodiment, a target user application to be released can be obtained by using a reward user ID that can uniquely identify the user terminal 100. Even if user information (for example, application user ID) is not registered, a reward process is provided in which a reward is given to a user who uses the user terminal 100 by associating the user information registered after the release with the reward user ID. It can be done easily. Therefore, according to the present embodiment, the motivation for the user to use the target application can be enhanced before the release of the target application.

<Modification>
The embodiment of the present invention has been described in detail with reference to the drawings. However, the specific configuration is not limited to the above-described embodiment, and includes a design and the like within a scope not departing from the gist of the present invention. For example, the functions described in the first to fourth embodiments can be arbitrarily combined. As an example, the mutual customer system 500 according to the first embodiment or the second embodiment may be combined with the mutual customer system 500a according to the third embodiment. That is, the mutual customer sending system 500 or the mutual customer sending system 500a may be equipped with functions of both a normal reward process or CP reward process for a released target application and a reward process for a target application scheduled to be released. For example, in the user terminal 100, the application list LT (FIG. 1) and the application list LT2 (FIG. 18) can be selectively displayed, and either the released target application or the target application scheduled to be released. It is good also as a structure which can select.
Note that the user terminal 100 can display an application list including both the released target application included in the application list LT (FIG. 1) and the target application scheduled to be released included in the application list LT2 (FIG. 18). It is good also as a simple structure. In this case, information indicating released or information indicating the release schedule is displayed in association with each target application included in the application list so that the released target application and the target application scheduled to be released can be distinguished. You may do it.

(1) In the above-described embodiment, the communication unit 210 (an example of the transmission / reception unit) of the management server 200 or the management server 200a is installed notification information, application list, list request notification information, customer information, instruction information, or reward grant notification An example in which information is directly communicated with the user terminal 100 has been described. Similarly, the terminal communication unit 130 (an example of a transmission / reception unit) of the user terminal 100 directly receives the installation notification information, application list, list request notification information, customer information, instruction information, or reward grant notification information directly from the management server 200 or The example of communicating with the management server 200a has been described.

  Here, the communication unit 210 of the management server 200 includes a customer-source application 10 (an example of a first application) or a customer-destination application 20 (an example of a second application), and an application server 300 (an example of a server device) corresponding thereto. After establishing a communication session via an example), the user terminal 100 may communicate directly. Similarly, the terminal communication unit 130 of the user terminal 100 communicates with the customer source application 10 (installed target application) or the customer destination application 20 (selected target application) via the application server 300 corresponding to each. You may communicate with the management server 200 directly after establishing a session.

In addition, the communication unit 210 of the management server 200a displays the customer application 10 (an example of a target application installed in the user terminal 100) or the customer application 50 (a selected application selected from the target applications scheduled to be released). And an application server 300 (an example of a server device) corresponding to each of them, and then communicating with the user terminal 100 directly. Similarly, the terminal communication unit 130 of the user terminal 100 receives the customer application 10 (an example of a target application installed in the user terminal 100) or the customer application 50 (a selected application selected from the target applications scheduled to be released). And a communication session may be established via the corresponding application server 300 and then directly communicate with the management server 200a.
The mutual customer sending system 500b of the fourth embodiment may be configured to include the application server 300 corresponding to the dedicated application 60. In this case, the user terminal 100 and the management server 200a are included in the dedicated application 60. You may communicate directly, after establishing a communication session via the corresponding application server 300. FIG.

In addition, when communicating with the management server 200 (200a) 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. 31 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. 31 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 way as the initialization process shown in FIG. 15, FIG. 24, or FIG. In FIG. 31, 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 a part of the installation notification information, application list, list request notification information, customer information, instruction information, or reward grant notification information is not directly communicated 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 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 (an example of the 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 or customer You may make it communicate with the user terminal 100 via the application server 300 corresponding to the previous application 20, or communicate with the user terminal 100 directly.

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.

In addition, the communication unit 210 (an example of the transmission / reception unit) of the management server 200a 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 (user terminal). Even if it communicates with the user terminal 100 via the application server 300 corresponding to the customer application 50 (an example of a selected application selected from among the target applications scheduled to be released). Good. Similarly, the terminal communication unit 130 (an example of a transmission / reception unit) of the user terminal 100 may communicate with the management server 200a via the application server 300 corresponding to the customer source application 10 or the customer destination application 50.
Thus, even if the user terminal 100 and the management server 200a communicate with each other via the application server 300, the mutual customer sending system 500a can perform customer sending processing and reward processing similar to those in the third embodiment. The same effect can be obtained. The mutual customer sending system 500b of the fourth embodiment may be configured to include the application server 300 corresponding to the dedicated application 60. In this case, the user terminal 100 and the management server 200a are included in the dedicated application 60. You may communicate via the corresponding application server 300. FIG.

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

  Further, the process of displaying the application list (application list) 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 executed by the SDK 11. Instead of the process, 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 granted. 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 normal reward process and the CP reward process of the first and second embodiments described above, an example of the process in which the reward in the customer source application 10 is given to the user has been described, but instead of the customer source application 10 It is good also as a process in which the reward in the customer's destination application 20 is given to a user. In this case, the management server 200, for example, the customer destination 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. Based on the notification destination URL (NoticeURL) included in the information, the reward grant information is transmitted to the application server 320 corresponding to the customer destination application 20. In the normal reward process and the CP reward process of the first and second embodiments, both a reward in the customer source application 10 and a reward in the customer destination application 20 may be given to the user.

  In the reward processing of the third embodiment, an example of processing in which a reward in the customer destination application 50 is given to the user has been described. However, a reward in the customer source application 10 is given in place of the customer destination application 50. It is good also as a process provided to a user. In this case, the management server 200a, for example, the customer application ID (ApIDfrom) included in the customer information stored in the customer information storage unit 237a and the target application stored in the target application information storage unit 231a. Based on the notification destination URL (NoticeURL) included in the information, the reward granting information is transmitted to the application server 310 corresponding to the customer source application 10. In the reward process of the third embodiment, both the reward in the customer destination application 50 and the reward in the customer source application 10 may be given to the user.

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

  Further, the storage unit 230 (230a) of the management server 200 (200a) may be provided in a server device different from the management server 200 (200a). Then, the management unit 220 or the control unit 240 (240a) of the management server 200 (200a) communicates with the storage unit 230 (230a) provided in the server device different from the management server 200 (200a) via the network NW. By doing so, you may manage each information which each part with which the memory | storage part 230 (230a) is provided memorize | stores.

  Further, the management server 200 (200a) and the application server 300 may be configured as a server device integrated.

  In the above embodiment, the list request unit 104 of the SDK 11 or the dedicated application 60 has been described as having a function of a list acquisition unit. However, the SDK 11 or the dedicated application 60 includes a list acquisition unit separately from the list request unit 104. It is good also as a structure.

In the above embodiment, the management server 200 (200a) includes various information such as installation notification information, list request notification information, customer information, reward grant notification information, etc. so that the reward user ID is included. However, although the example linked | related with the reward user ID which identifies 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 (200a) and the user terminal 100, the established communication session is associated with a reward user ID that identifies the user terminal 100. Also good. 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 200a 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.

(7) A program for realizing the functions of the management unit 220, the control unit 240 (240a), the SDK 11, or the dedicated application 60 described above is recorded on a computer-readable recording medium, and the program recorded on the recording medium May be executed by causing the computer system to read and execute the above. 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, network system, 10 customer application, 11, 11A, 11B, 11N SDK, 20, 50 customer application, 30 store, 40, resident application, 41 application information acquisition unit, 42 information presentation unit , 45 browser, 60 dedicated application, 100 user terminal (terminal device), 101 initialization processing unit, 104 list request unit, 105 display control unit, 106 customer information notification unit, 107 reward grant notification unit, 110 input unit, 120 Display unit, 130 Terminal communication unit, 140 Terminal storage unit, 150 Terminal control unit, 200, 200a Management server (management device), 210 Communication unit, 220 management unit, 221 Application management unit, 222 Installation information management unit, 223 Information management unit, 230, 230a Storage unit, 231, 231a Elephant application information storage unit, 232 Normal reward information storage unit, 233 Inter-app filter storage unit, 234 Campaign period information storage unit, 235 Campaign participation application information storage unit, 236 Installation information storage unit, 237, 237a Customer information storage unit, 238 reward establishment information storage unit, 239 release scheduled application information storage unit, 240, 240a 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 Timekeeping unit, 247 Application information notification unit, 300 application server, 310 application server (game A), 320 application server (game B), 350 application server (game N), 400 application store, 500, 500a, 500 , Mutual customer guiding system

Claims (15)

Manages information related to the application before the start of provision, which is an application before the start of provision, among a plurality of target applications to be managed, and the identification information of the selected application selected in the terminal device from among the applications before the provision start A terminal device capable of communicating with a management device that associates with unique identification information that identifies a terminal device and manages it as a record of customer information for the application before the start of provision,
A list acquisition unit that acquires an application list of at least one application before starting provision from the management device;
The unique identification that identifies the terminal information of the customer information including identification information of the selected application selected from at least one of the pre-providing applications included in the application list acquired by the list acquisition unit A customer information notifying unit for transmitting to the management device in association with information;
A terminal device comprising: A presentation unit that presents a presentation list based on the application list of the pre-providing application acquired by the list acquisition unit;
The list acquisition unit
The application list is acquired from the management device, and each of the pre-providing applications included in the application list has been selected in the terminal device based on the record of the customer information managed by the management device Information indicating whether or not from the management device,
The presenting unit
When presenting the presentation list, based on the information indicating whether or not the selection is acquired, which is acquired by the list acquisition unit, the application before the provision start that has been selected in the local terminal device and the unselected provision before the provision start The terminal device according to claim 1, wherein the terminal device is presented separately from an application. An application information acquisition unit for acquiring information on the selected application from the management device;
An information presentation unit for presenting information on the selected application acquired by the application information acquisition unit;
The terminal device according to claim 2, further comprising: The terminal device according to claim 3, wherein the information related to the selected application is information indicating that the selection application has started to be provided. A list requesting unit for associating list request notification information for requesting an application list of at least one pre-providing application with the unique identification information for identifying the terminal device;
With
The list acquisition unit
5. The application list of the pre-providing application transmitted from the management device in response to the list request unit transmitting the list request notification information. 5. The terminal device described in 1. The list request unit includes:
From the target application running on its own terminal device, send the list request notification information to the management device,
The list acquisition unit
In the target application that transmitted the list request notification information, obtain an application list of the application before the provision start,
The customer information notifying unit
The identification information of the target application that acquired the application list of the application before starting provision, and the identification information of the selected application selected from at least one of the applications before starting provision included in the application list in the target application The terminal device according to claim 5, wherein the customer information included is transmitted to the management device in association with unique identification information that identifies the terminal device. It is determined whether or not the unique identification information is stored in the storage unit, the unique identification information is acquired when it is determined that the unique identification information is not stored in the storage unit, and the acquired unique identification information Is stored in the storage unit so that it can be referred to from any target application installed in the terminal device,
The terminal device according to any one of claims 1 to 6, further comprising: Installation notification information indicating that the target application installed in the terminal device is installed, and the installation notification information including the identification information of the target application is associated with the unique identification information that identifies the terminal device An installation notification unit to be transmitted to the management device,
The terminal device according to any one of claims 1 to 7, further comprising: The installation notification unit
Associating the installation notification information including the user information in the installed target application of the user who installed the installed target application and the identification information of the target application with the unique identification information that identifies the terminal device The terminal device according to claim 8, wherein the terminal device is transmitted to the management device. The management device manages a reception period indicating a period for receiving a selection for the application before starting provision in the terminal device,
The customer information notifying unit
The terminal device according to any one of claims 1 to 9, wherein the customer information is transmitted to the management device within the reception period. A transmission / reception unit that communicates the application list or the customer information with the management device or directly with the management device via a server device corresponding to the target application or the selected application installed in the terminal device. ,
The terminal device according to claim 1, further comprising: The transmission / reception unit communicates with the management apparatus directly after establishing a communication session with the installed target application or the selected application via the corresponding server apparatus. Item 12. The terminal device according to Item 11. Manages information related to the application before the start of provision, which is an application before the start of provision, among a plurality of target applications to be managed, and the identification information of the selected application selected in the terminal device from among the applications before the provision start A terminal device control method capable of communicating with a management device that associates with unique identification information that identifies a terminal device and manages it as a record of customer information for the pre-providing application,
Obtaining an application list of at least one pre-providing application from the management device;
Associating the customer information including identification information of the selected application selected from at least one pre-providing application included in the acquired application list with the unique identification information that identifies the terminal device Transmitting to the management device;
The control method characterized by including. Manages information related to the application before the start of provision, which is an application before the start of provision, among a plurality of target applications to be managed, and the identification information of the selected application selected in the terminal device from among the applications before the provision start A computer provided in a terminal device capable of communicating with a management device that associates with unique identification information that identifies a terminal device and manages it as a record of customer information for the application before starting provision,
Obtaining an application list of at least one pre-providing application from the management device;
Associating the customer information including identification information of the selected application selected from at least one pre-providing application included in the acquired application list with the unique identification information that identifies the terminal device Transmitting to the management device;
A program for running Manages information related to the application before the start of provision, which is an application before the start of provision, among a plurality of target applications to be managed, and the identification information of the selected application selected in the terminal device from among the applications before the provision start A software program incorporated in an application installed in a terminal device capable of communicating with a management device that associates with unique identification information that identifies a terminal device and manages it as a record of customer information for the pre-providing application,
On the computer,
Obtaining an application list of at least one pre-providing application from the management device;
Associating the customer information including identification information of the selected application selected from at least one pre-providing application included in the acquired application list with the unique identification information that identifies the terminal device Transmitting to the management device;
A program for running

Images