KR20230091317A - Method of sending hub message with system and app messaging services - Google Patents

Abstract

A reliable proxy message transmission method of the present invention comprises: a contact database transmission step (S10) in which a client app (210) installed in at least one user terminal (200) transmits a contact database (201) of the user terminal (200) to a main management unit (110) of a manager system (100); a step (S20) in which the management module (110) in the manager system (100) adds owner information of the user terminal (200) as a separate field to individual contact information in the contact database (201) transmitted from the user terminal (200) to create a manager contact database (111) of the manager system; and a proxy command transmission step (S30) in which the manager system selects contacts (300a, 300b, 300c) in the manager contact database (111) and transmits a command to the user terminals (200) corresponding to owners corresponding to the contacts so that the selected contacts (300a, 300b, 300c) are operated as contacts in the user terminal (200).

Description

Method of sending hub message using system and app messaging services { Method of sending hub message with system and app messaging services }

The present invention relates to a reliable proxy message transmission method for an originating source.

Recently, it is possible to send a large amount of messages about advertisements or elections to an unspecified number of people. However, most of the recipients of such messages are often displeased. This is because of anxiety such as that a message came from someone unknown to him, and that his personal information was hacked.

In this case, no matter how many messages are sent, it is very difficult for advertisers to fully enjoy the advertising effect. This is because when an advertising message is transmitted, the reliability of the sender is not high. Accordingly, a technology for sending a message by minimizing people's displeasure or rejection is required.

The present invention has been made to solve the above conventional problems, and an object of the present invention is to provide a reliable proxy message transmission method for an originating source.

In the hub message transmission method according to an embodiment of the present invention, the contact database 201 of the user terminal 200 is stored in the manager system 100 by the client app 210 installed in at least one user terminal 200. Contact database transmission step to transmit to the main management unit 110 (S10); By the management module 110 in the manager system 100, the owner information of the corresponding user terminal 200 is added as a separate field to the individual contact information of the contact database 201 transmitted from the user terminal 200, so that the manager Creating (111) a contact database for system administrators (S20); The manager system 100 selects the contacts 300a, 300b, and 300c in the manager contact database 111 and operates as a contact in the user terminal 200 as the user terminal 200 corresponding to the owner corresponding to the contact. It includes; proxy command sending step (S30) of sending the command.

In one embodiment, after the proxy command sending step (S30), when the command sent in the proxy command sending step (S30) is completed, the command execution reward step of paying a reward to the owner of the user terminal 200 ( S40) characterized in that it further comprises.

In one embodiment, in the step (S20) of creating (111) the manager contact database, when the manager contact database 111 is created, the contact information in the contact database 201 of the user terminal 200 is the manager If it already exists in the user contact database 111, the owner information is characterized in that it is maintained and stored as existing owner information.

In one embodiment, in the proxy command sending step (S30), the command operated by the contacts (300a, 300b, 300c) in the user terminal 200 is through the basic message sending app 202 in the user terminal 200 It is characterized by message transmission.

In one embodiment, in the proxy command sending step (S30), the command operated by the contacts (300a, 300b, 300c) in the user terminal 200 is through the social app 220 in the user terminal 200. to be

In one embodiment, in the step of generating (111) the manager contact database (S20), when the manager contact database 111 is created, the contact information in the contact database 201 of the user terminal 200 is the manager If it already exists in the user contact database 111 or the social contact database 121 of the social app installed in the manager system 100, the owner information is maintained and stored as the existing owner information.

In one embodiment, the operating command of the proxy command sending step (S30) is characterized by sending a friend recommendation message within the social app 220 of the user terminal 200 or using a separate message function .

In one embodiment, the friend recommendation message is characterized in that it includes a characteristic information input function capable of inputting characteristic information of a friend recommendation target.

In one embodiment, after the proxy command sending step (S30), when the friend recommendation message sent in the proxy command sending step (S30) is sent, the command execution reward for providing a reward to the owner of the user terminal 200 It is characterized in that it further comprises step (S40).

In one embodiment, in the command execution reward step (S40), after the manager system 100 and the proxy command sending step (S30), when the contacts (300a, 300b, 300c) and friend addition are performed, additional compensation is performed characterized by

In one embodiment, in the step (S20) of generating (111) the manager contact database, the manager contact database 111 further includes a friend status field, and in the friend status field, a status of not being friends with the manager, It is characterized in that it is stored as one of a state of being friends with the manager, a state of being friends with the manager and then canceling, and a state of being friends again after termination.

