Advertising system and method using in-app advertisement module

Abstract

The present invention relates to an advertising system and method using an in-App advertisement module, which is capable of displaying an advertisement on a lock screen through an advertisement module which is inserted in one or more application and is installed in parallel to the applications and distributing saved rewards to the applications according to a user input through the lock screen on which the advertisement is displayed, thereby allowing the saved rewards to be used as points.

Claims

1. A computer-implemented advertising (Ad) system using an in-App advertisement module for displaying advertisements provided by an Ad server on a lock screen of a mobile device, comprising: one or more processors including one or more applications installed in a computer-readable medium of the mobile device; one or more processors including an Ad module which is inserted in each application, is installed in parallel to each application without being integrated with the application, and is configured to display externally-received Ad information on the lock screen, detect, by the processors, event information generated according to a user input through the mobile device having a display, generate, by the processors, rewards if the detected event information satisfies reward generation conditions set in association with the Ad information, and transmit the generated rewards to the Ad server; and the Ad server, using server computer-readable medium, configured to provide the Ad information for the Ad module, save the rewards received from the Ad module in association with the mobile device and transmit the saved rewards so that the saved rewards can be used in at least one of the applications, wherein the rewards generation conditions are differently set depending on the Ad information, wherein the Ad module displays the Ad information on the lock screen without displaying the Ad information on an execution screen of the at least one of the applications, wherein the Ad module is configured to provide a user interface which receives user input through the mobile device to selectively activate the Ad module that saves the rewards for the application installed in parallel with the Ad module, wherein the user interface is provided through the application installed in parallel with the Ad module.

2. The computer-implemented Ad system according to claim 1, wherein the reward generation conditions include event information set for at least one selected from a group consisting of lock state release, input to a user interface inserted in the Ad information, access to an address linked to the Ad information through the use input, and installation of an application corresponding to the Ad information through the user input.

3. The computer-implemented Ad system according to claim 1, wherein, if a plurality of applications, which use the processors and in which the Ad modules are inserted, is installed in the mobile device, the Ad modules, wherein identification (ID) information of each application is stored in the corresponding Ad module, are integrated into the first-installed Ad module and the first-installed Ad module adds or deletes the ID information of the application according to addition or deletion of the application.

4. The computer-implemented Ad system according to claim 1, wherein the Ad module transmits ID information of the latest-executed application in interlocking with execution of the application, and the Ad server transmits saved rewards so that the saved rewards can be used in the latest-executed application based on the ID information.

5. The computer-implemented Ad system according to claim 4, wherein the Ad module provides the ID information of the application for the Ad server and the Ad server provides Ad information based on the application ID information.

6. The computer-implemented Ad system according to claim 1, wherein the saved rewards are distributed and transmitted by the Ad server to each of the one or more applications according to a predetermined ratio.

7. The computer-implemented Ad system according to claim 6, wherein the predetermined ratio is variable and dependent on the number of installed applications.

8. The computer-implemented Ad system according to claim 6, the predetermined ratio is variable and dependent on user input received from the mobile device.

9. The computer-implemented Ad system according to claim 1, wherein the Ad server transmits the saved rewards to a server corresponding to each application and registers the saved rewards in the server so that the saved rewards can be used to purchase items or goods.

10. The computer-implemented Ad system according to claim 9, wherein the Ad server exchanges rewards assigned for each application for points according to an exchange rate set for each application and registers the points in the server corresponding to each application in association with user information of the mobile device.

11. The computer-implemented Ad system according to claim 1, wherein the one or more applications each comprises one or more items available for purchase by the user using the rewards.

12. The computer-implemented Ad system according to claim 1, wherein the Ad module displays multiple Ad information received from the Ad server on the lock screen at set intervals.

13. A computer-implemented advertising (Ad) method using an in-App advertisement module for providing Ads for a mobile device in communication of an Ad module with an Ad server the Ad module being inserted in one or more applications installed in the mobile device and being installed in parallel to each of the applications without being integrated with the application, comprising: a first step where the Ad module requests, by one or more processors, the Ad server to provide Ad information; a second step where the Ad module displays the Ad information received from the Ad server on a lock screen of the mobile device having a display; a third step where the Ad module detects, by the processors, event information generated according to a user input through the mobile device and compares the event information with reward generation conditions set to correspond to the Ad information; a fourth step where the Ad module generates, by the processors, rewards based on a result of the comparison of the third step and transmits the generated rewards to the Ad server; and a fifth step where the Ad server, using server computer-readable medium, saves the rewards received from the Ad module to correspond to the mobile device and transmits the saved rewards so that the saved rewards can be used in at least one of the applications, wherein the reward generation conditions are differently set according to the Ad information, wherein the Ad module displays the Ad information on the lock screen without displaying the Ad information on an execution screen of the at least one of the applications, wherein the Ad module is configured to provide a user interface which receives user input through the mobile device to selectively activate the Ad module that saves the rewards for the application installed in parallel with the Ad module, wherein the user interface is provided through the application installed in parallel with the Ad module.

