KR20100038991A - Mobile communication system and method for requesting disposition notification of im message for each of group members - Google Patents

Abstract

PURPOSE: A mobile communication system for requesting disposition notification of an im message for each of group members and a method thereof are provided to enable a sender to request IMDN(Instant Messaging Disposition Notification) to a desired member, thereby preventing an undesired notification from being received. CONSTITUTION: A transmission client transmits a generated IM message(100). An IM server regenerates an IM message for requesting disposition notification for the IM message according to each target client. The IM server transfers the regenerated IM message to the target clients(110). The target clients transfer reports that the transmission client requests(145).

Description

MOBILE COMMUNICATION SYSTEM AND METHOD FOR REQUESTING DISPOSITION NOTIFICATION OF IM MESSAGE FOR EACH OF GROUP MEMBERS}

The present invention relates to a mobile communication system and method for providing a messaging service, and more particularly, to a mobile communication system and method for requesting processing notification for a message when sending a message to group members based on the group messaging service. will be.

Currently within the Open Mobile Alliance (OMA) is the SIM for Instant Messaging and Presence Leverage Extensions (IMPLE) Instant Messaging (“IM”) service. This instant messaging technology allows users to send and receive messages between groups using user-defined groups of instant messages. This is called a group messaging service. As such, the group messaging service is based on the SIMPLE IM service, which can simultaneously send and receive messages between multiple users using the Session Initiation Protocol (SIP).

In the SIMPLE IM service, the sending user sends an Instant Messaging (IM) message, and then the sending user often wants to know if the receiving user actually received the message or read the message. In this case, the sender user may request a processing status, that is, an Instant Message Disposition Notification (IMDN) for a message transmitted to the receiver user or the receiver IM server. Specific details can be found in the reference document [draft-ietf-simple-imdn-07]. According to this reference, there are three main types of IMDN that can be requested by the sending user. IMDN has three types: processing report, delivery report, and read report.

First, the processing report serves to indicate whether the IM message sent by the sender user has been normally processed by the IM server. These processing reports include "processed" to indicate that the message was processed normally, "stored" to indicate that the message was stored on the network for later delivery, "error" to indicate that the message processing result could not be verified, and a processing report. It has four attributes, such as "forbidden", which indicates that it is not allowed.

The delivery report serves to indicate whether a message has been delivered to the corresponding receiving terminal, and is classified into positive delivery and negative delivery. This delivery report is “delivered” to indicate when the message is delivered to the receiving terminal, “failed” to indicate that the message cannot be delivered to the receiving terminal, “error” to indicate whether delivery could not be confirmed, It has four attributes, such as "forbidden", which indicate when a delivery report is not allowed.

The lead report serves to indicate whether the receiving user has confirmed or played the message. This lead report contains a “read” that indicates whether the receiving user has read or played the message, an “error” indicating when the receiving user does not know whether the message was read, or a “forbidden” indicating when the lead report is not allowed. It has three properties:

 Upon receiving the IMDN request, the receiving network or the receiving terminal may send several types of notifications to the sending network or the sending terminal by using a processing report, a delivery report, and a lead report according to the processing result of the message. have. Newly defined header fields, message formats, and other details for representing IMDN requests and responses can be found in [draft-ietf-simple-imdn-07].

As mentioned above, in a group messaging service, any user may request an IMDN when sending an IM message to other users participating in group messaging. However, in the current system, IM messages sent by the sender are delivered to all members participating in group messaging except the sender, so if the sender indicated intention to the IMDN request in the IM message, all terminals or users receiving the IM message They will be asked for an IMDN, and each will generate a corresponding report and send it back to the sender's network or sender's terminal.

This existing method is not efficient from the point of view of the sender as well as the network. If every user who receives an IM message generates a corresponding report according to the sender's IMDN request and sends the report to the sender, a heavy load is placed on the network, which can cause various network failures. Also, the sender is only interested in the results of the message being processed by a particular recipient, and if reports are received from all recipients, reports that are not of interest may feel like spam messages to the sender.

Accordingly, the present invention provides a mobile communication system and method for requesting a desired member to confirm processing of a message when a sender sends a message to group members based on a group messaging service.