In one embodiment, in the command execution reward step (S40), when the friend recommendation message sent in the proxy command sending step (S30) is sent, the command execution reward step of paying a reward to the owner of the user terminal 200 (S40) is further included, and additional compensation is performed when the value of the friend status field is changed from a state in which the friend status field was terminated after being friends with the manager, to a state in which the user became friends again after termination.

In one embodiment, in the proxy command sending step (S30), the command operated by the contacts (300a, 300b, 300c) in the user terminal 200, the basic message sending app 202 or social media in the user terminal 200 Characterized in that the message is transmitted through the app 220, and the proxy command sending step (S30) selects the message sending target (300a, 300b, 300c) within the manager contact database 111 of the manager system 100 Selecting a message sending destination step (S31); a message content input step of inputting message content to be sent (S33); Sending a message delivery command instructing the owner terminal 200 of the message transmission targets 300a, 300b, 300c selected in the manager contact database 111 to deliver the message contents to the transmission targets 300a, 300b, 300c ( S37); characterized in that it further comprises.

In one embodiment, the message transmission target selection step (S31); And after the message content input step (S33), a message transmission permission request step (S35) of requesting permission for sending a message transmission target and sending message, and proceeding to the message delivery command sending step (S37) if approved. It is characterized in that it further includes;

In one embodiment, after the step of sending the message delivery command (S37), the manager system 100 further includes a message delivery database that separately stores the message sent, the message send destination, and the time the message was sent. do.

In one embodiment, it is characterized in that it further comprises; sent message inquiry step (S50) for searching the sent message and the sending target by using the message sending database.

In one embodiment, in the step (S20) of creating (111) the manager contact database, the owner information of the corresponding user terminal 200 is added to the individual contact information of the contact database 201 transmitted from the user terminal 200. When added as a separate field, it is characterized in that a plurality of owner information is stored for each individual contact.

In one embodiment, in the contact database transmission step (S10), the number of contacts between the user terminal 200 and each contact for the plurality of contact databases 201 of the user terminal 200 is transmitted to the manager app 110. and in the step (S20) of generating (111) a contact database for the administrator, the owner information of the corresponding user terminal 200 and the number of contacts with the owner for the individual contact information are separate from the individual contact information of the contact database 201. It is added to the field of, and in the step of sending proxy commands (S30), when a command operated by an individual contact is sent, the command is sent to the user terminal 200 of the owner with a higher number of contacts.

Therefore, according to the present invention,

The manager transmits a message transmission command to the user terminal and the message is transmitted in the user's name, so the manager sends the message based on the trust of the user.

In addition, by instructing a number of unknown people to send a message from the user's terminal to the user's name by the administrator system, the administrator has the advantage of adding friends and sending messages based on the user's trust.

In addition, the manager pays a reward to the user for reliable message transmission through proxy, thereby having the advantage of being able to further induce participation of users.

In addition, the administrator can further increase the effect of message delivery by delivering the message through a user with higher reliability than when multiple agents are available.

1 is a system configuration diagram showing the configuration of a system for implementing a reliable proxy message transmission method according to an embodiment of the present invention.
2 is a flowchart illustrating a sequence of a reliable proxy message transmission method according to an embodiment of the present invention.
FIG. 3 is an image diagram illustrating a subscription page of an app installed on a user terminal in the embodiment of FIG. 2 .
FIG. 4 is an image diagram illustrating how a user database is transmitted to a manager system in the embodiment of FIG. 2 .
5 is a system configuration diagram showing the configuration of a system for implementing a reliable proxy message transmission method according to another embodiment of the present invention.
FIG. 6 is an image diagram illustrating a situation in which a friend recommendation message is sent and characteristic information of a friend recommendation target is received in the embodiment of FIG. 5 .
7 is a flowchart in which a compensating step for command execution is added according to another embodiment of the present invention.
FIG. 8 is an image diagram illustrating a state in which friend recommendation details are inquired in the embodiment of FIG. 7 .
9 is a flowchart illustrating a process of sending a message delivery command by a manager system according to another embodiment of the present invention.
FIG. 10 is an image diagram illustrating a request for permission for message transmission in the embodiment of FIG. 9 .
11 is a flowchart illustrating a process in which compensation is made when message transmission is completed according to another embodiment of the present invention.
12 is a flowchart illustrating a process of inquiry of a sent message when message sending is completed according to another embodiment of the present invention.
FIG. 13 is an image diagram illustrating a state in which inquiry of a sending message is performed in the embodiment of FIG. 12 .
14 is a conceptual diagram illustrating a contact database for an administrator for evaluating a user's reliability according to another embodiment of the present invention.

