KR101777809B1 - Method for deleting message, system and terminal - Google Patents

Abstract

A method for deleting a message in a receiving terminal based on a request from a calling terminal includes receiving a message deleting request including an originating message ID from a calling terminal, transmitting a received message ID query corresponding to a calling message ID to a message server, Receiving a response to the received message ID from the server, transmitting a message deletion request corresponding to the received message ID to the calling terminal, receiving a message deletion notification corresponding to the outgoing message ID from the calling terminal, , And deleting the message corresponding to the received message ID.

Description

METHOD FOR DELETING MESSAGE, SYSTEM AND TERMINAL}

The present invention relates to a method, system and terminal for deleting a message.

2. Description of the Related Art As mobile communication technologies have developed, functions of mobile communication terminals providing mobile communication services have been diversified. Particularly, a short message service (SMS) for transmitting a text message using a mobile communication network has already become widely used and widely used.

In recent years, additional functions of a mobile communication terminal have been examined based on a standardization function related to a text message. For example, the calling terminal arbitrarily deletes a text message of a receiving terminal arbitrarily for a text message sent from the calling terminal. This can cause the reliability of the text message because the sender can arbitrarily delete the text message of the recipient.

Korean Patent Laid-Open No. 2006-0062201 discloses deletion of a multimedia messaging service (MMS) message in a receiving portable terminal, a deletion request is made from an MMS client of a called portable terminal to delete an originating MMS message of an ID that notified a notification to the MMS server , And deletes the originating MMS message of the corresponding ID from the MMS server.

It is desirable to prevent a unilateral deletion request from the calling terminal for the text message transmitted from the calling terminal to the receiving terminal. And a method for deleting the text message from the receiving terminal after the calling terminal confirms that the text message is deleted first. If a response message is received from the message server corresponding to the ID of the originating message included in the message deletion request of the originating terminal, the originating terminal desires to delete the message corresponding to the originating message ID. In addition, when the deletion notification for the message is received from the calling terminal, the message corresponding to the received message ID is deleted in response to the message deletion notification. It is to be understood, however, that the technical scope of the present invention is not limited to the above-described technical problems, and other technical problems may exist.

According to a first aspect of the present invention, there is provided a method of deleting a message at a receiving terminal based on a request from a calling terminal, the method comprising: receiving a message deletion request including an origination message ID from the calling terminal; Receiving a message ID from the message server, receiving a message ID from the message server, transmitting a message deletion request corresponding to the received message ID to the calling terminal, Receiving a message deletion notification corresponding to the origination message ID from the calling terminal, and deleting the message corresponding to the received message ID in response to the message deletion notification.

 According to a second aspect of the present invention, a message deletion system in a receiving terminal based on a request of a calling terminal according to the second aspect of the present invention transmits a message deletion request including an originating message ID to the receiving terminal, A source terminal for receiving a message deletion request corresponding to the source message ID and transmitting a message deletion notification corresponding to the source message ID to the destination terminal; a destination terminal for receiving a destination message ID query corresponding to the source message ID from the destination terminal, A message server for transmitting a response to the ID query to the receiver and a message deletion request including the ID of the originating message from the originating terminal and transmitting a received message ID query corresponding to the ID of the originating message to the message server , Receives a received message ID from the message server, Receiving a message deletion notification corresponding to the origination message ID from the originating terminal, receiving a message deletion notification corresponding to the received message ID in response to the message deletion notification, And a receiving terminal for deleting the receiving terminal.

According to a third aspect of the present invention, a receiving terminal for deleting a message based on a request of a calling terminal comprises a memory for storing a message received from the calling terminal and a processing unit arranged to interface with the memory, The processing unit receives a message deletion request including the originating message ID from the originating terminal, transmits a received message ID query corresponding to the originating message ID to the message server, receives a received message ID from the message server, Receiving a message deletion request corresponding to the received message ID to the calling terminal, receiving a message deletion notification corresponding to the origination message ID from the calling terminal, and receiving, in response to the message deletion notification, Message. ≪ / RTI >