In order to achieve the above, the present invention provides a mobile communication system for requesting a disposition notification for an instant messaging (IM) message for each group member, the at least one target for receiving a disposition notification for an IM message. A sender for generating an IM message including information for designating a client and transmitting the generated IM message, and if the IM message is transmitted from the sender client, whether or not to include the information for designating the target client in the forwarded IM message. An IM server for determining and reproducing an IM message requesting processing notification for the IM message for each target client if the information specifying the target client is included, and delivering the regenerated IM message to the target client; When the IM message is received from the server, the received IM message is received. And at least one target client for generating a report requested by the sending client for the message and delivering the generated report to the sending client through the IM server.

The present invention also provides a method for requesting a disposition notification for an instant messaging (IM) message for each group member in a mobile communication system including a transmitting client, an IM server, and one or more target clients. Generating an IM message including information designating at least one target client to which the processing notification for the IM message is to be received, and the IM client requesting the processing notification for the IM message for each target client. Transmitting the generated IM message to the IM server regenerating and transmitting to the target client; and generating from one or more target clients generating a report requested by the sending client for the IM message received through the IM server. Reminded reports It is characterized in that it comprises a process of receiving the transmitting client.

According to the present invention, when the sender requests an IMDN for a group IM message sent by the sender, the existing method that is requested to all group members except the sender is improved, so that the sender receives an unwanted report by requesting the IMDN only from the desired member. Can be prevented. As a result, the burden on billing caused when exchanging and receiving unnecessary reports between the sender and the receiver is reduced, and the quality of the IM service is induced by preventing unnecessary waste of network resources and making more efficient use of the resources.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. It is to be noted that the same elements among the drawings are denoted by the same reference numerals whenever possible. In addition, detailed descriptions of well-known functions and configurations that may unnecessarily obscure the subject matter of the present invention will be omitted.

The present invention proposes a method for requesting a notification of processing of an IM message from a sender to a desired group member in a group messaging service. To this end, in the present invention, when the sender configures an IM (Instant Messaging) message to include information on members designated by the sender and transmits the message to the IM server, the IM server corresponds to the corresponding IM members based on the information. It generates a message and delivers the generated IM messages to the corresponding members. As a result, only those members who have received the IM message can create their own reports and forward them to the sender. This allows the sender to receive processing notifications only from the desired group members.

Prior to describing the present invention, a reference document [draft-ietf-simple-imdn-07] referred to in the present invention will be briefly described. This reference provides a mechanism for the sender to request an IMDN, and several new definitions of Common Profile for Instant Messaging (CPIM) headers are for this purpose. One of them is the "Disposition-Notification" header field. This header field is used to inform the receiver what report the sender is requesting.

In the present invention, the sender uses a "Disposition-Notification" header field to designate a target receiver among group members, and for this purpose, a new parameter is defined in the "Disposition-Notification" header field. Reference is made to FIG. 1 to describe this in detail.

FIG. 1 illustrates syntax for a “Disposition-Notification” header field according to an embodiment of the present invention. According to the syntax of FIG. 1, the “Disposition-Notification” header field may have any one of “negative-delivery”, “positive-delivery”, “processing”, and “read” as a field value. If you have more than one field value, each value is separated by a comma. In addition, 'generic-param' may be located immediately after each value separated by a comma. The field value is separated by a semicolon. In the present invention, a new parameter 200 for defining a target recipient for an IMDN request from a sender is defined in 'generic-param'.

As illustrated in FIG. 1, the new parameter 200 in which the parameter name is defined as “target” may have one or more URI values. If the parameter has more than one URI as its value, each URI must be separated by a delimiter. In the present invention, a comma is used as such a separator. However, when it is determined that it is inappropriate to use a comma, it may be changed to another more suitable separator.

By defining and using the “target” parameter as a new parameter as described above, when any sender participating in group messaging sends an IM message containing an IMDN request to the group members, the sender as well as the group's entire members, It is possible to select members and have the sender request the IMDN only for the selected members.

Hereinafter, an operation between components of the mobile communication system based on the group messaging service will be described with reference to FIG. 2. 2 is a diagram illustrating a message transfer process between a sender and a target receiver according to an embodiment of the present invention. In FIG. 2, member 1 is a sending client, member 2, member 3, and member 4 correspond to target clients designated by the sending client, and for the purpose of understanding the present invention, member 1 is called 'Alice', and member 2 is' Ann ', member 3 is called' Bob 'and member 4 is called' Tom '. In addition, hereinafter, for convenience of description, the transmitting client terminal is called a sender, and the target client terminal is called a target receiver.

