KR102205720B1 - Method of defining relation of invitation between users for application and server and system thereof - Google Patents

Abstract

A method of defining an invitation relationship between users for an application according to an embodiment of the present invention, the server system aims to define an invitation relationship between users when an invitation for installation and execution of an application is sent to an arbitrary user. do. According to an embodiment of the present invention, by clearly establishing an application invitation relationship, an object for future service compensation can be clearly designated. In addition, as the invitation relationship is clearly established, a more specific and clear reward service can be provided, thereby encouraging and motivating users to use the service.

Description

How to define an invitation relationship between users for an application, and a server and system for it {METHOD OF DEFINING RELATION OF INVITATION BETWEEN USERS FOR APPLICATION AND SERVER AND SYSTEM THEREOF}

The present invention relates to a method for defining an invitation relationship between users for an application, and a server and system therefor, and more particularly, to define an invitation relationship between users for an application that defines an invitation relationship for recommending application use between users. It relates to a method and a server and system therefor.

Due to the spread of smart terminals such as smart phones and tablet PCs, the spread and development of applications installed in such smart terminals is being activated. These applications are being developed and used for various fields such as games, learning, life, beauty, and other entertainment. Among them, one of the most active applications is game applications.

Conventional game programs have been used by users through a PC, and there are many things that are complicated and difficult to operate, but as applications are supplied through mobile, many applications that are easier to operate and simple to operate have been developed and supplied. Accordingly, as users of various classes are interested in game applications, the proportion of demand and supply for game applications has increased considerably.

As competition among these game applications accelerates, each game application maker is using the concept of “application invitation” as a marketing method. Publication No. 10-2013-0136073 (published date: 2013.12.12) discloses the concept that other users can be invited when using a mobile application. Further, in some services, when one user transmits an invitation message for installing or running an application to another user, the corresponding game application provides a service that pays compensation for it.

However, since sending the invitation message alone cannot guarantee that the invitee will necessarily install or run the application, the marketing power is insufficient to induce unsubscribed users to the service by sending the invitation message alone. Furthermore, even if compensation is provided on the premise of installing or running an application after sending an invitation message, it is difficult to provide an accurate service without defining the relationship as to which user invited to which user.

An embodiment of the present invention aims to define an invitation relationship between users when an invitation for installation and execution of an application is sent to an arbitrary user.

As a technical means for achieving the above-described technical problem, in a method of defining an invitation relationship between users for an application executed by a server according to a first aspect of the present invention, at least one other user from the terminal of the first user Receiving an invitation request from an application for; Providing an invitation link of the application including identification information on the first user to at least one other user according to the application's invitation request; Receiving the identification information from the terminal of the second user as a second user of the at least one other user installs or executes the application through the invitation link; And defining and storing an invitation relationship between the first user and the second user through the identification information received from the terminal of the second user.

In addition, the providing of the invitation link of the application to at least one other user may include transmitting an invitation message including the invitation link to the terminal of at least one other user designated by the first user, or including the invitation link It is characterized in that the uploaded post is uploaded to a public online area that can be viewed by any users.

In addition, the invitation message may be any one of SMS (Short Message Service), MMS (Multi-media Message Service), push message, chat message, and email.

In addition, the invitation link allows the second user's terminal to execute a program for installing the application when the application is not installed in the second user's terminal, and the second user's terminal with the application When is installed, the terminal of the second user may be connected to a script for executing the application.

In addition, the program for installing the application is characterized in that the market store page for the application that is commercially used in the operating system of the second user's terminal is executed.

In addition, the identification information received from the terminal of the second user may be stored in the terminal of the second user when the application is installed or executed through the invitation link of the second user.

In addition, the identification information is characterized in that the communication network unique information of the first user.

In addition, the method of defining an invitation relationship between users for the application includes: When the first user designates the second user and requests the invitation, first identification information for the first user and first identification information for the second user 2 further comprising the step of storing the identification information in the server, wherein the identification information included in the invitation link is location information in which the first and second identification information is stored in the server.

In addition, the method of defining an invitation relationship between users for the application further comprises the step of providing a reward to the account of the first user who invited the second user after the invitation relationship is defined. do.

In addition, the step of providing a reward to the account of the first user may include providing a reward to the account of the first user by referring to the defined invitation relationship when the second user has made payment for the application. It features.

