METHOD FOR TRANSFERRING AND STORING CPM SERVICE MESSAGE AND SERVICE THEREOF

• US 20130097265A1
• Filed: 06/21/2011
• Published: 04/18/2013
• Est. Priority Date: 06/23/2010
• Status: Active Grant

• Current Assignee: LG Electronics, Inc. (LG Corporation)
• Original Assignee: LG Electronics, Inc. (LG Corporation)
• Inventors: Christophe, Le Thierry d'Ennequin, Lee, Hyeonsoo
• Granted Patent: US 9,350,695 B2
• Time in Patent Office: Days
• US Class Current: 709/206
• CPC Class Codes: H04L 51/04 Real-time or near real-time messaging, e.g. instant messaging [IM]
• CPC Class Codes: H04L 51/216 Handling conversation history, e.g. grouping of messages in sessions or threads
• CPC Class Codes: H04L 51/56 Unified messaging, e.g. interactions between e-mail, instant messaging or converged IP messaging [CPM]
• CPC Class Codes: H04L 51/58 Message adaptation for wireless communication

Abstract

All the messages (even a session invitation message transmitted to establish a session for conversation) transmitted for conversion are stored by using a conversation ID and a contribution ID. Thus, a user A and a user B can read the stored conversation history any time through a certain terminal by using the conversation ID, the contribution ID, and the information regarding the object.

Claims

1. A method for transferring a converged IP messaging (CPM) service based message, the method performed by a server for handling terminals of a second user and the method comprising:

transmitting, by the server, one or more messages via a one-to-one session established between a first terminal of a first user and a second terminal of a second user;

receiving, by the server, a session initiation message for generating a group session from the first terminal of the first user,

wherein the session initiation message includes a header indicating that the session is to be replaced,

wherein the session initiation message includes a field indicating an identifier of the second terminal of the second user and an identifier of a third user, and

wherein the session initial message includes the same conversation ID as that of the one-to-one session and includes a new contribution ID different from that of the one-to-one session;

transmitting, by the server, the session initiation message to the second terminal of the second user in response to the reception of the session initiation message;

receiving, by the server, a termination message for terminating the one-to-one session from the second terminal of the second user;

transmitting, by the server, a termination message for terminating the one-to-one session to the first terminal in response to the reception of the termination message;

receiving, by the server, a response message from the first terminal;

constructing, by the server, one session history object including all messages transmitted between the terminals during the one-to-one session in response to the reception of the response message, wherein the one session history object further includes locally stored information including the conversation ID and the contribution ID;

receiving, by the server, a termination message for leaving the group session established among the first terminal of the first user, the second terminal of the second user, and a third terminal of the third user from any one of the first terminal, the second terminal and the third terminal; and

constructing, by the server, a new session history object including all the messages transmitted and received during the group session, in response to the reception of the termination message,

wherein the new session history object includes the same conversation ID and a new contribution ID,

wherein if each of the messages transmitted and received during the group session includes real-time media, the real time media is constructed as a single MIME object, the single MIME object is included in the new session history object.

2. The method of claim 1, further comprising:

receiving a response message from the second terminal of the second user after transmitting the session initiation message to the second terminal of the second user;

extracting information in the received session initiation message and locally storing the extracted information after receiving the response message; and

transmitting a response message to the first terminal of the first user in response to the reception of the response message.

3. The method of claim 2, further comprising:

after transferring the response message, receiving, by the server, an acknowledgement message from the first terminal; and

transmitting, by the server, an acknowledgement message to the second terminal in response to the reception of the acknowledgement message.

4. The method of claim 1, wherein the transmitting of the session initiation message to the second terminal of the second user comprises:

checking, by the server, the session initiation message in response to the reception of the session initiation message; and

if the session initiation message includes the header indicating that the session is to be replaced and information indicating that the session is the same as the one-to-one session, transmitting, by the server, a session initiation message directly to only the second terminal of the second user rather than to all registered terminals of the second user.

5. The method of claim 1, wherein the session initiation message is an SIP-based INVITE message, and the response message is an SIP-based 200 OK message, and the termination message is an SIP-based BYE message.

