KR101473672B1 - Transmitting and receiving method for SNS-based situation-aware mobile message - Google Patents

Abstract

A SNS-based context aware mobile message transmission and reception method is provided. The SNS-based context-aware mobile message transmission method includes receiving a recipient from a sender, confirming a friend relationship type between the sender and the recipient, receiving a message object from the sender, Determining a message service using the pair of the friend relationship type and the message object type, displaying the input message object and the determined message service on the screen of the sender terminal, And transmitting the received message object to the recipient terminal.

Description

Technical Field [0001] The present invention relates to an SNS-based situation-aware mobile message transmission and reception method,

The present invention relates to an SNS-based context aware mobile message transmission and reception method. More particularly, the present invention relates to a mobile messaging service providing method in which, in a mobile messaging service, a service type provided between a sender and a receiver varies depending on a relationship type between a sender and a receiver and an object type of the service.

Social Network Service (SNS) represents a community service that enables social relations to be established online and to share information among individuals. Such a social network service also provides a mobile message service that enables mobile messages to be transmitted and received between terminals. A mobile message service using a phone book list of a user terminal, such as a cacao talk, a line, etc., may be a representative example. Most of the conventional mobile message services utilize social relationships only to determine whether to block transmission / reception of mobile messages. That is, the sender can transmit a mobile message only to the recipient's terminal, which is a friend relationship, and is not allowed to transmit the mobile message to the recipient's terminal, not the friend relationship.

Korean Published Patent No. 2011-0118025

A problem to be solved by the present invention is to provide a SNS-based context-aware mobile message transmission method in which a message service is determined according to a situation (social relationship type between a sender and a receiver and a message object type).

Another problem to be solved by the present invention is to provide a SNS-based context-aware mobile message reception method in which a message service is determined according to a situation (a social relationship type between a sender and a receiver and a message object type).

The problems to be solved by the present invention are not limited to the above-mentioned problems, and other matters not mentioned can be clearly understood by those skilled in the art from the following description.

According to an aspect of the present invention, there is provided an SNS-based context aware mobile message transmission method for receiving a recipient from a sender, confirming a friend relationship type between the sender and the recipient, Determining a message service type of the received message object by using the pair of the friend relationship type and the message object type, and transmitting the determined message service and the determined message service to the sender And displaying the message object on the screen of the terminal, and transmitting the received message object to the receiver terminal according to the determined message service.

According to another aspect of the present invention, there is provided an SNS-based context-aware mobile message receiving method, comprising: receiving a message object from a sender terminal; confirming a friend relationship type between a sender and a recipient; Deriving a message service using the pair of the friend relationship type and the message object type, and displaying the received message object and the derived message service on the screen of the receiver terminal.

Other specific details of the invention are included in the detailed description and drawings.

According to the above-described SNS-based context aware mobile message transmission and reception method of the present invention, a message service is determined or derived using a pair of a friend relationship type of a sender and a receiver and a message object type of a received message object, Dynamically more flexible mobile messages can be sent and received.

1 is a diagram for explaining a social network service system.
2 is a block diagram illustrating a detailed configuration of the user terminal of FIG.
FIG. 3 is a table for explaining the schema of the friend relationship database of FIG. 1; FIG.
4 is a flowchart illustrating a method of transmitting a context aware mobile message according to an embodiment of the present invention.
5A to 5C are views for explaining screen display of a user terminal according to the context-aware mobile message transmission method of FIG.
FIGS. 6A and 6B are diagrams for explaining an application example of screen display of a user terminal according to the context-aware mobile message transmission method of FIG.
7 is a flowchart illustrating a method for receiving a context-aware mobile message according to an embodiment of the present invention.
8A and 8B are diagrams for explaining screen display of a user terminal according to the method of receiving a mobile communication message of FIG. 7;
9A and 9B are diagrams for explaining an application example of screen display of a user terminal according to a method of receiving a mobile communication message of FIG. 7.