On the other hand, the server according to the second aspect of the present invention, the invitation request receiving unit for receiving an invitation request of the application for at least one other user from the terminal of the first user; An invitation link providing unit for providing an invitation link of the application including identification information on the first user to at least one other user according to the invitation request of the application; An identification information receiving unit configured to receive the identification information from the terminal of the second user when a second user of the at least one other user installs or executes the application through the invitation link; And an invitation relationship defining unit for defining and storing an invitation relationship between the first user and the second user through the identification information received from the terminal of the second user.

In addition, the invitation link providing unit may transmit an invitation message including the invitation link to the terminal of at least one other user designated by the first user, or allow arbitrary users to view a post including the invitation link. It is characterized by uploading to a public online area.

In addition, the invitation message may be any one of SMS (Short Message Service), MMS (Multi-media Message Service), push message, chat message, and email.

In addition, the invitation link allows the second user's terminal to execute a program for installing the application when the application is not installed in the second user's terminal, and the second user's terminal with the application When is installed, the terminal of the second user may be connected to a script for executing the application.

In addition, the program for installing the application is characterized in that the market store page for the application that is commercially used in the operating system of the second user's terminal is executed.

In addition, the identification information received from the terminal of the second user may be stored in the terminal of the second user when the application is installed or executed through the invitation link of the second user.

In addition, the identification information is characterized in that the account information of the communication service subscribed to by the first user.

In addition, the server further includes a storage unit for storing first identification information for the first user and second identification information for the second user when the first user designates the second user and requests an invitation. The invitation link providing unit is characterized in that, as identification information included in the invitation link, location information in which the first and second identification information are stored in the server is designated.

Meanwhile, a system according to a third aspect of the present invention includes: an invitation request receiver configured to receive an invitation request for an application for at least one other user from a first user; An invitation link providing unit for providing an invitation link of the application including first identification information for the first user to at least one other user according to an invitation request from the application; An identification information receiver configured to receive the first identification information from a terminal of the second user when a second user among the at least one other user installs or executes the application through the invitation link; And an invitation relationship defining unit for defining and storing an invitation relationship between the first user and the second user through the first identification information received from the terminal of the second user; And when the second user accesses the server through the invitation link, storing the first identification information included in the invitation link, and storing the first identification information according to the installation or execution of the application by the second user. It characterized in that it comprises a; terminal of the second user transmitted to the server.

Meanwhile, in a method for defining an invitation relationship between users for an application executed by a server according to a fourth aspect of the present invention, when an application invitation request for at least one other user is received from a first user's terminal, Receiving identification information of the first user and identification information of the at least one other user from the terminal of the first user; And defining and storing an invitation relationship between the first user and the at least one other user through the identification information on the first user and the at least one other user.

In addition, the method of defining an invitation relationship between users for the application includes, after defining and storing the invitation relationship, invitation information related to the stored invitation relationship. Transmitting an invitation request for the application to the terminal of the at least one other user; And as the application is executed in the terminal of the at least one other user who has been invited, receiving the invitation information from the terminal of the at least one other user and identifying an inviter for the at least one other user. Include more.

In addition, the invitation information is storage location information indicating a location in which the first user and the at least one other user identification information or the invitation relationship is stored in the server.

According to any one of the above-described problem solving means of the present invention, in an embodiment of the present invention, by clearly establishing an application invitation relationship between users, an object for future service compensation can be clearly designated.

In addition, as the invitation relationship is clearly established, a more specific and clear reward service can be provided, thereby encouraging and motivating users to use the service.

The effects obtainable in the present invention are not limited to the above-mentioned effects, and other effects not mentioned can be clearly understood by those of ordinary skill in the art from the following description. will be.

1 is a block diagram of a system for defining an application invitation relationship between users according to a first embodiment of the present invention.
2 is a structural diagram of a server in the system according to the first embodiment of the present invention.
3 is a structural diagram of a second terminal in the system according to the first embodiment of the present invention.
4 is a flow chart showing a method of defining an application invitation relationship between users according to the first embodiment of the present invention.
5 is a flow chart illustrating an example of a method of defining an application invitation relationship between users according to the first embodiment of the present invention.
6 is a flow chart showing a method of defining an application invitation relationship between users according to a second embodiment of the present invention.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those of ordinary skill in the art can easily implement the present invention. However, the present invention may be implemented in various different forms and is not limited to the embodiments described herein. In the drawings, parts irrelevant to the description are omitted in order to clearly describe the present invention, and similar reference numerals are assigned to similar parts throughout the specification.

Throughout the specification, when a part is said to be "connected" to another part, this includes not only "directly connected" but also "electrically connected" with another element interposed therebetween. . In addition, when a part "includes" a certain component, it means that other components may be further included rather than excluding other components unless specifically stated to the contrary.

