WO2016043495A1

WO2016043495A1 - Method, server, and computer program for providing mobile service platform

Info

Publication number: WO2016043495A1
Application number: PCT/KR2015/009667
Authority: WO
Inventors: 김건수
Original assignee: 주식회사 제이투엔
Priority date: 2014-09-15
Filing date: 2015-09-15
Publication date: 2016-03-24
Also published as: KR20160032346A

Abstract

A server for providing a mobile service platform and a method performed by the server are disclosed. In an exemplary embodiment, a method for providing a mobile service platform may comprise the steps of: receiving, by a code server, at least one of a code for an application for a particular advertiser and a code for a particular advertising page of the particular advertiser, acquired by a user equipment; receiving, by an advertisement log server, at least one of the code for the application for the particular advertiser and the code for the particular advertising page of the particular advertiser, acquired by the user equipment, and user information on a user of the user equipment; searching, by a code server, a database for at least one record value included in at least one of the code for the application and the code for the particular advertising page, received from the user equipment; transmitting, by the code server, the at least one searched record value to the user equipment; receiving, by an application server, a request for the application for the particular advertiser on the basis of the at least one transmitted record value from the user equipment; and in response to the request for the application for the particular advertiser, searching, by the application server, the database for an application corresponding to the requested application, and transmitting data associated therewith to the user equipment.

Description

Method, server and computer program for providing mobile service platform

Unless otherwise indicated herein, the content described in this section is not prior art to the claims of this application and should not be recognized as prior art by inclusion in this section.

With the proliferation of smart devices today, not only mobile device users, but also advertisers who want to provide advertising to such mobile device users, bring together a broad spectrum of users who The demand for useful mobile platforms that can attract attention is growing day by day. In response to this demand, mobile service providers have made various attempts, such as providing mobile services with both SNS and commodity purchasing functions, but satisfying all the stakeholders in the mobile industry environment and further creating economic advertising effects. It is not easy to do that.

In one example, a method for providing a mobile service platform includes receiving, by a code server, at least one of a code relating to an application for a particular advertiser and a code relating to a specific advertisement page of a particular advertiser, acquired by a user device; Receiving, by the advertisement log server, at least one of a code relating to an application for a specific advertiser, a code relating to a specific advertisement page of a specific advertiser, and user information about a user of the user device, acquired by the user device; Retrieving, in the database, by the code server at least one record value contained in at least one of a code relating to an application received from a user device and a code relating to a particular advertisement page; Sending, by the code server, the retrieved at least one record value to the user device; Receiving, by the application server, a request from the user device of the application for a particular advertiser based on the transmitted at least one record value; And responsive to the request of the application for the particular advertiser, retrieving the application corresponding to the requested application from the database and transmitting, by the application server, data associated therewith to the user device.

In another example, a server system for providing a mobile service platform may include a database; A code server configured to receive at least one of a code relating to an application for a specific advertiser acquired by the user device and a code relating to a specific advertisement page of the specific advertiser; And an advertisement log server configured to receive at least one of a code regarding an application for a specific advertiser acquired by the user device, a code regarding a specific advertisement page of the specific advertiser, and user information about the user of the user device.

In another example, a computer program running on a server system including a database and stored on a medium to provide a mobile service platform may include code for an application for a particular advertiser acquired by the user device and for a particular advertiser's advertising space. Instructions to receive at least one of the codes; Instructions for receiving, by the user device, at least one of a code about an application for a specific advertiser, a code about a specific advertisement space of a specific advertiser, and user information about a user of the user device; Instructions for retrieving from the database at least one record value contained in at least one of a code relating to an application received from a user device and a code relating to a particular advertisement page; Sending the retrieved at least one record value to a user device; Instructions from the user device to receive a request of an application for a particular advertiser based on the transmitted at least one record value; And in response to a request of an application for a specific advertiser, search for an application corresponding to the requested application in a database and transmit data associated with the request to the user device.

The above summary is merely illustrative and is not intended to be limiting in any way. In addition to the illustrative aspects, embodiments, and features described above, additional aspects, embodiments, and features will become apparent by reference to the following detailed description and drawings.

The foregoing and other features of the present disclosure, in conjunction with the accompanying drawings, will become more fully apparent from the following description and the appended claims. These drawings will be described in more detail and in detail using the accompanying drawings, with the understanding that these drawings show only a few embodiments in accordance with the present disclosure and therefore should not be considered as limiting its scope.

1 illustrates an exemplary mobile comprising a code server, an advertisement log server, an application server, an SNS server, an entry server, a network, a user device, an advertisement space containing code relating to a user, an advertiser and an advertisement space, and a second user device. Shows a service platform system,

2 is a block diagram illustrating an example code server,

3 is a block diagram illustrating an example ad log server,

4 is a block diagram illustrating an example application server,

5 is a block diagram illustrating an example SNS server,

6 is a block diagram illustrating an example entry server,

7 is a block diagram illustrating an example user device,

8 is a flow chart illustrating an exemplary ad log data providing process of an ad log server;

9 is a flowchart illustrating an example application creation and provisioning process of an application server;

10 is a flowchart illustrating an exemplary state information data providing process of an SNS server;

11 is a flowchart illustrating an exemplary shared content provision process of an SNS server;

12 is a flowchart illustrating an example credit data and / or credit count providing process of an SNS server,

13 is a flowchart illustrating an example process of an entry server,

14 is a flowchart illustrating an example process of an example event performed by the entry server,

15 is a flow diagram illustrating an example process of a server system,

16 is a block diagram of an example computer program for providing a mobile service platform,

17 illustrates a general purpose computing device that can be used to implement a system for providing a mobile service platform, all in accordance with at least some embodiments described herein.

In the following detailed description, reference is made to the accompanying drawings, which form a part hereof. In the drawings, like reference numerals generally refer to like configurations unless otherwise indicated in the context. The embodiments described in the detailed description, drawings, and claims are not to be construed as limiting. Other embodiments may be utilized, or other changes may be made, without departing from the scope or spirit of the subject matter presented in this disclosure. Aspects of the present disclosure generally described in the present disclosure and illustrated in the drawings may be arranged, substituted, combined, and designed in a variety of different configurations, all of which are expressly contemplated and willing to form part of the present disclosure. Will be understood.

The present disclosure generally relates to an apparatus, a system, an apparatus and a computer program for providing a mobile service platform, among others. In the present disclosure, a user may access through the Internet by entering codes related to other user's mobile devices, web sites, applications and advertisers' advertising content. In particular, the user can access the advertisement content of the advertiser by inputting the code of the advertiser presented in the advertisement space installed in public transportation or on the street. The code may be conventionally mounted or externally connected to the user device and may be input by the user through a dial pad implemented mechanically or electronically on a display screen.