Hereinafter, with reference to the accompanying drawings, a preferred embodiment will be described with reference to the accompanying drawings. In this process, the thickness of lines or the size of components shown in the drawings may be exaggerated for clarity and convenience of description. In addition, terms to be described later are terms defined in consideration of functions in the present invention, which may vary according to the intention or custom of a user or operator. Therefore, definitions of these terms will have to be made based on the content throughout this specification.

In addition, the following examples do not limit the scope of the present invention, but are presented as examples only, and there may be various embodiments implemented through the technical idea.

Basic configuration of the system

Referring to FIG. 1, a system for implementing a reliable proxy message transmission method according to an embodiment of the present invention includes a manager system 100, a user terminal 200, and destinations 300a, 300b, and 300c, , The manager system 100 includes a management module 110 and a separate manager contact database 111 . When the manager system 100 is configured as a terminal, it may further include a general database in a separate manager system.

The user terminal 200 includes a contact database 201 and a basic message app 202 installed in the app. The default message app 202 may include a general SMS sending service app, and may include various installed apps capable of sending text messages to the terminal. In addition, the contact database 201 may be a general contact database stored in the user terminal 200, which does not necessarily have to be stored in the app, and may be stored in an external server in conjunction with a cloud service or other services. For convenience of description, it is described as being stored in the user terminal 200, but is not necessarily limited to this case.

The sending objects 300a, 300b, and 300c refer to the objects of contacts recorded in the contact database 201 existing in the user terminal 200.

How to send a proxy message

Referring to FIG. 2 , in a reliable proxy message transmission method according to an embodiment of the present invention, a contact database 201 of a user terminal 200 is performed by a client app 210 installed in at least one user terminal 200. ) to the main management unit 110 of the manager system 100 (S10), the contact database transmitted from the user terminal 200 by the main management unit 110 in the manager system 100 ( 201) adding the owner information of the corresponding user terminal 200 as a separate field to the individual contact information to create a contact database for the manager of the manager system (111) (S20) and the manager in the manager system 100 A proxy command for selecting contacts 300a, 300b, and 300c in the contact database 111 for the contact, and sending a command operated as a contact in the user terminal 200 to the user terminal 200 corresponding to the owner corresponding to the contact. It includes a sending step (S30).

(a) contact database transmission step

Referring to FIG. 3 , the user sign-up process will be described. The user is authenticated on the user terminal 200 . The name authenticated by personal information authentication and the user's mobile phone number are automatically entered. User ID and password for the user. In addition, a page for inputting characteristic information such as age group, gender, region of residence, occupation, support party, and recommender information is provided.

When the subscription procedure is completed, a contact database transmission step (S10) is performed. This is performed when the client app 210 distributed and installed in the user terminal 200 receives an access right from the user and transmits the contact database in the user terminal 200 to the manager system 100 . The plurality of contact databases of the user terminal 200 are contact databases stored in a separate app installed on the user terminal 200 . A plurality of user contact databases may be stored in a separate server, and in this case, the database is acquired by accessing with contact database access rights.

When a user joins the manager system 100 , a contact database 111 for the manager is created in the management system 100 . The manager contact database 111 may be managed by a separate server. In this case, the manager system 100 accesses the manager contact database 111 by accessing the management server. In the present invention, the manager contact database 111 is not limited to being physically stored in the main management unit 110 or the management system 100 .

(a) and (b) of FIG. 4 are diagrams showing how the contact database 201 of the user terminal 200 is transferred to the management system 100 by an app installed by the user.

Referring to FIG. 4 , the contact database 201 of the user terminal 200 is transmitted to the main management unit 110 of the manager system 100 by the client app 210 installed by the user (S10).

Also, referring back to (b) of FIG. 4 , the client app 210 of the user terminal 200 can manage whether or not to send a message for each internal contact. An activation button (A) is provided on the contact inquiry screen (b) of the client app 210 installed in the user terminal 200 to check activation information. The user can control activation by selecting the activation button (A).