In addition, a singular expression used in the present specification may include a plurality of expressions, unless the context clearly indicates otherwise. In addition, terms including ordinal numbers such as first and second used in this specification can be used to describe various elements, but the above terms are used only for the purpose of distinguishing one element from other elements. Elements are not limited by the above terms.

Hereinafter, the present invention will be described in detail with reference to the accompanying drawings.

First, referring to FIG. 1, a system for sharing logins between applications according to an embodiment of the present invention includes terminals 100 and 200 and a main server 300 that are communicated with each other through a network (N).

Network (N) is a local area network (LAN), a wide area network (WAN), a value added network (VAN), a personal area network (PAN), a mobile communication network ( mobile radio communication network), Wibro (Wireless Broadband Internet), Mobile WiMAX, HSDPA (High Speed Downlink Packet Access), or satellite communication network.

The terminals 100 and 200 are composed of a first terminal 100 and a second terminal 200, and are connected to a remote server through a network (N), or a computer, portable terminal, or television that can be connected to other terminals and servers. It can be implemented as Here, the computer includes, for example, a notebook equipped with a web browser, a desktop, a laptop, and the like, and the portable terminal is, for example, a wireless communication device that ensures portability and mobility. , PCS (Personal Communication System), PDC (Personal Digital Cellular), PHS (Personal Handyphone System), PDA (Personal Digital Assistant), GSM (Global System for Mobile communications), IMT (International Mobile Telecommunication)-3000, CDMA (Code Division Multiple Access)-3000, W-Code Division Multiple Access (W-CDMA), Wireless Broadband Internet (Wibro), Smart Phone, Mobile Worldwide Interoperability for Microwave Access (WiMAX), etc. (Handheld)-based wireless communication device may be included. In addition, the television may include Internet Protocol Television (IPTV), Internet Television (Internet Television), terrestrial TV, cable TV, and the like.

At least one application may be installed in each of the terminals 100 and 200. An application refers to a set of computer programs designed to perform a specific task, and is also called an "application program." For example, it can be classified into games, education, life, beauty, and messenger applications according to the type of service provided by the application. The application may be displayed and installed in the form of an icon in a communication network terminal such as a smartphone, tablet PC, notebook, desktop, PDA, and the like.

Although only the first terminal 100 and the second terminal 200 are illustrated in FIG. 1, this is only an example, and other number of terminals may be connected to the main server 300.

The servers 300, 400, 500 are computers that communicate with a remote user terminal or other server through a network. Servers (300, 400, 500) are composed of a main server (300) and first and second application servers (400, 500). In one embodiment of the present invention, the main server 300 is interlocked with the application servers 400 and 500 to serve as a hub. The hub role may be a function of a user's access to a game server, management of a user who has accessed the game, inviting other users, and providing rewards for invitees. For example, the first application server 400 may provide a game service to the first terminal 100 connected to its own server 400. At this time, when the game user wants to invite another user to the first application, the main server 300 manages the user list of the first application, so the main server 300 is different from the first application server 400. You can perform an invitation function for users. That is, each game server only needs to provide content that provides a game service, and the main server 300 may perform a function related to user management accessing each application. The main server 300 and the application servers 400 and 500 may be services operated by the same or different operating entities.

Hereinafter, internal configurations of the second terminal 200 and the main server 300 according to the first embodiment of the present invention will be described in detail through FIGS. 2 and 3. Hereinafter, a user using the first terminal 100 is defined as a first user, a user using the second terminal 200 is defined as a second user, and it is assumed that the first user and the second user are different users. .

Referring to FIG. 2, the main server 300 according to the first embodiment of the present invention includes an invitation request receiving unit 310, an invitation link providing unit 320, a server-side storage unit 320, and an identification information receiving unit 340. And an invitation relationship definition unit 350.

When the first user requests an invitation to a specific application from at least one other user through the first terminal 100, the invitation request receiving unit 310 receives the invitation request. In this case, the application being executed by the first user communicates with the application server 400 or 500 to provide various services related to the application, but may be preprogrammed to communicate with the main server 300 in relation to the invitation request function. Here, the specific application includes a function of allowing a person in the first user's friend list to request an invitation to recommend the use of the specific application. The first user's friend list includes other users registered in the first terminal 100 and friends of the social network service to which the first user is registered. For example, the invitation interface of the specific application may include a banner “invitation”, and may be configured to transmit an invitation request message to the main server 300 when the banner “invite” is clicked. In addition, the "invitation" in the first embodiment of the present invention may include an invitation to recommend installation of an application, an invitation to use an application item, or an invitation to an application event.