14. The computer-implemented Ad method according to claim 13, wherein the reward generation conditions include event information set for at least one selected from a group consisting of lock state release, input to a user interface inserted in the Ad information, access to an address linked to the Ad information through the use input, and installation of an application corresponding to the Ad information through the user input.

15. The computer-implemented Ad method according to claim 13, wherein the first step includes: by the Ad module, transmitting stored identification (ID) information of each of the applications to the Ad server, and wherein the second step includes: receiving Ad information based on the ID information of each of the applications from the Ad server.

16. The computer-implemented Ad method according to claim 13, wherein the first step includes: by the Ad module, transmitting ID information of the latest-executed application to the Ad server, and wherein the fifth step includes: by the Ad server, transmitting the saved rewards so that the saved rewards can be used in an application corresponding to the ID information received from the Ad module.

17. The computer-implemented Ad method according to claim 13, wherein the fifth step includes: by the Ad server, distributing and transmitting the saved rewards at a ratio set for each of the applications so that the saved rewards can be used in each of the applications.

18. The computer-implemented Ad method according to claim 17, wherein the fifth step includes: by the Ad server, varying the set ratio according to the number of applications installed in the mobile device.

19. The computer-implemented Ad method according to claim 17, wherein the fifth step includes: by the Ad server, receiving a user input provided from the mobile device and varying the set ratio according to the received user input.

20. The computer-implemented Ad method according to claim 13, wherein the fifth step includes: by the Ad server, transmitting the saved rewards to a server corresponding to each of the applications and registering the saved rewards so that the saved rewards can be used to purchase items or goods.

21. The computer-implemented Ad method according to claim 20, wherein the fifth step includes: exchanging rewards assigned to each of the applications for points according to an exchange rate set for each of the applications and registering the points in association with user information of the mobile device corresponding to each of the applications.

22. The computer-implemented Ad system according to claim 3, wherein the Ad module provides the ID information of the application for the Ad server and the Ad server provides Ad information based on the application ID information.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) The above and/or other aspects and advantages of the present invention will become apparent and more readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings of which:

(2) FIG. 1 is a configuration environment view of an Ad system using an in-App Ad module according to an embodiment of the present invention.

(3) FIG. 2 is a configuration view showing installation of an Ad module constituting an Ad system using an in-App Ad module in a user terminal according to an embodiment of the present invention.

(4) FIG. 3 is a configuration view showing Ad module integration of an Ad system using an in-App Ad module according to an embodiment of the present invention.

(5) FIG. 4 is an operation configuration view of an Ad module depending on a change in state of an application according to an embodiment of the present invention.

(6) FIG. 5 is an operation configuration view of an Ad system using an in-App Ad module according to an embodiment of the present invention.

(7) FIG. 6 is a configuration view showing application reward distribution, according to a user input, of an Ad system using an in-App Ad module according to an embodiment of the present invention.

(8) FIG. 7 is a configuration view showing parallel installation, execution and Ad output of an in-App Ad module according to another embodiment of the present invention.

(9) FIG. 8 is a detailed configuration view of an Ad module according to an embodiment of the present invention.

(10) FIG. 9 is a configuration view showing event detection depending on a user input through Ad information displayed on a lock screen of an Ad module according to an embodiment of the present invention.

(11) FIG. 10 is a configuration view showing selective Ad reception of an Ad module and Ad information reward generation conditions according to an embodiment of the present invention.

(12) FIG. 11 is a detailed configuration view of an Ad server constituting an Ad system using an in-App Ad module according to an embodiment of the present invention.

(13) FIG. 12 is an operation configuration view showing reward distribution, according to a user input, of an Ad system using an in-App Ad module according to an embodiment of the present invention.

(14) FIG. 13 is a configuration view showing reward distribution setup, according to a user input, of an Ad system using an in-App Ad module according to an embodiment of the present invention.

(15) FIG. 14 is an operation configuration view showing application reward exchange of an Ad system using an in-App Ad module according to an embodiment of the present invention.

(16) FIG. 15 is a sequence diagram showing an advertising method of an Ad system using an in-App Ad module according to an embodiment of the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

(17) An Ad system using an in-App Ad module according to an embodiment of the present invention will now be described in detail with reference to the drawings.

(18) FIG. 1 is a configuration environment view of an Ad system using an in-App Ad module according to an embodiment of the present invention. Referring to FIG. 1, the Ad system using an in-App Ad module includes a plurality of user terminals 10, each of which is installed with a plurality of applications 20, an App store server 300 for providing the plurality of applications 20 for each user terminal 10 via a network, a membership database (DB) 220 for storing user information (membership information) of each user terminal 10, an Ad DB 210 for storing advertisements, and an Ad server 200 for providing the advertisements stored in the Ad DB 210 for each user terminal 10 via the network.