The authority to send a message to the user's name can be controlled by the activation button (A). Authorization of message transmission can be changed according to the user's intention. By selecting the activation button (A), whether to grant message transmission authority is changed. If the user disables this, the administrator is not granted permission to send messages.

(b) Creation of contact database for administrators

By adding the owner information of the user terminal 200 as a separate field to the individual contact information of the contact database 201 of the user terminal 200 by the client app 210 installed by the user, the manager system 100 A contact database 111 for administrators is created (S20).

Owner information of the user terminal 200 may be expressed in various meanings such as recommender information or introducer information. As long as it is possible to distinguish the subject providing the contact database in the user terminal 200, it can be expressed in various meanings.

When the manager contact database 111 is created, if the contact information in the contact database 201 of the user terminal 200 already exists in the manager contact database 111, the owner information includes the existing owner information. can keep it. As will be mentioned later, a plurality of owners may be registered in the manager contact database 111 . This is because there may be several users who provide specific contact information. In order to increase reliability when sending, a separate process can be added to select a better user.

(c) sending proxy orders;

In the proxy command sending step (S30), the manager system 100 selects the contacts 300a, 300b, and 300c in the manager contact database 111 and sends the user terminal 200 to the user terminal 200 corresponding to the owner corresponding to the contact. At 200, it sends an operating command to the contact.

In this way, the manager system 100 can send a desired command from the user terminal 200 corresponding to the owner to a desired target. Most of the commands are to send a message to the selected contacts 300a, 300b, and 300c from the user terminal 200 corresponding to the owner.

A method of transmitting such a message may be message transmission to selected contacts 300a, 300b, and 300c through the default message sending app 202 in the user terminal 200. In this case, the client app 210 may obtain permission to access the basic message sending app 202 and send a message through it.

In addition, as a method of transmitting such a message, the message may be transmitted to the contacts 300a, 300b, and 300c through the separately installed social app 220 in the user terminal 200. This will be explained later with reference to FIG. 5 .

Example using an external social app

5 is a system configuration diagram showing the configuration of a system for implementing a reliable proxy message transmission method according to another embodiment of the present invention.

Referring to FIG. 5 , in the proxy message transmission method according to another embodiment of the present invention, the user terminal 200 further includes a separately installed social app 220 . Within the social app 220, a separate user social app contact database 221 used in the social app 220 is further included.

The social app contact database 221 for the user may be stored within the app or may be stored on a separate server.

Representative social apps 220 may be KakaoTalk, Facebook, or Instagram messenger. Since the social app 220 can manage a separate address book, the in-device contact database 201 and a separate user social app contact database 221 can be applied. In this case, the user social app contact database 221 may be transmitted to the main management unit 110 of the manager system 100 .

In addition, the manager system 100 further includes a separate social app interlocking unit 120 and a separate contact database 121 used in the social app interlocking unit 120 . The social app linking unit 120 may be viewed as a configuration in which an API or the like capable of linking with a commonly used social app is implemented. In this case, a separate social app contact database 121 can be implemented within one account, and since it is possible to set and manage friend relationships, followers, and following relationships with these accounts, the main management unit 110 In addition to the contact database 111 for their manager, a separate social app contact database 121 for managers can be used together.

FIG. 6 is an image diagram illustrating a situation in which a friend recommendation message is sent and characteristic information of a friend recommendation target is received in the embodiment of FIG. 5 .

Recent social apps include a function to establish a friend relationship between users. When one party requests the other party to establish a friendship and accepts it, a friendship relationship is normally established, and friendship can be established in a more free way. In the present embodiment, the user terminal 200 is able to establish a friend relationship with the manager account set in the manager system 100 and the account corresponding to the contacts 300a, 300b, and 300c. It is the content that conveys the message.

6(a) is an image showing a result of sending a friend recommendation message to the sending target 300 . The manager's terminal may command the friend recommendation message to be sent to the sending target 300 in the user's name upon request (S30). The recommended friend, that is, the sending target (300a, 300b, 300c) receives the message with the name of the user registered in the user terminal 200 among the friends of the sending target (300a, 300b, 300c) as the sender.

In this case, in the step (S20) of generating (111) the manager contact database, the manager contact database 111 further includes a friend status field, and in this friend status field, the manager and not friends, the manager and friend It can be saved in one of the following states: being a friend, being friends with an administrator and then canceling, or being friends again after being terminated.