BRIEF DESCRIPTION OF THE DRAWINGS The advantages and features of the present invention and the manner of achieving them will become apparent with reference to the embodiments described in detail below with reference to the accompanying drawings. The present invention may, however, be embodied in many different forms and should not be construed as being limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Is provided to fully convey the scope of the invention to those skilled in the art, and the invention is only defined by the scope of the claims. Like reference numerals refer to like elements throughout the specification.

As used herein, the term 'module' refers to a hardware component such as software, FPGA or ASIC, and the 'module' performs certain roles. However, "module" is not limited to software or hardware. The ' module ' may be configured to reside on an addressable storage medium and may be configured to play back one or more processors. Thus, by way of example, a "module" may include components such as software components, object-oriented software components, class components and task components, and processes, functions, Subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays and variables. The functions provided in the components and 'modules' may be combined into a smaller number of components and 'modules' or further separated into additional components and 'modules'.

Although the first, second, etc. are used to describe various elements, components and / or sections, it is needless to say that these elements, components and / or sections are not limited by these terms. These terms are only used to distinguish one element, element or section from another element, element or section. Therefore, it goes without saying that the first element, the first element or the first section mentioned below may be the second element, the second element or the second section within the technical spirit of the present invention.

The terminology used herein is for the purpose of illustrating embodiments and is not intended to be limiting of the present invention. In the present specification, the singular form includes plural forms unless otherwise specified in the specification. It is noted that the terms "comprises" and / or "comprising" used in the specification are intended to be inclusive in a manner similar to the components, steps, operations, and / Or additions.

Unless defined otherwise, all terms (including technical and scientific terms) used herein may be used in a sense commonly understood by one of ordinary skill in the art to which this invention belongs. Also, commonly used predefined terms are not ideally or excessively interpreted unless explicitly defined otherwise.

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

1 is a diagram for explaining a social network service system.

Referring to FIG. 1, a social network service system includes a first user terminal 100, a second user terminal 200, and a social network service (SNS) server 300.

The first user terminal 100, the second user terminal 200, and the SNS server 300 are connected to each other via a network. For example, the network may include various communication networks such as 3G (3G), 4G (4Generation), WiFi (Wireless Fidelity), Internet and the like. The communication network to which the first user terminal 100 is connected and the communication network to which the second user terminal 200 is connected may be the same or different from each other. For example, the first user terminal 100 and the SNS server 300 may be connected via WiFi, and the second user terminal 200 and the SNS server 300 may be connected through 4G.

The SNS server 300 may provide a Social Network Service (SNS). SNS represents a community service that enables social relations to be established online and information among individuals can be shared. In addition, the SNS server 300 may provide a mobile message service for transmitting / receiving mobile messages between terminals based on the SNS. For example, the mobile message service may be but is not limited to a mobile messaging service that uses a phone book list of a user terminal, such as a kakao talk, line, or the like.

In an embodiment of the present invention, the mobile messaging service suffices if the sender terminal sends a mobile message to the recipient terminal over the network, and the recipient terminal can receive the mobile message from the sender terminal over the network.

The user terminals 100 and 200 may connect to the SNS server 300 to send mobile messages to other user terminals 100 and 200 or to receive mobile messages from other user terminals 100 and 200 have. These mobile messages may be relayed between the user terminals 100 and 200 by the SNS server 300. [

In an embodiment of the present invention, a first user terminal 100 and a second user terminal 200 are terms used to distinguish a user terminal from a second user terminal 200, a first user terminal 100, And may correspond to other user terminals capable of transmitting and receiving mobile messages. The first user terminal 100 may be a sender terminal when transmitting a mobile message to a second user terminal 200 and may be a receiver terminal when receiving a mobile message from a second user terminal 200.

Illustratively, the user terminals 100 and 200 may be, but are not limited to, mobile systems such as smartphones, tablet PCs, and the like.

2 is a block diagram illustrating a detailed configuration of the user terminal of FIG. Since the second user terminal 200 can be configured substantially the same as the first user terminal 100, the first user terminal 100 will be described as an example.

Referring to FIG. 2, the user terminal 100 of FIG. 1 includes a real-time message transmission / reception module 110, a message service selection module 120, a friend relationship database 130, a message object database 140, a message display module 150 ).