The invitation link providing unit 320 provides an invitation link to at least one other user according to an invitation request. The method of providing the invitation link may be a method of including the invitation link in the invitation message and sending it. For example, when a first user invites a second user, or when the first user invites other users in a chat window provided by a social network service, SMS (Short Message Service) to the invited user, Any one of a multi-media message service (MMS), a push message, a chat message, and an email may be transmitted, and an invitation link may be included in the message. Another method of providing an invitation link may be a method of uploading a post including an invitation link to a public online area that can be accessed by any other user. For example, the first user may upload an invitation link and a post in which a comment is written to a blog, a homepage, or a social network site such as Facebook or LinkedIn.

The invitation link may include a URL address and may be implemented in the form of a hyperlink. The invitation link may be configured to access the main server 300 through a web browser or an application program operated by various operating systems (eg, mobile operating systems such as Android and iOS) according to how the URL scheme is implemented. .

In addition, the invitation link includes identification information. The identification information serves as an intermediary for defining an invitation relationship, and may include user identification information or invitation relationship information. Specifically, the identification information may include at least one of first identification information for a first user and storage location information indicating a location of a column in which the first identification information is stored in the server-side storage unit 320. For example, when a first user invites a second user and a second user installs a corresponding application, it is possible to check whether the first user is an inviter only when a special identifier is received when the application is installed. In this case, when the identification information is transmitted to the terminal of the second user through a link and finally received by the main server 300, the main server 300 may define that the first user is an inviter.

Here, the first identification information may be account information of a communication service subscribed by the user. The user's communication service account information is, for example, the account information or unique information of the user subscribed to the invited application, the account information or unique information of the user subscribed to another website, and the identification number of the mobile communication service that the user subscribed to. It may be (for example, a phone number). The account information or unique information may be, for example, an email address, a user ID, a password, and user account information. For example, when the first user invites the second user, the invitation link includes at least one of unique information about the first user's invitation application and storage location information indicating the location of the column storing the unique information in the server. May be included.

The identification information included in the invitation link may be added as a parameter to the URL address of the invitation link and displayed. On the other hand, since identification information is directly expressed in the address of the invitation link, there is a risk of personal information exposure, so storage location information indicating the location where the first identification information of the first user is stored in the server may be included in the invitation link and displayed. have.

The server-side storage unit 320 may store user identification information such as the first identification information mentioned above, and storage location information indicating a location where the identification information is stored. In addition, the server-side storage unit 320 may store various setting values for providing a service of an application in which the invitation function has been performed.

The identification information receiving unit 340 receives identification information from a terminal of a user who has installed or executed an application through an invitation link. The identification information is identification information included in the invitation link, and is stored in the terminal of the invited user when the invited user clicks the invite link to run or install an application. For example, when the first user invites the second user, the identification information included in the invitation link is transmitted from the main server 300 to the second terminal 200, and the second user installs and executes the application. In this case, it is transmitted from the second terminal 200 to the main server 300.

The invitation relationship definition unit 350 defines and stores an invitation relationship between users through the received identification information. For example, it is assumed that the first and third users invite a second user. At this time, if the second user installs the application through the first user's invitation link, the main server 300 will receive the first user's identification information from the second user's terminal, from which the first user 2 You can confirm that you are the user's invitee. Alternatively, when the first user uploads the invitation link to the blog, and when the nth user installs the application through the blog, the identification information of the first user is received from the terminal of the nth user, from which the nth user The user's inviter may determine that he is the first user.

Subsequently, referring to FIG. 3, the second terminal 200 according to the first embodiment of the present invention includes an invitation link receiving unit 210, a display unit 220, an input unit 230, a terminal-side storage unit 240, and an invitation. A link response processing unit 250 and an identification information transmitting unit 260 are included. In the first embodiment of the present invention, the configuration of the second terminal 200 may be included not only in the first terminal 100 but also in all terminals.

The invitation link receiver 210 receives the invitation link provided from the main server 300. Specifically, the invitation link receiving unit 210 may receive an invitation message including an invitation link or extract an invitation link from a post including the invitation link.

The display unit 220 displays an invitation message or post including an invitation link provided from the main server 300. In one area of the invitation message or post, an invitation link may be displayed to be arranged in the form of a hyperlink.

When the invitation link is displayed through the display unit 220, the input unit 230 may input the invitation link acceptance through a method such as touching the invitation link area or moving a cursor to the invitation link area and clicking. The input unit 230 may be configured in the form of, for example, a keyboard, a mouse, and a touch screen.