(19) Examples of the user terminals 10 used herein may include smart phones, PDAs (Personal Digital Assistants) and the like.

(20) The Ad system using an in-App Ad module may include an Ad module 100 which is inserted in an application 20 installed in each user terminal 10 and is installed along with the application 20. The Ad module 100 may be configured in an in-App form.

(21) As shown in FIG. 2, when the Ad module 100 is inserted in different applications 21, 22 and 23 and the applications 21, 22 and 23 are installed in each user terminal 10, the Ad module 100 may be installed in the user terminal 10 along with the applications 21, 22 and 23.

(22) In addition, as shown, when a plurality of Ad modules 101, 102 and 103 inserted in the plurality of different applications 21, 22 and 23 are installed in parallel, the plurality of Ad modules may be integrated into a single Ad module 100.

(23) In this case, each Ad module 101, 102 and 103 may store identification (ID) information of the different applications and the single Ad module 100 may store application ID information on one or more of the different applications.

(24) In more detail, as shown in FIG. 3A, if AD module1 101 first installed in the user terminal along with App1 21 exists, Ad module2 102 and Ad module3 103 respectively inserted in App2 22 and App3 23 installed later are not installed in parallel and ID values (key values) of App2 22 and App3 23 respectively stored in Ad module 2 and Ad module3 may be stored in Ad module1 101. At this time, Ad module2 102 and Ad module3 103 are overlapped with Ad module1 101 and the ID information of App2 22 and App3 23 can be stored in Ad module1 101.

(25) Accordingly, Ad module1 101 stores the ID information of App1 to App3 21, 22 and 23 to be integrated into the single Ad module 100 as shown in FIG. 3B and the Ad module 100 communicates with the Ad server 200 to output Ad information received from the Ad server 200 on a lock screen of the user terminal 10.

(26) Accordingly, the Ad module 100 can provide information for identifying an application installed in the user terminal 10 by transmitting one or more different information stored therein to the Ad server 200, and the Ad server 200 can determine the status of the application installed in the user terminal based on the one or more ID information received from the Ad module 100.

(27) On the other hand, the Ad module 100 integrally installed in the user terminal can store the ID information on the one or more applications 21 and 22 as described above, and, as shown in FIG. 4A, the Ad module 100 can receive the Ad information from the Ad server 200 and output the received Ad information to a lock screen 30 of the user terminal 10.

(28) At this time, as shown in FIG. 4B, if one 21 of the applications installed in the user terminal is deleted, the Ad module 100 can delete ID information corresponding to the deleted application 21 among the stored ID information.

(29) Accordingly, the Ad module 100 can transmit the current stored one or more ID information to the Ad server 200 at a request for transmission of Ad information to the Ad server 200, and the Ad server 200 can determines the deleted application based on the ID information received from the Ad module 100.

(30) In addition, the Ad module 100 can provide a user interface to allow a user to determine whether to activate the Ad module 100, as shown in FIG. 4C, in interlocking with the user terminal 10 in which a mobile operating system (OS) is installed, and can activate the Ad module selectively based on a user input received through the user terminal. Accordingly, if the user does not want the Ad information to be displayed on the lock screen, the Ad module is deactivated to prevent the Ad information from being displayed on the lock screen. At this time, the user interface to allow the user to determine whether to activate the Ad module 100 may be provided through the application in addition to the mobile OS installed in the user terminal.

(31) A detailed operation configuration of the Ad system using the Ad modules included in the application according to an embodiment of the present invention with the configuration described above will now be described with reference to FIG. 5. As shown, Ad module1 101 and Ad module2 102 respectively inserted in the applications 21 and 22 installed in the user terminal 10 are installed along with the applications and are integrated into the single Ad module 100 in the user terminal 10 ({circle around (1)}). In addition, the Ad module 100 can be activated upon completion of the installation or activated according to a user input through the user terminal 10. At this time, if an application in which the Ad module is inserted is initially installed in the user terminal 10, the Ad module is installed together without being integrated with the application.

(32) Accordingly, the activated Ad module 100 can receive Ad information from the Ad server 200 ({circle around (2)}) and display the Ad information on the lock screen 30 of the user terminal 10 ({circle around (3)}).

(33) Lock screen 30 used herein will be described in detail below. The user terminal 10 is set to be in a locking state to prevent the user terminal 10 from malfunctioning due to persistent generation of an input through a touch screen, an external input button or the like irrespective of the intention of the user. Accordingly, the user terminal 10 displays the lock screen 30 on a display of the user terminal according to the locking state at initial driving and can use a desired function by releasing the locking only when a preset input corresponding to the release of the locking state.