The real-time message transmission / reception module 110 can access the SNS server 300 via the network to transmit a mobile message or receive a mobile message. The mobile message is transmitted and received in the form of a message object that is dependent on the mobile application service, rather than simple data such as conventional characters and pictures. That is, not only the message object but also the message service applicable to the message object are transmitted between the user terminals 100 and 200. The real-time message transmission / reception module 110 can send and receive the address of this message object through the network.

The message service selection module 120 can recognize the situation and select the message service. Here, the context includes a friend relation type of a sender and a receiver, and a message object type. More specifically, the situation can be defined as a pair of < friend relationship type, message object type >.

Friend relationship types represent types of social relationships defined by mobile application services, such as family relationships, alumni relationships, work colleague relationships, club member relationships, seller / buyer relationships, and enemy / friend relationships. For example, family and alumni relationships can be defined according to the application service of the phonebook list. As another example, the seller / buyer relationship can be defined as an e-commerce friend relationship according to the application service of the electronic commerce. As another example, an enemy / friendly relationship can be defined as a game friend relationship depending on the application service of a specific mobile game. These types of friendships may be called social relationships, personal relationships, etc., as the case may be. The friend relationship type has various types according to the mobile application service and can be changed dynamically.

The message object type represents the type of object that is dependent on a particular mobile application service. For example, the message object type can be defined in various ways such as a product, a gift, a game item, a game service, a voice call service, a video call service, and a calendar service, in addition to conventional characters, pictures, icons, maps and videos. For example, in the case of a shirt, a message object can be selected as a gift type with a coupon or the like for obtaining the shirt added to the photograph of the shirt.