Codes for devices, websites, applications, and content that you want to access are generated by combining special numbers (such as * or #) present on the dial pad with a general subscription or specific number based on a conventional telephone number system. (Eg, a specific number + * or # or subscriber individual phone number + * or #). In the case of not limiting a specific region or country, one or more of a country code, a region code or a network identification number, or a station code may be further included and combined before the subscriber individual telephone number (for example, country code + area code or network). Identification number + station code + subscriber's individual telephone number + * or #). #).

In some examples, a service individual number may be further included and combined following a special number (eg, * or #) (eg, special number + * or # + service individual number or subscriber individual phone number + * or # + Service individual number).

In some examples, the code for the advertiser may be followed by the code for the advertising page. The code for the advertising page may include at least one number. The entire code that a user enters to access the advertiser's advertising content may be combined to further include a code for the advertising page that may follow a special number (eg, * or #) (eg, special number + * or # + Specific number on the advertising page).

In the case of registering as a new user (for example, an advertiser) in the code server, the phone number combined with the code may be given priority to a general subscription phone number already used. Otherwise, you can specify a specific number.

Code (e.g. phone number + * or #) about the device, website, application, and content that you want to access may include information for accessing content such as applications, sites, email addresses and media addresses, P2P type information, operating system information, etc. It may include a plurality of record values of, such a record type may be represented as Plain Text, XML, JSON or Binary.

1 is a code server 111, an ad log server 112, an application server 113, an SNS server 114, an entry server 115, a network 120, according to at least some embodiments described herein. Exemplary mobile service platform system 100 comprising a user device 130, a user 131, an advertisement page 132 including code 133 for an advertiser and an advertisement page, and a second user device 140. ). The mobile service platform system 100 may further include other advertiser devices, user devices, and / or advertising pages in addition to the components shown.

In FIG. 1, the code server 111, the advertisement log server 112, the application server 113, the SNS server 114 and the application shown as included in the mobile service platform system or server system 110 shown in broken lines are shown. Server 115 is shown as a separate server, but may be combined into fewer groups of servers, divided into a larger number of servers, or some servers may be removed from server system 110, It can even be integrated into a single server.

In some embodiments, the code server 111 receives code from the advertiser device about the application for the advertiser and the code about the advertising space and stores it in a database associated with the code server 111 to register the code for the application for the advertiser. It can be configured to. The database may be in a form included in the code server 111 or may be stored in a separate external server and accessible to the code server 111.

In some embodiments, the code server 111 may be configured to receive at least one of a code relating to an application for an advertiser and a code relating to an advertiser's advertising page acquired by the user 131 from the user device 130. . By way of example, and not limitation, the code for the application for the advertiser may include at least one number and at least one symbol, and the code for the advertisement page may include at least one number. By way of example, and not limitation, the advertising page may refer to the means for the advertiser to execute the advertisement. For example, the advertising space may relate to such a specific advertising point as it may be the ground of bus stops, subway stations and street billboards.

As shown in FIG. 1, a user 131 travels to Hawaii, which is a combination of a code for an application for an advertiser, “1111 #” and a code “1” for an advertising page 132 on the advertising page 132. The code "1111 # 1" 133 relating to the advertisement containing the discount sale advertisement information of can be obtained. Ad space 132 may refer to any of one or more ad spaces, such as bus stops, subway stations, and street billboards, and the code for the ad space assigned to ad space 132 is "1". When the user 131 enters the code “1111 # 1” 133 into the user device 130, the user device is expected to return an application that can obtain information about a great sale advertisement for a trip to Hawaii. Code 130 can be entered.

In some embodiments, the code server 111 may be configured to retrieve in its database code for an application for an advertiser and code for an advertiser's advertising page received from the user device 130. In some embodiments, the code server 111 may be configured to return to the user device 130 record values included in the code for the application for the retrieved advertiser and the code for the advertising page.

In some embodiments, the ad log server 112 may be configured to receive at least one of a code about an application for an advertiser, a code about an advertising page, and user information about a user 131 of the user device 130. . In some embodiments, ad log server 112 may store at least one of a code relating to an application for a given advertiser, a code relating to an advertising page, and user information about a user of a user device to a database associated with ad log server 112. Can be configured to store. The database may be in a form included in the advertisement log server 112 or may be stored in a separate server externally accessible to the advertisement log server 112.

In some embodiments, ad log server 112 may be configured to retrieve in its database code for an application for a received advertiser and code for an advertiser's ad space. In some embodiments, the advertisement log server 112 may be configured to store advertisement log data in association with the retrieved advertiser with code relating to the application and code relating to the advertisement page and user information in its database.

In some embodiments, the ad log server 112 may be configured to receive a request for ad log data from the advertiser device, and in response, the code relating to the application for the advertiser of the advertiser device and the advertiser stored in its database. And at least one advertisement log data including user information associated with a code relating to an advertisement page to an advertiser device.

In some embodiments, application server 113 may be configured to receive from the user device 130 a request of an application for an advertiser based on a record value returned to the user device 130. The user device 130 may request a user to execute and / or install an application for an advertiser, and thus, the user's request may include at least one of an execution request and an installation request.

In some embodiments, in response to receiving the application's request for the advertiser from the user device 130, the application server 113 displays an application corresponding to the application for the requested advertiser in a database associated with the application server 113. Can be configured to search. In some embodiments, if an application corresponding to the application requested by the user is retrieved from its database, the application server 113 may be further configured to send data associated with the retrieved application stored in its database to the user device 130. . As the application's request to the user's advertiser may include at least one of a launch request or an install request, the data associated with the retrieved application that the application server 113 sends to the user device 130 may execute the requested application. It may include at least one of data for or data for installation.

In some embodiments, the application server 113 may be configured to receive a template type and at least one content of an application requested by the advertiser from the advertiser device. The template type may be determined based on the type of application, such as commerce, education, transportation and / or restaurant, etc., by way of example and not by way of limitation, depending on the characteristics of the application that the advertiser intends to create. Also, by way of example, and not limitation, at least one content may include at least one of an image, text, and / or video, and the at least one content may be included in the application or included as content constituting the application. Can be used as an icon image.

In some embodiments, application server 113 may be configured to retrieve from its database a template source corresponding to the received template type. For example, if the template type received from the advertiser device is a template type included in a type of application such as commerce, the application server 113 may select from its database a template source corresponding to one of a plurality of template types associated with commerce. You can search. The database may be in a form included in the application server 113 or may be stored in an external separate server and accessible to the code server 113.

In some embodiments, the application server 113 may be configured to generate the required application based on the retrieved template source and at least one content received from the advertiser device. For example, when the application server 113 retrieves a template source corresponding to a template type included in a type of application such as commerce received from an advertiser device, the application server 113 may search for an commerce type application based on the retrieved template source. The at least one content may be published to the application, construct the application, or included as an icon image of the application and used to create the application.

In some embodiments, application server 113 may store the generated application and data associated with the generated application in its database and may be configured to send to the advertiser device. The advertiser may upload an application for the generated advertiser received through the advertiser device to any application store and share it with other users. For example, in FIG. 1, when the user 131 enters the code “1111 # 1” 133 into the user device 130, an application of an application for an advertiser that may obtain information about a discount sale advertisement for a trip to Hawaii. At least one of the data for execution or data for installation will be returned, through which an application for the advertiser created by the application server 113 will be executed or installed on the user device 130.

In some embodiments, SNS server 114 may be configured to receive a list of users 131 from user device 130 and store them in a database of a plurality of users of SNS server 114. The database may be in a form included in the SNS server 114 or may be stored in a separate external server and accessible to the SNS server 114. The list may include information of one or more other users associated with the user 131. By way of example, and not limitation, a list associated with a particular user, such as a list, may include an address book stored in the memory of the user device 130 (eg, an address book including phone numbers, email addresses, homepage addresses, etc. of other users associated with the user 131). Or, a contact associated with a user's social network service (SNS) account.

In some embodiments, SNS server 114 may be configured to receive shared content that includes information provided by an application for an advertiser from user device 130. In some other examples, SNS server 114 may be configured to receive, along with its shared content, a tag of at least one user designated by user 131 among one or more other users included in the list. For example, if the user 131 wants to share his or her shared content by limiting to a specific user, the SNS server 114 may be configured to receive a tag of the specific user specified by the user 131 from the user device 130 together. Can be. By way of example, and not limitation, the user 131 may be content that can be configured to be shared with other users, and may include various types of files such as text, images, video files, and audio files. For example, in FIG. 1, when a user 131 runs or installs an application for an advertiser capable of obtaining information about a discount sale advertisement for a trip to Hawaii, the shared content may be based on the Hawaii travel provided by the application for that advertiser. It may be content including discount sale information.

In some embodiments, the SNS server 114 stores the received shared content in a database associated with the SNS server, and transmits the shared content received from the user device 130 to the user device of one or more other users included in the list. Can be configured. For example, when receiving a tag of at least one user designated by the user 131 among one or more other users included in the list from the user device 130, at least one of the at least one designated by the user 131 based on the received tag It may be configured to transmit the received shared content to the user device of one user, for example, the second user device 140.

In some embodiments, entry server 115 may be configured to receive a response by user 131 of user device 130 for one or more payment methods for which rewards may be provided. For example, the code server 111 receives from the user device 130, at least one of a code for an application for the advertiser and a code for a particular advertisement space of the advertiser, or from the user device 130, for the advertiser. When the application server 113 receives a request of an application, or when the SNS server 114 receives shared content including information provided by an application for an advertiser from the user device 130, the application server 113 receives one or more payment methods. The user 130 may be regarded as receiving a response by the user 131 of the device.

In some embodiments, entry server 115 may be configured to provide a reward to an account associated with user 131 when receiving a response by user device 130 of user device 130. By way of example, and not limitation, a reward may include at least one of an entry ticket and points that can participate in an event.

In some embodiments, code server 111, ad log server 112, application server 113, SNS server 114, entry server 115, network 120, user device 130, user 131 ), The advertiser's page 132 and the second user device 140, including code 133 for the advertiser and the page, can communicate with each other via the network 120. The network 120 includes a local area network, a Wi-Fi network, a WiGig network, a radio frequency cellular network, a Bluetooth communication network, and a USB interfaced communication network. Can be any one type.

By way of example, and not limitation, user device 130 and / or second user 140 may be, for example, a cell phone, a personal data assistant, a personal media player device, a wireless web-watch device, a personal headset. It may be any type of small-form factor portable (or mobile) electronic device, such as a device, a special purpose device, or a hybrid device including any of the above functions.

2 is a block diagram illustrating an example code server 111, in accordance with at least some embodiments described herein. As shown in FIG. 2, the code server 111 may include a processing unit 210, a registration unit 220, and a database 230. While each unit of FIG. 2 is shown as a separate component, various components may be separated into additional components, combined into fewer components, or removed without departing from the scope of the disclosed subject matter. Those skilled in the art will appreciate that each function and / or operation of a component may be implemented individually and / or collectively by hardware, software, firmware or virtually any combination thereof.

In some embodiments, the processing unit 210 may be configured to receive code from the user device 130 regarding the advertising content of another user's mobile device, website, application, and advertiser. By way of example, and not limitation, the received code may include at least one number and at least one symbol, and in some other embodiments, the received code may further include a code relating to the advertising page. In some embodiments, processing unit 210 may be configured to retrieve code from database 230 regarding the advertising content of another user's mobile device, web site, application, and advertiser received from user device 130. In some embodiments, processing unit 210 may be configured to return the record value that the retrieved code includes to user device 130.

In some embodiments, processing unit 210 may be configured to transmit a record value from the user device 130 to the user device 130 that includes a code that frequently generates queries. Through such cache management, the record value of some codes may be cached in advance in the user device 130 to effectively reduce the load.

In some embodiments, registration unit 220 receives codes from any user device (eg, user device 130, second user device 140, and / or advertiser device) and stores them in a database 230. And register the received code.

In some embodiments, database 230 may be configured to store code for registered user devices and record values associated therewith. By way of example, and not limitation, the database 230 may be an internal memory located inside the advertisement log server 112 as illustrated in FIG. 2, but alternatively, an external database or an internal memory and an external database electrically connected to the outside. It may be any combination of. The database 230 also includes one or more of volatile memory, nonvolatile memory, flash memory, programmable variables or states, random access memory (RAM), read-only memory (ROM), or other static or dynamic storage media. One or more embodiments may include various memory media.

3 is a block diagram illustrating an example advertising log server 112, in accordance with at least some embodiments described herein. As shown in FIG. 3, the ad log server 112 may include a receiving unit 310, a database 320, a retrieving unit 330, a processing unit 340, and a transmitting unit 350. Each unit of FIG. 3 is shown as a separate component, but various components may be separated into additional components, combined into fewer components, or removed without departing from the scope of the disclosed subject matter. Those skilled in the art will appreciate that each function and / or operation of a component may be implemented individually and / or collectively by hardware, software, firmware or virtually any combination thereof.

In some embodiments, the receiving unit 310 may be configured to receive the code for the advertiser and the code for one or more advertisement pages, directly from the advertiser device and / or indirectly through the code server 111. By way of example, and not limitation, the code relating to an advertiser may include at least one number and at least one symbol, and the code relating to one or more advertisement pages may include at least one number. In some embodiments, the receiving unit 310 may be configured to further receive the advertising content directly from the advertiser device and / or indirectly through the code server 111. In some embodiments, the receiving unit 310 is a code relating to a particular advertiser obtained by the user 131, specific to a particular advertiser, directly from the user device 130 and / or indirectly through the code server 111. It may be configured to receive at least one of a code relating to the advertising page and information about the user 131 of the user device 130. By way of example, and not limitation, the user information may include at least one of a user's gender, age, occupation, region of residence, and hobbies. In some embodiments, the receiving unit 310 may be configured to receive a request for advertisement log data directly from the advertiser device and / or indirectly through the code server 111.

In some embodiments, database 320 may be configured to store code for a received advertiser and code for one or more advertising pages. In some other embodiments, database 320 may be further configured to store the received advertising content. In some embodiments, database 320 may be configured to store advertisement log data processed by processing unit 350. By way of example, and not limitation, the database 320 may be an internal memory located inside the advertisement log server 112 as illustrated in FIG. 3, but alternatively, an external database or an internal memory and an external database electrically connected to the outside. It may be any combination of. Further, database 320 includes one or more of volatile memory, nonvolatile memory, flash memory, programmable variables or states, random access memory (RAM), read-only memory (ROM), or other static or dynamic storage media. One or more embodiments may include various memory media.

In some embodiments, the search unit 330 may be configured to search the database 320 for a code relating to a particular advertiser received and a code relating to a particular advertisement space of a particular advertiser. For example, the search unit 330 may identify whether the received specific advertiser is registered in the ad log server 112 by searching the database 320 for the code relating to the received specific advertiser and the code for the specific advertising page of the particular advertiser. Can be.

In some embodiments, the processing unit 340 may be configured to store advertisement log data in the database 320 that includes code associated with the retrieved particular advertiser and user information associated with code associated with the particular advertisement page and user information. Can be. By way of example, and not by way of limitation, the advertisement log data may include user information as well as IP (IP) associated with the user device 130, the time at which the user 131 received information about the user 131 of the user device 130, and the user 131. The device 130 may include at least one of location information inputting a code about a specific advertiser.

In some embodiments, the sending unit 350 sends at least one advertisement log data to the advertiser device, the user information associated with a code about the advertiser of the advertiser device stored in the database 320 and a code about the advertiser's advertisement space. It may be configured to transmit directly and / or indirectly via code server 111. In some embodiments, the sending unit 350 may be configured to send the stored advertising content directly to the user device 130 and / or via the code server 111.

4 is a block diagram illustrating an example application server 113, in accordance with at least some embodiments described herein. As shown in FIG. 4, the application server 113 stores the receiving unit 410, the retrieving unit 420, the application generating unit 430, the transmitting unit 440, the modification unit 450, and the database 460. It may include. While each unit of FIG. 4 is shown as a separate component, various components may be separated into additional components, combined into fewer components, or removed without departing from the scope of the disclosed subject matter. Those skilled in the art will appreciate that each function and / or operation of a component may be implemented individually and / or collectively by hardware, software, firmware or virtually any combination thereof.

In some embodiments, the receiving unit 410 is configured to receive the template type and at least one content requested by the subscriber from the subscriber device (eg, the user device 130, the second user device 140, and / or the advertiser device). Can be configured. The template type may be determined based on the type of application such as commerce, education, transportation and / or restaurant, etc., by way of example and not by way of limitation, and the at least one content may include at least one of an image, text and / or video. have. In some embodiments, the receiving unit 410 may be further configured to receive a request of the user's application from the user device 130. For example, the request of the user's application may include at least one of an execution request or an installation request. In some embodiments, the receiving unit may be further configured to receive the second content from the subscriber device (eg, the user device 130, the second user device 140, and / or the advertiser device). For example, the second content can be used to modify the subscriber's generated application according to the subscriber's needs.

In some embodiments, the search unit 420 may generate a template source corresponding to a template type received from a subscriber device (eg, user device 130, second user device 140, and / or advertiser device). It can be configured to search in. For example, if the template type is included in a type of application such as commerce, the search unit 420 can retrieve from the database 460 a template source corresponding to one of a plurality of template types associated with commerce. In some embodiments, search unit 420 may be further configured to search for an application corresponding to the requested application in database 460 in response to receiving the request of the application from user device 130.

In some embodiments, the application generation unit 430 is based on the retrieved template source and at least one content received from the subscriber device (eg, the user device 130, the second user device 140, and / or the advertiser device). It can be configured to generate the required application. For example, a commerce type application can be built based on a template source corresponding to one of a plurality of template types associated with commerce. In some embodiments, at least one content may be published to an application, construct an application, or included as an icon image of the application to be used to create the application.

In some embodiments, the sending unit 440 is configured to send the application generated by the application generating unit 430 to the subscriber device (eg, the user device 130, the second user device 140, and / or the advertiser device). Can be configured. By way of example, and not by way of limitation, the sending unit 440 may access an application created on a subscriber device (eg, the user device 130, the second user device 140, and / or the advertiser device) via a program such as an email or a web browser. Can transmit In some embodiments, when an application corresponding to an application requested by the user is retrieved by the retrieving unit 420, the transmitting unit 440 transmits data associated with the retrieved application stored in the database 460 to the user device 130. It can be further configured to. The data associated with the retrieved application that the sending unit 440 sends to the user device 130 may include at least one of data for execution or data for installation of the requested application.

In some embodiments, modification unit 450 is in response to receiving the second content from the subscriber device (eg, user device 130, second user device 140, and / or advertiser device), thereby requesting the subscriber. The application generation unit 430 may be configured to modify the application generated based on the received second content.

In some embodiments, database 460 may be configured to store an application generated by application generation unit 430 and data associated with the generated application. For example, the database 460 may be configured to classify the generated application according to the template type of the generated application, and store the generated application and data associated with the generated application. In some embodiments, the database 460 may be further configured to store the application modified by the modifying unit 450 and data associated with the modified application. In some embodiments, database 460 may be configured to store template sources previously developed by the developer to suit various template types, depending on the application type. By way of example, and not limitation, the database 460 may be an internal memory located inside the application server 113 as illustrated in FIG. 4, but alternatively, an external database or an internal memory and an external database electrically connected to the outside may be used. It may be any combination. The database 460 also includes one or more of volatile memory, nonvolatile memory, flash memory, programmable variables or states, random access memory (RAM), read-only memory (ROM), or other static or dynamic storage media. One or more embodiments may include various memory media.

5 is a block diagram illustrating an SNS server 110, in accordance with at least some embodiments described herein. As shown in FIG. 5, the SNS server 114 may include a receiving unit 510, a database 520, a processing unit 530, and a transmitting unit 540. While each unit of FIG. 5 is shown as a separate component, various components can be separated into additional components, combined into fewer components, or eliminated without departing from the scope of the disclosed subject matter. Those skilled in the art will appreciate that each function and / or operation of a component may be implemented individually and / or collectively by hardware, software, firmware or virtually any combination thereof.

The receiving unit 510 is configured to receive a list of users from the user device 130, and the received list may be stored in the database 520. The list may include information of one or more other users associated with the user. In some embodiments, the receiving unit 510 may be configured to receive status information data for at least a second user included in the list from the user device 130. By way of example, and not by way of limitation, the state information data may include state information of the user for at least some of the second user and / or other one or more other users included in the list of users. In some embodiments, the receiving unit 510 may be configured to receive a status information request from the second user device 140 of the second user. By way of example, and not limitation, the status information request may include at least one of a call from the second user device 140 to the user device 130 and a call from the user device 130 to the second user device 140. . The call may be driven by the user through an application associated with the SNS server 114 on the user device, but is not limited thereto.

In some embodiments, the receiving unit 510 may be configured to receive shared content from the user device 130, and in some other examples, at least one specified by the user among one or more other users included in the list along with the shared content And may be configured to receive tags of a user of a. In some embodiments, the receiving unit 510 may be configured to receive the subscription content from the user device 130 along with the tag of another user included in the list that created the shared content sent to the user device 130. In some embodiments, receiving unit 510 may be configured to receive credit data for a particular user from one or more other users included in the list from user device 130. By way of example, and not limitation, credit data may be data that a user configures for a particular user. In some embodiments, the receiving unit 510 shares the tag of the user of the user device 130 from the second user device 140 when the call from the second user device 140 to the user device 130 fails. It may be configured to receive with the content. In some embodiments, the receiving unit 510 is a user of the second user device 140 included in the list from the user device 130 when the call from the user device 130 to the second user device 140 fails. May be configured to receive a tag of the with shared content.

Database 520 may be configured to store a list of received users. In some embodiments, database 520 may be configured to store state information data for at least a second user received from user device 130. In some embodiments, database 520 may be configured to store received shared content. In some embodiments, database 520 may be configured to store credit data for a particular user received.

By way of example, and not limitation, the database 520 may be configured to store a list in the form of a table, and the database 520 may further store a list for each of the plurality of users as a table. An example of the list is shown in Table 1 below.

이름name	전화번호Phone number	상태 정보 데이터Status information data	그룹 지정Specify group	크레딧 카운트Credit count
제2 사용자Second user	010-1111-1111010-1111-1111	Text a "제2 사용자님, 저 지금 하와입니다. 통화 불가능할 수도 있습니다"Text a "Second user, I'm Eve now. Calls may not be possible."	없음none	1515
제3 사용자3rd user	010-1111-2222010-1111-2222	Text b "안녕하세요"Text b "hello"	AA	33
제4 사용자4th user	010-1100-2233010-1100-2233	Text b "안녕하세요"Text b "hello"	AA	1One
제5 사용자5th user	010-1111-4444010-1111-4444	Refuse "착신 금지"Refuse "Do not call"	없음none	55
제6 사용자6th user	010-2222-4444010-2222-4444	Image a "image.jpg"Image a "image.jpg"	없음none	00

The list received from the user and stored in the database 520 may include a name and a telephone number as shown in Table 1. As shown in Table 1, the list of users may include a second user, a third user, a fourth user, a fifth user, and a sixth user. Each state information data about the second user, the third user, the fourth user, the fifth user, and the sixth user is provided from the user device 130 and may include various types of data such as text and an image.

As shown in Table 1, one or more users included in the list may be managed by being divided into groups, and when included in the same group, the same state information data may be designated. In addition, the status information data may be designated as "do not disturb", for example, when the user device 130 receives a call from a fifth user designated as "do not disturb", the SNS server 114 and / or a call associated with it. The server (not shown) may not allow this call. In addition, for example, the user may include all the users included in the list in one same group to designate the same state information data for all the users.

In addition, as shown in Table 1, the list may include a credit count for each user included in the list. If another user device sends credit data for a particular user, the credit count of that particular user may be increased by one. As a result, as shown in Table 1, a credit count for each user included in the list may be generated and / or updated. In some embodiments, such credit data may be provided once per day by each user to other users, and the credit count of each user may correspond to the cumulative number of credit data received thereon. For example, in Table 1 the credit count of the second user is 15, which represents the total sum of credit data transmitted for the second user by other users, including the third to sixth users. As a non-limiting example, the credit count may be reset after accumulating for a certain period, which may be preset by the operator of the SNS server 114.

The basic list received from the user is described as including a name and a phone number, but this is merely an example, and may include other contact means other than the phone number, and also includes various information such as a user's profile picture. It may be received from the user device by the receiving unit 510 and stored in the database 520.

By way of example, and not limitation, the database 520 may be an internal memory located inside the SNS server 114 as shown in FIG. 5, but alternatively, an external database or an internal memory and an external database that are externally communicatively connected. It may be any combination of. The database 520 also includes one or more of volatile memory, nonvolatile memory, flash memory, programmable variables or states, random access memory (RAM), read-only memory (ROM), or other static or dynamic storage media. One or more embodiments may include various memory media.

The processing unit 530 retrieves a list of users from the database 520, for example, when the state information data for the second user is received from the user device 130, and displays the second user's information included in the list. And may be configured to associate and store state information data for the user. Storing state information data in the database 520 may take the form or method shown in Table 1, but is not limited thereto. In some embodiments, processing unit 530 may be configured to retrieve status search information data from database 520 in response to the status information request. For example, if the status information request from the second user device 140 includes a call with the user device 130, the processing unit 530 retrieves a list of users from the database 520 and includes the list of users. And retrieve user-specified state information data for the second user. In some embodiments, the processing unit 530 may be configured to retrieve an account associated with the user from the database 520 and associate and store the received shared content in the account when shared data is received from the user device 130. Can be.

In some embodiments, upon receipt of credit data for a particular user from user device 130, processing unit 530 retrieves an account associated with the particular user from database 520 and associates the credit data received with that account. Can be configured to store. In some embodiments, processing unit 530 may be configured to increase the credit count for a particular user in database 530 by 1 in response to receiving the credit data. For example, the processing unit 530 may be configured to retrieve an account associated with a particular user from the database 530, and increment and store the credit count included in that account by one. Accordingly, the processing unit 530 may be configured to increment the credit counts for all the specific users in the list of at least one user having the list including the particular user by one. In some embodiments, the processing unit 530 may be configured to sort the list based on a predetermined rule based on the credit count for each user included in the list. By way of example, and not by way of limitation, a predetermined rule may be a rule for sorting accumulated credit counts in ascending or descending order, or a rule for sorting accumulated credit counts by a time limit, a rule for sorting users included in a list into groups, and the like. It may include, and may be set by the user or the operator of the SNS server 114.

In some embodiments, the sending unit 540, in response to the request for status information from the second user device 140, retrieves the status information data for the second user retrieved by the processing unit 530 from the second user device ( 140 may be configured to transmit. In some embodiments, the sending unit 540 may be configured to send the shared content received from the user device 130 to the user device of one or more other users included in the list. In some other embodiments, upon receiving from the user device 130 a tag of at least one user specified by the user among one or more other users included in the list, based on the received tag, the sending unit 540 may be configured to And transmit the received shared content to the user device of the designated at least one user. In some embodiments, when the subscription content is received together with the tag of another user included in the list that created the shared content sent to the user device 130, based on the received tag, the transmitting unit 540 may select the user device ( 130 may be configured to transmit the received subscription content to the user device of another user included in the list for which the shared content sent to 130 is created. In some embodiments, the sending unit 540 is configured to send the shared content received from the second user device 140 and the user device 130 when the call from the second user device 140 to the user device 130 fails. Based on the tag of the user, it may be configured to transmit the received shared content to the user device 130. In some embodiments, the sending unit 540, when the call from the user device 130 to the second user device 140 fails, the second user device included in the list and the shared content received from the user device 130. Based on the tag of the user of 140, it may be configured to transmit the received shared content to the second user device 140.

In some embodiments, the sending unit 540 may be further configured to send the credit data to the user device of the particular user. By way of example, and not by way of limitation, when the SNS server 114 transmits the credit data to the user device of a specific user, the SNS server 114 removes and generates the generation information of the credit data (for example, information of the user who generated the credit data and the user device). It can be configured to. In some embodiments, the sending unit 540 may be configured to send the list sorted according to a predetermined rule by the processing unit 530 to the user device 130.

6 is a block diagram illustrating an entry server 115, in accordance with at least some embodiments described herein. As shown in FIG. 6, the application server 115 may include a payment method providing unit 610, a reward providing unit 620, an event providing unit 630, an event execution unit 640, and a database 650. Can be. While each unit of FIG. 6 is shown as a separate component, various components may be separated into additional components, combined into fewer components, or removed without departing from the scope of the disclosed subject matter. Those skilled in the art will appreciate that each function and / or operation of a component may be implemented individually and / or collectively by hardware, software, firmware or virtually any combination thereof.

In some embodiments, the payment method providing unit 610 transmits one or more payment methods to which the reward can be provided to the user device 130, and the user of the user device 130 for the one or more payment methods from the user device. And receive a response by 131. One or more of the payment methods include how to install the app, how to use the app, how to watch ads, how to ad banners, how to participate in surveys, how to participate in quizzes, how to pay online, how to participate in games, and how to convert points associated with other accounts of the user 131. It may include at least one of the manner. For example, when a user launches an Internet browser on a smartphone and navigates to a specific mobile web page, any advertiser's logo provided by the entry server 115 is presented, and by the user responding, the response to clicking on the logo is presented. It may be sent to the entry server 115.

In some embodiments, the reward providing unit 620 receives a response by the user 131 of the user device 130 for one or more payment methods, as described above, and the user 131 receives a reward for the response. It may be configured to provide to an account associated with. If a reward is provided to an account associated with the user 131 by the reward providing unit 620, the database 650 may be configured to include an account associated with the user 131 and information about the account. Appropriate rewards according to any response may be designed to differ depending on the nature and type of advertising scheme.

In some embodiments, the reward may include at least one of an entry ticket and points that can participate in the event. The provided points may be converted into an entry ticket that can be found and used like cash or participate in an event provided by the application server 115. When the reward providing unit 620 receives a request from the user device to convert the point into an entry right, the reward providing unit 620 may be configured to convert the point into an entry right according to the request. When the user is provided with the entry right, the user may use the event to participate in the event provided by the entry server 115. In addition, the reward providing unit 620 may be configured to determine a user's rating based on points in an account associated with the user 131. Accordingly, the user 131 may participate in the differentiated event according to the determined grade of the user 131.

In an example embodiment, the event providing unit 630 may be configured to receive a request to participate in an event from the user device 130 and to provide at least some of the program command some data associated with the event to the user device in accordance with the request. Can be. Furthermore, the event providing unit 630 may be further configured to provide at least some of the program instructions and data associated with the differentiated event to the user device according to the determined grade of the user 131. Accordingly, the user 131 may determine whether to execute the event or not and transmit an execution instruction.

In an example embodiment, the event execution unit 640 may be configured to receive an instruction regarding the execution of the event from the user device 130 and to execute the event in accordance with the instruction. Since the user 131 needs to use the reward to participate in the event, the event execution unit 640 subtracts at least a part of the reward of the account associated with the user according to the event execution instruction, and the result of the event execution is the user device. And may be further configured to provide 130.

In some demonstrative embodiments, the provided event may include an alphabetical matching event associated with the advertisement. The alphabet matching event is implemented by one or more instructions stored in the entry server 115. In response to such an instruction, the entry server 115 causes the at least one English word associated with the advertisement to be displayed on the user device 130 and at least one of the plurality of alphabets according to the instruction regarding the execution of the event from the user device 130. Can be configured to randomly select. In addition, the entry server 115 determines whether any combination of the at least one selected alphabet matches at least one English word, and if the determination result matches, provides the result to the account associated with the user 131. It can be further configured.

7 is a block diagram illustrating an example user device 130, in accordance with at least some embodiments described herein. As shown in FIG. 7, the user device 130 may include a code application 710, a store application 720, an SNS application 730, an application application 740, and a memory 750. Although not shown in FIG. 7, the user device 130 may further include an operating system, a processor, a display, and a dial pad. While each unit of FIG. 7 is shown as a separate component, various components may be separated into additional components, combined into fewer components, or removed without departing from the scope of the disclosed subject matter. Those skilled in the art will appreciate that each function and / or operation of a component may be implemented individually and / or collectively by hardware, software, firmware or virtually any combination thereof.

The code application 710 of the user device 130 may further communicate with the code server 111 via the network 120. In some embodiments, each of the one or more codes may be matched with data associated therewith and stored in a memory of a code server, and furthermore, at least some of the one or more codes may be cached from the code server to store the memory 750 of the user device 130. ) May be matched with and stored in the data associated therewith.

In some embodiments, the code application 710 may be configured to receive any code from an user via an input device such as a dial pad (eg, a separate mechanical pad, a GUI pad represented on a display, etc.). In response to receiving any code, in some embodiments, the code application 710 may be further configured to retrieve data that matches the code entered by the user in the memory 750 of the user device 130. By way of example, and not by way of limitation, if no data matching the code entered into the memory 750 is retrieved, the code application 750 communicates with the code server 111 to match the code entered from the code server 111. Can be configured to receive data, such as record values. In some other embodiments, in some other embodiments, the code application 710 is directed to the ad log server 112 and / or the code server 111 for code for a particular advertiser, code for a particular advertiser's particular page of advertising, and a user. It may be configured to transmit at least one of the information about the user 131 of the device 130. In some embodiments, the code application 710 may be configured to receive from the code server 111 a record value that includes a code about a particular advertiser and a code about a particular advertisement page.

In some embodiments, the code application 710 calls the store application 720 to proceed with the execution and / or installation of a particular application when data matching the retrieved code is associated with the execution and / or installation of the particular application. It can be further configured to. The invoked user application 720 may be configured to send a request of the application to be executed and / or installed to the application server 113 based on the data matching the retrieved code. In some other embodiments, the code application 710 may be configured to query the advertising content to the advertiser device of the particular advertiser based on the received record value, and may be configured to receive the advertising content queried from the advertiser device of the particular advertiser. Can be. In some embodiments, user device 130 may be configured to receive advertisement content of a particular advertiser device from ad log server 111 and / or code server 112.

In some embodiments, store application 720 may be configured to send a request of an application that a user wishes to run and / or install to application server 113. Accordingly, by way of example and not by way of limitation, the request of the application may include at least one of a request for execution or an installation request of the application. In some embodiments, store application 720 may be further configured to receive data associated with the requested application from application server 113. By way of example, and not limitation, associated data may include at least one of data for execution or data for installation. In some embodiments, the store application 720 may be further configured to run and / or install the requested application on the user device 130 using the received data.

In some embodiments, SNS application 730 may be configured to send a list of users to SNS server 114. In some embodiments, the SNS application 730 may be configured to transmit status information data for at least a second user included in the list received from the user to the SNS server 114. In some embodiments, SNS application 730 may be configured to send a status information request to SNS server 114. By way of example, and not limitation, the status information request may include at least one of a call from the second user device 130 to the user device 130 and a call from the user device 130 to the second user device 140. . In some embodiments, SNS application 730 may be configured to receive status information data of a particular user from SNS server 114. For example, when the state information request from the user device 130 includes a call with the second user device 130, the received state information data may be state information data designated by the second user for the user, and the user device. 130 may be configured to display the state information data received on the display 330 together with the calling screen to the second user device 130.

In some embodiments, SNS application 730 may be configured to send shared content to user status information server 110. In some other examples, when a user wants to share his or her shared content by restricting it to a specific user, the SNS application 730 may share the tag of at least one user specified by the user among one or more other users included in the list with the shared content. It may be configured to transmit to the SNS server 114 together, and may also be configured to receive other users' shared content from the SNS server 114. In some embodiments, SNS application 730 may be configured to send subscription content to SNS server 114 along with tags of other users included in the list that created the received shared content.

In some embodiments, SNS application 730 may be configured to transmit credit data for a particular user among one or more other users included in the list. In addition, the SNS application 730 may be configured to receive credit data generated by another user from the SNS server 114. In some embodiments, SNS application 730 may be configured to receive from SNS server 114 an ordered list based on a predetermined rule based on a credit count for each user included in the list.

In some embodiments, entry application 740 may be configured to receive some of the program instructions and data associated with the event from entry server 115. It may also be configured to send a response of the user 131 to the entry server 115 and may be configured to display the entry event execution and / or the result of the execution on a display of the user device.

In some embodiments, memory 750 may be configured to store data relating to

various applications

710, 720, 730, and 740 and / or user 131 on user device 130. By way of example, and not limitation, the memory 750 may be an internal memory located inside the user device 130 as shown in FIG. 7, but alternatively, an external database or an internal memory and an external database electrically connected to the outside may be used. It may be any combination. The memory 750 also includes one or more of volatile memory, nonvolatile memory, flash memory, programmable variables or states, random access memory (RAM), read-only memory (ROM), or other static or dynamic storage media. Various memory media that are not limited thereto may be included.

Although in FIG. 7, the code application 710, the store application 720, the SNS application 730, and the application application 740 are implemented as separate applications, these are only some examples, and depending on the implementation method, two or more applications may be used. The application may be integrated into one application, and each application may be divided into two or more applications according to the plurality of functions. By way of example, and not limitation, the code application 710 may be integrally implemented as one functional module of the store application 720. In this case, according to the embodiment, when the user device 130 transmits the code to the code server (eg, the code server 111), the user equipment 130 does not go through the procedure of receiving a record value corresponding to the code from the code server. Instead, the application itself (eg, the application server 113) may receive the application itself or some data about the code.

8 is a flow diagram illustrating an example advertisement log data providing process of the advertisement log server 112, in accordance with at least some embodiments described herein. The process is shown to be performed sequentially starting with block 810 and finally with block 870. It will be appreciated that blocks 810-870 may be rearranged appropriately to suit a particular embodiment, and that some or some of these blocks may be performed concurrently in some embodiments. It will also be appreciated that in some embodiments various blocks may be removed, divided into additional blocks, and / or combined with other blocks.

The process may begin at block 810 "receive code for each advertiser, code for one or more advertising pages, and advertising content" from multiple advertiser devices. The advertisement log server 112 may receive the code for each advertiser, the code for one or more advertisement pages, and the advertisement content, directly and / or indirectly from the plurality of advertiser devices, through the code server 111.

Block 810 may be followed by block 820 "code for each advertiser received, code for one or more ad spaces, and storage of ad content". The ad log server 112 may store the received code for each advertiser, the code for one or more advertisement pages, and the advertisement content in the database 320.

Block 820 may be followed by block 830 "receiving at least one of a code for a particular advertiser among a plurality of advertisers, a code for a particular advertisement space of a particular advertiser and information about a user of a user device". The ad log server 112 may be associated with a code relating to a particular advertiser acquired by the user 131, directly from the user device 130 and / or indirectly through the code server 111, relating to a particular advertiser's specific advertising space. A code and at least one of information about the user 131 of the user device 130 may be received. By way of example, and not limitation, the user information may include at least one of a user's gender, age, occupation, region of residence, and hobbies.

Block 830 may be followed by block 840 "search for code in a database for a particular advertiser and code for a particular advertiser's specific page of advertising". The advertisement log server 112 may search the database 320 for a code regarding a specific advertiser and a code regarding a specific advertisement space of a specific advertiser.

Block 840 may be followed by block 850 "storing ad log data in a database that includes code associated with the retrieved particular advertiser and user information associated with code associated with the particular advertisement page and user information." . The advertisement log server 112 may store advertisement log data including a user information associated with a code related to a searched specific advertiser and a code related to a specific advertisement page and user information.

Block 850 may be followed by block 860 "receiving a request for advertisement log data from at least one advertiser device of a plurality of advertiser devices". The advertisement log server 112 may receive a request for advertisement log data, directly from the advertiser device and / or indirectly through the code server 111.

Block 860 may be followed by block 870 "in response to the request, sending ad log data stored in a database to at least one advertiser device". In response to the request of the advertiser device, the advertisement log server 112 is processed by the processing unit 340 to directly and / or indirectly through the code server 111 the advertisement log data stored in the database 320 to the advertiser device. Can be sent.

9 is a flowchart illustrating an example application creation and provisioning process of an application server 113, in accordance with at least some embodiments described herein. The process is shown to be performed sequentially starting with block 911 and finally to block 922. It will be appreciated that blocks 911-922 may be rearranged appropriately to suit a particular embodiment, and that some or some of these blocks may be performed concurrently in some embodiments. It will also be appreciated that in some embodiments various blocks may be removed, divided into additional blocks, and / or combined with other blocks.

The process may begin at block 911 "receive at least one content and template type of application required from subscriber device". The receiving unit 410 of the application server 113 is a template type and at least one content of an application requested by the subscriber from the subscriber device (eg, the user device 130, the second user device 140, and / or the advertiser device). Can be received.

Block 911 may be followed by block 912 "retrieving the template source in the database corresponding to the received template type". The search unit 420 of the application server 113 may search the database 460 for a template source corresponding to the received template type.

Block 912 may be followed by block 913 "generating the required application based on the retrieved template source and at least one content". The application generating unit 430 of the application server 113 is based on the retrieved template source and at least one content received from the subscriber device (eg, the user device 130, the second user device 140, and / or the advertiser device). To generate the required application.

Block 913 may be followed by block 914 "storing the generated application and data associated with the generated application in a database". The database 460 of the application server 113 may store the generated application and data associated with the generated application.

Block 914 may be followed by block 915 "Send the generated application to the subscriber device". In some embodiments, the sending unit 440 of the application server 113 may send the generated application to the subscriber device (eg, the user device 130, the second user device 140, and / or the advertiser device). If receiving second content from the subscriber device, block 914 may continue to block 916 and if receiving a request of an application from the user device 130, block 914 to block 920. You can continue.

Block 915 may then begin at block 916 "receive second content from subscriber device". The receiving unit 410 of the application server 113 may receive the second content from the subscriber device (eg, the user device 130, the second user device 140, and / or the advertiser device).

Block 916 may be followed by block 917 "modifying an application generated based on the second content, in response to receiving". The modification unit 450 of the application server 113 may modify the application generated by the application server 113 based on the second content in accordance with the subscriber's request.

Block 917 may be followed by block 918 "storing the data associated with the modified application and the modified application in a database". The database 460 of the application server 113 may store the modified application and data associated with the modified application.

Block 918 may be followed by block 919 "Send the modified application to the subscriber device". The sending unit 440 of the application server 113 may send the application to the subscriber device (eg, the user device 130, the second user device 140, and / or the advertiser device).

Block 915 or block 919 may begin next to block 920 "receiving a request of an application from a user device". The receiving unit 410 of the application server 113 may receive a request of an application of the user from the user device 130.

Block 920 may be followed by block 921 "search for an application corresponding to the requested application in the database in response to the request". The retrieval unit 420 of the application server 113 may retrieve the application corresponding to the requested application from the memory in response to receiving the request of the application from the user device 130.

Block 921 may be followed by block 922 "transfer associated data for the retrieved application to the user device". The transmitting unit 440 of the application server 113 may transmit data associated with the retrieved application stored in the database 460 to the user device 130. When performed from block 920 to block 921 next to block 919, the sending unit 440 sends the application modified by the modifying unit 450 to the user device 130 based on the second content. Can transmit

10 is a flow diagram illustrating a process of providing exemplary state information data for an SNS server 114, in accordance with at least some embodiments described herein. The process is shown to be performed sequentially, beginning with block 1010 and finally with block 1050. It will be appreciated that blocks 1010-1050 may be rearranged appropriately to suit particular embodiments, and such blocks or portions thereof may be performed concurrently in some embodiments. It will also be appreciated that in some embodiments various blocks may be removed, divided into additional blocks, and / or combined with other blocks.

The process may begin at block 1010 "Receive a list containing information of one or more other users associated with the user from the user device and store in a database". The SNS server 114 may receive a list of users from the user device 130 and store them in the database 520 of the plurality of users of the SNS server 114.

Block 1010 may be followed by block 1020 “receive state information data for at least a second user included in the list from the user device of the user”. The SNS server 114 may receive state information data for at least a second user included in the list from the user device 130 of the user.

Block 1020 may be followed by block 1030 “storing state information data in a database”. In some embodiments, SNS server 114 may store the received state information data in database 520. For example, when the state information data for the second user is received from the user device 130, the database 520 retrieves a list of users, and the state information of the second user is included in the information of the second user included in the list. You can associate and store data.

Block 1030 may be followed by block 1040 “receive a status information request from a second user device of a second user”. The SNS server 114 may receive a status information request from the second user device 140 of the second user. By way of example, and not limitation, the status information request may include a call from the second user device 140 to the user device 130.

Block 1040 may be followed by block 1050 "transmitting the status information data stored in the database to the second user device in response to the status information request". The SNS server 114 may transmit the state information data stored in the database 520 to the second user device 140 in response to the state information request.

11 is a flowchart illustrating an example shared content providing process of the SNS server 114, in accordance with at least some embodiments described herein. The process is shown to be performed sequentially, beginning with block 1110 and finally with block 1130. It will be appreciated that blocks 1110-1130 may be rearranged appropriately to suit a particular embodiment, and that some or some of these blocks may be performed concurrently in some embodiments. It will also be appreciated that in some embodiments various blocks may be removed, divided into additional blocks, and / or combined with other blocks.

The process may begin at block 1110 "receive shared content from a user device". The SNS server 114 may receive shared content from the user device 130. In some other examples, the SNS server 114 may receive, together with the shared content, a tag of at least one user designated by the user among one or more other users included in the list.

Block 1110 may be followed by block 1120 "store received shared content in a database." The SNS server 114 may store the received shared content in the database 520.

Block 1120 may be followed by block 1130 "send the received shared content to the user device of one or more other users included in the list". The SNS server 114 may transmit the shared content received from the user device 130 to the user device of one or more other users included in the list. When the SNS server 114 receives a tag of the at least one user specified by the user among the one or more other users included in the list from the user device 130, based on the received tag, the SNS server 114 of the at least one user specified by the user The received shared content may be transmitted to the user device.

12 is a flowchart illustrating an example credit data and / or credit count provision process of the SNS server 114, in accordance with at least some embodiments described herein. The process is shown to be performed sequentially, beginning with block 1210 and finally with block 1250. It will be appreciated that blocks 1210-1250 may be rearranged appropriately to suit a particular embodiment, and that some or some of these blocks may be performed concurrently in some embodiments. It will also be appreciated that in some embodiments various blocks may be removed, divided into additional blocks, and / or combined with other blocks.

The process may begin at block 1210 “receive credit data for a particular user from one or more other users included in the list from the user device”. The SNS server 114 may receive credit data for a particular user from one or more other users included in the list from the user device 130.

Block 1210 may be followed by block 1220, "storing credit data for a particular received user in a database." The SNS server 114 may store the credit data for the received specific user database 520. For example, the SNS server 114 may retrieve an account associated with a particular user from the database 520 and associate and store the credit data received in that account.

Block 1220 may be followed by block 1230 "increasing the credit count for a particular user in the database by one". SNS server 114 may increment the credit count for a particular user in database 520 by one. The SNS server 114 may search for an account associated with a specific user in the database 520, and increase and store a credit count included in the account by one.

Block 1230 may be followed by block 1240 "transfer credit data to a user device of a particular user". The SNS server 114 may transmit the credit data to the user device of the specific user.

Block 1240 may be followed by block 1250 "receiving a second content from the subscriber terminal at the user device by sorting the credit count for each user included in the list based on a predetermined rule". The SNS server 114 may sort the credit count for each user included in the list based on a predetermined rule and transmit the credit count to the user device 130.

13 is a flow diagram illustrating an example process of an entry server 115, in accordance with at least some embodiments described herein. The process is shown to be performed sequentially, beginning with block 1310 and finally with block 1350. It will be appreciated that blocks 1310-1350 may be rearranged appropriately to suit a particular embodiment, and such blocks or portions thereof may be performed concurrently in some embodiments. It will also be appreciated that in some embodiments various blocks may be removed, divided into additional blocks, and / or combined with other blocks.

The process may begin at block 1310 "transfer one or more payment methods to which a reward may be provided to a user device". For example, the application server 115 may include an app installation method, an app usage method, an advertisement viewing method, an advertisement banner method, a survey participation method, a quiz participation method, an online payment method, a game participation method, and a user 131 as described above. One or more payment methods including at least one of the point conversion methods associated with another account may be transmitted to the user device 130.

Block 1310 may be followed by block 1320 "receive a response by the user of the user device for one or more payment methods from the user device". Depending on the payment method provided, different user responses may be sent from the user device 130, for example to the entry server 115.

Block 1320 may then be followed by block 1330 "in accordance with the receipt of the response, providing a reward for the response to an account associated with the user". For example, the entry server 115 may provide an appropriate reward according to the user response to the account associated with the user 131, and provide corresponding information to the database 650. In some demonstrative embodiments, the database 650 may update information about an account associated with a user. In some embodiments, entry server 115 may determine a user's rating based on a reward of an account associated with the user.

Block 1330 may then follow block 1340 "receive a request to join an event from the user device, thereby providing at least some of the program instructions and data associated with the event to the user device". Accordingly, the user device may, for example, receive information associated with the event from the entry server 115, and the user may determine whether or not to execute the event and transmit the execution instruction to the entry server 115. In some embodiments, entry server 115 may provide at least some of the program instructions and data associated with the differentiated event to the user device in accordance with the determined grade of user 131.

Block 1340 is next received by block 1350 "instructions regarding the execution of the event from the user device, executes the event in accordance with the instructions, thereby deducting at least some of the rewards of the account associated with the user, and executing the event. Provide the user with a result according to the " Receive an instruction regarding the execution of the event from the user device 130 and execute the event according to the instruction, and the user participates in the event using the reward, and thus may be some or all of the rewards of the account associated with the user, The predetermined reward corresponding to the participating event may be subtracted, and the result of the event execution may be provided to the user device.

14 is a flowchart illustrating an example process of an example event performed by the entry server 115, in accordance with at least some embodiments described herein. The process is shown to be performed sequentially, beginning with block 1410 and finally with block 1430. It will be appreciated that blocks 1410-1430 may be rearranged appropriately to suit particular embodiments, and such blocks or portions thereof may be performed concurrently in some embodiments. It will also be appreciated that in some embodiments various blocks may be removed, divided into additional blocks, and / or combined with other blocks.

The process may begin at block 1410 “displaying at least one English word associated with an advertisement on a user device”. In order to maximize advertising effectiveness, at least one English word associated with an advertiser's advertisement is transmitted to the user device, or such English word on the user device using at least some of the program instructions and data associated with the event provided for the event execution. Can be displayed.

Block 1410 may be followed by block 1420, "optionally selecting at least one of the plurality of alphabets in accordance with an instruction regarding the execution of the event from the user device". The user device may receive an instruction regarding execution of an event from the user device, and thus may select at least one of a plurality of alphabets.

Block 1420 is followed by block 1430 "determine whether any combination of the at least one selected alphabet matches at least one English word and, if so, provide the result to the account associated with the user." Can follow. At least one of the plurality of alphabets is selected, the result is compared with the English word, and the result is provided to the account associated with the user if it matches. In some demonstrative embodiments, database 650 may be configured to update information for an account associated with a user, for example, if the event is a giveaway event, the user may obtain a giveaway based on the result.

15 is a flowchart illustrating an example process of server system 110, in accordance with at least some embodiments described herein. The process is shown to be performed sequentially starting with block 1501 and finally with block 1513. It will be appreciated that blocks 1501-1513 may be rearranged appropriately to suit particular embodiments, and such blocks or portions thereof may be performed concurrently in some embodiments. It will also be appreciated that in some embodiments various blocks may be removed, divided into additional blocks, and / or combined with other blocks.

The process may begin at block 1501 “receive at least one of a code relating to an application for an advertiser and a code relating to an advertiser's advertising page obtained by a user from a user device”. The code server 111 may receive, from the user device 130, at least one of a code relating to an application for an advertiser acquired by the user 131 and a code relating to an advertisement page of the advertiser. By way of example, and not limitation, the code for the application for the advertiser may include at least one number and at least one symbol, and the code for the advertisement page may include at least one number. By way of example, and not limitation, the advertising page may refer to the means for the advertiser to execute the advertisement.

Block 1501 may be followed by block 1502 "Receive at least one of a code about an application for an advertiser, a code about an advertising space, and user information about a user of the user device" acquired by the user from the user device. have. The advertisement log server 112 may receive and store in the database 320 at least one of a code regarding an application for an advertiser, a code regarding an advertisement page of an advertiser, and information about a user of a user device.

Block 1502 may be followed by block 1503 "searching the database for code relating to the application for the advertiser and code for the advertiser's advertising space received from the user device". The code server 111 and / or the ad log server 112 may retrieve from the

respective databases

230 and 320 the codes relating to the application for the advertiser and the codes relating to the advertiser's advertising space received from the user device 130. Can be.

Block 1503 may be followed by block 1504 "Return to the user device the record value that the code for the application for the retrieved advertiser and the code for the advertisement page contains". The code server 111 may return to the user device 130 a record value included in the code for the application for the searched advertiser and the code for the advertisement page of the advertiser.

Block 1504 may be followed by block 1505 "storing ad log data comprising a code relating to an application for a searched advertiser and a code relating to an advertisement page and user information to a database". The advertisement log server 112 may store the advertisement log data including the code regarding the application for the searched advertiser and the code regarding the advertisement page and the user information in the database 320.

Block 1505 may be followed by block 1506 "receiving a request for advertisement log data from an advertiser device and transmitting at least one advertisement log data stored in a database to an advertiser device". The ad log server 112 may be configured to receive a request for ad log data from the advertiser device, and in response, the code relating to the application for the advertiser of the advertiser device stored in the database 320 and the advertiser's ad space. At least one advertisement log data including user information associated with the code may be transmitted to the advertiser device.

Block 1506 may be followed by block 1507 "receiving an application's request for an advertiser from a user device". The application server 113 may receive a request of an application for an advertiser from the user device 130. The user device 130 may request a user to execute and / or install an application for an advertiser, and thus, the user's request may include at least one of an execution request and an installation request.

Block 1507 may be followed by block 1508 "in response to the request of the application for the advertiser, searching the database for an application corresponding to the application for the requested advertiser". The application server 113 may, in response to receiving the request of the application for the advertiser from the user device 130, retrieve the application from the database 460 corresponding to the application for the requested advertiser.

Block 1508 may be followed by block 1509 "Send data associated with the retrieved application to the user device". When an application corresponding to the application requested by the user is retrieved from the database 460, the application server 113 may transmit data associated with the retrieved application stored in its database to the user device 130. As the application's request to the user's advertiser may include at least one of a launch request or an install request, the data associated with the retrieved application that the application server 113 sends to the user device 130 may execute the requested application. It may include at least one of data for or data for installation.

Block 1509 may be followed by block 1510 "receiving shared content that includes information provided by an application for an advertiser from a user device". The SNS server 114 may receive shared content including information provided by an application for an advertiser from the user device 130. In some other examples, the SNS server 114 may receive, along with its shared content, a tag of at least one user designated by the user 131 among one or more other users included in the list. By way of example, and not limitation, the user 131 may be content that can be configured to be shared with other users, and may include various types of files such as text, images, video files, and audio files.

Block 1510 may be followed by block 1511 "store the received shared content in a database and send the shared content to the user device of one or more other users included in the list". The SNS server 114 may store the received shared content in the database 520 and transmit the shared content received from the user device 130 to the user device of one or more other users included in the list. For example, when receiving a tag of at least one user designated by the user 131 among one or more other users included in the list from the user device 130, at least one of the at least one designated by the user 131 based on the received tag is received. The received shared content may be transmitted to the user device of one user.

Block 1511 may be followed by block 1512 “receive a response by the user of the user device for one or more payment methods for which rewards may be provided”. In some embodiments, entry server 115 may receive a response by user 131 of user device 130 for one or more payment methods for which rewards may be provided. For example, the code server 111 receives, or from the user device 130, an application for an advertiser from the user device 130, at least one of a code for an application for the advertiser and a code for the advertiser's advertising page. Of the user 130 for one or more payment methods when the application server 113 receives a request of the user or the SNS server receives, from the user device 130, shared content including information provided by an application for an advertiser. ) May be considered to have received a response by the user 131 of the device.

Block 1512 may be followed by block 1513, "If a response is received by the user of the user device, providing a reward to an account associated with the user." The application server 115 may provide a reward to an account associated with the user 131 when receiving the response by the user 131 of the user device 130. By way of example, and not limitation, a reward may include at least one of an entry ticket and points that can participate in an event.

16 is a block diagram of an example computer program for providing advertisement log data, in accordance with at least some embodiments described herein. Program product 1600 may include a signal bearing medium 1602. The signal bearing medium 1602 may include one or more instructions 1604 that, when executed by a processor, for example, may provide the functionality described above with respect to FIGS. 8-15. For example, the instructions 1604 may include one or more instructions to cause the user device to receive at least one of a code relating to an application for a particular advertiser and a code relating to a specific advertisement page of the specific advertiser; One or more instructions for receiving, by the user device, at least one of a code about the application for the specific advertiser, a code about the specific advertisement page of the specific advertiser, and user information about the user of the user device; One or more instructions for retrieving at least one record value contained in at least one of a code relating to the application and a code relating to the specific advertisement page received from the user device; One or more instructions for transmitting the retrieved at least one record value to the user device; One or more instructions for receiving, from the user device, a request of an application for the particular advertiser based on the transmitted at least one record value; And in response to a request of an application for the specific advertiser, one or more instructions for retrieving an application corresponding to the requested application from the database and transmitting data related thereto to the user device.

In some implementations, the signal bearing medium 1602 can include, but is not limited to, computer readable media 1606, such as a hard disk drive, CD, DVD, digital tape, memory, and the like. In some implementations, the signal bearing medium 1602 can include, but is not limited to, a recordable medium 1608 such as a memory, read / write (R / W) CD, R / W DVD, and the like. In some implementations, the signal bearing medium 1602 can include a communication medium 1610 such as digital and / or analog communication media (eg, fiber optic cables, waveguides, wired communication links, wireless communication links, etc.). However, it is not limited thereto. Thus, for example, the program product 1600 may include a signal bearing medium 1602 to an RF signal bearing medium 1602 carried by the wireless communication medium 1610 (eg, a wireless communication medium conforming to the IEEE 802.11 standard). By one or more modules.

17 illustrates a general purpose computing device 1700 that may be used to implement a system for providing advertisement log data, in accordance with at least some embodiments described herein. In this example, the components of computing device 1700 may be arranged or configured for an advertising system. In a very basic configuration 1702, computing device 1700 typically includes one or more processors 1704 and system memory 1706. Memory bus 1708 may be used for communication between processor 1704 and system memory 1706.

Depending on the configuration desired, the processor 1704 may be of any type including, but not limited to, a microprocessor (μP), a microcontroller (μC), a digital signal processor (DSP), or any combination thereof. The processor 1704 may include one or more levels of caching, processor cores 1714 and registers 1716, such as level 1 cache 1710 and level 2 cache 1712. The example processor core 1714 may include an arithmetic logic unit (ALU), a floating point unit (FPU), a digital signal processing core (DSP core), or any combination thereof. The example memory controller 1718 may also be used with the processor 1704, or in some implementations, the memory controller 1718 can be an internal component of the processor 1704.

Depending on the configuration desired, system memory 1706 may be of any type, including but not limited to volatile memory (such as RAM), nonvolatile memory (such as ROM, flash memory, etc.), or any combination thereof. System memory 1706 may include an operating system 1720, one or more applications 1722, and program data 1724. The application 1722 may include instructions 1726 that may be arranged to perform the functions described herein, including the operations described with respect to the process of FIGS. 4-6. Program data 1724 may include advertisement log data 1728 that may be used to implement instructions 1726. In some examples, application 1722 may be arranged to operate with program data 1724 on operating system 1720 to implement the instructions described herein.

Computing device 1700 may have additional features or functionality, and additional interfaces to facilitate communication between basic configuration 1702 and any desired device and interface. For example, the bus / interface controller 1730 may be used to facilitate communication between the basic configuration 1702 and one or more data storage devices 1732 via the storage interface bus 1734. The data storage device 1732 can be a removable storage device 1736, a non-removable storage device 1738, or a combination thereof. Examples of removable and non-removable storage devices include, in some words, magnetic disk devices such as flexible disk drives and hard disk drives (HDDs), optical disks such as compact disk (CD) drives or digital versatile disk (DVD) drives. Drives, solid state drives (SSDs), and tape drives. Exemplary computer storage media may include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. have.

System memory 1706, removable storage 1736, and non-removable storage 1738 are examples of computer storage media. Computer storage media may include RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical storage device, magnetic cassette, magnetic tape, magnetic disk storage device or other magnetic storage device, or It includes, but is not limited to, any other medium that can be used to store desired information and can be accessed by the computing device 1700. Any such computer storage media may be part of computing device 1700.

The computing device 1700 facilitates communication from various interface devices (eg, output device 1742, peripheral interface 1744, and communication device 1746) through the bus / interface controller 1730 to the basic configuration 1702. It may also include an interface bus 1740 to facilitate. Exemplary output device 1742 includes a graphics processing unit 1748 and an audio processing unit 1750, which is configured to communicate to various external devices such as a display or speaker via one or more A / V ports 1756. Can be. Exemplary peripheral interface 1744 includes a serial interface controller 1754 or a parallel interface controller 1756, which is connected to one or more input devices (eg, keyboard, mouse, pen, voice input) through one or more I / O ports 1758. Devices, touch input devices, etc.) or other peripheral devices (eg, printers, scanners, etc.). Exemplary communication device 1746 includes a network controller 1760, which may be arranged to facilitate communication with one or more other computing devices 1762 on a network communication link via one or more communication ports 1764. .

The network communication link may be one example of a communication medium. Communication media may typically be implemented by computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier or other transmission mechanism, and may include any information delivery media. A "modulated data signal" can be a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct wired connection, and wireless media such as acoustic, radio frequency (RF), microwave, infrared (IR), and other wireless media. It may include. The term computer readable media as used herein may include both storage media and communication media.

Computing device 1700 may be a mobile phone, personal data assistant, personal media player device, wireless web-watch device, personal headset device, special purpose device, or a hybrid including any of the above functions. It may be implemented as part of a small form factor portable (or mobile) electronic device such as a device. Computing device 1700 may also be implemented as a personal computer including both laptop computers and non-laptop computer configurations.

The present disclosure is not to be limited in terms of the particular embodiments described in this application, which are intended as illustrations of various aspects. As will be apparent to those skilled in the art, many modifications and variations can be made without departing from the spirit and scope thereof. In addition to those listed herein, methods and apparatus that are functionally equivalent within the scope of the present disclosure will be apparent to those skilled in the art from the above description. Such modifications and variations are intended to fall within the scope of the appended claims. This disclosure will be limited only by the terms of the appended claims, along with the full scope of equivalents to which such claims are entitled. It is to be understood that this disclosure is not limited to particular methods, reagents, compounds, compositions or biological systems, which may of course vary. It is also to be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting.

With respect to the use of virtually any plural and / or singular term herein, one skilled in the art can interpret the plural to singular and / or the plural to plural, as appropriate to the context and / or application. Various singular / plural substitutions may be explicitly described herein for clarity.

Those skilled in the art will understand that the terms generally used herein and in particular used in the appended claims (eg, the appended claims text) are generally intended to be “open” terms (eg, terms "Comprising" should be interpreted as "including but not limited to", the term "having" is "having at least", and the term "comprising" is "including but not limited to" and the like). Moreover, those skilled in the art will understand that, where a specific number of descriptions in the claims introduced are intended, such intent will be expressly stated in the claims, and in the absence of such description, no such intent is given. For example, for purposes of understanding, the following appended claims may introduce claims disclosure, including the use of introductory phrases such as “at least one” and “one or more”. However, the use of such phrases, where the introduction of a claim description by the indefinite article “a” (“a” or “an”), includes, in one embodiment, such a claim description. It should not be construed as limiting any particular claim, including indefinite articles such as "one or more" or "at least one" and "one" ("a" or "an"), in which the same claim is introduced. Should be interpreted as well (eg, "one" should be interpreted to mean "at least one" or "one or more"). This also applies to the case of definite articles used to introduce claim recitations. In addition, even if a particular number of claims disclosures is expressly stated, those skilled in the art will understand that such descriptions should typically be interpreted to mean at least the stated number (eg, without two modifiers, the "two descriptions" A simple description "means at least two entries or two or more entries). In addition, where rules similar to “at least one of A, B and C, etc.” are used, it is generally intended that such interpretations will be understood by those skilled in the art (eg, “A, B and C”). A system having at least one of the following: A has only A, has only B, has only C, has A and B together, has A and C together, has B and C together, Systems having B and C together, and the like). Where rules similar to “at least one of A, B or C, etc.” are used, it is generally intended that such interpretations will be understood by those skilled in the art (for example, at least one of “A, B or C”). A system with one "has only A, only B, only C, or A and B together, A and C together, B and C together, A, B and Systems with C, and the like). Those skilled in the art will also recognize that substantially any disjunctive word and / or a phrase indicating two or more alternative terms, whether one in the description, claims or drawings, is one of those terms, the term It will be understood that it should be understood to consider the possibility of including either or both of the terms. For example, the phrase "A or B" will be understood to include the possibility of "A" or "B" or "A and B".

In addition, if a feature or aspect of the disclosure is described in terms of Markush groups, those skilled in the art will recognize that the disclosure is described in terms of any individual element or subgroup of elements in the Markush group.

As will be appreciated by those skilled in the art, for any and all purposes, such as in providing a written description, all ranges disclosed herein also include any and all possible subranges and combinations of such subranges. Any listed range can be readily appreciated as fully describing and enabling the same range, which is divided into at least 1/2, 1/3, 1/4, 1/5, 1/10, and the like. By way of example, and not limitation, each range discussed herein may be divided into a lower third, a middle 1/3, an upper 1/3, and the like. In addition, it should be understood by those skilled in the art that all languages, such as "up to", "at least", and the like, include numbers that are described and that may be subsequently subdivided into the foregoing subranges. Finally, it should be understood that the scope includes each individual element. Thus, for example, a group having 1-3 cells refers to groups having 1, 2 or 3 cells. Similarly, a group having 1-5 cells refers to a group having 1, 2, 3, 4 or 5 cells, and the like.

From the foregoing, various embodiments of the present disclosure have been described herein for purposes of illustration, and it will be understood that various modifications may be made without departing from the spirit and scope of the present disclosure. Accordingly, the various embodiments disclosed herein are not intended to be limiting, the true scope and spirit of which are set forth in the following claims.

Claims

As a method for providing a mobile service platform,

Receiving, by a code server, at least one of a code relating to an application for a specific advertiser and a code relating to a specific advertisement page of the specific advertiser acquired by the user device;

Receiving, by an advertisement log server, at least one of a code relating to the application for the specific advertiser acquired by the user device, a code relating to the specific advertisement page of the specific advertiser, and user information about a user of the user device. step;

Retrieving, by the code server, at least one record value in the database, the code relating to the application and the code relating to the particular advertisement page received from the user device;

Transmitting, by the code server, the retrieved at least one record value to the user device;

Receiving, by the application server, a request from the user device of an application for the particular advertiser based on the transmitted at least one record value; And

Responsive to a request of an application for the particular advertiser, retrieving an application corresponding to the requested application from the database and transmitting, by the application server, data associated therewith to the user device;

How to include.
The method of claim 1,

Wherein the code relating to the application for the particular advertiser includes at least one number and at least one symbol.
The method of claim 1,

And wherein the code for the particular advertising page includes at least one number.
The method of claim 1,

The database is for a plurality of advertisers, and stores code for an application for each advertiser and code for one or more advertisement pages, wherein the method includes:

Retrieving, by the advertisement log server, the code relating to the application for the specific advertiser and the code relating to the specific advertisement page of the specific advertiser in the database; And

Storing, by the advertisement log server, advertisement log data including code associated with the application for the searched specific advertiser and code associated with the specific advertisement page and the associated user information in association with the user information. Steps to

How to include more.
The method of claim 4, wherein

Wherein each of the one or more ad spaces relates to a particular advertising point.
The method of claim 4, wherein

Wherein the user information includes at least one of a gender, age, occupation, region of residence and hobby of the user.
The method of claim 4, wherein

Receiving, by the advertisement log server, a request for the advertisement log data from the device of the particular advertiser; And

Transmitting, by the advertisement log server, the advertisement log data to the device of the specific advertiser in response to the request of the advertisement log data.

How to include more.
The method of claim 1,

Receiving, by the application server, a template type and at least one content of a required application from the device of the particular advertiser;

Retrieving, by the application server, a template source corresponding to the received template type from the database;

Generating, by the application server, the required application based on the retrieved template source and the at least one content; And

Storing, by the application server, the generated application and data associated with the generated application in the database.

How to include more.
The method of claim 8,

The storing of the generated application may further include classifying the generated application according to the type of the template, and storing the generated application and the data associated with the generated application in the database by the application server. How.
The method of claim 1,

Wherein the request of the application for the particular advertiser includes at least one of a request for execution or an installation of the application for the specific advertiser.
The method of claim 10,

And the data associated with the retrieved application includes at least one of data for execution or data for installation of the application for the particular advertiser requested.
The method of claim 1,

The database relates to a plurality of users, and to store a list containing information of one or more other users associated with the user of the plurality of users, the method comprising:

Receiving, by the SNS server, shared content including information provided by an application for the specific advertiser running or installed on the user device, from the user device;

Storing the received shared content in the database by the SNS server; And

Transmitting, by the SNS server, the received shared content to a user device of one or more other users included in the list.

How to include more.
The method of claim 12,

Receiving the shared content, receiving, by the SNS server, a tag of at least one user designated by the user from the one or more other users included in the list, from the user device;

The transmitting of the shared content may include transmitting, by the SNS server, the received shared content to a user device of at least one user designated by the user based on the tag. .
The method of claim 12,

Wherein the shared content includes a validity period of content.
The method of claim 12,

Receive, by the code server, at least one of a code regarding the application and a code relating to the specific advertisement page of the specific advertiser from the user device;

Receive, by the application server, a request of an application for the particular advertiser from the user device, or

When receiving, by the SNS server, shared content including information provided by an application for the specific advertiser from the user device,

In response, providing a reward, by the entry server, to an account associated with the user.

How to include more.
As a server system for providing a mobile service platform,

Database;

A code server configured to receive at least one of a code relating to an application for a specific advertiser acquired by the user device and a code relating to a specific advertisement page of the specific advertiser; And

An advertisement log server configured to receive at least one of a code relating to the application for the specific advertiser acquired by the user device, a code relating to the specific advertisement page of the specific advertiser, and user information about a user of the user device

Server system comprising a.
The method of claim 16,

The code server,

Retrieve from the database at least one record value contained in at least one of a code relating to the application and a code relating to the particular advertisement page received from the user device;

And further transmit the retrieved at least one record value to the user device.
The method of claim 17,

Receive, from the user device, a request of an application for the particular advertiser based on the transmitted at least one record value;

In response to a request of an application for the particular advertiser, an application server configured to retrieve an application corresponding to the requested application from the database and transmit data associated therewith to the user device;

Server system further comprising a.
The method of claim 16,

Wherein the code relating to the application for the particular advertiser includes at least one number and at least one symbol.
The method of claim 16,

Wherein the code for the particular advertising page includes at least one number.
The method of claim 16,

The database relates to a plurality of advertisers, and stores a code relating to an application for each advertiser and a code relating to one or more advertisement pages, wherein the ad log server,

Retrieve code in the database for the application for the particular advertiser and for the particular advertisement page of the particular advertiser;

And store the advertisement log data in the database, the advertisement log data comprising the associated user information in association with the code for the application for the retrieved particular advertiser and the code for the particular advertisement space and the user information. system.
The method of claim 21,

Wherein each of the one or more advertising pages is associated with a particular advertising point.
The method of claim 22,

And the user information includes at least one of sex, age, occupation, region of residence and hobby of the user.
The method of claim 21,

The advertisement log server is configured to receive a request for advertisement log data from a device of the particular advertiser;

And transmit the advertisement log data to the device of the particular advertiser in response to the request of the advertisement log data.
The method of claim 18,

The application server receives, from the device of the particular advertiser, a template type and at least one content of the requested application;

Retrieve from the database a template source corresponding to the received template type;

Generate the required application based on the retrieved template source and the at least one content;

And store the generated application and data associated with the generated application in the database.
The method of claim 25,

The application server is further configured to classify the generated application according to the type of the template, and to store the generated application and its associated data in the database.
The method of claim 18,

Wherein the request of the application for the specific advertiser includes at least one of a request for execution or an installation of the application for the specific advertiser.
The method of claim 27,

The data associated with the retrieved application includes at least one of data for execution or data for installation of the application for the requested particular advertiser.
The method of claim 18,

The database relates to a plurality of users, storing a list including information of one or more other users associated with the user among the plurality of users,

The server system,

Receiving, from the user device, shared content including information provided by an application for the particular advertiser running or installed on the user device;

Store the received shared content in the database;

SNS server configured to transmit the received shared content to the user device of one or more other users included in the list

Server system further comprising a.
The method of claim 29,

The user status information providing server, from the user device, receives a tag of at least one user designated by the user among the one or more other users included in the list;

Based on the tag, further configured to transmit the received shared content to a user device of the at least one user specified by the user.
The method of claim 29,

Wherein the shared content includes a validity period of content.
The method of claim 29,

The code server receives at least one of a code regarding the application and a code relating to the specific advertisement page of the specific advertiser from the user device,

The application server receives a request of an application for the specific advertiser from the user device, or

When the SNS server receives the shared content containing information provided by the application for the particular advertiser from the user device,

In response, the entry server is configured to provide a reward to an account associated with the user.

Server system further comprising a.
A computer program executed in a server system including a database and stored in a medium for providing a mobile service platform,

Instructions for receiving, by the user device, at least one of a code relating to an application for a specific advertiser and a code relating to a specific advertisement page of the specific advertiser;

Instructions for receiving, by the user device, at least one of a code about the application for the specific advertiser, a code about the specific advertisement page of the specific advertiser, and user information about the user of the user device;

Instructions for retrieving at least one record value included in at least one of a code relating to the application and a code relating to the specific advertisement page received from the user device;

Instructions for transmitting the retrieved at least one record value to the user device;

Instructions from the user device to receive a request of an application for the particular advertiser based on the transmitted at least one record value; And

In response to a request of an application for the particular advertiser, searching for an application corresponding to the requested application in the database and transmitting data associated with the request to the user device;

Computer program comprising a.