First, if member 1 (10) wants to be notified of an IM message reception, processing result, etc., the sending client terminal corresponding to member 1 (10) conforms to the standard defined in [draft-ietf-simple-imdn-07]. Create an IM message to contain the IMDN request. In particular, according to an embodiment of the present invention, an IM message including information of a target recipient is configured to designate desired group members. For this purpose, a newly defined “target” parameter is used in the “Disposition-Notification” header field as shown in FIG. 1.

When the IM message designating the target recipient is generated as described above, the IM message is transmitted to the IM server 20 in step 100. In this case, since the IM message delivered to the IM server 20 includes "target" parameter information that designates a target recipient for each request report type, the IM server 20 interprets the "target" parameter included in the IM message. Each target recipient must then request the report as intended by the sender.

3 and 4 show an example of a configuration of an IM message transmitted to the IM server 20. 3 is a diagram illustrating a case in which the target receiver is directly expressed according to an embodiment of the present invention, and FIG. 4 is a diagram illustrating a case in which the target receiver is indirectly expressed according to an embodiment of the present invention.

Figure 3 illustrates the body part of an IM message generated by using the "target" parameter when the sender requests the lead report and positive delivery report for this text message while delivering the text "Hello World." For example, if the sender requests only a lead report from Bob, member 3, requests a lead report and positive delivery report from Ann, member 2, and no report from Tom, member 4, as shown in FIG. The information of the target recipient can be represented in a manner. For reference, the body part of an IM message including an IMDN request is expressed as content in CPIM format.

In FIG. 3, the "Disposition-Notificaton" header field 300 has "read" and "positive-delivery" as field values and has a "target" parameter associated with each field value. The "target" parameter associated with "read" has Bob's address as the parameter value, and the "target" parameter associated with "positive-deliver" has Bob's and Ann's address as parameter values. On the other hand, since Tom does not have the requested report, Tom's address does not belong to any of the "target" parameters above. As shown in FIG. 3, in the “target” parameter of the “Disposition-Notifiation” header field, a URI that is an address of target recipients for a corresponding report request can be directly expressed.

Meanwhile, unlike in FIG. 3, a URI, which is an address of target recipients, may be indirectly expressed in a “target” parameter, which may be expressed as illustrated in FIG. 4. In this case, a URI-List and an id pointing to it are used.

Specifically, the URI of the target receiver for the IMDN request is expressed in a URI-List (XML document) and inserted into the body part of the CPIM message. Instead, the “target” parameter has an id indicating a URI-List as a value. 4 illustrates an example of representing a target receiver for an IMDN request by using a URI-List and an id of a URI-List. In FIG. 4, the URI-List representing the Ann's URI and Bob's URI is inserted into the body portion 410 of the CPIM region of the IM message, and the field value of the “Disposition-Notification” header field 400, “read”. The “target” parameter dependent on “” has a pointer 405 indicating a URI-List as a parameter value. A pointer 405 to this URI-List is assigned to the “target” parameter, which points to the content-id 415 of the body portion 410 of the CPIM region.

As described above, FIGS. 3 and 4 express that content of requesting a lead report to Ann and Bob. In FIG. 4, the “target” parameter dependent on the field value of the “Disposition-Notification” header field 400 and the “positive-delivery” may also indirectly express the target recipient for the request as the field value “read”. Can be. However, when there is only one target recipient, the URI-List of the target subjects to be expressed indirectly must be attached to the body part of the CPIM content, and as a result, only the total size of the IM message is unnecessarily increased. It is more efficient to express directly as

The IM message constructed in the same manner as in FIG. 3 or FIG. 4 described above is transferred to the IM server 20, and the IM server 20 determines whether the IM message includes "target" parameter information. If it is determined that the "target" parameter information is included, the IM server 20 regenerates an IM message to be delivered to each member according to the "target" parameter information in step 105.