Friendships are established by mutual agreement, but withdrawal is possible only with one party's intention, so a new friend recommendation can be made to an administrator's account who was a friend in the past but has lost friendship. To manage this status, a friend status field is further included and managed.

Referring to (b) of FIG. 6, when adding a friend is selected by the sending target (300a, 300b, 300c), the sending target (300a, 300b, 300c) to the friend who is the sending target (300a, 300b, 300c) A form for inputting characteristic information of may be provided. This is to identify the characteristic information of each sending target while requesting a friend from the sending targets 300a, 300b, and 300c. The characteristic information input form may be performed by being connected to a separate app. In the characteristic information input form, the manager to be added as a friend is displayed. It also shows who the user recommended the manager to be.

According to this embodiment, the manager transmits a message transmission command to the user terminal 200 and the message is sent to the user's name, so that the manager can use the trust of the user. In more detail, the manager system 100 allows the manager to send a friend addition message to an unknown person in the user's name, so that the manager can add a friend based on the user's trust.

reward for following orders

7 is a flowchart in which a compensating step for command execution is added according to another embodiment of the present invention.

Referring to FIG. 7 , when a message is sent through the user's terminal by the manager system 100, the user is compensated through the user terminal 200 (S40).

This reward may be a reward for simple message delivery or a reward for establishing a friend relationship due to message delivery for a friend relationship request. In addition, separately from this, if the collection of characteristic information for a new contact is completed, compensation for this may be performed.

Compensation may be made on the client app installed by the user. Compensation may be divided into a case of recommending a friend and a case of becoming friends with a manager, respectively.

FIG. 8 is an image diagram illustrating a state in which friend recommendation details are inquired in the embodiment of FIG. 7 .

Referring to FIG. 8 , in the app installed on the user terminal 200, the number of friend recommendation messages sent to the user's name and the manager system 100 and the sending target 300a, 300b, 300c become friends by the friend recommendation A review of the recorded history is provided. Details can be viewed on a date and for a certain period of time. The number of sending friend recommendation messages and details of becoming friends are stored in the message sending database managed by the management system 100 .

Since the details of the number of friend recommendations and the number of established friends are stored and viewed for each period in the manager system 100, the user can check them and estimate the reward he or she will receive.

Specific Steps of the Message Passing Command

9 is a flowchart illustrating a process of sending a message delivery command by a manager system according to another embodiment of the present invention.

Referring to FIG. 9 , in a message transmission method with enhanced reliability according to another embodiment of the present invention, a message transmission target selection step of selecting a message transmission target within the manager contact database 111 of the manager system 100 ( S31), message content input step of inputting the message content to be sent (S33), message delivery command sending step of instructing the owner terminal of the message delivery target 300 selected in the contact database to deliver the message content to the send target 300 (S37) is included.

Although it has been described above that the user is provided with an activation button (A) on the app, the manager system 100 selects only the sending destinations 300a, 300b, and 300c for which message authorization is activated by the user.

The manager inputs a message to be delivered through the manager system 100 (S33).

Next, by the manager system 100, the owner terminal 200 of the selected message transmission target 300a, 300b, 300c transmits the contents of the message to the transmission target 300a, 300b, 300c to the user terminal 200. A command is sent (S37). When the delivery instruction command sent by the manager system 100 reaches an app installed by the user, the app installed by the user instructs the message transmission app having a friend relationship function to send a message. At this time, the separately installed app is given permission to access the message sending app.

Send message forwarding command by requesting permission to send message

FIG. 10 is an image diagram illustrating a request for permission for message transmission in the embodiment of FIG. 9 .

A function for the user to report to the manager system 100 is provided. To this end, after the message transmission target selection step and the message content input step, request permission for the message transmission target (300a, 300b, 300c) and transmission message, and if approved, to proceed to the message delivery command transmission step A message transmission permission request step (S35) is further included.

Referring to FIG. 10(a), it is provided to create a title, report content, and attachment items in reporting of an app provided to the user. When writing complete is selected, the written content is transmitted to the manager system 100 .

Referring to FIG. 10(b), report details or message transmission permission request details (not shown) transmitted from the user's terminal to the manager system 100 are browsed. Details are provided to be viewed by period, and detailed reports or requests can be viewed by selecting the corresponding report details.

Reward for sending messages