The above-described task solution is merely exemplary and should not be construed as limiting the present invention. In addition to the exemplary embodiments described above, there may be additional embodiments described in the drawings and the detailed description of the invention.

According to any one of the above-mentioned objects of the present invention, it is possible to prevent a request for unilateral deletion of a calling party from a calling terminal to a receiving terminal. After confirming that the calling terminal first deleted the text message, the receiving terminal can delete the corresponding text message. When the receiving terminal receives the request for deleting the message from the calling terminal, the receiving terminal itself can prevent the message from being deleted unilaterally. Also, the receiving terminal can accurately delete the message corresponding to the ID by querying the message server with the ID of the message in which the deletion request is received.

1 is a configuration diagram of a message deletion system according to an embodiment of the present invention.
2 is a detailed configuration diagram of a receiving terminal shown in FIG. 1 according to an embodiment of the present invention.
FIG. 3 is a flowchart illustrating a message deletion method according to an embodiment of the present invention.
4A and 4B are operation flowcharts illustrating a message deletion method according to another embodiment of the present invention.
5 is a flowchart illustrating an example of a message deletion method according to an embodiment of the present invention.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings, which will be readily apparent to those skilled in the art. The present invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. In order to clearly illustrate the present invention, parts not related to the description are omitted, and similar parts are denoted by like reference characters throughout the specification.

Throughout the specification, when a part is referred to as being "connected" to another part, it includes not only "directly connected" but also "electrically connected" with another part in between . Also, when an element is referred to as "comprising ", it means that it can include other elements as well, without departing from the other elements unless specifically stated otherwise.

In this specification, the term " part " includes a unit realized by hardware, a unit realized by software, and a unit realized by using both. Further, one unit may be implemented using two or more hardware, or two or more units may be implemented by one hardware.

In this specification, some of the operations or functions described as being performed by the terminal or the device may be performed in the server connected to the terminal or the device instead. Similarly, some of the operations or functions described as being performed by the server may also be performed on a terminal or device connected to the server.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Reference will now be made in detail to embodiments of the present invention, examples of which are illustrated in the accompanying drawings.

1 is a configuration diagram of a message deletion system according to an embodiment of the present invention.

Referring to FIG. 1, a message deletion system may include a calling terminal 100, a receiving terminal 110, and a message server 120. However, since the message deletion system of FIG. 1 is only one embodiment of the present invention, the present invention is not limited to FIG. 1 and may be configured differently from FIG. 1 according to various embodiments of the present invention.