(34) The Ad module according to the present invention is preferably executed in iOS as an Apple's mobile OS, Android as a Google's mobile OS, or the like but is not limited thereto.

(35) As a result, unlike existing Ad serve models proceeding with an advertisement in the form of a banner or pop-up on a screen provided by an application, thereby hindering use of the application, the Ad module does not hinder the use of the application by displaying the Ad information on the lock screen displayed on the display of the user terminal.

(36) In particular, for a game application having a game screen on which a user input is generated as a whole, if Ad information is displayed on a portion of the game screen, hindrance to the progress of game due to erroneous input for the Ad information occurs frequently. However, the present invention provides no possibility of occurrence of erroneous input by displaying the Ad information on the lock screen without displaying the Ad information on an execution screen of the application and can provide more effective Ad information than a limitative Ad form such as a banner or a pop-up by displaying the Ad information on the lock screen.

(37) Here, the Ad information may include image data, video data, flash data and the like to improve a static Ad form subordinate to a screen provided by an existing application, thereby providing a high-concentration level of advertisements.

(38) In the meantime, the Ad module 100 can detect event information generated according to a user input through the user terminal 10 ({circle around (4)}), compare the event information with a reward generation condition preset to correspond to the Ad information, generate a reward if the event information corresponding to the reward generation condition is detected, and transmit the generated reward to the Ad server 200 ({circle around (5)}).

(39) As used herein, the term reward refers to a kind of cyber money paid to users in association with Ad information, which can be used to use services provided by applications.

(40) In addition, the reward generation condition may be set with a variety of event information based on user inputs including release of the lock state, input to the user interface inserted in the Ad information, access to an address linked to the Ad information through the use inputs, access to the App store server 300 through the Ad information for installation of an application corresponding to the Ad information, etc.

(41) Thereafter, the Ad server 200 can save the reward provided from the Ad module 100 installed in the user terminal 10 and transmit the saved reward to a server corresponding to the application so that the saved reward can be used in at least one of the applications 21 and 22 installed in the user terminal 10 ({circle around (6)}).

(42) In the above-described procedure, the Ad module 100 can store the ID information on App1 21 and App2 22 and transmit it to the Ad server 200.

(43) Accordingly, the Ad server 200 can identify App1 21 and App2 22 installed in the user terminal 10 based on the ID information received from the Ad module 100 and provide the saved reward so that the saved reward can be used in at least one of App1 21 and App2 22.

(44) As one example, as shown in FIG. 6, the Ad server 200 can provide information on the saved reward through a web site of the Ad server 200 and provide a setup interface for allocating the saved reward to a desired application through the web site according to a user input received from the user terminal 10 accessed the web site.

(45) Accordingly, the Ad server 200 transmits the reward input for each application 21 and 22 to a server corresponding to each application 21 and 22 based on the user input through the setup interface so that the reward can be used in an application desired by the user.

(46) In addition, the Ad server 200 can automatically distribute the saved rewards to each application 21 and 22 at a preset ration and transmit the distributed rewards to a server corresponding to each application, as will be described below.

(47) In addition, the Ad server 200 can exchange the rewards, which are distributed for each of the applications 21 and 22 in which the Ad modules 101 and 102 are respectively inserted, for points corresponding to each application 21 and 22 and register and save the points in a server associated with each application 21 and 22.

(48) At this time, it is obvious that the Ad server 200 can provide rewards distributed with no exchange to each application-related server where exchange is achieved or the rewards are used as points.

(49) Accordingly, a user can use rewards saved through Ad information watching or specific input as points used for purchase of goods such as items provided by each application.

(50) Accordingly, as shown, rewards saved through the single Ad module 100 into which Ad module1 101 and Ad module2 102 respectively inserted in game App1 21 and game App2 22 installed in the user terminal are integrated are distributed to the game applications 21 and 22 and are exchanged for points corresponding to game App1 21 and game App2 22 to purchase items provided by each game application 21 and 22. In addition, the saved rewards can be intensively allocated to one application desired by the user.

(51) On the other hand, in addition to the above-described configuration, as shown in FIG. 7, if a plurality of Ad modules 101 and 102 inserted in different applications 21 and 22 are installed in parallel, these Ad modules may be individually installed in parallel without being integrated and a corresponding installed Ad module may be executed when each application is executed.

(52) Referring to FIG. 7A in more detail, the applications 21 and 22 corresponding respectively to the Ad modules 101 and 102 are installed and an Ad module corresponding to an application executed in the user terminal can be executed to display an advertisement on the lock screen of the user terminal.

(53) At this time, when each of the Ad modules 21 and 22 stores the ID information of a corresponding application and is activated with execution of the corresponding application, each of the Ad module can transmit the stored ID information to the Ad server 200. Accordingly, as will be described later, the Ad server 200 can transmit Ad information associated with the received ID information to the activated Ad module.

