KR20200068113A - A method for displaying whether a message to be read and a server performing the same - Google Patents

Abstract

Disclosed are a method for displaying whether a message has been read or not in an opened social network service system and a server for performing the same. The method which is performed by a server which provides the opened social network service, wherein a message received or transmitted through a first user account is disclosed to a plurality of users, comprises: a step of receiving a text message, which includes a first text which specifies at least one second user account, and a second text, which is a message to be transmitted to the second user, from a first user terminal related to the first user account; a step of generating a unique value for the text message, and mapping and storing the text message and the unique value; a step wherein the terminal of the second user accesses the server, and detects whether the text message is read or not; a step wherein the terminal of the second user accesses the server, and if it is detected that the text message is read, deletes the unique value which is stored; and a step of responding to the deletion of the unique value, and notifying the first user terminal that the second user has read the text message.

Description

A method for indicating whether a message is checked in an open social network service system and a server performing the same {A METHOD FOR DISPLAYING WHETHER A MESSAGE TO BE READ AND A SERVER PERFORMING THE SAME}

The present invention relates to a method for displaying whether a message is confirmed in an open social network service system and a server performing the same. More specifically, in the present invention, in an open social network service disclosed to an unspecified number of people, when a message is written to a specific other user, a unique value corresponding to the message is generated and stored, and when the other user confirms the message It relates to a server and a method for monitoring whether a message is confirmed and displaying it by deleting the unique value.

Due to the increase in the prevalence of miniaturization and personalized computer devices, and the broadband and high-speed of mobile data networks, social networks between multiple users are being formed through the Internet. In accordance with this trend, services are provided that enable individuals to engage with others on their Internet, that is, services that provide communication and share various information.Social Networking Services (SNS) ).

These social network services can be broadly divided into closed and open. The former is designed to enable communication only between users who have already formed social relationships. It limits the object of communication to a specific group, and the messages exchanged within the group are not disclosed to users other than the group. Have On the other hand, the latter does not specify the object of communication, and the messages exchanged with other users in the service have the characteristic of being disclosed to a large number of unspecified users, unless there are special requests or restrictions of the users.

In the case of an open social network service, a user who subscribes to the service can read or post a message to another user's account without any restrictions. Because of this openness, open social networks have the advantage of exchanging opinions with a wide variety of people.

However, the currently provided open social network service does not provide a means for confirming whether the other party has read the message delivered to another person, and thus has a problem in that it is impossible to confirm the reaction of the other party to the message.

The present invention is to solve the above problems of the prior art, in an open social network service that is open to a large number of unspecified, when a message is written to a specific other user, a unique value corresponding to the message is generated and stored. It is an object of the present invention to provide a method and server for monitoring and displaying whether a message is confirmed by deleting a unique value when another user confirms the message.

The method for notifying whether a message is performed by a server providing an open social network service provided by an embodiment of the present invention includes: specifying a second user account from a first user terminal associated with the first user account; Receiving a text message comprising one text and a second text that is a message to be sent to the second user; Generating an eigenvalue for the text message, and mapping and storing the eigenvalue with the text message; Detecting whether the second user terminal accesses the server and checks the text message; If it is detected that the second user terminal accesses the server and checks the text message, deleting the stored unique value; And in response to the deletion of the eigenvalue, notifying the first user terminal that the second user has confirmed the text message.

The method may further include notifying the second user terminal corresponding to the second user account that the text message has been transmitted from the first user.

Meanwhile, in the step of informing the first user terminal that the second user has confirmed the text message, the message confirmation status flag indicating whether the second user has confirmed the text message is set to a first state corresponding to unconfirmed. Setting and adding to the text message; And displaying the message confirmation status flag and the text message in a list of posts of the first user account.

In addition, the step of informing the first user terminal that the second user has confirmed the text message includes: when the unique value is deleted, changing the message confirmation state to a second state corresponding to the confirmation; And displaying the changed message confirmation status flag and the text message in the post list of the first user account.

The message confirmation status flag and the text message are disclosed to other users accessing the posting list of the first user account.

In addition, the step of informing the first user terminal that the second user has confirmed the text message may further include displaying the message confirmation status flag and the text message in the post list of the second user account. Can be.

