KR20150125743A - Profit share method and system for distributing application - Google Patents

Abstract

Disclosed are a profit share method and system for distributing application. The profit share method includes a step of concatenating a profit distribution rate set by the developer of the application with the application and storing it, a step of concatenating an editor who requires a promotion for the application, and a user who downloads the application though the marketing channel of the editor, with the application and storing it, and a step of sharing a sale according to purchase with the editor and the developer based on the profit distribution rate corresponding to the application when the user purchases contents though the application.

Description

PROFIT SHARE METHOD AND SYSTEM FOR DISTRIBUTING APPLICATION FOR DISTRIBUTING APPLICATIONS [0002]

Embodiments of the present invention relate to a revenue sharing method and system for distribution of applications.

Smartphones are fundamentally different from ordinary mobile phones, so you can add and use applications (called 'apps'), which are application programs, depending on their purpose. Users can generally download such applications through the App store and install and use them on their own devices.

The App Store is an online mobile content market that sells a variety of apps that can be installed on smartphones. Apps developed by developers such as individuals and businesses can be uploaded to the App Store and sold to users. In this case, the developer pays the app store a fee for the sale of the apps. In other words, developers can improve their accessibility to their apps by paying fees to existing app stores and distributing apps developed through existing app stores.

If you are recruiting an editor who is a promoter for your application and you are generating revenue through purchases related to the user's application that has downloaded the application in association with the editor, you can distribute the revenue between the developer and the editor based on the revenue- Provide a revenue sharing method and system that can be used.

Storing a revenue share ratio set by a developer of the application in association with the application; Associating and storing the user who has downloaded the application through the marketing channel of the editor and the application in association with each other; And a step of, when the user purchases the content through the application, sharing revenue from the purchase with the editor and the developer based on a profit distribution ratio corresponding to the application. / RTI >

According to one aspect, the marketing channel includes an on-line or off-line path for promoting download of the application by promoting the application to users, and the revenue sharing method includes a step of transmitting, And identifies the download of the application through the marketing channel using an identifier.

According to another aspect of the present invention, the profit sharing method is characterized in that, for a plurality of applications, a profit sharing ratio is set for each application.

According to another aspect of the present invention, in the revenue sharing method, a profit distribution ratio is set for each of a plurality of editors, for each editor based on public relations results for each editor.

According to another aspect of the present invention, there is provided a method for sharing a revenue, the method comprising: receiving, by a plurality of users who have downloaded the application through a marketing channel of the editor, And a distribution ratio is set.

According to another aspect of the present invention, when the profit distribution ratio of the application is changed by the developer, the profit distribution ratio applied to the sales is calculated based on the point at which the user downloads the application and the point at which the profit distribution ratio is changed The profit distribution ratio before the change or the profit distribution ratio after the change.

According to another aspect of the present invention, the revenue sharing method identifies a download through the marketing channel of the application using an identifier of the editor delivered through the user in the marketing channel.

According to another aspect of the present invention, the identifier of the editor is transferred through the user's terminal in the marketing channel according to the control of the app store app installed in the terminal of the user to provide the app store service have.

According to another aspect of the present invention, the step of associating and storing the editor, the user, and the application may include receiving an identifier of the editor, an identifier of the installer page, Receiving and storing information on an IP address, information on the terminal of the user and access time to the installation page of the terminal; Receiving information on an IP address of the download page, information on the terminal of the user, and information on the access time of the terminal to the download page through a download page for downloading the application; And identifying that the user has downloaded the application through the marketing channel by comparing the IP address, access times, and information of the terminal with the installation page and the download page have.

A profit distribution ratio storage unit for storing a profit distribution ratio set by a developer of an application in association with the application; An application-specific editor and a user-relationship storage unit for storing the application in association with the user who has downloaded the application through the marketing channel of the editor, and the application in association with each other; And a sales share unit for sharing sales of the purchase with the editor and the developer based on a profit distribution ratio corresponding to the application when the user purchases the content through the application. System is provided.