11 is a flowchart illustrating a process in which compensation is made when message transmission is completed according to another embodiment. Referring to FIG. 11 , the method for transmitting a reliable proxy message according to another embodiment of the present invention further includes compensating for message transmission (S40). As in the case of compensation for friend recommendation and establishment of friends, compensation is made through the user terminal 200 when message transmission is completed through the user terminal 200 by the manager system 100 .

Inquiry of sent message

12 is a flowchart illustrating a process of inquiry of a sent message when message sending is completed according to another embodiment of the present invention. FIG. 13 is an image diagram illustrating how inquiry of a sending message is performed in the embodiment of FIG. 12 .

Referring to FIG. 12, in another embodiment, a sent message inquiry step (S50) is further included. This is data for compensation, and allows the user to view the message delivery details. The manager system 100 further includes a message delivery database that separately stores the sent message, the message delivery target 300, and the time the message was sent.

In FIG. 13(a), it is provided to the user to search for messages sent from the app installed in the user terminal 200 according to a period. When the user selects the searched message details (B), as shown in FIG. 13(b), the contents of the sent message are created in a pop-up window (C) and viewed.

Trusted user's choice

14 is a conceptual diagram illustrating a contact database for an administrator for evaluating a user's reliability according to another embodiment of the present invention.

In this embodiment, in the process of sending a message to a specific contact, a plurality of user terminal 200 candidates are selected, and a user short hair 200 or owner with higher reliability is selected to be delivered in a more reliable method. is the purpose

To this end, in step S20 of creating a contact database for the manager (111), the owner information of the corresponding user terminal 200 is set as a separate field in the individual contact information of the contact database 201 received from the user terminal 200. When adding, it is characterized in that a plurality of owner information is stored per one individual contact.

Accordingly, a plurality of owners may exist in one contact information instead of having one owner information.

14, in addition, in the contact database transmission step (S10), the number of contacts between the user terminal 200 and each contact for the plurality of contact databases 201 of the user terminal 200 is the manager app 110. ) is sent to At this time, the number of contacts of the contact can determine that there is a frequent relationship between the owner and the contact object by various variables such as the number of phone calls, the number of messages sent in social apps, as well as the number of views and likes in social apps.

In step S20 of creating a contact database for the manager (111), individual contact information of the contact database 201 includes information about the owner of the corresponding user terminal 200 and the number of times of contact with the owner of the individual contact information in a separate field. is added as Therefore, based on this contact frequency information, it is possible to select a more reliable message delivery agent.

In the proxy command sending step (S30), when a command operated to an individual contact is sent, the command is sent to the user terminal 200 of the owner with a higher number of contacts.

One embodiment of the present invention described above is only exemplary, and those skilled in the art will appreciate that various modifications and equivalent other embodiments are possible therefrom. . Therefore, it will be well understood that the present invention is not limited to the forms mentioned in the detailed description above. Therefore, the true technical protection scope of the present invention should be determined by the technical spirit of the appended claims. It is also to be understood that the present invention includes all modifications, equivalents and alternatives within the spirit and scope of the present invention as defined by the appended claims.

100: manager system
200: user terminal
300a, 300b, 300c: dispatch destinations
A: Activate button
B: History of retrieved messages
C: Pop-up window for the contents of the sent message

Claims (18)

Contact database transmission step of transmitting the contact database 201 of the user terminal 200 to the main management unit 110 of the manager system 100 by the client app 210 installed in at least one user terminal 200 ( S10);
By the management module 110 in the manager system 100, the owner information of the corresponding user terminal 200 is set as a separate field in the individual contact information of the contact database 201 received from the user terminal 200. In addition, creating (111) a contact database for the manager of the manager system (S20);
The manager system 100 selects the contacts 300a, 300b, 300c in the manager contact database 111, and sends the user terminal 200 to the user terminal 200 corresponding to the owner corresponding to the contact. A hub message transmission method comprising: sending a proxy command sending step (S30) of an operating command to the contact.
According to claim 1,
After the proxy command sending step (S30),
The hub message transmission method further comprising a command execution compensation step (S40) of paying a reward to the owner of the user terminal (200) when the command sent in the proxy command transmission step (S30) is completed. .
According to claim 1,
In the step (S20) of generating (111) the contact database for the manager,
When the contact database 111 for the manager is created,
When the contact information in the contact database 201 of the user terminal 200 already exists in the manager contact database 111, the owner information is maintained and stored as existing owner information.