The method may further include displaying the changed message confirmation status flag and the text message in the post list of the second user account.

The changed message confirmation status flag and the text message are disclosed to other users accessing the list of posts of the second user account.

A server providing an open social network service provided by an embodiment of the present invention includes: a first text and a second text specifying at least one second user account from a first user terminal associated with the first user account A message eigenvalue generation unit that generates a eigenvalue for the text message when a text message including the second text that is a message to be sent to the user is received; A message eigenvalue storage unit that maps and stores the text message and the eigenvalue; When the terminal of the second user detects that the text message has been accessed by accessing the server, and when the terminal of the second user detects that the text message has been accessed by accessing the server, a message for deleting the stored unique value Eigenvalue management unit; And a message confirmation status display unit in response to the deletion of the eigenvalue, informing the first user terminal that the second user has confirmed the text message.

The message confirmation status display unit sets the message confirmation status flag indicating whether the second user confirms the text message to a first status corresponding to an unconfirmed status, and adds the message confirmation status flag and the text to the text message. It may be configured to display a message in the list of posts of the first user account.

When the unique value is deleted, the message confirmation status display unit changes the message confirmation status to a second status corresponding to the confirmation, and the changed message confirmation status flag and the text message are added to the list of posts of the first user account. It can be configured to display.

The message confirmation status display unit may be configured to display the message confirmation status flag and the text message in the post list of the second user account.

The message confirmation status flag and the text message are disclosed to other users accessing the list of posts of the first user account or the list of posts of the second user account.

According to a server and method for providing an open social network service according to the present invention, in an open social network service disclosed to an unspecified number of people, when a message is written to a specific other user, a unique value corresponding to the corresponding message is generated to generate When the user checks the message after saving it, the unique value is deleted to monitor whether the message is checked or not, and by displaying it, it is possible to check whether the message has been read, so there is an effect that smooth communication is possible. In addition, by allowing users other than the sender and the recipient of the message to check whether they have read the exchanged message between them, there is an effect of inducing other users' interest in the content of the conversation between the two users.

1 is a conceptual diagram showing the configuration of an open social network service system according to an embodiment of the present invention.
2 is a block diagram showing the configuration of an open social network service server according to an embodiment of the present invention.
3 is a chart showing a processing sequence of a social network service according to an embodiment of the present invention.
4 is a chart showing a processing sequence of a social network service according to another embodiment of the present invention.
5 is a chart illustrating a processing sequence of a social network service according to another embodiment of the present invention.

The present invention can be variously changed and can have various forms, and specific embodiments will be illustrated in the drawings and described in detail in the text.

However, this is not intended to limit the present invention to a specific disclosure form, and it should be understood as including all modifications, equivalents, and substitutes included in the spirit and scope of the present invention. Terms such as first and second may be used to describe various components, but the components should not be limited by the terms. The terms are used only for the purpose of distinguishing one component from other components. For example, the first component may be referred to as a second component without departing from the scope of the present invention, and similarly, the second component may also be referred to as a first component.

Terms used in the present application are only used to describe specific embodiments, and are not intended to limit the present invention. Singular expressions include plural expressions unless the context clearly indicates otherwise. In this application, terms such as “include” or “have” are intended to indicate that a feature, number, step, operation, component, part, or combination thereof described in the specification exists, or that one or more other features or It should be understood that the existence or addition possibilities of numbers, steps, actions, components, parts or combinations thereof are not excluded in advance.

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

1 is a conceptual diagram showing the configuration of an open social network service system according to an embodiment of the present invention.

The open social network service system includes a plurality of mobile terminals 10, an open social network service server 20 and a data network. The mobile terminal 10 and the open social network service server 20 exchange signals and data necessary for the open social network service through the data network. The mobile terminal 10 refers to a communication device capable of transmitting and receiving voice calls and text messages through a mobile phone network, and exchanging data through a wireless data communication network.

The social network service provided by the present invention is open. That is, messages transmitted and received through the social network service account are all disclosed to a plurality of unspecified service users who access the account, and service users can freely transmit messages to other service users. The message can be written for a specific user. The message of the open social network service is linked to the account of the message creator and is disclosed to all users, so if you want to deliver a message to another user, you need to specify the target. A common practice in open social network services is to add text specifying the target user before the message. For example, if the user wants to deliver the message message#1 to another user USER_A, the message format may be defined as "@USER_A message#1". Hereinafter, the present invention will be described with an example of the above message format.