The terminal-side storage unit 240 stores identification information included in the invitation link according to the click of the invitation link. The identification information may be stored in a cookie of a web browser requesting a stored document of an address included in the invitation link to the server 200 or in a local storage area of other application programs.

The invitation link response processing unit 250 performs response processing for installation or execution of an application according to the user's click on the invitation link. The script connected with the invitation link causes the second terminal 200 to store the terminal identification information sent from the main server 300, and when the application is installed in the terminal 100, the application installed in the terminal 100 is called. And, when the application is not installed in the terminal 100, it is configured to call a program for installing the application. When the application is not installed, the script connected to the invitation link may be configured to deliver identification information on the application to the program to provide a page for installing the application. Here, the program may be a web browser or a market store application. The invitation link response processing unit 250 executes the application when the application is installed according to the script, and executes the application installation program when the application is not installed.

When the application is installed or executed, the identification information transmitting unit 260 transmits the identification information stored in the terminal-side storage unit 240 to the main server 300. The transmitted identification information is used in the main server 300 to define an invitation relationship between users. For example, when the first identification information of the first user is transmitted from the second terminal 200 of the second user, the invitation relationship definition unit 350 of the main server 300 is an invitation between the first and second users. You will be able to define relationships.

Hereinafter, a method of defining an invitation relationship between users for an application according to the first embodiment of the present invention will be described in detail with reference to FIG. 4.

First, the main server 300 receives an application invitation request for at least one other user from a first user (S100). For example, when the first user is receiving the service through the application server, if the first user clicks the'invitation' banner for the second user, the invitation request for the second user is sent to the main server 300 Can be sent to. In this case, the first user may request an invitation to send an invitation message to specific users, or may request an invitation by uploading a post including an invitation link to an arbitrary website for unspecified users.

The main server 300 provides an invitation link to at least one other user in response to an invitation request from the first user (S101). The main server 300 provides an invitation link in a manner that includes an invitation link in an invitation message or a post uploaded by the first user. As described above, the invitation link includes identification information to define the invitation relationship. The identification information may be transmitted from the first terminal 100 of the first user or may be a value extracted from the main server 300 by tracking the service use details of the first user.

For example, when the first user invites the second user, the first identification information of the first user may be included in the invitation link. The identification information may be included in the invitation link in a manner that is displayed by being added to the URL address of the invitation link. The identification information may be composed of a user ID of the first user, an email address, and unique information for using an application service. In this case, if the identification information is displayed in the URL address, there is a risk of personal information leakage, so the first identification information is stored in the server-side storage unit 320, and storage location information indicating the location where the first identification information is stored is invited. It may also be included in the link.

Subsequently, the main server 300 determines whether at least one other user has clicked the invitation link (S102). When the invitation link is clicked, a signal for requesting a web document connected to the invitation link is transmitted to the main server 300, and thus whether the invitation link is clicked may be determined by the main server 300.

If the user does not click the invitation link, there is no procedure for defining the invitation relationship, but when the user clicks the invitation link, the terminal receives and executes the script associated with the invitation link from the server. Thus, the terminal stores the identification information included in the invitation link in the terminal (S103).

Subsequently, the terminal determines whether the application is installed by the script command, and executes a program for installing or executing the application according to the installation status (S104). Specifically, when the application is not installed, the terminal executes a program in the terminal (eg, a market store application) so that a page for installing the application appears, and when installed, the terminal immediately executes the application.

Subsequently, the terminal 200 determines whether the application has been executed (S105).

When the application is not executed, there is no procedure for defining the invitation relationship, but when the application is executed, the main server 300 receives the identification information stored in the invitation link from the terminal (S106). For example, when the second user installs and executes the application in response to the first user's invitation, the identification information stored in the second terminal 200 of the second user will be transmitted to the main server 300.

The main server 300 defines and stores an invitation relationship between users through the received identification information (S107). For example, assuming that the first user invites the second user, the identification information is the first identification information of the first user, or the storage location information indicating the location where the first identification information is stored in the main server 300 Can be The invitation relationship defining unit 350 of the main server 300 may define and store who is an invitee among the first user and the second user through the identification information.

Through this process, the first embodiment of the present invention can define an invitation relationship between users. Hereinafter, for easier understanding, a case in which the first embodiment of the present invention is applied in a specific example through FIG. 5 will be described in detail.

First, it is assumed that the first user inputs an invitation request for an application through the first terminal 100 (S200). At this time, the main function of the application is provided through the application server (400 or 500), the invitation function is provided through the main server (300). In addition, it is assumed that the invitation request is a request for inviting a second user who has not installed the application.