(54) On the other hand, if App2 22 is executed to activate Ad module2 102 while Ad module1 101 is activated together App1 21 corresponding to Ad module1 101 to output Ad information in FIG. 7A, Ad module2 102 stops (deactivate) the execution of Ad module1 101 and can be activated to display the Ad information on the lock screen 30 of the user terminal.

(55) At this time, each of the Ad modules can interlock with an application and an Ad module having the same ID information as the latest-executed application can be operated to display the Ad information on the lock screen.

(56) Accordingly, Ad module2 102 can replace the ID information of App1 21 stored in Ad module1 101 with the ID information of App2 22 stored in Ad module 2 102, transmit the ID information of App2 22 to the Ad server 200, receives Ad information from the Ad server 200, and display the Ad information on the lock screen 30 of the user terminal.

(57) Accordingly, while stopping Ad module1 101 to output the Ad information associated with App1 21, the activated Ad module2 102 can display the Ad information associated with App2 22 on the lock screen 30 of the user terminal.

(58) In addition, as shown in FIG. 7B, the Ad modules 101 and 102 independently installed in parallel to correspond respectively to the applications 21 and 22 may be added and deleted in association with addition and deletion of the applications 21 and 22. Accordingly, as shown, if App1 21 is deleted, Ad module1 101 installed in parallel to App1 21 can be deleted together.

(59) Even in this case, irrespective of the deletion of App1 and Ad module1, when App2 22 is executed, Ad module2 202 is executed to still display the Ad information on the lock screen 30 of the user terminal.

(60) On the other hand, as shown in FIG. 7C, each application 20 can receive information on whether or not the Ad module 100 installed in parallel to the application 20 is activated, through a user input of the user terminal, and, based on this activation information, it is determined whether to execute the Ad module 100 and, based on this determination, the Ad information can be selectively displayed on the lock screen 30 of the user terminal.

(61) In the configuration of FIG. 7, each Ad module can save rewards in the Ad server and the rewards saved in the Ad server can be distributed to applications, which can result in extension of a range of use of rewards.

(62) According to the above-described configuration, the Ad modules are inserted in specific applications and are installed in parallel in the user terminal. However, the range of use of rewards generated by the Ad modules is not limited to the specific applications but the rewards may be used to purchase goods of different applications with Ad modules inserted therein. This may result in extension of the range of use of rewards by users.

(63) In addition, although one of applications in which the Ad module is deleted, since an Ad module installed in another application can consistently display Ad information on the lock screen, an advertiser can proceed with an advertisement stably if only Ad information is provided to the Ad server, without cling to preference of an application having a short cycle duration. In addition, if preference of a particular application in which an Ad module is inserted becomes high, the advertiser can benefit from increase in the preference of the particular application without any separate intervention.

(64) FIG. 8 is a detailed configuration view of the above-described Ad module 100. As shown, the Ad module 100 may include an Ad information collection unit 110, an activation unit 120, a lock screen interlocking unit 140, an event detecting unit 150, a reward processing unit 160 and a controller 130.

(65) First, the Ad information collection unit 110 can receive Ad information in communication with the Ad server 200 and provide the Ad information to the controller 130.

(66) The controller 130 can provide the Ad information can transmit the Ad information received from the Ad information collection unit 110 to the lock screen interlocking unit 140, and the lock screen interlocking unit 140 can detect a locking state of the user terminal 10 and display the Ad information on the lock screen based on the locking state.

(67) The activation unit 120 can receive a user input through the user terminal 10, receive selection information on activation or deactivation of the Ad module 100, and transmit the selection information to the controller 130.

(68) The controller 130 can control the Ad information collection unit 110 based on the selection information to determine whether or not the Ad information is received.

(69) The event detecting unit 150 can detect event information generated according to the user input through the user terminal, receive the preset reward generation conditions corresponding to the Ad information displayed on the lock screen from the controller 130, compare the reward generation conditions with the event information, generate result information if the event information satisfies the reward generation conditions, and transmit the result information to the reward processing unit 160.

(70) At this time, the reward generation conditions may be stored in the Ad information and different reward generation conditions may be set depending on the type of Ad information.

(71) A configuration of the event detecting unit 150 as described above will now be described in more detail with reference to FIG. 9. The event detecting unit 150 can receive the reward generation conditions corresponding to the Ad information 40 from the controller 130 when the Ad information 40 is displayed on the lock screen 30, detect an event generated according to a user input, generate result information based on whether or not the detected event matches with the reward generation conditions, and transmit the result information to the reward processing unit 160.

(72) As one example, as shown in FIG. 9A, if the reward generation conditions corresponding to the Ad information 40 displayed on the lock screen 30 is locked state release 31, the event detecting unit 150 can detect an event for the locked state release 31 according to the user input and transmit result information 50 to the reward processing unit 160 if the locked state is released.