2 is a block diagram showing the configuration of an open social network service server according to an embodiment of the present invention.

Referring to FIG. 2, the open social network service server 20 according to an embodiment of the present invention includes a message eigenvalue generation unit 21, a message eigenvalue management unit 22, and a message confirmation status display unit 23. Includes.

The message eigenvalue generating unit 21 is a text including first text specifying at least one second user account and second text that is a message to be sent to the second user, from a first user terminal associated with the first user account Upon receiving the message, a eigenvalue corresponding to the text message is generated. The eigenvalues are mapped 1:1 to the message and the object of the message. When the message is targeted to multiple other users, the eigenvalues may be generated for each other user. For example, if the message is written as "@USER_A @USER_B @USER_C message#1", the message content message#1 targets multiple other users USER_A, USER_B, USER_C, so the unique value is for message message#1. It can be created one by one for each of USER_A, USER_B, and USER_C.

The generated eigenvalues are mapped to corresponding text messages and stored in a repository (not shown). That is, when the user composes a message for a specific person, the server 20 generates a unique value for the specific person and the message content and stores it in a repository. The storage may be a memory embedded in the server 20 or a separate storage medium or a database server.

The message unique value management unit 22 detects whether the terminal of the second user accesses the server and checks the text message, and when the terminal of the second user accesses the server and detects that the corresponding text message is confirmed, the message unique value management unit 22 Delete function. For example, when the first user composes a message for the second user, the server 20 may transmit a notification message informing the second user that the first user composes the message for the second user. In this case, when the second user clicks the link included in the notification message, the corresponding message in the message list of the first user's account can be read, and the message unique value management unit 22 detects this and deletes the message unique value. Can be. In addition, even when the notification message is not transmitted, the message unique value management unit 22 may delete the message unique value when the second user accesses the account of the first user and checks the corresponding message from the message list.

The message confirmation status display unit 23 performs a function of notifying the first user terminal that the second user has confirmed the corresponding text message in response to the deletion of the eigenvalue. There may be several ways to inform the second user whether the message has been read. For example, when the second user accesses the first user's account and checks the corresponding message, the message confirmation status display unit 23 may be configured to transmit a notification message informing the first user terminal. Alternatively, the message confirmation status display unit 23 may be configured to display a message confirmation status flag indicating whether the second user checks the corresponding text message in the message list of the first user account. In this case, when the message targeting the second user is created by the first user, the message confirmation status display unit 23 sets the first status corresponding to unconfirmed, and adds it to the corresponding text message, and the message confirmation status The flag and the corresponding text message are displayed in the post list of the first user account. Thereafter, when the eigenvalue is deleted by the message eigenvalue management unit 22, the message confirmation status display unit changes the message confirmation status to a second status corresponding to'OK', and removes the changed message confirmation status flag and text message. 1 Display in the list of posts of the user account.

The message confirmation status flag and text message generated through the above process are disclosed to other users accessing the posting list of the first user account. That is, other users accessing the first user account can confirm whether the second user has read the message even if the second user is not the target of the message.

According to an embodiment of the present invention, the message confirmation status display unit 23 displays not only the account of the first user who is the creator of the message, but also the second user's account, which is the target of the message. Can be configured. That is, the message confirmation status display unit 23 may be configured to display the message confirmation status flag and the text message in the post list of the second user account. At this time, the change and display of the message confirmation status flag for the second user account are the same as those performed in the first user account. The message confirmation status flag and the text message generated through the above process are disclosed to other users accessing the posting list of the second user account. That is, other users who have accessed the second user account can check whether the second user has read the message even if the user is not the second user to whom the message is delivered.