According to claim 1,
In the proxy command sending step (S30),
Commands operated by the contact points 300a, 300b, and 300c in the user terminal 200 include:
Hub message transmission method, characterized in that the message transmission through the basic message sending app (202) in the user terminal (200).
According to claim 1,
In the proxy command sending step (S30),
Commands operated by the contact points 300a, 300b, and 300c in the user terminal 200 include:
Hub message transmission method, characterized in that through the social app (220) in the user terminal (200).
According to claim 5,
In the step (S20) of generating (111) the contact database for the manager,
When the contact database 111 for the manager is created,
If the contact information in the contact database 201 of the user terminal 200 already exists in the manager contact database 111 or the social contact database 121 of a social app installed in the manager system 100, the owner information Hub message transmission method characterized in that maintained and stored as existing owner information.
According to claim 5,
The operating command of the proxy command sending step (S30) is,
The hub message transmission method, characterized in that for sending a friend recommendation message in the social app 220 of the user terminal 200 or using a separate message function.
According to claim 7,
The method of transmitting a hub message, characterized in that the friend recommendation message includes a feature information input function capable of inputting feature information of a friend recommendation target.
According to claim 7,
After the proxy command sending step (S30),
and a command execution reward step (S40) of paying a reward to the owner of the user terminal (200) when the friend recommendation message sent in the proxy command sending step (S30) is sent. transmission method.
According to claim 9,
In the command execution compensation step (S40),
The manager system 100 and
The hub message transmission method, characterized in that performing additional compensation when a friend is added to the contact information (300a, 300b, 300c) after the proxy command sending step (S30).
According to claim 7,
In the step (S20) of generating (111) the contact database for the manager,
The manager contact database 111 further includes a friend status field,
The hub message transmission method, characterized in that, in the friend status field, one of a status of not being friends with the manager, a status of being friends with the manager, a status of being friends with the manager and then canceling, and a status of being friends again after termination.

According to claim 11,
In the command execution compensation step (S40),
Further comprising a command execution compensation step (S40) of paying a reward to the owner of the user terminal 200 when the friend recommendation message sent in the proxy command sending step (S30) is sent,
The method of transmitting a hub message, characterized in that performing additional compensation when the value of the friend status field is changed from a state where the friend was a friend to the administrator and then became a friend again after the termination.
According to claim 1,
In the proxy command sending step (S30),
Commands operated by the contacts 300a, 300b, and 300c in the user terminal 200 include:
Characterized in that the message is transmitted through the basic message sending app 202 or social app 220 in the user terminal 200,

In the proxy command sending step (S30),
a message transmission target selection step (S31) of selecting message transmission targets (300a, 300b, 300c) within the manager contact database 111 of the manager system 100;
a message content input step of inputting message content to be sent (S33);
Delivery of a message instructing the owner terminal 200 of the message transmission targets 300a, 300b, 300c selected in the manager contact database 111 to deliver the message contents to the transmission targets 300a, 300b, 300c The hub message transmission method further comprising; sending a command (S37).
According to claim 13,
Selecting the message transmission target step (S31); And after the message content input step (S33),
Further comprising a message transmission permission request step (S35) of requesting permission for the message transmission target and transmission message, and proceeding to the message delivery command transmission step (S37) if approved. How to send hub messages.
According to claim 8,
After the message delivery command sending step (S37),
The hub message transmission method according to claim 1 , wherein the manager system (100) further comprises a message delivery database separately storing the sent message, the target of the message, and the time at which the message was sent.
According to claim 15,
Using the message transmission database,
A method for transmitting a hub message, further comprising a step (S50) of inquiring a sent message and a sent message to which the sent message is sent.
According to claim 1,
In the step (S20) of generating (111) the contact database for the manager,
When the owner information of the corresponding user terminal 200 is added as a separate field to the individual contact information of the contact database 201 received from the user terminal 200,
The method of transmitting a hub message, characterized in that a plurality of owner information is stored for each individual contact.
18. The method of claim 17,
In the contact database transmission step (S10),
Transmitting the number of times of contact between the user terminal 200 and each contact for the plurality of contact databases 201 of the user terminal 200 to the manager app 110,
In the step (S20) of generating (111) the contact database for the manager,
Owner information of the corresponding user terminal 200 and the contact frequency with the owner for the individual contact information are added as separate fields to the individual contact information of the contact database 201,
In the proxy command sending step (S30),
and sending a command to the user terminal 200 of the owner with a higher number of contacts when a command operated to the individual contact is sent.

Images