6. The method of claim 1, wherein the header indicating that the session is to be replaced is a Session Replace header, and the identifier of the second terminal is a GRUU, and the field including the identifier is a Request-URI field.

7. A method for transferring a converged IP messaging (CPM) service based message, the method is performed by a server for handling a source terminal and the method comprising:

receiving, by the server, a session initiation message for establishing a CPM session between the source terminal and one or more of target entities from the source terminal,

wherein if there exists an existing conversation ID, the session initiation message includes the existing conversation ID, and if there is no existing conversation ID, the session initiation message includes a newly generated conversation ID,

wherein the session initiation message further includes a newly generated contribution ID;

transmitting, by the server, a session initiation message to the one or more of the target entities in response to the reception of the session initiation message;

receiving, by the server, a response message from the one or more of the target entities;

transferring, by the server, one or more messages including one or more of a text, an image, a video, and a voice between the source terminal and the one or more of the target entities through a generated session;

receiving, by the server, a termination message for terminating the generated session from the source terminal;

constructing one session history object including all the messages transmitted and received through the session after receiving the termination message,

wherein the session history object includes the conversation ID and the contribution ID, and

wherein if each of the messages transmitted and received in the session includes real-time media, the real-time media is constructed as a single MIME object and the single MIME object is included in the session history object.

8. The method of claim 7, wherein the session initiation message is an SIP-based INVITE message, the response message is an SIP-based 200 OK message, and the termination message is an SIP-based BYE message.

9. The method of claim 7, further comprising:

checking a user preference with respect to the user of the source terminal after receiving the termination message,

wherein the construction step of the history object is performed if in the user preference there is an element indicating that a history of the session has to be stored.

10. The method of claim 7, further comprising:

extracting information from the received session initiation message and locally storing the extracted information; and

extracting information from the received termination message and locally storing the extracted information.

11. The method of claim 7, further comprising:

if each message is received in units of chunks, waiting for all chucks before delivering the message.

12. A converted IP messaging (CPM) server transferring a message, the server comprising:

a transceiver; and

a processor configured to control the transceiver, wherein the processor controls the transceiver to perform;

transmitting one or more messages via a one-to-one session established between a first terminal of a first user and a second terminal of a second user;

receiving a session initiation message for generating a group session from the first terminal of the first user,

wherein the session initiation message includes a header indicating that the session is to be replaced,

wherein the session initiation message includes a field indicating an identifier of the second terminal of the second user and an identifier of a third user, and

wherein the session initial message includes the same conversation ID as that of the one-to-one session and includes a new contribution ID different from that of the one-to-one session;

transmitting the session initiation message to the second terminal of the second user in response to the reception of the session initiation message;

receiving a termination message for terminating the one-to-one session from the particular terminal of the second user;

transmitting a termination message for terminating the one-to-one session to the first terminal in response to the reception of the termination message;

receiving a response message from the first terminal;

constructing one session history object including all messages transmitted between the terminals during the one-to-one session in response to the reception of the response message, wherein the one session history object further includes locally stored information including the conversation ID and the contribution ID;

receiving a termination message for leaving the group session established among the first terminal of the first user, the second terminal of the second user, and a third terminal of the third user from any one of the first terminal, the second terminal and the third terminal; and

constructing a new session history object including all the messages transmitted and received during the group session, in response to the reception of the termination message,

wherein the new session history object includes the same conversation ID and a new contribution ID,

wherein if each of the messages transmitted and received during the group session includes real-time media, the real time media is constructed as a single MIME object, the single MIME object is included in the new session history object.

13. The server of claim 12, wherein the transmitting of the session initiation message comprises:

checking the session initiation message in response to the reception of the session initiation message; and

if the session initiation message includes a header indicating that the session is to be replaced and information indicating that the session is the same as the one-to-one session, transmitting a session initiation message directly to only the second terminal of the second user, rather than to all of the terminals of the second user.

14. The server of claim 12, wherein the session initiation message is an SIP-based INVITE message, and the response message is an SIP-based 200 OK message, and the termination message is an SIP-based BYE message.

15. The server of claim 12, wherein the header indicating that the session is to be replaced is a Session Replace header, and the identifier of the second terminal is a GRUU, and the field including the identifier is a Request-URI field.