Meanwhile, each of the message eigenvalue generation unit 21, the message eigenvalue management unit 22, and the message confirmation status display unit 23 may be hardware, software, or a combination of hardware and software configured to perform the above-described processing. . For example, the message eigenvalue generating unit 21 includes first text specifying at least one second user account from the first user terminal associated with the first user account, and second text that is a message to be sent to the second user. When a text message is received, it may be configured by software including instructions necessary to process a function such as generating an eigenvalue corresponding to the text message, and a processor in the server 20 that performs processing according to the instruction. Similarly, the message eigenvalue management unit 22 detects whether the terminal of the second user described above accesses the server and checks the text message, and when the terminal of the second user accesses the server and detects that the corresponding text message is confirmed, the stored unique value It may be configured by software including instructions necessary to perform a function such as deleting a value and a processor in the server 20 performing processing according to the instructions. Message confirmation status display unit 23, in response to the deletion of the eigenvalue, the software including the commands necessary to perform a function to inform the first user terminal that the second user has confirmed the corresponding text message and according to the command It can be configured by a processor in the server 20 to perform the processing. At this time, the software constituting the message eigenvalue generation unit 21, the message eigenvalue management unit 22, and the message confirmation status display unit 23 may be installed in the server 20. In addition, the message eigenvalue generation unit 21, the message eigenvalue management unit 22, and the message confirmation status display unit 23 may be configured by independent software and hardware, respectively, and integrated into one software and hardware. It may be configured to be performed by each function distributed by various software and hardware.

Hereinafter, the operation of the open social network service server according to the preferred embodiment of the present invention will be described in more detail with reference to FIGS. 3 to 5.

3 is a chart showing a processing sequence of a social network service according to an embodiment of the present invention, FIG. 4 is a chart showing a processing sequence of a social network service according to another embodiment of the present invention, and FIG. It is a chart showing a processing sequence of a social network service according to another embodiment of the present invention.