(73) In addition, as shown in FIG. 9B, if the reward generation conditions corresponding to the Ad information 40 displayed on the lock screen 30 are installation of an application corresponding to the Ad information, the event detecting unit 150 can detect an access to the App store server 300 through a user input for the user interface 51 inserted in the Ad information, detect application installation 62 corresponding to the As information 40 from the App store server 300, and transmit result information to the reward processing unit 160 upon completion of the installation. At this time, the event detecting unit 150 may not generate result information if the installation is not completed after the access to the App store server 300.

(74) If the reward generation conditions are a user input for the user interface 51 inserted in the Ad information, the event detecting unit 150 can generate result information only with an input for the user interface inserted in the Ad information. If the reward generation conditions are an access to an address linked to the Ad information, the event detecting unit 150 can generate result information only with an address access through the Ad information.

(75) The reward generation conditions may include event information on actions such as bookmark addition, membership joining, recommendation function supported by SNS (Social Networking Service), secondary viral advertisement and so on, which can be obtained with an access to a Web page linked to the Ad information according to CPA (Cost Per Action), event information on actions of purchasing real goods with an access to a Web page according to CPS (Cost Per SALE), and event information on membership joining through the Ad information according to CPL (Cost Per Lead). Such reward generation conditions may be differently set for different Ad information, as described above.

(76) The reward processing unit 160 can receive the result information, generate rewards based on the result information, and transmit the generated rewards to the Ad server 200 which then accumulate the rewards.

(77) The event detecting unit 150 can set rewards having different values depending on different reward generation conditions and provide the set rewards as result information, and the reward processing unit 160 can generate rewards based on the reward values included in the result information. In addition, the reward processing unit 160 can generate rewards having different values for different Ad information in association with the controller 130.

(78) Based on the above-described configuration, the Ad module can selectively receive advertisements associated with applications installed in the user terminal, an embodiment of which will be described in detail below with reference to FIG. 10.

(79) Referring to FIG. 10, the controller 130 may include an App identification unit 131, an Ad information selection unit 132 and a reward creation condition setting unit 133. The App identification unit 131 can store ID information on one or more applications installed in the user terminal 10 and transmit the stored ID information to the Ad information collection unit 110.

(80) Then, the Ad information collection unit 110 can transmit the ID information to the Ad server 200. The Ad server 200 can provide advertisements associated with applications installed in the user terminal based on the ID information. As one example, the Ad server 200 can transmit Ad information provided by an advertiser, for example, a developer of an application installed in the user terminal 10, to the Ad information collection unit 110.

(81) In addition to the above-described configuration, the Ad information selection unit 132 can select one of multiple Ad information provided by the Ad information collection unit 110 and transmit the selected Ad information to a lock screen interlocking unit 140. The lock screen interlocking unit 140 can display the selected Ad information on the lock screen.

(82) The Ad information selection unit 132 can transmit multiple Ad information to the lock screen interlocking unit 140 one by one at preset intervals and display the individual Ad information sequentially on the lock screen.

(83) Further, the Ad information selection 132 can transmit the selected Ad information to the reward generation condition setting unit 133. The reward generation condition setting unit 133 can extract the reward generation conditions included in the Ad information and transmit the extracted reward generation conditions to the event detecting unit 150.

(84) Then, the event detecting unit 150 can compare the reward generation conditions with user input-based event information and generate result information based on a result of the comparison, as described above.

(85) FIG. 11 shows a detailed configuration of the Ad server 200 according to the embodiment of the present invention. As shown, the Ad server 200 may include an App managing unit 201, an Ad managing unit 202, a reward saving unit 203, a reward distribution unit 204, a reward exchange unit 205, a point registration unit 206, a membership DB 220 for storing membership information related to the user terminal, and an Ad DB 210 for storing Ad-related information.

(86) First, the App managing unit 201 can determine a status of installation of an application in which an Ad module is inserted among applications installed in the user terminal 10 in communication with the user terminal 10. Specifically, the Ad module 100 installed in parallel to one or more different applications can transmit stored one or more application ID information to the App managing unit 201, and then, the App managing unit 201 can identify an application in which an Ad module is inserted, based on the one or more application ID information transmitted from the Ad module 100 in correspondence to the user terminal. Accordingly, the App managing unit 201 can store the one or more application ID information, as application installation status information 221, in membership information of the membership DB 220 corresponding to the user terminal 10.

(87) The Ad managing unit 202 can transmit the Ad information stored in the Ad DB 210 to the Ad module 100 installed in parallel to the application in the user terminal. At this time, application ID information 212 and multiple Ad information 213 corresponding to each application in which the Ad module 100 is inserted may be stored in the Ad DB 210. Then, the Ad managing unit 202 can compare the application installation status information 221 of the membership DB 220 with the application ID information to identify the application installed in the user terminal and transmit the Ad information corresponding to each application to the Ad module 100 installed in the user terminal 10. At this time, the Ad information may be stored in the Ad DB 210, irrespective of the application, in which case it is obvious that the Ad managing unit 202 can randomly select and transmit the Ad information to the Ad module 100.