In accordance with the invitation request, the first terminal 100 transmits an invitation request signal for the second user to the main server 300 (S201).

The main server 300 extracts first identification information for a first user and generates an invitation message including an invitation link including the first identification information (S202). The first identification information may be transmitted and extracted from the first terminal 100. The invitation message may be a chat message provided through a social network service application.

The main server 300 transmits an invitation message including an invitation link to the second terminal 200 (S203).

Next, it is assumed that the second user views the invitation message and clicks the invitation link (S204).

According to the click of the invitation link, the second terminal 200 requests a web document connected to the invitation link to the main server 300 (S205).

The main server 300 provides a script connected to the invitation link according to the web document request (S206).

The second terminal 200 executes the provided script (S207), and stores the first identification information according to the command of the script (S208). Subsequently, the second terminal 200 examines whether the application is installed in the second terminal 200 according to the command of the script (S209). Subsequently, if the application is not installed, the second terminal 200 installs the application (S210) and then executes the application, and if the application is already installed, immediately executes the application (S211). When installing an application, an application market store page suitable for the system operating system of the second terminal 200 may be provided to the second terminal 200 through a script. A program providing an application market store may receive identification information for a corresponding application and provide a download page of a corresponding application required by a user among various applications in the market store.

As the application is executed, the first identification information stored in the local area of the second terminal 200 is transmitted to the main server 300 (S212).

The main server 300 defines and stores an invitation relationship through the first identification information received from the second terminal 200 (S213). When the main server 300 receives the first identification information from the second terminal, it can know that it is transmitted from the account of the second user, so that the first user is an inviter of the second user and can store it. . In the first embodiment of the present invention, the defined invitation relationship can be referred to when rewarding a user in the future. For example, in the first embodiment of the present invention, when user A installs or runs an application or pays for one of the services provided by the application, a reward can be provided to the inviter of user A. In the first embodiment, a user A's invitee can be identified by referring to a defined invitation relationship, and a reward can be provided to the inviter.

On the other hand, the method of defining the invitation relationship according to the second embodiment of the present invention can define the invitation relationship in a simpler method than the first embodiment. Hereinafter, a second embodiment of the present invention will be described with reference to FIG. 6.

First, when a first user requests an invitation to an application from at least one other user, the main server 300 (refer to FIG. 2) receives such an invitation request (S300). The invitation request may include first identification information for a first user and identification information for at least one other user. The identification information for the first user and at least one other user serves as an intermediary for defining the invitation relationship, as mentioned in the first embodiment. Here, the identification information may be account information of a communication service subscribed to by the user, and this will be replaced with the content described in the first embodiment. In addition, the first user may invite only one user, or may invite a plurality of users by grouping them into a group.

For example, when the first user attempts to invite a second user who is not subscribed to the first application, the account information of the first user and the mobile communication identification number of the second user are included in the invitation request. It may be transmitted to the main server 300.

Subsequently, the main server 300 defines and stores an invitation relationship using identification information of the first user and at least one other user included in the invitation request (S301). For example, since the main server 300 receives an invitation request from the terminal of the first user, the first user may define and store the relationship that the first user is an inviter to at least one other user. Alternatively, it may be stored only to the extent that the first user and at least one other user are in an invitation relationship without the definition of the inviter.

Subsequently, the main server 300 transmits an invitation message including invitation information related to the invitation relationship to at least one other user (S302). Here, the invitation information is the identification information of the first user and at least one other user transmitted from the user's terminal, or a storage location indicating a column in which the identification information of the first user and at least one other user is stored in the main server 300 It could be information. As mentioned in the first embodiment, the invitation message may be transmitted in the form of an SMS, MMS, or messenger message.

When at least one user receives the invitation message and installs or executes the application according to the invitation message, the main server 300 receives the invitation information again from at least one user's terminal (S303).

Subsequently, the main server 300 may determine that the inviter of the user who installed or executed the application is the first user through the invitation information (S304). When the invitation information is storage location information indicating a column in which the identification information of the first user and at least one other user is stored in the main server 300, the main server 300 searches the storage location indicated in the invitation information and The invitation relationship can be identified.

In the second embodiment of the present invention, step S301 may simply define the invitee and the invitee for the application, but step S304 may define the invitee of the invited person who installed or executed the application according to the invitation. . That is, if a reward is given to the invitee on condition of installation or execution of an application by the invitee in the future, step S304 may be used as a step for determining an object for such reward. For example, if the first user invites the second, third, and fourth users and only the second user runs the application, the inviter of the second user who ran the application becomes the first user, and the first The user can only receive rewards for the second user.