The friend relationship database 130 may include information regarding the above-described friend relationship types. 3, the schema of the friend relationship database 130 includes data such as an ID, a name, an application service, a friend relationship type, a registration date, etc. of a receiver (specifically, a person to receive a mobile message) . The friend relationship database 130 may include some data of the phonebook list of the user terminal 100. [ When sending a mobile message, the message service selection module 120 searches the friend relationship database 130 for the recipient (the user of the recipient terminal) selected by the sender (the user of the sender terminal) can confirm. When receiving a mobile message, the message service selection module 120 may retrieve the sender of the mobile message from the friend relationship database 130 and determine the friend relationship type from the search result.

The message object database 140 may include information about a message object and a message object type. Although not explicitly shown, the schema of the message object database 140 may include data such as message objects, names of message objects, application services, message object types, and the like. When sending a mobile message, the message service selection module 120 may retrieve the message object selected by the sender in the message object database 140 and determine the message object type from the search result. When receiving a mobile message, the message service selection module 120 searches the message object database 140 for the received message object, and confirms the message object type from the search result.

The friend relationship database 130 and the message object database 140 are storage devices such as ROM (Read Only Memory), MRAM (Magnetic Random Access Memory), PRAM (Phase-change Random Access Memory) But is not limited thereto. The data stored in the friend relationship database 130, the message object database 140 may be input from a user or received via a network.

The message display module 150 is configured to display text, images, etc. on the screen of the user terminal 100. [ When sending and receiving a mobile message, the message display module 150 can display a mobile message on the screen of the user terminal 100. [ For example, the message display module 150 may display a dialog between the sender and the recipient on the screen of the user terminal 100, and may display the message object and the message service in the dialog. For example, the message display module 150 can drive various display devices such as an LCD (Liquid Crystal Display) panel, an LED (Light Emitting Diode) panel, and an OLED (Organic Light Emitting Diode) panel.

If the corresponding message object is stored in the message object database 140, the message display module 150 may display the stored message object. If the corresponding message object is not stored in the message object database 140, the message display module 150 can receive and display the message object stored in the SNS server 300 or the like through the network.

In addition, although not explicitly shown, the user terminal 100 may include other well-known components, such as a controller, a touch panel, a button, a speaker, etc., for controlling the overall operation of the user terminal 100 An input / output device, and the like.

Hereinafter, a method of transmitting and receiving a mobile message using the configuration of the user terminal 100 will be described.

4 is a flowchart illustrating a method of transmitting a context aware mobile message according to an embodiment of the present invention.

Referring to FIG. 4, in the context aware mobile message transmission method, the user terminal 100 receives a recipient from a sender (S410). At this time, the sender can select the recipient from the friend list displayed on the screen of the user terminal 100. [

Then, the user terminal 100 confirms the friend relationship type between the sender and the receiver (S420). At this time, the user terminal 100 searches the friend relationship database 130 for the recipient, and confirms the friend relationship type between the sender and the recipient from the search result.

Then, the user terminal 100 receives the message object from the sender (S430). At this time, the sender can select any message object from the message object list displayed on the screen of the user terminal 100.

Then, the user terminal 100 confirms the message object type of the received message object (S440). At this time, the user terminal 100 searches for a message object received from the message object database 140, and confirms the message object type of the received message object from the search result.

Subsequently, the user terminal 100 determines a message service using a pair of a friend relationship type and a message object type (S450). Since the friend relationship type and the message object type can be defined in various ways, the user terminal 100 differently determines the message service according to a situation, that is, a pair of a friend relationship type and a message object type.

For example, if the friend relationship is different for the first friend relationship type and the second friend relationship type, and the message object is the same for a particular message object type, then the user terminal 100 may send a first message service 2 Message service can be determined. Here, the first message service and the second message service may be different from each other.

In addition, even if the friend relationship is the same as the first friend relationship type, if the message object type is different for the first message object type and the second message object type, the user terminal 100 transmits the first message service The third message service can be determined. Here, the first message service and the third message service may be different from each other.

Then, the user terminal 100 displays the input message object and the determined message service on the screen (S460). Then, the user terminal 100 transmits the received message object to the recipient terminal (user terminal of the recipient) according to the determined message service (S470).

Meanwhile, in some embodiments, the context-aware mobile message transmission method may be modified in the order of receiving a message object, confirming a message object type, receiving a recipient, and confirming a friend relationship type of a sender and an input recipient. Alternatively, the context aware mobile message transmission method may be modified in order to confirm the friend relationship type and the message object type of the sender and the recipient input after receiving the receiver and the message object. That is, the order of execution of the steps constituting the context aware mobile message transmission method is not limited to the order shown in FIG.

5A to 5C are views for explaining screen display of a user terminal according to the context-aware mobile message transmission method of FIG.

Referring to FIG. 5A, a friend list may be displayed on the screen of the user terminal. For example, assume that xxx (f1) and yyy (f2) are displayed in the friend list of user zzz. In the friend list, the name of the receiver (the user of the receiver terminal), a photograph, and the like may be displayed together. The user zzz can select yyy (f2) as a recipient from the friend list and input it to send the mobile message. The users zzz and yyy (f2) assume that the friend relationship type is defined as a family relationship and stored in the friend relationship database 130. [

Referring to FIG. 5B, after the user zzz selects and inputs a recipient, a message object list may be displayed on the screen of the user terminal. Various types of message objects (ob1 to ob4) may be displayed in the message object list, for example, a shirt, a glasses, a camera, a headset, and the like. The user zzz can select and input a specific type of message object, for example, shirt (ob1), from the message object list.

Referring to FIG. 5C, as the user zzz selects the shirt ob1 as the message object, a message service that can be applied to the shirt ob1 may be displayed on the screen of the user terminal. In this case, yyy (f2) is a sister of the user zzz, and since the friend relationship type is a family relationship, the message service can be determined by sending a gift (ms_t1). In accordance with the gift sending message service ms_t1, for example, a gift sending button may be displayed on the screen of the user terminal together with the shirt ob1. Here, the gift sending message service ms_t1 is determined by the pair of the message object type of the shirt ob1 and the friend relationship type of the family relationship. The user zzz may select the send gift button to send the mobile message to the user terminal at yyy (f2).

FIGS. 6A and 6B are diagrams for explaining an application example of screen display of a user terminal according to the context-aware mobile message transmission method of FIG.

Referring to FIG. 6A, the user zzz may select a recipient xxx (f1) from the friend list to send a message. The users zzz and xxx (f1) assume that the friend relationship type is defined as a seller / buyer relationship and is stored in the friend relationship database 130. [

Referring to Fig. 6B, as the user zzz selects the shirt ob1 as the message object, a message service that can be applied to the shirt ob1 may be displayed on the screen of the user terminal. In this case, since the friend relationship type is the e-commerce friend relationship as the buyer of the user zzz, xxx (f1) can be determined by the new product registration notification ms_t2. In accordance with the new product registration notification message service ms_t2, for example, a product registration notification button may be displayed on the screen of the user terminal together with the shirt ob1. In Fig. 6B, a new goods registration notification message service (ms_t2) is determined by the pair of the message object type of the shirt ob1 and the friend relationship type of the e-commerce friend relationship. The user zzz can select the product registration notification button and transmit the mobile message to the user terminal of xxx (f1).

7 is a flowchart illustrating a method for receiving a context-aware mobile message according to an embodiment of the present invention.

Referring to FIG. 7, in the context aware mobile message reception method, the user terminal 100 receives a message object from a sender terminal (a sender's user terminal) (S510).

Then, the user terminal 100 confirms the friend relationship type between the sender and the receiver (S520). At this time, the user terminal 100 searches the friend relationship database 130 for the sender, and confirms the friend relationship type of the sender and the receiver from the search result.

Then, the user terminal 100 confirms the message object type of the received message object (S530). At this time, the user terminal 100 can search the message object received from the message object database 140, and confirm the message object type of the received message object from the search result.

Then, the user terminal 100 derives a message service using a pair of a friend relationship type and a message object type (S540). Since the friend relationship type and the message object type can be defined in various ways, the user terminal 100 differently derives the message service according to a situation, that is, a pair of a friend relationship type and a message object type.

For example, if the friend relationship is different for the first friend relationship type and the second friend relationship type, and the message object is the same for a particular message object type, then the user terminal 100 may send a first message service 2 message service can be derived. Here, the first message service and the second message service may be different from each other.

In addition, even if the friend relationship is the same as the first friend relationship type, if the message object type is different for the first message object type and the second message object type, the user terminal 100 transmits the first message service A third message service can be derived. Here, the first message service and the third message service may be different from each other.

Then, the user terminal 100 displays the received message object and the derived message service on the screen (S550).

On the other hand, in some embodiments, the context aware mobile message reception method may be modified to check the type of the message object of the received message object, and then confirm the type of friend relationship between the sender and the recipient. That is, the order of execution of the steps constituting the context aware mobile message reception method is not limited to the order shown in FIG.

8A and 8B are diagrams for explaining screen display of a user terminal according to the method of receiving a mobile communication message of FIG. 7;

Referring to FIG. 8A, a message reception notice of &quot; zzz has sent a gift &quot; may be displayed in the dialogue window of the user terminal of yyy. The message object ob1 and the message service ms_r1 may be displayed together on the screen of the user terminal of yyy. For example, an auditing button may be displayed on the screen of the user terminal of yyy along with the shirt ob1, depending on the message service ms_r1 derived by the pair of the friend relationship type of the family relationship and the message object type of the shirt have. yyy can select an audit button and send an audit message to the user zzz.

Referring to FIG. 8B, a message reception notification of &quot; the sister yyy has sent an audit message &quot; may be displayed in the dialogue window of the user terminal of the user zzz. Then, on the screen of the user terminal of the user zzz, the message object (ob1) and "Thank you. OK !! "message may be displayed together.

9A and 9B are diagrams for explaining an application example of screen display of a user terminal according to a method of receiving a mobile communication message of FIG. 7.

Referring to FIG. 9A, a message reception notification of &quot; zzz has registered a new product &quot; may be displayed in the dialog window of the user terminal of xxx. The message object ob1 and the message service ms_r2 may be displayed together on the screen of the user terminal of xxx. The purchase request button is displayed on the screen of the user terminal of xxx together with the shirt ob1, for example, in accordance with the message service ms_r2 derived by the pair of the friend relationship type of the e-commerce friend relationship and the message object type of the shirt Can be displayed. xxx can select a purchase application button and send a purchase application message to the user zzz.

Referring to FIG. 9B, a message receiving notification that &quot; xxx has sent a purchase request &quot; may be displayed in the dialogue window of the user terminal of the user zzz. On the screen of the user terminal of the user zzz, message contents of the message object ob1 and the message of "please send it by courier" can be displayed together.

The steps of a method or algorithm described in connection with the embodiments of the present invention may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of computer readable recording medium It is possible. An exemplary recording medium is coupled to a processor, which is capable of reading information from, and writing information to, the recording medium. Alternatively, the recording medium may be integral with the processor. The processor and the storage medium may reside within an application specific integrated circuit (ASIC). The ASIC may reside within the user terminal. Alternatively, the processor and the storage medium may reside as discrete components in a user terminal.

While the present invention has been described in connection with what is presently considered to be practical exemplary embodiments, it is to be understood that the invention is not limited to the disclosed embodiments, but, on the contrary, You will understand. It is therefore to be understood that the above-described embodiments are illustrative in all aspects and not restrictive.

100: first user terminal
110: Real-time message transmission / reception module
120: message service selection module
130: Friend relationship database
140: Message object database
150: message display module
200: second user terminal
300: SNS server

Claims (10)

A mobile message transmission method using a mobile message service provided from an SNS server,
Receiving, by a sender terminal, a receiver from a sender;
Confirming a type of a friend relationship between the sender and the recipient input by the sender terminal;
Receiving, by the sender terminal, a message object from the sender;
Confirming a message object type of the received message object by the sender terminal;
The sender terminal determining a message service using a pair of the friend relationship type and the message object type;
The sender terminal displaying the received message object and the determined message service; And
Wherein the sender terminal transmits the received message object to the recipient terminal according to the determined message service. The method according to claim 1,
Wherein determining the message service comprises: determining a first message service using a pair of a first friend relationship type and a message object type, determining a second friend relationship type different from the first friend relationship type, Determining a second message service using a pair of the first message service and the second message service,
Wherein the first message service and the second message service are different from each other. 3. The method of claim 2,
Wherein determining the message service comprises: determining a first message service using a pair of the first friend relationship type and a first message object type, determining the first friend relationship type, Determining a third message service using a pair of two message object types,
Wherein the first message service and the third message service are different from each other. The method according to claim 1,
Wherein the step of confirming the friend relationship type of the sender and the recipient inputted comprises: searching the friend relationship database of the sender terminal for the received recipient; checking the friend relationship type of the sender and the recipient from the search result; Wherein the SNS-based context-aware mobile message transmission method comprises the steps of: The method according to claim 1,
The checking of the message object type of the received message object may include searching the message object database of the sender terminal for the received message object and checking the message object type of the received message object from the search result Based context aware mobile message transmission method. A mobile message receiving method using a mobile message service provided from an SNS server,
Receiving a message object from a sender terminal;
Confirming the friend relationship type of the sender and the receiver by the receiver terminal;
Confirming a message object type of the received message object;
Deriving a message service using the pair of the friend relationship type and the message object type; And
Wherein the recipient terminal comprises the step of displaying the received message object and the derived message service. The method according to claim 6,
Wherein deriving the message service further comprises: deriving a first message service using a pair of a first friend relationship type and a message object type, deriving a second friend relationship type different from the first friend relationship type, And deriving a second message service using a pair of the first message service and the second message service,
Wherein the first message service and the second message service are different from each other. 8. The method of claim 7,
Wherein deriving the message service further comprises: deriving a first message service using a pair of the first friend relationship type and a first message object type, and deriving a first message service using the first friend relationship type, And deriving a third message service using a pair of two message object types,
Wherein the first message service and the third message service are different from each other. The method according to claim 6,
Wherein the step of verifying the friend relationship type of the sender and the recipient comprises the step of retrieving the sender from the friend relationship database of the recipient terminal and verifying the type of friendship between the sender and the recipient from the search result. SNS based context aware mobile message receiving method. The method according to claim 6,
Wherein the step of verifying the message object type of the received message object comprises the steps of: retrieving the received message object from the message object database of the recipient terminal and verifying the message object type of the received message object from the retrieval result; Based context aware mobile message receiving method.

Images