If you are recruiting an editor who is a promoter for your application and you are generating revenue through purchases related to the user's application that has downloaded the application in association with the editor, you can distribute the revenue between the developer and the editor based on the revenue- .

From the viewpoint of the editor, it is possible to obtain the profit from the promotion of the application. In addition, from the viewpoint of the developer, the advertisement effect of the application through the advertisement of the editor can be obtained and the profit of the editor can be shared only with the actual profit, You can proceed.

From the viewpoint of the App Store, it is possible to expect the advertisement revenue by selling the advertisement product that recruits the editor through the advertisement using the profit distribution ratio to the developers registering the application, and it is possible to induce the participation of the new developers through the more efficient advertisement have.

1 is a diagram illustrating a revenue sharing system in an embodiment of the present invention.
2 is a diagram illustrating a revenue sharing system in another embodiment of the present invention.
FIG. 3 is a diagram illustrating an example in which a profit distribution ratio is set for each application according to an embodiment of the present invention.
4 is a diagram illustrating an example in which a profit distribution ratio is set for each application and for each editor in an embodiment of the present invention.
5 is a diagram illustrating an example in which a profit distribution ratio is set for each application and for each user in an embodiment of the present invention.
FIG. 6 is a diagram illustrating an example in which a profit distribution ratio is set for each application for the same application in an embodiment of the present invention.
7 is a diagram illustrating a revenue sharing method according to an embodiment of the present invention.
8 is a diagram showing an example of a process of transmitting identification information in an embodiment of the present invention.
9 is a block diagram illustrating an internal configuration of a revenue sharing system according to an embodiment of the present invention.
10 is a flowchart illustrating a revenue sharing method according to an embodiment of the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

In the revenue sharing system and the revenue sharing method according to the embodiments of the present invention, a plurality of applications, editors as promoters for applications, and users who download applications through editors can be managed in association with each other . In addition, the revenue sharing system can further manage information related to revenue generated when a specific user purchases content (for example, a game item or a service provided by an application) through a specific application to generate revenue . A revenue sharing system can provide developers with information about revenue, and a developer can share revenue by providing rewards that are part of that revenue to the editor associated with the user who generated the revenue. At this time, the profit distribution ratio may be a rate of compensation that is shared with the editors among the profits, and can be freely set by a developer for each application, editor, user, or viewpoint.