Meanwhile, in the second embodiment, the invitation relationship is not defined in step S301, and identification information of the first user and at least one other user is included in the invitation message as invitation information, and the invitation information is received in step S304. It is also possible to define an invitation relationship between a user and at least one other user.

The method for defining an invitation relationship between users for an application according to the embodiments of the present invention described above, the server system can clearly designate an object for service compensation later by explicitly establishing the application invitation relationship. In addition, as the invitation relationship is clearly established, a more specific and clear reward service can be provided, thereby encouraging and motivating users to use the service.

The method for defining an invitation relationship between users for an application according to the embodiment described with reference to FIGS. 4 to 5 may also be implemented in the form of a recording medium including instructions executable by a computer such as a program module executed by a computer. have. Computer-readable media can be any available media that can be accessed by a computer, and includes both volatile and nonvolatile media, removable and non-removable media. Further, the computer-readable medium may include both computer storage media and communication media. Computer storage media includes both 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. Communication media typically includes computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave, or other transmission mechanism, and includes any information delivery medium.

The above description of the present invention is for illustrative purposes only, and those of ordinary skill in the art to which the present invention pertains will be able to understand that it can be easily modified into other specific forms without changing the technical spirit or essential features of the present invention. will be. Therefore, it should be understood that the embodiments described above are illustrative in all respects and not limiting. For example, each component described as a single type may be implemented in a distributed manner, and similarly, components described as being distributed may also be implemented in a combined form.

The scope of the present invention is indicated by the claims to be described later rather than the detailed description, and all changes or modified forms derived from the meaning and scope of the claims and their equivalent concepts should be interpreted as being included in the scope of the present invention do.

100: first terminal 300: server
310: invitation request receiving unit 320: invitation link providing unit
330: server-side storage unit 340: identification information receiving unit
350: invitation relationship definition unit 300: second terminal
310: invitation link receiving unit 320: display unit
330: input unit 340: terminal-side storage unit
350: invitation link response processing unit 360: identification information transmission unit

Claims (22)