Specifically, the IM server 20 generates and delivers an IM message requesting a lead report and a positive delivery report to Ann, the member 2 30, in step 110 according to the target recipient information in FIG. 3 or 4. In step 3, Bob, member 3 (40), generates and delivers an IM message requesting a lead report. In step 120, the IM server 20 generates and delivers an IM message requesting no report to Tom, the member 4 (50). At this time, all of the regenerated IM messages must include the text "Hello World", which is user data that Alice, member 1 (10) wants to deliver. In addition, assuming that all group members are in the same service provider area, as shown in FIG. 2, a separate IM server is not required for each target receiver, and an IM message is directly transmitted from the sending IM server 20 to each target receiver. do. Otherwise, the IM server 20 delivers the regenerated IM message to the receiving IM server to deliver the regenerated IM message to the respective members 30-50. To each of the regenerated IM messages.

On the other hand, the above operation is also applied to the case that the "Disposition-Notification" header field has a plurality of values, some of which have a "target" parameter. For example, the "Disposition-Notification" header field has the "target" parameter associated with "read" with "positive-delivery" and "read" as the field values, of which the "target" parameter associated with "positive-delivery" Assume that we do not have. In this case, the lead report is requested only to the target recipient specified by the "target" parameter, while a positive delivery report without an associated "target" parameter is requested to all recipients of the IM message, i.e. all of the group members. In other words, the "Disposition-Notification" header field value without the "target" parameter is processed according to the existing method, and the report requested by the corresponding "Disposition-Notification" header field value is requested to all recipients.

On the other hand, when each target recipient receives an IM message containing a request for a report, the target recipients generate the requested report and return it to the sender by accepting the request. At this time, if the report request from the sender is rejected, the target receiver generates and returns the corresponding report. However, in this case, instead of including the requested message status or processing information, the report contains that the report requested by the sender was rejected by the target recipient. See [draft-ietf-simple-imdn-07] for details.

Since Ann, a member 2 (30), has requested a lead report and a positive delivery report in step 110, member 2 (30) forwards the positive delivery report to the IM server 20 in step 125, and IM in step 130. Transfer to server 20. In step 135, the IM server 20 combines the two reports into one and delivers the combined report to the sender member 1 (10). Since the lead report is requested to Bob, the member 3 (40) in step 115, member 3 (40) delivers the lead report to the IM server 20 in step 140. In step 145, the IM server 20 transmits the lead report to the member 1 (10). As such, when the sending IM server 20 receives a report from each target receiver, the transmitting IM server 20 transmits the report to the sender. At this time, the IM server 20 may deliver the report immediately to the sender immediately after receiving the report. Alternatively, the IM server 20 may wait for a certain period of time, and then transfer the received report into one.

Hereinafter, an operation of the transmitter IM server 20 will be described in detail with reference to FIG. 5. 5 is a flowchart illustrating operations of a sending IM server according to an exemplary embodiment of the present invention.

Referring to FIG. 5, the IM server 20 determines whether an IM message is received in step 500. If it is determined that the IM message is received, it is determined in step 505 whether the IMDN request is included in the IM message. Specifically, it is determined whether an IM message includes a processing notification request for the message from the target receiver, and whether or not to include the “Disposition-Notification” header field may be determined. Accordingly, when an IM message includes an IMDN request, it means that the "Disposition-Notification" header field is included in the IM message.

If the IMDN request is not included, the IM server 20 processes the IM message in a conventional manner in step 510. That is, the IM server 20 replicates the IM message by the number of all group members and transmits the IM message to each group member. To this end, the IM server 20 may change the recipient address field of the replicated IM messages to the IM address of each group member.

In contrast, when the IMDN request is included, the IM server 20 analyzes the processing notification header in step 515. In other words, it analyzes the "Disposition-Notification" header field. In operation 520, it is determined whether the header field includes "target" parameter information. If the "target" parameter information does not exist in the header field, the IM server 20 proceeds to step 510 and processes the same as the method of processing an IM message including an IMDN request. Consequently, the IMDN requested by the sender is requested by all recipients of the IM message, that is, the entire group.

In contrast, when the "target" parameter information is present, the IM server 20 determines whether the value of the "target" parameter is a URI-List type in step 525. Specifically, the IM server 20 determines whether the value of the "target" parameter indicates the IM address of the target receiver, that is, the URI value, or indicates the URI-List included in the body part of the IM message.

If the value of the “target” parameter points to a URI-List included in the IM, the IM server 20 sends each IM message including the specified report request to the members having the address of the URI-List in step 530. Create Accordingly, the IM server 20 includes a request for a report indicated by the value of the "Disposition-Nofication" header field associated with the "target" parameter for each target recipient in the IM message to be delivered to the IM address expressed in the URI-List.

