Method for transferring and storing CPM service message and service thereof

• US 9,350,695 B2
• Filed: 06/21/2011
• Issued: 05/24/2016
• Est. Priority Date: 06/23/2010
• Status: Expired due to Fees

• Current Assignee: LG Electronics, Inc. (LG Corporation)
• Original Assignee: LG Electronics, Inc. (LG Corporation)
• Inventors: Lee, Hyeonsoo, Christophe, Le Thierry d'Ennequin
• Primary Examiner(s): Bates, Kevin
• Assistant Examiner(s): Pant, Ranjan
• Application Number:
  US13/704,892
• Publication Number:
  US 20130097265A1
• Time in Patent Office: 1,799 Days
• US Class Current: 1/1
• 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

A method is described for transferring a converged IP messaging (CPM) service based message using a server. The server transmits 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. The server receives a first session initiation protocol (SIP) invite message for extending the one-to-one session to a group session from the first terminal of the first user. The server extracts and locally stores various headers and IDs from the received first SIP invite message, and at least part of session description protocol (SDP) attributes with media streams from the received first SIP invite message if the first SIP invite message includes SDP content describing the media streams. The server transmits a second SIP invite message to the second terminal of the second user, and receives a termination message for terminating the one-to-one session.

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 the second user;

receiving, by the server, a first session initiation protocol (SIP) invite message for extending the one-to-one session to a group session from the first terminal of the first user,

wherein the first SIP invite message includes a header indicating the one-to-one session to be replaced by the group session, and a field indicating an identifier of the second terminal of the second user and an identifier of a third user, and

extracting and locally storing, by the server, a ‘

From’

header, a ‘

To’

header, a ‘

Date’

header, a same conversation ID and a new contribution ID from the received first SIP invite message;

extracting and locally storing at least part of session description protocol (SDP) attributes associated with media streams from the received first SIP invite message if the received first SIP invite message includes SDP content describing the media streams;

transmitting, by the server, a second SIP invite message to the second terminal of the second user in response to the reception of the first SIP invite message;

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

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

receiving, by the server, a first response message from the first terminal in response to the reception of the second termination message;

constructing, by the server, a one session history object including all contents extracted and locally stored during the one-to-one session in response to the reception of the first termination message; and

transmitting, by the server, a second response message for the first termination message to the second terminal of the second user.

2. The method of claim 1, further comprising:

receiving, by the server, a third response message from the second terminal of the second user after transmitting the second SIP invite message to the second terminal of the second user; and

transmitting, by the server, a fourth response message to the first terminal of the first user in response to the reception of the third response message.

3. The method of claim 2, further comprising:

after transmitting the fourth response message, receiving, by the server, a first acknowledgement message from the first terminal; and

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

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

checking, by the server, the first SIP invite message in response to the reception of the first SIP invite message; and

if the first SIP invite message includes the header indicating the one-to-one session to be replaced by the group session and information indicating that the group session is same as the one-to-one session, transmitting, by the server, the second SIP invite 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 first SIP invite message is an SIP-based INVITE message, the first response message is an SIP-based 200 OK message, and the first termination message is an SIP-based BYE message.

6. The method of claim 1, wherein the header indicating the one-to-one session to be replaced by the group session is a Session Replace header, the identifier of the second terminal is a GRUU, and the field indicating the identifier of the second terminal 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 first session initiation protocol (SIP) invite message for establishing a CPM session between a source terminal and one or more target entities from the source terminal,

wherein if there exists an existing conversation ID, the first SIP invite message includes the existing conversation ID,

wherein if there is no existing conversation ID, the first SIP invite message includes a newly generated conversation ID, and

wherein the first SIP invite message further includes a newly generated contribution ID;

extracting and locally storing, by the server, a ‘

From’

header, a ‘

To’

header, a ‘

Date’

header, a same conversation ID and a new contribution ID from the received SIP invite message;

extracting and locally storing at least part of session description protocol (SDP) attributes associated with media streams from the first SIP invite message if the first SIP invite message includes SDP content describing the media streams;

transmitting, by the server, a second SIP invite message to the one or more target entities in response to the reception of the first SIP invite message;

receiving, by the server, a response message from the one or more 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 target entities through the established CPM session;

receiving, by the server, a termination message for terminating the established CPM session from the source terminal; and

constructing a one session history object including all contents extracted and locally stored during the established CPM session in response to the reception of the termination message,

wherein if each of the messages transmitted and received through the established CPM 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 first SIP invite 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 a user of the source terminal after receiving the termination message, wherein the construction of the one session history object is performed if the user preference includes an element indicating that a history of the established CPM session has to be stored.

10. The method of claim 7, further comprising:

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 chunks before delivering the message.

12. A converged IP messaging (CPM) server comprising:

a memory;

a transceiver; and

a processor operably connected to the memory and the transceiver, the processor configured to;

control the transceiver to transmit 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;

control the transceiver to receive a first session initiation protocol (SIP) invite message for extending the one-to-one to a group session from the first terminal of the first user,

wherein the first SIP invite message includes a header indicating the one-to-one session to be replaced by the group session, and a field indicating an identifier of the second terminal of the second user and an identifier of a third user, and

extract and locally store in the memory a ‘

From’

header, a ‘

To’

header, a ‘

Date’

header, a same conversation ID and a new contribution ID from the received first SIP invite message,

extract and locally store in the memory at least part of session description protocol (SDP) attributes associated with media streams from the received first SIP invite message if the received first SIP invite message includes SDP content describing the media streams;

control the transceiver to transmit a second SIP invite message to the second terminal of the second user in response to the reception of the first SIP invite message;

control the transceiver to receive a first termination message for terminating the one-to-one session from the second terminal of the second user;

control the transceiver to transmit a second termination message for terminating the one-to-one session to the first terminal in response to the reception of the first termination message;

control the transceiver to receive a first response message from the first terminal in response to the reception of the second termination message;

construct a one session history object including all contents extracted and locally stored during the one-to-one session in response to the reception of the first termination message; and

control the transceiver to transmit a second response message for the first termination message to the second terminal of the second user.

13. The CPM server of claim 12, wherein the processor is further configured to:

check the first SIP invite message in response to the reception of the first SIP invite message; and

if the first SIP invite message includes a header indicating the one-to-one session to be replaced by the group session and information indicating that the group session is same as the one-to-one session, control the transceiver to transmit the second SIP invite message directly to only the second terminal of the second user, rather than to all registered terminals of the second user.

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

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