In a method of defining an invitation relationship between users for an application executed by a server,
Receiving an application invitation request for at least one other user from the terminal of the first user;
Providing an invitation link of the application including identification information on the first user to at least one other user according to the application's invitation request;
Receiving the identification information stored in the terminal of the second user from the terminal of the second user as a second user of the at least one other user installs or executes the application through the invitation link; And
Defining and storing an invitation relationship between the first user and the second user through the identification information received from the terminal of the second user;
Including,
The invitation link above is,
If the identification information is included as a parameter, and the application is not installed in the terminal of the second user, the terminal of the second user executes a program for installing the application, and the terminal of the second user When the application is installed, it is connected with a script that causes the terminal of the second user to execute the application,
The above script,
When executed by the terminal of the second user, the parameter included in the invitation link is stored in the terminal of the second user,
The above application,
When executed by the terminal of the second user, the identification information stored in the terminal of the second user is read and transmitted to the server. A method of defining an invitation relationship between users for an application. The method of claim 1,
Providing the invitation link of the application to at least one other user,
Transmitting an invitation message including the invitation link to the terminal of at least one other user designated by the first user, or
The method of defining an invitation relationship between users for an application by uploading the post including the invitation link to a publicly available online area that can be viewed by arbitrary users. The method of claim 2,
The invitation message,
SMS (Short Message Service), MMS (Multi-media Message Service), push message, chat message, any one of email, a method of defining an invitation relationship between users for an application. delete The method of claim 1,
The program for installing the above application,
A method of defining an invitation relationship between users for an application, executing a market store page for the application that is used in the operating system of the second user's terminal.
delete The method of claim 1,
The identification information,
A method of defining an invitation relationship between users for an application, which is account information of the communication service subscribed to by the first user. The method of claim 1,
A method of defining an invitation relationship between users for the application,
When the first user designates the second user and requests for an invitation, storing first identification information for the first user and second identification information for the second user in the server,
Identification information included in the invitation link,
A method of defining an invitation relationship between users for an application, wherein the first and second identification information is location information stored in the server. The method of claim 1,
A method of defining an invitation relationship between users for the application,
After the invitation relationship is defined, the method further comprising providing a reward to the account of the first user who has invited the second user. The method of claim 9,
Providing a reward to the account of the first user,
When the second user makes payment for the application, a method of defining an invitation relationship between users for an application, providing a reward to the account of the first user with reference to the defined invitation relationship. An invitation request receiving unit for receiving an invitation request for an application for at least one other user from a terminal of a first user;
An invitation link providing unit for providing an invitation link of the application including identification information on the first user to at least one other user according to the invitation request of the application;
An identification information receiving unit configured to receive the identification information stored in the terminal of the second user from the terminal of the second user when a second user of the at least one other user installs or executes the application through the invitation link; And
Including; an invitation relationship defining unit for defining and storing an invitation relationship between the first user and the second user through the identification information received from the terminal of the second user,
The invitation link above is,
If the identification information is included as a parameter, and the application is not installed in the terminal of the second user, the terminal of the second user executes a program for installing the application, and When the application is installed, it is connected with a script that causes the terminal of the second user to execute the application,
The above script,
When executed by the terminal of the second user, the parameter included in the invitation link is stored in the terminal of the second user,
The above application,
When executed by the terminal of the second user, the identification information stored in the terminal of the second user is read and transmitted to a server, defining an invitation relationship between users for an application. The method of claim 11,
The invitation link providing unit,
Transmitting an invitation message including the invitation link to the terminal of at least one other user designated by the first user, or
Server for defining an invitation relationship between users for an application to upload a post including the invitation link to a publicly available online area where arbitrary users can view. The method of claim 12,
The invitation message,
A server that defines an invitation relationship between users for an application, either SMS (Short Message Service), MMS (Multi-media Message Service), push message, chat message, or email. delete The method of claim 11,
The program for installing the above application,
A server defining an invitation relationship between users for an application, which executes a market store page for the application that is used in the operating system of the second user's terminal.
delete The method of claim 11,
The identification information is account information of a communication service subscribed to by the first user, a server defining an invitation relationship between users for an application. The method of claim 17,
The server,
When the first user designates the second user and requests the invitation, further comprising a storage unit for storing first identification information for the first user and second identification information for the second user,
The invitation link providing unit,
As identification information included in the invitation link, a server defining an invitation relationship between users for an application for designating location information in which the first and second identification information is stored in the server. An invitation request receiver configured to receive an invitation request for an application for at least one other user from a first user; An invitation link providing unit for providing an invitation link of the application including first identification information for the first user to at least one other user according to an invitation request from the application; Identification information receiving unit for receiving the first identification information stored in the terminal of the second user from the terminal of the second user when a second user of the at least one other user installs or executes the application through the invitation link ; And an invitation relationship defining unit for defining and storing an invitation relationship between the first user and the second user through the first identification information received from the terminal of the second user; And
When the second user accesses the server through the invitation link, the first identification information included in the invitation link is stored, and the first identification information is transmitted according to the installation or execution of the application by the second user. Including; the terminal of the second user transmitted to the server,
The invitation link above is,
If the first identification information is included as a parameter, and the application is not installed in the terminal of the second user, the terminal of the second user executes a program for installing the application, and the second user When the application is installed in the terminal, it is connected with a script that causes the terminal of the second user to execute the application,
The above script,
When executed by the terminal of the second user, the parameter included in the invitation link is stored in the terminal of the second user,
The above application,
When executed by the terminal of the second user, the first identification information included in the parameter stored in the terminal of the second user is read and transmitted to the server. In a method of defining an invitation relationship between users for an application executed by a server,
Receiving the first user's identification information and the at least one other user's identification information from the first user's terminal upon receiving an application invitation request for at least one other user from the terminal of the first user step;
Defining and storing an invitation relationship between the first user and the at least one other user through identification information on the first user and the at least one other user;
After defining and storing the invitation relationship, transmitting an invitation link to the application including invitation information related to the stored invitation relationship to the terminal of the at least one other user; And
As the application is executed in the terminal of at least one other user receiving the invitation link, the invitation information stored in the terminal of the at least one other user is received from the terminal of the at least one other user, and the at least one Including; Including,
The above invitation information,
Storage location information indicating a location where identification information or the invitation relationship for the first user and the at least one other user is stored in the server,
The invitation link above is,
If the invitation information is included as a parameter, and the application is not installed in the at least one other user's terminal, the at least one other user's terminal executes a program for installing the application, and the at least one When the application is installed on another user's terminal of, the at least one other user's terminal is connected to a script to execute the application,
The above script,
When executed by the terminal of the at least one other user, the parameter included in the invitation link is stored in the terminal of the at least one other user,
The above application,
A method of defining an invitation relationship between users for an application, in which the invitation information stored in the terminal of the at least one other user is read and transmitted to the server. delete delete

Images