Referring first to FIG. 3, the server 20 receives a message written by the first user USER_A for the second user USER_B (S1). The received message includes a part (@USER_B) that identifies the subject of the message, and a part (message#1) that is the content of the message.

The message unique value generation unit 21 of the server 20 generates a message unique value (unique value 1) mapped 1:1 to the subject of the message and the content of the message and stores it in the storage (S2). The unique value of the message may be stored in the repository in the form of a table T mapped to the message target (USER_B) and message content (message#1).

When the message unique value (unique value 1) is generated, the message confirmation status display unit 23 of the server 20 sets the message confirmation status to the unconfirmed status, and inserts a flag corresponding to the unconfirmed status into the message to the first user It is displayed in the list of posts of the account (ML_A) (S3). In the example of Fig. 3, the flag corresponding to the unconfirmed state is indicated by the character "[not read]". In this state, if the first user who wrote the message (USER_A) or the third user (USER_D) accesses the server 20 and reads the list of posts (ML_A) of the first user account, the message displays "[Do not Read]. Therefore, it is possible to confirm that the corresponding message has not been read by the second user (USER_B) not only the first user who is the author but also the other user who is the third person.

On the other hand, when the message unique value (unique value 1) is generated, the message confirmation status display unit 23 of the server 20 informs the second user terminal USER_B that there is a message written by the first user (S4). The message notification step S4 may be performed simultaneously with the message confirmation status setting step S3 or before the message confirmation status setting step S3. Also, the message notification step S4 may be omitted.

Subsequently, the server 20 detects whether the second user USER_B accesses the server and reads the corresponding message (message#1) (S5). Since the method for detecting whether the second user has read the message has been described above, the description is omitted here. If it is detected that the second user USER_B has read the corresponding message (message#1), the message eigenvalue management unit 22 of the server 20 deletes the eigenvalue (unique value 1) stored in the eigenvalue storage. (S6).

The message confirmation status display unit 23 of the server 20 changes the message confirmation status to read when the eigenvalue is deleted, and inserts a flag corresponding to the read status of the changed message confirmation status to read the account of the first user USER_A This message is displayed on the message list ML_A (S7). In the example of Fig. 3, the flag corresponding to the confirmation state is indicated by the character "[Read]". In this state, when the first user who wrote the message (USER_A) or the third user (USER_D) accesses the server 20 to view the list of posts (ML_A) of the first user account, the message reads "[Read ]". Therefore, it is possible to confirm that the corresponding message has been read by the second user (USER_B) not only the first user who is the author but also the other user who is the third person.

In the embodiment of Fig. 3, the flags corresponding to the message confirmation status are indicated by "[read]" and "[unread]", but various modifications are possible. For example, it is displayed as "[Not read]" in the unconfirmed state, but it is also possible to display nothing when changed to the confirmed state. In the unconfirmed state, the message is displayed in bold font, and in the confirmed state, the message is usually displayed. It can also be displayed in the font.

As described above, according to an embodiment of the present invention, the server 20 not only lists the posts (ML_A) of the account of the first user (USER_A) who is the message creator, but also accounts of the second user (USER_B) that is the subject of the message. It can be configured to display a confirmation status in the list of posts.

FIG. 4 is a chart showing a process of an embodiment in which a message confirmation status is also displayed on a post list of a first user account as a message creator and a post list of a second user account as a target of a message.

Since the message reception (S1) of FIG. 4, the generation and storage of the message unique value (S2), the message notification (S4), the detection of the message confirmation (S5), and the deletion of the message unique value (S6) are the same as the embodiment of FIG. The description is omitted here.

After generating and saving (S2) a unique value (unique value 1) mapped to the message destination (USER_B) and the content of the message (message#1), the server 20 sets the message confirmation status to unconfirmed and unconfirmed The flag "[not read]" corresponding to is inserted into the message to display in the list of posts of the first user account (ML_A) and the list of posts of the second user account (ML_B). That is, the message (message#1) written by the first user (USER_A) to the second user (USER_B) is also displayed in the first user account's post list (ML_A), and the second user account's post list (ML_B) In both cases, a flag that can confirm whether or not the second user has read is inserted in both sides.

In this state, when the first user who wrote the message (USER_A) or the third user (USER_D) accesses the server 20 and reads the list of posts (ML_A) of the first user account, the message is displayed as "[Do not Read]. Therefore, it is possible to confirm that the corresponding message has not been read by the second user (USER_B) not only the first user who is the author but also the other user who is the third person. On the other hand, when a third-party user (USER_D) accesses the server 20 and browses the list of posts (ML_B) of the second user account, he sees the flag marked as "[Not read]" in the message. Therefore, the third user, the other user, can confirm that the corresponding message has not been read by the second user (USER_B) in the post list (ML_B) of the second user account.

Subsequently, when the message unique value is deleted (S6), the server 20 changes the message confirmation status to read, and inserts a flag “[read]” corresponding to the changed message confirmation status into the message to display the first user account. It is displayed in the posting list (ML_A) and the posting list (ML_B) of the second user account. In this state, when the first user who wrote the message (USER_A) or the third user (USER_D) accesses the server 20 and reads the list of posts (ML_A) of the first user account, the message "[Read] ]". Therefore, it is possible to confirm that the corresponding message has been read by the second user (USER_B) not only the first user who is the author but also the other user who is the third person. On the other hand, when a third-party user (USER_D) accesses the server 20 and browses the list of posts (ML_B) of the second user account, he sees the flag marked as "[Read]" in the message. Therefore, the third user, the other user, can confirm that the message has been read by the second user (USER_B) in the post list (ML_B) of the second user account.

5 is a chart showing a processing process when a plurality of target users are included in the message.

In the embodiment of FIG. 5, the generation of the message unique value (S2), the setting of the message confirmation state (S3), the message notification (S4), the detection of the message confirmation (S5, S5'), the deletion of the message unique value (S6, S6') ), and detailed processing of the message confirmation state change (S7, S7') is the same as that described in the embodiment of FIG. However, in the embodiment of FIG. 5, the processing steps (S2 to S7') are performed separately for USER_B and USER_C, which are the targets of the message, respectively, and the result is in the post list (ML_A) of the first user (USER_A) account It is different from the embodiment of FIG. 3 in that it is displayed together.

Referring to FIG. 5, the first user USER_A creates one message content (message#1) against a plurality of users USER_B and USER_C. Upon receiving the message (S1), the server 20 generates a unique value (unique value 1, unique value 2) mapped to the message content (message#1) for each of USER_B and USER_C included in the message (S2). . The unique value of the message may be stored in the storage in the form of a table T mapped to the message content (message#1) for each of the objects (USER_B, USER_C) of the message.

When a message unique value (unique value 1, unique value 2) is generated, the message confirmation status display unit 23 of the server 20 sets the message confirmation status to the unconfirmed status for both USER_B and USER_C, and corresponds to the unconfirmed status The flag "[not read]" is inserted into the message and displayed in the list of posts (ML_A) of the first user account (S3). In the embodiment of FIG. 5, the message displayed on the first user account has the format "@USER_B [not read] @USER_C [not read] message#1". In this state, when the first user (USER_A) or the third user (USER_D) who wrote the message accesses the server 20 to view the list of posts (ML_A) of the first user account, the plurality of second users ( For both USER_B and USER_C), you will see a flag marked "[Not Read]". Accordingly, it is possible to confirm that the corresponding message has not been read by a plurality of second users (USER_B, USER_C), as well as the first user who is the author as well as other users who are third parties.

On the other hand, when the message unique value (unique value 1) is generated, the message confirmation status display unit 23 of the server 20 notifies that there is a message written by the first user in the plurality of second user terminals USER_B and USER_C. (S4). The message notification step S4 may be performed simultaneously with the message confirmation status setting step S3 or before the message confirmation status setting step S3. Also, the message notification step S4 may be omitted.

Subsequently, the server 20 detects whether the corresponding messages (message#1) have been read for each of the plurality of second users (USER_B, USER_C) (S5, S5'). Since the method for detecting whether the second user has read the message has been described above, the description is omitted here. If it is detected that the second user USER_B has read the corresponding message (message#1), the message eigenvalue management unit 22 of the server 20 deletes the eigenvalue (unique value 1) stored in the eigenvalue storage. (S6, S6').

The message confirmation status display unit 23 of the server 20 changes the message confirmation status of the second user mapped to the unique value to read when any one of the plurality of eigenvalues is deleted, and reads the changed message confirmation status. The corresponding message is displayed on the message list ML_A of the account of the first user USER_A by inserting the flag “[Read]” corresponding to the state (S7, S7').

In this embodiment, the first user (USER_A) account's post list (ML_A) includes a message indicating the message confirmation status for each of the message target users USER_B and USER_C, along with the content (message#1) of the message written by the first user. Is displayed.

In the example of FIG. 5, among a plurality of second users, message confirmation of USER_B is first detected (S5). The server 20 deletes the unique value (unique value 1) mapped to USER_B where message confirmation is detected from the repository (S6), changes the message confirmation status of USER_B to read, and inserts the flag "[read]" to remove 1 The corresponding message is displayed on the message list ML_A of the account of the user USER_A (S7). In this state, if the first user who wrote the message (USER_A) or the third user (USER_D) accesses the server 20 and reads the list of posts (ML_A) of the first user account, the corresponding message (message#1 ), you will see the flag marked "[Read]" for USER_B. At this time, since the second second user USER_C has not yet read the message (message#1), the flag for USER_C is maintained at the first set "[not read]". Therefore, it is possible to confirm that the corresponding message was read only by USER_B among the plurality of second users, as well as the first user who is the author as well as the other users who are the third users.

Subsequently, the server 20 detects whether or not the message is checked for the remaining second user (USER_C) (S5'). If it is detected that the remaining second user (USER_C) has read the corresponding message (message#1), the server deletes the unique value (unique value 2) mapped to the remaining second user (USER_C) from the repository (S6'), The message confirmation status of USER_C is changed to read, and the flag "[read]" is inserted to display the corresponding message on the message list ML_A of the account of the first user USER_A (S7'). In this state, if the first user who wrote the message (USER_A) or the third user (USER_D) accesses the server 20 and reads the list of posts (ML_A) of the first user account, the corresponding message (message#1 ), you will see the flag marked "[Read]" for USER_C. At this time, it is natural that the flag is changed to "[read]" for USER_B that has already read the message. Therefore, it is possible to confirm that the corresponding message has been read by all the second users (USER_B, USER_C), not only the first user who is the author, but also other users who are third parties.

It is also possible to combine the embodiment of FIG. 4 with the embodiment of FIG. 5. That is, when a message is written for a plurality of second users, a flag indicating whether the second user has read the corresponding message may be inserted into a list of postings of each second user's account. For example, in the example of FIG. 5, a flag indicating whether USER_B and USER_C read the message (message#1) created by the first user is inserted into and displayed in the posting list of the accounts of the plurality of second users USER_B and USER_C. Can be.

In the detailed description of the present invention described above, it has been described with reference to preferred embodiments of the present invention, but those skilled in the art or those skilled in the art will appreciate the spirit of the present invention as set forth in the claims below. And it will be understood that various modifications and changes can be made to the present invention without departing from the technical scope.

10: User terminal supporting autoplay 20: Server
21: message eigenvalue generation unit 22: message eigenvalue management unit
23: Message confirmation status display

Claims (17)

In a method performed by a server providing an open social network service in which messages received or sent through a first user account are disclosed to a plurality of users,
Receiving, from a first user terminal associated with the first user account, a text message comprising a first text specifying at least one second user account and a second text that is a message to be sent to the second user;
Generating an eigenvalue for the text message, and mapping and storing the eigenvalue with the text message;
Detecting whether the terminal of the second user accesses the server and checks the text message;
If it is detected that the terminal of the second user accesses the server and confirms the text message, deleting the stored unique value; And
In response to the deletion of the eigenvalue, notifying the first user terminal that the second user has confirmed the text message
How to include.
According to claim 1,
And notifying the second user terminal corresponding to the second user account that the text message has been transmitted from the first user.
The method of claim 1, wherein informing the first user terminal that the second user has confirmed the text message,
Setting a message confirmation status flag indicating whether the second user checks the text message to a first status corresponding to unconfirmed and adding it to the text message; And
Displaying the message confirmation status flag and the text message in a list of posts of the first user account
How to include.
The method of claim 3, wherein informing the first user terminal that the second user has confirmed the text message,
When the unique value is deleted, changing the message confirmation state to a second state corresponding to the confirmation; And
Displaying the changed message confirmation status flag and the text message in a list of posts of the first user account
How to include.
5. The method of claim 4, wherein the message confirmation status flag and the text message are disclosed to other users accessing the posting list of the first user account.
The method of claim 4, wherein informing the first user terminal that the second user has confirmed the text message,
Displaying the message confirmation status flag and the text message in a list of posts of the second user account
How to include more.
The method of claim 6,
Displaying the changed message confirmation status flag and the text message in the post list of the second user account
How to include more.
The method of claim 7, wherein the message confirmation status flag and the text message are disclosed to other users accessing the post list of the second user account.
The method of claim 1, wherein the first text specifies a plurality of second user accounts,
The unique value is generated and stored for each second user account.
A server providing an open social network service in which messages received or transmitted through a first user account are disclosed to a plurality of users,
When receiving a text message from the first user terminal associated with the first user account, the first text specifying at least one second user account and the second text that is a message to be sent to the second user, the text message A message eigenvalue generator for generating eigenvalues for;
A message eigenvalue storage unit that maps and stores the text message and the message eigenvalue;
If it is detected that the terminal of the second user accesses the server to check the text message, and when the terminal of the second user accesses the server to detect the text message, a message for deleting the stored unique value Eigenvalue management unit; And
In response to the deletion of the eigenvalue, a message confirmation status display unit indicating to the first user terminal that the second user has confirmed the text message
Server comprising a. The method of claim 10,
The message confirmation status display unit sets the message confirmation status flag indicating whether the second user confirms the text message to a first status corresponding to an unconfirmed status, and adds the message confirmation status flag and the text to the text message. A server that displays a message in the list of posts of the first user account.
The method of claim 11,
When the unique value is deleted, the message confirmation status display unit changes the message confirmation status to a second status corresponding to the confirmation, and the changed message confirmation status flag and the text message are added to the list of posts of the first user account. Server to display.
The server of claim 12, wherein the message confirmation status flag and the text message are disclosed to other users accessing the list of postings of the first user account.
The method of claim 11,
The message confirmation status display unit, the server to display the message confirmation status flag and the text message in the list of posts of the second user account.
The method of claim 14,
The message confirmation status display unit, the server to display the changed message confirmation status flag and the text message in the post list of the second user account.
16. The server of claim 15, wherein the message confirmation status flag and the text message are disclosed to other users accessing the post list of the second user account.
The method of claim 10, wherein the first text specifies a plurality of second user accounts,
A server characterized in that the unique value is generated and stored for each second user account.

Images