1 is a diagram illustrating a revenue sharing system in an embodiment of the present invention. 1 shows a revenue sharing system 100, a developer system 110, an editor system 120, and a user system 130. [ Each of the systems may be implemented as a computer system including a memory, a processor, and a network interface, and may be a device capable of communicating with other systems by wire or wireless using a network interface.

The developer system 110 may include a device that a developer uses to communicate with the revenue sharing system 100 over a network. The developer system 110 can upload information about the application to the revenue sharing system 100 according to the operation of the developer. In one example, the information about the application may include information such as text, images and / or moving pictures associated with the application, and information on the profit share ratio. The revenue sharing system 100 can store and manage information about an uploaded application in a database in association with a developer.

The editor system 120 may include an apparatus that the editor uses to communicate with the revenue sharing system 100 over a network. The editor system 120 can select a specific application using information about the applications provided by the revenue sharing system 100. [ In this case, the revenue sharing system 100 can store and manage the selected application and the editor in a database, and the editor can promote the selected application to the users through the marketing channel.

In the present specification, 'marketing channel' may mean an online or offline path for the editors to promote the application to the users and induce the download. As an example of an online path, the editor a can set a link to the download page of the application along with information about the application on its mobile homepage. At this time, the user 1 visiting the mobile homepage of the editor using the terminal can visit the download page through the link to download and install the application. As an example of an offline route, the editor b may be a business operator operating a smartphone sales store. The editor b can promote the application to the user 2 who visited the smartphone to purchase the smartphone and direct the user to install the application on the smartphone purchased by the user 2 or directly install the application on the smartphone purchased by the user 2. [ How the user who has downloaded the application through various marketing channels in the revenue sharing system 100 can relate to the editor will be described in more detail later.

In addition, one editor may utilize a plurality of marketing channels. For example, the editor c may utilize a marketing channel that provides a link to the download page of the application through the site of editor c, and may promote the download and installation of the application in off-line. In view of the revenue sharing system 100, since the editor and the user who downloaded the application are related to each other, it is not important whether a user downloads and installs the application through a marketing channel among a plurality of marketing channels utilized by one editor . Therefore, the revenue sharing system 100 can recognize a plurality of marketing channels utilized by one editor simply as a marketing channel of the corresponding editor. The 'marketing channel' to be described later may refer to a marketing channel of the editor in terms of the revenue sharing system 100.

Further, the editor is not limited to a specific person, but may be identified as a specific site or a specific company. For example, a company may promote its applications using a variety of online / offline marketing channels of its own. As a more specific example, a company providing game-related information can induce users' interest by exposing their own banner advertisement for a game application through a company site through a company site.

The user system 130 may include a user's device. For example, the user system 130 may be a device such as a smart phone that can download and install the promoted application through a marketing channel.

If the user purchases the content from the application and generates revenue to the developer after downloading and installing the application to the user system 130 through the marketing channel of the editor, the developer can use a certain ratio (profit distribution ratio) By providing the corresponding compensation to the editor, the editors can voluntarily induce the application to be promoted to the users.

The revenue sharing system 100 may be implemented as a separate system as in the embodiment of FIG. 1, or may be implemented by a system included in the application store or a system associated with the application store.

2 is a diagram illustrating a revenue sharing system in another embodiment of the present invention. FIG. 2 illustrates an example in which the revenue sharing system 100 is implemented as a system included in the App Store system 210. FIG.

As described above, in the embodiment of FIG. 1, the developer system 110 separately transmits information on the application to the revenue sharing system 100, while in the embodiment of FIG. 2, the developer system 110 includes the application store system 210 ). ≪ / RTI > The developer can choose whether to promote the editor with the registered application. If the developer intends to promote using the editor, the developer can set the profit distribution ratio.

The editor accessing the application store system 210 through the editor system 120 can select a desired application among the applications and can promote the application through a marketing channel. The user can select an application in the user system 130 according to the advertisement of the editor Download and install. For example, the marketing channel may provide a link to a download page of an application provided by the application store system 210, and the user system 130 may download the application from the application store system 210 via the link May be installed in the user system 130.

In this case, if the user purchases the content from the application after downloading and installing the application to the user system 130 through the marketing channel of the editor, and the revenue is generated to the developer, the developer calculates a certain rate of profit ) Can be provided to the editor.

FIG. 3 is a diagram illustrating an example in which a profit distribution ratio is set for each application according to an embodiment of the present invention. The embodiment of FIG. 3 shows an example of the profit distribution ratio set by the developer of the application for each application with respect to the three applications of application A, application B, and application C. More specifically, FIG. 3 shows an example in which a profit distribution ratio is set such that application A is 10%, application B is 5%, and application C is 7%.

For example, user 1 represents a user who has downloaded application A and application B via editor a, respectively. If the user 1 purchases the content through the application A and the revenue is generated, the developer of the application A can share the revenue by providing 10% of the generated revenue to the editor a as compensation. As another example, if user 1 purchases content through application B and revenue is generated, the developer of application B can share revenue by providing 5% of the generated revenue to editor a as a reward.

4 is a diagram illustrating an example in which a profit distribution ratio is set for each application and for each editor in an embodiment of the present invention. In the embodiment of FIG. 4, the profit distribution ratios are set differently for each application, and the profit distribution ratios are also set differently for each editor.

For example, the revenue sharing system 100 can calculate the performance of each of the editors when the advertiser experiences the promotion through the editors. The performance of these editors can be provided to the developers of the application, and the developers can set different revenue sharing ratios for each editor to provide the editors who want to promote the application. In FIG. 4, the developer of the application A sets an income distribution ratio of 10% with respect to the editor a, and sets a profit distribution ratio of 7% with respect to the editor b.

5 is a diagram illustrating an example in which a profit distribution ratio is set for each application and for each user in an embodiment of the present invention. In the embodiment of FIG. 5, the profit distribution ratios are set differently for each application, and the profit distribution ratios are set differently for each user.

For example, a developer may set a 10% profit distribution ratio for a user who first downloaded an application through publicity using an editor, and set the profit distribution ratio at a certain rate (for example, 0.1 %), Respectively. 5 shows that for application A, 10% for editor a associated with user 1, 9.9% for editor a associated with user 2, 9.8% for editor a associated with user 3, and 10% for editor b associated with user 4 9.7% for user 5, and 9.6% for editor b related to user 5, for example, as the number of users who downloaded the application through advertisement using the editor increased, the profit distribution ratio with the editor related to the user decreased. Respectively.

In an embodiment different from the embodiment of FIG. 5, the developer may set the profit distribution ratio such that the profit distribution ratio increases at a certain rate as the user increases.

FIG. 6 is a diagram illustrating an example in which a profit distribution ratio is set for each application for the same application in an embodiment of the present invention. In FIG. 6, a time point t1 indicates a time when the developer sets the profit distribution ratio to 10%, and a time point t2 indicates a point in time when the user 1 downloads the developer's application through the editor a. At this time, the profit distribution ratio for the user 1 of the editor a can be set to 10%. In addition, the time point t3 may indicate the point in time when the developer re-sets the profit distribution ratio to 7%, and the point in time t4 may indicate the point in time when the user 2 downloaded the developer's application through the editor a. At this time, the profit distribution ratio for the user 2 of the editor a can be set to 7%. In other words, in the embodiment of FIG. 6, the profit distribution ratio of the editor to the user who downloaded the application through the marketing channel can be changed according to the profit distribution ratio finally set by the developer.

In this way, the developer can set the profit distribution ratio in various ways as needed, and the revenue sharing system 100 can provide the developer with an interface to set the profit distribution ratio in various ways.

Once the application, marketing channel (editor), and the revenue share ratio for the user are set once, this revenue share ratio can be fixed and unchanged.

In addition, the matching relationship between the editor and the user can be applied only to the user who installed the application for the first time. For example, if a user with a history of installing an application reinstalls the application, the user may be excluded from matching between the editor and the user.

Hereinafter, how the editor and the user are matched will be described.

7 is a diagram illustrating a revenue sharing method according to an embodiment of the present invention. 7 shows an example of a profit sharing process between the profit sharing system 700, the developer 710, the editor 720, and the user 730. The transfer of data between the revenue sharing system 700, the developer 710, the editor 720, and the user 730 is performed by the revenue sharing system 700, the developer 710, the editor 720, and the user 730 The data communication using the network between the devices is performed. In FIG. 7, the description of the devices will be omitted for the convenience of explanation.

At step 751, the developer 710 may register the application with the revenue sharing system 700. [ For example, the developer 710 may send information about the application to the revenue sharing system 100. In another embodiment, if the revenue sharing system 700 is a system included in the App Store system, the developer 710 may transmit information about the application and an installation file for installing the application to the App Store system.

Further, the developer 710 can set the profit distribution ratio for the application. At this time, the developer 710 can freely select a point at which to set the profit distribution ratio, and step 752 can be performed after the profit distribution ratio is set. For example, the revenue sharing system 700 may recruit editors using the revenue share ratio selected by the developer 710.

In step 752, the revenue sharing system 700 may provide identification information to the editor 720. For example, the revenue sharing system 700 allocates an editor identifier to an editor 720 that wants to promote a specific application, and generates an editor identifier and identification information including an application identifier of an application to be announced by the editor 720 And provide it to the editor 720. The application identifier may include an identification code of the application or a URL of a download page provided for downloading the application.

In another embodiment, the identification information may include an editor identifier and a campaign identifier. For example, a developer can start a campaign with a specific revenue share in relation to the application. In this case, the revenue sharing system 700 may generate the identification information including the campaign identifier together with the editor identifier, and provide it to the editor 720.

In step 753, the editor 720 may provide the identification information to the user 730 who wants to download the application via the marketing channel. For example, a page of the editor 720 provided as a marketing channel may include a link to a download page for downloading an application and a function for transmitting identification information to a terminal of the user 730 that selected the link . In the case of a marketing channel on the off-line, the editor 720 may directly input the identification information through the terminal of the user 730. [

At step 754, the user 730 may download and install the application to the terminal of the user 730. [ For example, the user 730 may access the download page of the application through the terminal and download and install the application. For example, the user 730 can access the download page through the terminal according to a link provided by an on-line marketing channel or an operation of the editor 720 on the off-line.

At this time, the identification information transmitted from the editor 720 to the user 730 may be transmitted from the user 730 to the revenue sharing system 700. In addition, a user identifier for identifying the user 730 may further be transmitted to the revenue sharing system 700. [ A more detailed process in which the identification information is transmitted to the profit sharing system 700 will be described in more detail later.

At step 755, the revenue sharing system 700 may associate and store the application, the editor 720, and the user 730. For example, the revenue sharing system 700 may store the user identifier and the application identifier included in the identification information in association with each other.

At step 756, the user 730 may purchase the content through the application. For example, the user 730 may purchase a game item in the process of installing the game application in the terminal. As another example, the user 730 may install an application that provides location-related services to the terminal and purchase usage rights of the advanced services to utilize the advanced services.

At step 757, the revenue sharing system 700 may provide revenue information to the developer 710. For example, the revenue sharing system 700 may include information about the content purchase of the user 730, information about the editor 720 associated with the user 730, and information about the rewards that reflect the revenue share ratio to the revenue, 710).

At step 758, the developer 710 may provide compensation to the editor 720.

8 is a diagram showing an example of a process of transmitting identification information in an embodiment of the present invention. The steps 810 to 890 included in the transfer process of FIG. 8 may be included in the step 754 described above with reference to FIG. 7, and may be performed by the user 730. FIG. The user 730 may be substantially the device of the user 730, as described above. Hereinafter, an example in which the steps 810 to 890 are performed by the terminal of the user 730 will be described.

In step 810, the terminal of the user 730 checks whether the app store application is installed, and performs step 820 if the app store application is installed, and performs step 840 if the app store application is not installed . The App Store app can be an application provided by the App Store system.

In step 820, the terminal of the user 730 checks whether the user 730 is logged in to the service. If the user is logged in, step 830 is performed. If the user is not logged in, step 850 is performed can do. Here, the service may be a service provided through the App Store application.

In step 830, the terminal of the user 730 can receive the installation file of the application through the App Store system and install the application.

In this way, when the app store application is installed in the terminal and the user logs in the service provided through the app store application, the terminal recognizes the identification information provided by the editor 720 according to the control of the app store application, To the shared system 700. In other words, the app store application may include a function for recognizing the identification information transmitted through the marketing channel and controlling the terminal to transmit the identification information to the profit sharing system 700.

In step 840, the terminal of the user 730 may install the App Store app. For example, a device can access the installation page of the App Store app to receive the installation file of the App Store app, and install the App Store app using the installation file received.

In step 850, the terminal of the user 730 confirms whether the user 730 is subscribed to the service, performs step 860 if the subscriber is subscribed, and performs step 870 if the subscriber is not subscribed can do.

In step 860, the terminal of the user 730 may process the process of the user 730 logging in to the service. For example, the terminal may forward the information entered by the user 730 to the revenue sharing system 700 or the App Store system to log in to the service. When the user 730 is logged in to the service, the terminal may perform step 830. [

In step 870, the terminal of the user 730 may process the process of the user 730 subscribing to the service. For example, the terminal may forward the information entered by the user 730 to the revenue sharing system 700 or the App Store system to subscribe to the service. If the user 730 is subscribed to the service, the terminal may perform step 860. [

As described above, if the application store application is installed in step 810 and the service store application is subscribed to the service provided through the application store application in step 820, the user 730 transmits the marketing channel of the editor 720 It can be easily tracked that the application is downloaded and installed.

On the other hand, if the app store application is not installed in step 810, the revenue sharing system 700 checks whether the user 730 has downloaded and installed the application through the marketing channel of the editor 720 Is difficult.

The revenue sharing system 700 then transmits the identification information received from the editor 720 to the user 730 in step 840, the IP address of the installation page of the app store application accessed by the terminal of the user 730, Information on the terminal (for example, device type, OS (Operating System) version, etc.) and information on the access time to the install page can be received and stored through the install page. In addition, if the terminal of the user 730 accesses the download page of the application in step 830, the revenue sharing system 700 transmits the IP address of the download page and information about the terminal (for example, device type, OS Operating System) version and the like) and the access time to the download page through the download page. At this time, the revenue sharing system 700 compares the IP address of the download page, the access time, and the information about the terminal accessing each page, and transmits the received information to the user 730, which has downloaded the application, It can be confirmed that the user 730 has received the identification information.

FIG. 9 is a block diagram illustrating an internal structure of a revenue sharing system according to an exemplary embodiment of the present invention. FIG. 10 is a flowchart illustrating a revenue sharing method according to an exemplary embodiment of the present invention.

The revenue sharing system 900 according to the present embodiment may include a processor 910, a bus 920, a network interface 930, and a memory 940. Memory 940 may include an operating system 941 and a revenue sharing routine 942. The processor 910 may include a revenue share ratio storage unit 911, an application-specific editor and user relationship storage unit 912, and a sales share unit 913. In other embodiments, revenue sharing system 900 may include more components than the components of FIG. However, there is no need to clearly illustrate most prior art components. For example, the revenue sharing system 900 may include other components such as a display or a transceiver.

The memory 940 may be a computer-readable recording medium and may include a permanent mass storage device such as a random access memory (RAM), a read only memory (ROM), and a disk drive. Also, the memory 940 may store program codes for the operating system 941 and the profit sharing routine 942. [ These software components may be loaded from a computer readable recording medium separate from the memory 940 using a drive mechanism (not shown). Such a computer-readable recording medium may include a computer-readable recording medium (not shown) such as a floppy drive, a disk, a tape, a DVD / CD-ROM drive, or a memory card. In other embodiments, the software components may be loaded into memory 940 via a network interface 930 rather than a computer-readable recording medium.

The bus 920 may enable communication and data transfer between components of the revenue sharing system 900. The bus 920 may be configured using a high-speed serial bus, a parallel bus, a Storage Area Network (SAN), and / or other suitable communication technology.

Network interface 930 may be a computer hardware component for connecting revenue sharing system 900 to a computer network. The network interface 930 may connect the revenue sharing system 900 to the computer network via a wireless or wired connection.

The processor 910 may be configured to process instructions of a computer program by performing basic arithmetic, logic, and revenue sharing system 900 input / output operations. The instructions may be provided by the memory 940 or network interface 930 and to the processor 910 via the bus 920. The processor 910 may be configured to execute program codes for the revenue share ratio storage unit 911, the application-specific editor and user relationship storage unit 912, and the revenue share unit 913. Such program code may be stored in a recording device such as memory 940. [

The revenue share ratio storage unit 911, the application-specific editor and user relationship storage unit 912, and the sales share unit 913 may be configured to perform the steps 1010 to 1030 of FIG.

In step 1010, the revenue share ratio storage unit 911 may store the profit sharing ratio set by the developer of the application in association with the application. For example, 10% of the revenue share of application A and application A can be stored in the database in association with each other.

In step 1020, the application-specific editor and user relationship storage unit 912 may store the user and the application downloaded through the marketing channel of the editor and the editor, requesting advertisement for the application, in association with each other. For example, for application A (editor a, user 1), matching relationships can be stored in association with each other.

In step 1030, when the user purchases the content through the application, the revenue sharing unit 913 may share the sales of the purchase with the editor and the developer based on the profit distribution ratio corresponding to the application. For example, suppose a 9: 1 revenue share ratio is established between a developer and a revenue sharing system (900). Also assume that the revenue share ratio for application A is 10%. In this case, 10% of sales can be shared with the revenue sharing system 900, and 90% of sales can be shared with developers. In addition, 90% of the revenue shared by the developer, and 10% of the revenue, can be shared back to the editor.

Here, the marketing channel may include an online or offline path for the editor to promote the application to the users and to guide the download of the application. At this time, the application-specific editor and user relationship storage unit 912 can identify the download through the marketing channel of the application using the identifier of the editor delivered from the user. For example, an application-specific editor and user relationship storage unit 912 may identify downloads of the application through the marketing channel using the identifier of the editor delivered via the user in the marketing channel.

The delivery of the identifier of such an editor has already been described in detail with reference to FIGS. 7 and 8. FIG. For example, the identifier of the editor may be transferred through the user's terminal in the marketing channel according to the control of the app store application installed on the user terminal in order to provide the app store service.

If such an app store application is not installed in the user's terminal, step 1020 is performed through an installation page for installation of the app store application for providing the app store service with the identifier of the editor, the IP address of the installation page, (Not shown) for receiving and storing information on the access point to the installation page of the terminal, information on the IP address of the download page, information on the user's terminal, A step (not shown) of receiving information on the access time to the download page, and comparing the IP addresses, the access times, and the terminal information of the install page and the download page to determine that the user has downloaded the application through the marketing channel (Not shown). The above-described unillustrated steps may also be performed by the application-specific editor and user relationship storage 912. The identifier of the editor may further include information for identifying the application or the campaign, in addition to information for identifying the editor.

In another embodiment, for a plurality of applications, a revenue share ratio may be set for each application. For example, even for applications of the same developer, the profit share ratio for application A may be set at 10%, while for application B, the profit share ratio may be set at 7%. This embodiment has already been described in detail with reference to FIG.

In another embodiment, for each of a plurality of editors, a profit distribution ratio may be set for each editor based on public relations results for each editor. For example, in the case of editor A, which induces users to generate a large amount of revenue, the profit sharing ratio is set to 10% for application A, while for editor b, The distribution ratio can be set to 7%. This embodiment has already been described in detail with reference to FIG.

In another embodiment, different revenue sharing ratios may be set for a plurality of users who downloaded the application through the marketing channel of the editor, based on the order in which a plurality of users downloaded the applications. For example, a revenue share ratio may be set so that a higher revenue share ratio is applied to a user with a faster download order for the same application A and a matched editor. Such an embodiment has already been described in detail with reference to FIG.

In yet another embodiment, the revenue share ratio can be changed in the middle and reset. At this time, the profit distribution ratio applied to the sales can be determined as the profit distribution ratio before the change or the profit distribution ratio after the change based on the point of time when the user downloaded the application and the profit distribution ratio was changed. Such an embodiment has already been described in detail with reference to FIG.

As described above, according to the embodiments of the present invention, when an editor, which is a promoter for an application, is collected and a profit is generated through purchases related to an application of a user who downloaded the application in association with the editor, You can distribute revenue between developers and editors based on your revenue share.

In addition, from the viewpoint of the editor, it is possible to obtain profit from the advertisement of the application, and from the viewpoint of the developer, by obtaining the advertisement effect of the application through the advertisement of the editor and sharing the profit with the editor only for the actual profit, .

Also, from the viewpoint of the App Store, it is possible to expect the advertisement revenue by selling the advertisement product that recruits the editor through the advertisement using the profit distribution ratio to the developers registering the application, and induce the participation of the new developers through the more efficient advertisement can do.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is to be understood that the invention is not limited to the disclosed exemplary embodiments. For example, it is to be understood that the techniques described may be performed in a different order than the described methods, and / or that components of the described systems, structures, devices, circuits, Lt; / RTI > or equivalents, even if it is replaced or replaced.

Therefore, other implementations, other embodiments, and equivalents to the claims are also within the scope of the following claims.

Claims (17)

Storing a revenue share ratio set by a developer of the application in association with the application;
Associating and storing the user who has downloaded the application through the marketing channel of the editor and the application in association with each other; And
Sharing sales of the purchase with the editor and the developer based on a profit distribution ratio corresponding to the application when the user purchases the content through the application
The method comprising the steps of: The method according to claim 1,
Wherein the marketing channel includes an on-line or off-line path for promoting downloading of the application by promoting the application to users,
And identifies the download through the marketing channel of the application using the identifier of the editor delivered from the user. The method according to claim 1,
Wherein a profit sharing ratio is set for each of a plurality of applications. The method according to claim 1,
Wherein a profit distribution ratio is set for each of the plurality of editors based on the public relations performance for each editor. The method according to claim 1,
Wherein a profit distribution ratio is set for each of a plurality of users who have downloaded the application through a marketing channel of the editor based on the order in which the applications are downloaded by the plurality of users . The method according to claim 1,
Wherein, when a profit distribution ratio of the application is changed by the developer, a profit distribution ratio applied to the sales is calculated based on a time when the user has downloaded the application and a profit distribution ratio before the change Or a profit distribution ratio after the change. The method according to claim 1,
Wherein the downloading through the marketing channel of the application is identified using the identifier of the editor delivered via the user in the marketing channel. 8. The method of claim 7,
Wherein the identifier of the editor is transferred through the user's terminal in the marketing channel under the control of an app store app installed in the terminal of the user to provide the app store service. 8. The method of claim 7,
The step of associating and storing the editor, the user and the application,
An installation page for installing an app store application for providing an app store service, an identifier of the editor, an IP address of the install page, information on the terminal of the user, and a time point of accessing the install page of the terminal Receiving and storing information;
Receiving information on an IP address of the download page, information on the terminal of the user, and information on the access time of the terminal to the download page through a download page for downloading the application; And
Comparing the IP address, access times and information about the terminal of the install page and the download page to identify that the user has downloaded the application through the marketing channel
The method comprising the steps of: A computer-readable recording medium having recorded therein a program for executing the method according to any one of claims 1 to 9. A profit distribution ratio storage unit for storing a profit distribution ratio set by a developer of an application in association with the application;
An application-specific editor and a user-relationship storage unit for storing the application in association with the user who has downloaded the application through the marketing channel of the editor, and the application in association with each other; And
A sales sharing unit for sharing sales of the purchase with the editor and the developer based on a profit distribution ratio corresponding to the application when the user purchases the content through the application,
And a profit sharing system. 12. The method of claim 11,
Wherein the marketing channel includes an on-line or off-line path for promoting downloading of the application by promoting the application to users,
And identifies a download through the marketing channel of the application using an identifier of the editor delivered from the user. 12. The method of claim 11,
Wherein a revenue sharing ratio is set for each of a plurality of applications. 12. The method of claim 11,
And a revenue sharing ratio is set for each of the plurality of editors based on the public relations performance for each editor. 12. The method of claim 11,
Wherein a profit distribution ratio different for each user is set for a plurality of users who have downloaded the application through the marketing channel of the editor based on the order in which the plurality of users downloaded the application. . 12. The method of claim 11,
Wherein, when a profit distribution ratio of the application is changed by the developer, a profit distribution ratio applied to the sales is calculated based on a time when the user has downloaded the application and a profit distribution ratio before the change Or a profit distribution ratio after the change. 12. The method of claim 11,
And identifies the download through the marketing channel of the application using the identifier of the editor delivered via the user in the marketing channel.

Images