The calling terminal 100 can transmit a message to the receiving terminal 110. [ At this time, the header of the message may include the ID of the outgoing message. Here, the originating message ID may be transation information transmitted from the message server 120 when the originating terminal 100 originates a message.

Meanwhile, the receiving terminal 110 may receive the message from the calling terminal 100, extract the received message ID contained in the header of the message, and store the received message with the message. Here, the received message ID may be transation information received from the message server 120 when the receiving terminal 110 receives the message.

Thereafter, the calling terminal 100 may forward the message deletion request including the ID of the calling message to the receiving terminal 110.

The receiving terminal 110 inquires the message server 120 about the received message ID corresponding to the outgoing message ID and sends the received message ID to the message server 120 in response to the message deletion request received from the calling terminal 100 After receiving the message deletion request, the message deletion request corresponding to the received message ID can be transmitted to the calling terminal 100 again. Here, the received message ID query may include at least one of an originating message ID, a received message ID, a calling number, a receiving number, and a time stamp (time information).

The reason why the message server 120 and the received message ID are inquired and responded is that there is no identification number that can identify a message shared between the calling terminal 100 and the receiving terminal 110 Because.

On the other hand, when the calling terminal 100 receives a message delete request corresponding to the received message ID from the receiving terminal 110, the calling terminal 100 may first delete the message corresponding to the calling message ID. In the calling terminal 100, it is possible to determine the progress of deleting the message based on the presence or absence of the received message ID included in the message deletion request of the receiving terminal 110 in response to the reception terminal 110 as to whether or not the message deletion request progresses.

The calling terminal 100 may first delete the message corresponding to the calling message ID and then notify the receiving terminal 110 of a message deletion notification corresponding to the calling message ID.

The receiving terminal 110 may receive a message deletion notification corresponding to the origination message ID from the calling terminal 100 and may delete the message corresponding to the received message ID in response to the message deletion notification.

As described above, the calling terminal 100 and the receiving terminal 110 can check whether the calling terminal 100 and the receiving terminal 110 delete the message 100 by deleting the message. If the message deletion notification check fails between the calling terminal 100 and the receiving terminal 110, the calling terminal 100 notifies the receiving terminal 110 of the deletion failure and the receiving terminal 110 separately It may not proceed with the notification process.

The calling terminal 100 and the receiving terminal 110 may include a mobile terminal capable of wireless communication and according to various embodiments of the present invention the calling terminal 100 and the receiving terminal 110 may be connected to various types of devices Lt; / RTI > For example, the calling terminal 100 and the receiving terminal 110 may be portable terminals that can access a remote server through a network. Here, as an example of a portable terminal, a portable communication device that is guaranteed to be portable and mobility may be a personal communication system (PCS), a global system for mobile communications (GSM), a personal digital cellular (PDC), a personal handyphone system (PHS) (Personal Digital Assistant), IMT (International Mobile Telecommunication) -2000, CDMA (Code Division Multiple Access) -2000, W-CDMA (W-CDMA), Wibro (Wireless Broadband Internet) , Tablet PCs, and the like, all of which may include handheld based wireless communication devices. However, the calling terminal 100 and the receiving terminal 110 are not limited to those shown in FIG. 1 or those illustrated above.

The message server 120 may receive the received message ID query corresponding to the originating message ID from the receiving terminal 110 and may transmit a response to the received received message ID query to the receiving terminal 110. [ At this time, the message server 120 confirms the received message ID corresponding to the outgoing message ID by using at least one of the outgoing message ID, the received message ID, the calling number, the receiving number, and the time stamp included in the received message ID query And can inquire.

In general, the components of the message deletion system of FIG. 1 are connected through a network 130. The network refers to a connection structure in which information can be exchanged between each node such as terminals and servers. Examples of such a network include a 3rd Generation Partnership Project (3GPP), a Long Term Evolution (LTE), a WIMAX World Interoperability for Microwave Access), Wi-Fi, 3G, 4G, and the like.

Hereinafter, the operation of each component of the message deletion system of FIG. 1 will be described in more detail.

2 is a detailed configuration diagram of the receiving terminal 110 shown in FIG. 1 according to an embodiment of the present invention.

2, the receiving terminal 110 is a terminal for deleting a message based on a request from the calling terminal 100, and includes a memory 200 for storing a message received from the calling terminal 100, (Not shown).

The processing unit 201 can receive the message from the calling terminal 100 and extract the received message ID included in the header of the received message. Further, the processing unit 201 may store the extracted received message ID in the memory 200 together with the message.

The processing unit 201 may receive a message deletion request including the origination message ID from the calling terminal 100. [

The processing unit 201 may send a received message ID query corresponding to the outgoing message ID to the message server 120. [ At this time, the received message ID query may include at least one of an originating message ID, a received message ID, a calling number, a receiving number, and a time stamp. Here, the originating message ID may be transation information transmitted from the message server 120 when the originating terminal 100 originates a message. The received message ID may be transation information received from the message server 120 when the receiving terminal 110 receives the message.

In addition, the processing unit 201 may receive the received message ID in response to a received message ID query from the message server 120.

The reason why the message server 120 and the received message ID are inquired and responded is that there is no identification number that can identify a message shared between the calling terminal 100 and the receiving terminal 110 Because.

The processing unit 201 can search the memory 200 for a message corresponding to the received message ID. Specifically, the processing unit 201 searches for a message corresponding to the received message ID while confirming the identification number (for example, the calling number, the receiving number, the message size, etc.) can do.

If the message corresponding to the received message ID is not found, the processing unit 201 may transmit a message deletion failure to the calling terminal 100. [ On the other hand, if the processing unit 201 searches for a message corresponding to the received message ID, the processing unit 201 can transmit a message deletion request corresponding to the received message ID to the calling terminal 100.

Meanwhile, the processing unit 201 can confirm the read history of the message corresponding to the received message ID. At this time, when the reading history of the message corresponds to the reading, the processing unit 201 can transmit the message deletion failure to the calling terminal 100.

The processing unit 201 may receive a message deletion notification corresponding to the outgoing message ID from the calling terminal 100. [ Here, the calling terminal 100 deletes the message corresponding to the calling message ID, and then transmits a deletion notification of the deleted message to the receiving terminal 110.

In response to the message deletion notification, the processing unit 201 can delete the message corresponding to the received message ID. Specifically, the processing unit 201 can delete the message corresponding to the received message ID only when the message deletion notification is received from the calling terminal 100. [ This may mean that the message corresponding to the received message ID is not deleted from the receiving terminal 110 when the message deletion notification corresponding to the sending message ID is not received from the calling terminal 100. [

When the processing unit 201 deletes the message corresponding to the received message ID, the processing unit 201 can transmit a message deletion notification to the calling terminal 100. [

On the other hand, the processing unit 201 does not display a message deletion alarm on the screen of the receiving terminal 110 after the message deletion notification is notified to the calling terminal 100, but the present invention is not limited thereto.

In an embodiment of the present invention, the processing unit 201 may perform a process of deleting a message corresponding to a received message ID on the screen of the receiving terminal 110 only when the reading history of the message corresponding to the received message ID corresponds to reading A separate delete indication UI can be displayed.

FIG. 3 is a flowchart illustrating a message deletion method according to an embodiment of the present invention.

Referring to FIG. 3, in step S301, the calling terminal 100 may request the receiving terminal 110 to delete a message including the calling message ID.

In step S302, the receiving terminal 110 can inquire the message server 120 about the received message ID corresponding to the sending message ID.

The receiving terminal 110 may receive a response to the received message ID from the message server 120 in step S303.

In step S304, if there is a message including the received message ID, the receiving terminal 110 may request the calling terminal 100 to delete the message corresponding to the received message ID (message including the sending message ID) .

In step S305, the calling terminal 100 may delete the message including the calling message ID corresponding to the received message ID.

In step S306, the calling terminal 100 may transmit a message deletion notification corresponding to the calling message ID to the receiving terminal 110. [

In step S307, when receiving the message deletion notification, the receiving terminal 110 may delete the message including the received message ID corresponding to the outgoing message ID.

The receiving terminal 110 may transmit a message deletion notification corresponding to the received message ID to the calling terminal 100 in step S308.

4A and 4B are operation flowcharts illustrating a message deletion method according to another embodiment of the present invention.

Referring to FIGS. 4A and 4B, in step S401, the receiving terminal 110 may receive a message including the originating message ID from the calling terminal 100. FIG.

In step S402, the receiving terminal 110 may store the received message ID included in the header of the received message in the memory 200 of the receiving terminal 110 together with the message.

In step S403, the receiving terminal 110 may receive a message deletion request including the originating message ID from the calling terminal 100. [

In step S404, the receiving terminal 110 may inquire the message server 120 about the received message ID corresponding to the sending message ID.

The receiving terminal 110 may receive a response to the received message ID from the message server 120 in step S405.

In step S406, the receiving terminal 110 can check whether or not a message corresponding to the received message ID is retrieved from the memory 200. [

In step S407, if the message corresponding to the received message ID is not found, the receiving terminal 110 may transmit a message deletion failure to the calling terminal 100. [

In step S408, when the message corresponding to the received message ID is retrieved, the receiving terminal 110 can confirm the reading history of the message corresponding to the received message ID.

In step S409, when the reading history of the message corresponds to the reading, the receiving terminal 110 may transmit a message deletion failure to the calling terminal 100. [

If it is determined in step S410 that the reading history of the message is unread, the receiving terminal 110 may transmit a message deletion request corresponding to the received message ID to the calling terminal 100. [

In step S411, the calling terminal 100 may delete the message including the calling message ID corresponding to the received message ID.

In step S412, the calling terminal 100 can transmit a message deletion notification corresponding to the calling message ID to the receiving terminal 110. [

In step S413, when receiving the message deletion notification, the receiving terminal 110 may delete the message including the received message ID corresponding to the calling message ID.

The receiving terminal 110 may transmit a message deletion notification corresponding to the received message ID to the calling terminal 100 in step S414.

5 is a flowchart illustrating an example of a message deletion method according to an embodiment of the present invention.

The message deletion method according to the embodiment shown in FIG. 5 is performed in a time series manner in the calling terminal 100, the receiving terminal 110, and the message server 120 according to the embodiment shown in FIGS. 1 to 4 . Therefore, the description about the calling terminal 100, the receiving terminal 110, and the message server 120 in FIGS. 1 to 4 can be applied to the message deletion method according to the embodiment shown in FIG. 5 . ≪ / RTI >

Referring to FIG. 5, in step S501, the receiving terminal 110 may receive a message deletion request including the originating message ID from the calling terminal 100. [

In step S503, the receiving terminal 110 may transmit a received message ID query corresponding to the sending message ID to the message server 120. [ Here, the received message ID query may include at least one of an originating message ID, a received message ID, a calling number, a receiving number, and a time stamp.

In step S505, the receiving terminal 110 may receive a received message ID from the message server 120. [ Also, the receiving terminal 110 can search the memory 200 for a message corresponding to the received received message ID.

In step S507, if there is a message corresponding to the received message ID, the receiving terminal 110 may transmit a message deletion request corresponding to the received message ID to the calling terminal 100. [

The receiving terminal 110 may receive a message deletion notification corresponding to the outgoing message ID from the calling terminal 100 in step S509.

In step S511, the receiving terminal 110 may delete the message corresponding to the received message ID in response to the message deletion notification.

Although not shown in FIG. 5, when the message corresponding to the received message ID is not retrieved after step S505, the message deletion method further includes a step (not shown) of transmitting a message deletion failure to the calling terminal 100 .

Although not shown in FIG. 5, if the message deletion notification corresponding to the outgoing message ID is not received from the calling terminal 100 in step S509, the message deletion method may not delete the message corresponding to the received message ID .

In the above description, steps S501 to S511 may be further divided into additional steps or combined into fewer steps, according to an embodiment of the present invention. Also, some of the steps may be omitted as necessary, and the order between the steps may be changed.

One embodiment of the present invention may also be embodied in the form of a recording medium including instructions executable by a computer, such as program modules, being executed by a computer. Computer readable media can be any available media that can be accessed by a computer and includes both volatile and nonvolatile media, removable and non-removable media. In addition, the computer-readable medium may include both computer storage media and communication media. Computer storage media includes both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Communication media typically includes any information delivery media, including computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave, or other transport mechanism.

It will be understood by those skilled in the art that the foregoing description of the present invention is for illustrative purposes only and that those of ordinary skill in the art can readily understand that various changes and modifications may be made without departing from the spirit or essential characteristics of the present invention. will be. It is therefore to be understood that the above-described embodiments are illustrative in all aspects and not restrictive. For example, each component described as a single entity may be distributed and implemented, and components described as being distributed may also be implemented in a combined form.

It is intended that the present invention covers the modifications and variations of this invention provided they come within the scope of the appended claims and their equivalents. .

100: calling terminal
110:
120: message server

Claims (20)

A message deletion method in a receiving terminal based on a request from a calling terminal,
Receiving a message deletion request including an origination message ID from the calling terminal;
Transmitting a received message ID query corresponding to the origination message ID to a message server;
Receiving a received message ID from the message server;
Transmitting a message deletion request corresponding to the received message ID to the calling terminal;
Receiving a message deletion notification corresponding to the origination message ID from the calling terminal; And
Deleting a message corresponding to the received message ID in response to the message deletion notification;
The method comprising the steps of:
The method according to claim 1,
And transmitting a message deletion notification corresponding to the received message ID to the calling terminal.
The method according to claim 1,
Wherein the received message ID query includes at least one of the originating message ID, the received message ID, the originating number, the receiving number, and the timestamp.
The method according to claim 1,
After receiving the received message ID,
Confirming a read history of a message corresponding to the received message ID; And
Transmitting the message deletion failure to the calling terminal when the reading history corresponds to reading;
Further comprising the steps of:
The method according to claim 1,
Before the step of receiving the message deletion request,
Receiving a message from the calling terminal; And
Storing the received message ID included in the header of the message together with the message
Further comprising the steps of:
The method according to claim 1,
After receiving the received message ID,
Retrieving a message corresponding to the received message ID; And
Transmitting a message deletion failure to the calling terminal if a message corresponding to the received message ID is not retrieved
Further comprising the steps of:
The method according to claim 1,
When the message deletion notification corresponding to the origination message ID is not received from the calling terminal, the message corresponding to the received message ID is not deleted
Further comprising the steps of:
A message deletion system in a receiving terminal based on a request from a calling terminal,
A message deletion request including an outgoing message ID is transmitted to the reception terminal, a message deletion request corresponding to the reception message ID is received from the reception terminal, and a message deletion notification corresponding to the transmission message ID is transmitted to the reception terminal A calling terminal;
A message server receiving a received message ID query corresponding to the origination message ID from the receiving terminal and transmitting a response to the received message ID query to the receiving terminal; And
Receiving a message deletion request including the originating message ID from the originating terminal, transmitting a received message ID query corresponding to the originating message ID to the message server, receiving a received message ID from the message server, A message deletion request corresponding to the message ID is transmitted to the calling terminal, a message deletion notification corresponding to the calling message ID is received from the calling terminal, and in response to the message deletion notification, A receiving terminal
The message deletion system.
9. The method of claim 8,
Wherein the receiving terminal transmits a message deletion notification corresponding to the received message ID to the calling terminal.
9. The method of claim 8,
Wherein the received message ID query includes at least one of the originating message ID, the received message ID, the originating number, the receiving number, and the timestamp.
9. The method of claim 8,
The receiving terminal checks the reading history of the message corresponding to the received message ID,
Wherein the receiving terminal transmits a message deletion failure to the calling terminal when the reading history corresponds to reading.
12. The method of claim 11,
Wherein the receiving terminal transmits a message deletion request corresponding to the received message ID to the calling terminal when the reading history corresponds to not reading the reading history.
9. The method of claim 8,
Wherein the receiving terminal stores a received message ID included in a header of a message received from the calling terminal together with the message.
9. The method of claim 8,
The receiving terminal searches for a message corresponding to the received message ID,
Wherein the receiving terminal transmits a message deletion failure to the calling terminal when a message corresponding to the received message ID is not retrieved.
15. The method of claim 14,
Wherein the receiving terminal transmits a message deletion request corresponding to the received message ID to the calling terminal when the message corresponding to the received message ID is searched.
9. The method of claim 8,
Wherein the calling terminal deletes a message corresponding to the calling message ID in response to a message deletion request corresponding to the received message ID.
9. The method of claim 8,
Wherein the receiving terminal does not delete a message corresponding to the received message ID if the receiving terminal fails to receive a message deletion notification corresponding to the origination message ID from the calling terminal.
A receiving terminal for deleting a message based on a request from an originating terminal,
A memory for storing a message received from the calling terminal; And
And a processing unit arranged to interface with the memory,
The processing unit comprising:
Receiving a message deletion request including an origination message ID from the calling terminal,
Transmits a received message ID query corresponding to the origination message ID to the message server,
Receiving a received message ID from the message server,
Transmits a message deletion request corresponding to the received message ID to the calling terminal,
Receiving a message deletion notification corresponding to the origination message ID from the calling terminal,
And delete the message corresponding to the received message ID in response to the message deletion notification.
19. The method of claim 18,
The processing unit
And send a message deletion notification corresponding to the received message ID to the calling terminal.
19. The method of claim 18,
Wherein the received message ID query includes at least one of the originating message ID, the received message ID, the originating number, the receiving number, and the time stamp.

Images