(88) Accordingly, since an advertiser can directly insert an Ad module in his/her application and provide his/her related Ad information for the Ad server, as the frequency of installation of his/her application by users becomes high, his/her related Ad information can be intensively displayed on the lock screen of the user terminal, which can lead to increase in Ad effects. With this configuration, the present invention can actively induce the advertiser to insert the Ad module in his/her application.

(89) The reward saving unit 203 can save rewards generated by the Ad module and store accumulated reward information 222 in the membership information of the membership DB 220 corresponding to the user terminal 10, and the reward distribution unit 204 can transmit the saved rewards according to the accumulated reward information 222 to a server corresponding to an application desired by a user according to a user input through the user terminal, thereby allowing the user to use the rewards in the corresponding application.

(90) In addition, the reward distribution unit 204 can distribute the saved rewards for each application according to the application installation status information 221.

(91) At this time, as shown in FIG. 12, the reward distribution unit 204 can distribute the saved rewards for each application in which each Ad module is inserted, at ratios set based on the number of applications installed in the user terminal according to the application installation status information 221.

(92) As one example, as shown in FIG. 12A, the reward distribution unit 204 can set a high distribution ratio of the saved rewards for the first installed App1 and adjust the distribution ratio to a ratio set according to App2 and App3 installed thereafter, thereby distributing the saved rewards at a ratio of 4:3:3 (10 in total) for App1 to App3. In this case, the set ratio may be variably set along with installation of each application. As one example, the reward distribution unit 204 may set the distribution ratio to 10/10 according to the set ratio when App1 is installed in the user terminal, thereafter, set the distribution ratio for App1 to 5/10 according to the set ratio when App2 is installed in the user terminal, and set the distribution ratio for App1 to 4/10 according to the set ratio when App3 is installed in the user terminal.

(93) Thereafter, if App3 is deleted, the reward distribution unit 204 can adjust the distribution ratio for App1 and App2 to 5:5 (10 in total), as shown in FIG. 12B, by adjusting the distribution ratio to the set ratio based on the number of installed applications.

(94) Thereafter, if App4 is installed, the reward distribution unit 204 can adjust the distribution ratio for App1, App2 and App4 to 4:3:3 (10 in total), as shown in FIG. 12C, by adjusting the distribution ratio to the set ratio based on the number of installed applications.

(95) The above-described distribution scheme of FIG. 12 is merely one example. It is obvious that the reward distribution unit 204 can adjust the distribution ratio to the set ratio based on information on download rank or popularity rank of an application provided by the App store server 300, or alternatively, may employ other different schemes. It is also obvious that a variety of schemes may be applied to the distribution ratio adjustment for application deletion and addition.

(96) In addition, as shown in FIG. 13, the Ad server 200 can provide a Web site for reward distribution setting and the reward distribution unit 204 can receive a user input from the user terminal 10 accessed the Web site and adjust the distribution ratio of the applications installed in the user terminal 10 according to the user input. In addition, the reward distribution unit 204 can store the distribution ratio adjusted according to the user input, as reward distribution setting information 223, in the member DB 200 in association with membership information of the user terminal. In this case, as a matter of course, the distribution ratio may be adjusted so that the saved rewards are assigned only for one application.

(97) As a result, rewards can be intensively assigned for an application desired by a user.

(98) The point registration unit 206 can transmit a reward assigned for each application in which an Ad module is inserted, according to the distribution ratio, to an application-related server 400 related to each application and, then, a user can use the reward to purchase items or goods provided by the application-related server 400 through the applications installed in the user terminal.

(99) In this case, since values of rewards for points used to purchase the items or goods for each application in which the Ad module 100 is inserted may be different, the Ad server 200 according to the present invention may further include the reward exchange unit 205 for supporting exchange of the rewards for points for each application. In this case, the points may include electronic money unit supported by each application. As one example, the points may include a variety of names such as point, gold and so on.

(100) The Ad DB 210 may store application exchange information 211. The App exchange information 211 may include point-related information used to purchase the items or goods for each application, and information on exchange rates between the rewards and the points.

(101) Accordingly, the reward exchange unit 205 can exchange the rewards assigned for each application for points supported by each application and transmit the points to the point registration unit 206. The point registration unit 206 can transmit the points to the App-related server 400 for saving.