In contrast, when the value of the "target" parameter is not a URI-List type, that is, when the value of the "target" parameter is the URI value of the target receiver, the IM server 20 checks for the members whose URI is the address in step 535. Create an IM message containing the specified report request. Accordingly, the IM server 20 includes a request for a report indicated by the value of the "Disposition-Nofication" header field associated with the "target" parameter for each target recipient in the IM message to be delivered to the target recipient of the corresponding URI value.

When each IM message is generated for each target recipient through the above process, the IM server 20 transmits each generated IM message to each member corresponding to the target receiver in step 540. At this time, the sender IM server 20 directly delivers the IM message to the target receiver when the target receiver exists in the same network area as the sender. Otherwise, the receiver side provides the group messaging service to the group members. The message is passed through the IM server. According to the present invention as described above, the sender can designate desired members of the group members and receive a processing notification from only those designated members, thereby improving the quality of the IM service.

1 is a syntax for “Disposition-Notification” header field according to an embodiment of the present invention;

2 is a diagram illustrating a message delivery process between a sender and a target receiver according to an embodiment of the present invention;

3 is a diagram illustrating a case where a target recipient is directly expressed according to an embodiment of the present invention;

4 is a diagram illustrating a case of indirectly expressing a target receiver according to an embodiment of the present invention;

5 is a flowchart of operation in a sending IM server according to an embodiment of the present invention;

Claims (11)

A mobile communication system for requesting a disposition notification for an instant messaging (IM) message for each group member, A sending client for generating an IM message including information specifying at least one target client to receive a processing notification for the IM message, and transmitting the generated IM message; When the IM message is transmitted from the sending client, it is determined whether the delivered IM message includes the information specifying the target client, and when the information specifying the target client is included, the notification of the processing of the IM message for each target client. An IM server that regenerates the IM message requesting the request and delivers the regenerated IM message to the corresponding target client; Receiving the IM message from the IM server, generating at least one target client for the received IM message and passing the generated report to the sending client via the IM server. A mobile communication system for requesting a processing notification for an IM message for each group member. The method of claim 1, wherein the information designating the one or more target clients includes: And a processing notification for a group member IM message, wherein the processing notification header field is inserted into the processing notification header field in the IM message. The method of claim 1, wherein the information designating the one or more target clients includes: And a processing parameter for a group member IM message, wherein the target parameter defined in the processing notification header field of the IM message is expressed as a URI value of the target client. The method of claim 1, wherein the information designating the one or more target clients includes: A mobile communication system for requesting a processing notification for an IM message for each group member, wherein the target parameter defined in the processing notification header field in the IM message is expressed as a point for a URI list indicating the URI of the target client. The method of claim 1, wherein the IM server, Whenever a report is received from the target client, the mobile communication system for requesting a processing notification for an IM message for each group member is delivered to the transmitting client or a combination of one or more reports received during a waiting time. . A method for requesting a disposition notification for an instant messaging (IM) message for each group member in a mobile communication system including a sending client, an IM server, and one or more target clients, the method comprising: Generating, by the sending client, an IM message including information specifying at least one target client to which the processing notification for the IM message is to be delivered; Transmitting, by the sending client, the generated IM message to the IM server which regenerates an IM message for requesting processing notification of the IM message for each target client and transmits the IM message to the target client; Receiving the generated report from at least one target client generating a report requested by the sending client with respect to the IM message received through the IM server. Method for requesting a disposition notification for a disposition. The method of claim 6, wherein the information designating the one or more target clients includes: And inserting a processing notification header field in the IM message. The method of claim 6, wherein the information designating the one or more target clients includes: And a target parameter defined in a processing notification header field in the IM message, expressed as a URI value of the target client. The method of claim 6, wherein the information designating the one or more target clients includes: And a point for a URI list indicating a URI of the target client in a target parameter defined in a processing notification header field in the IM message. The process of claim 6, wherein the transmitting client receives the generated report. And a process of receiving the IM message for each group member, wherein the IM server receives the generated report from the target client. The process of claim 6, wherein the transmitting client receives the generated report. And receiving the combined report when the one or more reports received from the target client by the IM server are combined by the IM server.

Images