(102) As one example of an operation configuration for the above-described reward exchange unit 205, as shown in FIG. 14, if saved rewards 100 are distributed at a ratio of 5:5 for App1 and App2, the reward exchange unit 205 and if a value (exchange rate) of point vs. reward in App1 is 1:1, the reward exchange unit 205 can exchange assigned 50 rewards for 50 points which is the point unit supported by the application. In addition, if a value of point vs. reward in App2 is 1:2, the reward exchange unit 205 can exchange assigned 50 rewards for 25 points (in the shown example, App2 sets points to gold).

(103) In this manner, the reward exchange unit 205 can exchange rewards for points according to an exchange rate for each application and transmit the points to the point registration unit 205, and the point registration unit 206 can transmit and register the points to the App-related server 400 corresponding to each application. Accordingly, a user can use saved rewards in a plurality of applications.

(104) Through the above-described configuration, while proceeding with an advertisement through a variety of applications in agreement with the subject of the Ad server, an advertiser can insert and distribute the Ad module in his/her application and, thereafter, if preference of the corresponding application becomes high, intensively save rewards generated by users in the corresponding application, thereby allowing recovery of costs due to Ad expenditure in terms of rewards, which can result in saving of high Ad costs.

(105) In the meantime, if each Ad module 100 is installed in parallel to each application, with no integration, in the user terminal according to the configuration of FIG. 7, the Ad server 200 can identify the Ad module 100 transmitting the ID information as the Ad module 100 activated in the user terminal and also save rewards in an application corresponding to the activated Ad module.

(106) Accordingly, the Ad server 200 can identify the latest-executed application and save rewards in the corresponding application.

(107) Even in the case of an integrated Ad module, ID information of the latest-executed application in interlocking with each application can be transmitted to the Ad server, thereby allowing rewards to be saved in the latest-executed application.

(108) Accordingly, rewards can be consistently saved in a particular application through the consistent execution of the particular application.

(109) That is, if a user intends to consistently save rewards only in a desired application, only the desired application can be consistently executed to allow the rewards to be intensively saved in only one application.

(110) On the other hand, the configuration of the reward distribution unit 204 of the Ad server 200 may be included in the reward processing unit 160 of the Ad module 100, and an application in which the Ad module 100 is inserted may interlock with the Ad module 100 installed in parallel in the user terminal and select activation or deactivation for the Ad module 100.

(111) According to the configuration as described above, the Ad module 100 can save the generated rewards, distribute the saved rewards for each application according to a status of an application installed in the user terminal 10, and transmit the distributed rewards to the Ad server 200. The Ad server 200 can transmit the rewards distributed for each application to the application-related server 400 corresponding to each application so that a user can use the corresponding rewards in an application.

(112) In particular, the Ad module 100 can detect whether or not the application is executed, give a high weight to the latest-executed application, and adjust a distribution ratio according to the weight.

(113) Accordingly, the Ad module 100 can save the generated rewards and intensively allocate the saved rewards to the latest-executed application.

(114) In this case, it is obvious that the Ad module 100 can receive setup information on a reward distribution for each application from the Ad server 200 or through a user input, and adjust a distribution ratio based on the received setup information.

(115) In addition, each application installed in the user terminal 10 can select activation or deactivation of the Ad module 100. The Ad module 100 can receive selection information on activation or deactivation of each application and transmit application ID information corresponding to an application activated based on the selection information to the Ad server 200. Then, the Ad server 200 can operate to transmit Ad information related to an application corresponding to the received application ID information to the Ad module and provide only Ad information on an application desired by a user.

(116) FIG. 15 is a sequence diagram showing an advertising method of an Ad system using an Ad module included in the above-described application. As shown, when an application in which an Ad module is inserted is installed in the user terminal (S1), the Ad module can be automatically activated (S2) or activated according to a user input for activation of the Ad module.

(117) The activated Ad module 100 can transmit application ID information and a signal for Ad information request to the Ad server 200 (S3) and the Ad server 200 can transmit the Ad information to the Ad module 100 (S4).

(118) The Ad module 100 can display the Ad information received from the Ad server 200 on the lock screen of the user terminal 10 (S5), detect event information generated according to the user input (S6), compare the event information with reward generation conditions set in association with the Ad information, and, if both match with each other, generate rewards (S7).

(119) The Ad module 100 can transmit and save the generated rewards to the Ad server 200 (S8). The Ad server 200 can distribute the generated rewards for each application according to a user input or a preset distribution ratio depending on an installation status of an application installed in the user terminal through the application ID information (S9).

(120) Thereafter, the Ad module 100 can transmit the distributed rewards to an application-related server corresponding to each application (S10) so that a user can use the rewards to purchase items or goods provided by each application.

(121) While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it will be understood by those skilled in the at that various changes in form and details may be made therein without departing from the spirit and scope of the present invention. The exemplary embodiments are provided for the purpose of illustrating the invention, not in a limitative sense. Thus, it is intended that the present invention covers the modifications and variations of this invention provided they come within the scope of the appended claims and their equivalents.