KR101689196B1 - Method for transmitting and receiving session history in communication system - Google Patents

Abstract

A method for receiving a session history of a control function (CF) in a communication system, the method comprising the steps of: determining whether a CF belonging to a first domain is a Conversation Server (CS) belonging to the first domain, Transmitting a first message requesting a session history from a CS belonging to the second domain to a second domain that has the session history from a CS belonging to the first domain, if the CS belonging to the first domain does not have a session history; Receiving a second message including access information on a CS belonging to a domain, and requesting the session history from a CS belonging to the second domain having the session history, based on the access information, Receiving a fourth message including the session history from a CS belonging to the second domain, the method comprising the steps of: The first message and the third message include a destination address of a CS belonging to the first domain or a CS belonging to the second domain, a content-type requesting session history related information, and information on a session identifier.

Description

[0001] METHOD FOR TRANSMITTING AND RECEIVING SESSION HISTORY IN COMMUNICATION SYSTEM [0002]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a communication system, and more particularly, to a method of transmitting and receiving session history in a communication system.

In recent years, due to performance enhancement and bandwidth expansion of wireless communication, a basis for performing services that could only be performed in a wired environment is being established in a wireless environment. Also, according to the demand of the users, the services should be provided in an all IP (Internet Protocol) based wired / wireless network. Accordingly, OMA (Open Mobile Alliance), a global mobile phone standardization organization, tries to integrate a mobile service and an IP-based service through a session called CPM (Converged IP Messaging) .

As such, protocols used for providing an integrated service include a session initiation protocol (SIP), a message session relay protocol (MSRP), and a real time transfer protocol (RTP) Protocol).

Among the above protocols, SIP defines a standard in an Internet Engineering Task Force (IETF) Request for Comment (RFC) 3261 document, and application-level signaling for setting, modifying, and terminating a session for multimedia communication such as video and audio Protocol. The SIP transmits / receives a message in a request / response manner with a protocol existing on UDP (user datagram protocol) / TCP (transmission control protocol) / IP layer. The SIP-based request message may include an INVITE, an ACK, an BYE, a REGISTER, and a REGISTER message, as defined in RFC 3261. [ Registration of the client's location information in the database of the register server), CANCEL (cancel request pending), and option (OPTIONS: request information about the server). The SIP-based response message includes 1xx (information response), 2xx (success response), 3xx (redirection response), 4xx (client error), 5xx (server error), and 6xx .

The MSRP defines a standard in the IETF RFC 4975 document and is used for text data transmission within a session. The MSRP is designed to compensate for the disadvantage that the text data transmission method using an existing SIP-based MESSAGE message does not take into account the relationship between messages at all, and the MSRP is used to transmit the SEND (message transmission) and REPORT Lt; / RTI >

BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a diagram showing the structure of a general CPM system. FIG.

1, the CPM system includes a CPM client 100, a CPM conversation server 110, a CPM control function (hereinafter, referred to as 'CF' 120, an application control function 130, an interworking selection function 140, an interworking function 150, a message and media And a Message and Media Storage Server (M & MS) 170. The M & The M & MS 170 may exist as a separate component or may be included in the CS 110.

 The CPM Client 100, as a service requestor, creates a session with another CPM Client through the CS 110 and receives a service. The M & MS 170 stores data transmitted and received through a session created between the CPM clients. Whether or not the CPM session data is stored is determined by the user preference and the service provider policy.

The CF 120 creates and manages a session between the CPM Client 100 and the CS 110. That is, when the group session is created, the CF 120 creates a session between the CPM Client 100 and the CS 110 and the CF 120 of the corresponding user domain. After the session is created, the CF 120 transmits a message received from the CPM Client 100, which is a subscriber of the group session, to another subscriber of the group session. Here, the domain is divided by a service provider.

On the other hand, all kinds of data sets sent and received between the CPM clients from the start of the session to the present are referred to as session history. The session history is managed by a CPM Conversation History Function (not shown) within the CS 110 and may be stored in the CPM conversation history function in the M & have.

The session history of the current one-to-one session is managed in the CPM conversation history function of the CS 110 and may be temporarily stored in the CPM conversation history function of the M & MS 170 or CS 110. In addition, the session history of the one-to-one sessions may be separately managed for each CS of each domain, and may not be stored according to the user preference and service provider policy.

US 20070100908 'Method and apparatus for tracking history information of a group session' (hereinafter referred to as 'jain') discloses a method for tracking histological information about a group session. However, the session history tracking of the group in the jain must be preceded by group selection. In addition, the jain does not describe the process of creating a group session and the details of how the session history is transmitted and received.

Accordingly, the present invention proposes a concrete method of generating a session history in a communication system, and managing and transmitting the generated session history.

A first method of the present invention is a method for receiving a session history of a control function (CF) in a communication system, wherein a CF belonging to a first domain is a conversation server (CS) belonging to the first domain The method comprising the steps of: transmitting a first message requesting a session history to a second domain that holds the session history from a CS belonging to the first domain if the CS belonging to the first domain does not have a session history; Receiving a second message including access information on a CS belonging to the first domain and a third message requesting the session history from a CS belonging to the second domain having the session history based on the access information; And receiving a fourth message including the session history from a CS belonging to the second domain, And the third message include a destination address of a CS belonging to the first domain or a CS belonging to the second domain, a content-type requesting session history related information, and information on a session identifier.

A second method of the present invention is a method for transmitting / receiving a group session history in a communication system in which a group session is created between at least two client terminals, wherein a client terminal belonging to a first domain includes a conversation server (CS The method comprising: transmitting a first message requesting a group session history to a Conversation Server; Receiving a second message including access information on a storage area in which the group session history is stored from a control function (CF) belonging to a second domain; Reading the group session history from the storage area based on the first group message history and transmitting the read group session history to the client terminal, A destination address of a CS belonging to the second domain, a content-type requesting session history related information, and information on a session identifier.

A third method of the present invention is a method for transmitting / receiving a group session history in a communication system in which a group session is created between at least two client terminals, characterized in that a client terminal belonging to a first domain includes a conversation server (CS The method comprising the steps of: transmitting a first message requesting a group session history to a Conversation Server (CS) from a Control Function (CF) belonging to a second domain; The method comprising: receiving a second message including access information; transmitting, by the CS, the access information to a client terminal belonging to the first domain; And reading the group session history from the storage area based on the access information, wherein the first message includes a CS belonging to the first domain or a destination address of a CS belonging to the second domain A content-type requesting session history related information, and information on a session identifier.

A fourth method of the present invention is a method for transmitting / receiving a group session history in a communication system in which a group session is created between at least two clients, wherein a client belonging to the first domain sends a group session (CS) belonging to the first domain receiving the first message transmits a second message requesting the group session history to a control function unit (CF) belonging to a second domain, Transmitting a third message requesting the group session history to a CS belonging to a third domain, and transmitting the third message to a CS belonging to the third domain from a memory in which the group session history is stored Obtaining the group session history and transmitting the obtained group session history to a CF belonging to the second domain; The CF belonging to the second domain receives the group session history and transmits the received group session history to the CS belonging to the first domain; and the CS belonging to the first domain receives the group session history And transmitting the received group session history to a client belonging to the first domain.

A fifth method of the present invention is a method for transmitting / receiving a group session history in a communication system in which a group session is created between at least two clients, wherein a client belonging to the first domain communicates with a conversation server (CS) (CS) belonging to the first domain, which receives the first message, transmits a first message requesting a session history to a second functional entity (CF) belonging to a second domain, Wherein the CF belonging to the second domain receiving the second message obtains the access information of the CS belonging to the third domain managing the memory in which the group session history is stored, The method comprising: receiving access information on a memory in which a group session history is stored from a CS belonging to a domain; Transmitting a group session history from the memory using the received access information to a CS belonging to the first domain; receiving the access information from the memory; And transmitting the obtained group session history to a client belonging to the first domain.

A sixth method of the present invention is a method for transmitting / receiving a group session history in a communication system in which a group session is created between at least two clients, wherein a client belonging to the first domain communicates with a conversation server (CS) (CS) belonging to the first domain, which receives the first message, transmits a first message requesting a session history to a second functional entity (CF) belonging to a second domain, Wherein the CF belonging to the second domain receiving the second message obtains the access information of the CS belonging to the third domain managing the memory in which the group session history is stored, The method comprising: receiving access information on a memory in which a group session history is stored from a CS belonging to a domain; Transmitting the access information acquired by the CS to a CS belonging to the first domain, receiving the access information, and transmitting the received access information to a client belonging to the first domain And a client belonging to the first domain receiving the access information and obtaining the group session history from the memory using the received access information.

A seventh method of the present invention is a method for transmitting / receiving a group session history in a communication system in which a group session is created between at least two clients, wherein a client belonging to the first domain communicates with a conversation server (CS) (CS) belonging to the first domain, which receives the first message, transmits a first message requesting a session history to a second functional entity (CF) belonging to a second domain, And the CF of the second domain receiving the second message requests the group session history to the CS belonging to the third domain managing the memory in which the group session history is stored, Message from the memory, and the CS belonging to the third domain receiving the third message obtains the group session history from the memory The CF belonging to the second domain receives the group session history from the CS belonging to the third domain, and the received group session history To a CS belonging to the first domain, a CS belonging to the first domain receiving the group session history, and transmitting the received group session history to the clients belonging to the same domain .

In the eighth method of the present invention, in a communication system in which a group session is created between at least two clients, in a group session history transmission / reception method, a client belonging to the first domain is grouped into a conversation server (CS) belonging to the same domain (CS) belonging to the first domain, which receives the first message, transmits a first message requesting a session history to a second functional entity (CF) belonging to a second domain, After the second message is transmitted, the CF belonging to the second domain obtains the group session history from the memory in which the group session history is stored, and transmits the obtained group session history to the first domain To a CS belonging to the first domain; receiving a group session history from a CS belonging to the first domain; And transmitting the history to the clients belonging to the first domain.

As described above, the present invention provides a concrete method of efficiently transmitting and receiving session history in a communication system, thereby providing an improved service in data communication between users.

1 is a view showing the structure of a general CPM system;
2 is a diagram showing a communication system structure when a CS manages session history in the present invention
3 is a diagram illustrating a communication system structure in the case where CF manages session history in the present invention
FIGS. 4A and 4B are diagrams illustrating a process in which the CS of the domain B informs the CF of the domain A of the session history in the communication system according to the first embodiment of the present invention
5 is a diagram illustrating a process in which CS B transmits a group session history to CF A in the communication system according to the second embodiment of the present invention
6 is a diagram illustrating a process in which a client C obtains a group session history in a communication system according to a third embodiment of the present invention
7 is a diagram illustrating a process in which a client C acquires a group session history in a communication system according to a fourth embodiment of the present invention
8A and 8B are diagrams illustrating a process in which a CS C transmits a group session history to a client C in a communication system according to a fifth embodiment of the present invention
9A and 9B are diagrams illustrating a process in which a client C obtains a group session history from an M & MS B in a communication system according to a sixth embodiment of the present invention
10A and 10B are diagrams illustrating a process in which a client C obtains a group session history in a communication system according to a seventh embodiment of the present invention
11A and 11B are diagrams illustrating a process of transmitting a session history until a group session is created in a one-to-one session in the communication system according to the eighth embodiment of the present invention
12 is a flowchart illustrating a process of transmitting a session history to a client C by a CF A managing a session history according to a ninth embodiment of the present invention

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. In the following description of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present invention rather unclear.

The present invention proposes a concrete method of generating a session history in a communication system, and managing and transmitting the generated session history. Hereinafter, the present invention will be described separately in the case where the session history is managed by the CS and the case where the session history is managed by the CF. The session history includes both a one-to-one session history and a group session history.

FIG. 2 is a diagram illustrating a system structure when the CS manages session history in the present invention.

2, when the client A 212 of the domain A and the client B 222 of the domain B create a one-to-one session and conduct a conversation, the client C 212 of the domain C ) To create a group session to add a group conversation. In this case, it is assumed that the CS 221 of the domain B manages the session history.

After the group session is created, each of the clients 212 and 232 of the domains A and C requests and receives the group session history via the direct or different path of the CS 221 of the domain B to know the group session history. The group session history may be stored in the CS 221 or the M & MS 223.

If the client B 222 of the domain B leaves the group session, the CS 221 can not receive the data related to the conversation transmitted and received in the group session, and thus the group session history can not be managed do. In this case, the CF 200 needs to manage the group session history. In FIG. 3, the case of managing the group session history in the CF 200 will be described.

FIG. 3 is a diagram showing a system structure in the case where the CF manages the session history in the present invention.

Referring to FIG. 3, the CF 300 must have a Conversation History Function (CHF) defined in the CS. The CF 300 includes a group session history (MMS) 313 and an Internet Message Access Protocol (IMAP) .

4A and 4B are diagrams illustrating a process in which the CS of the domain B informs the CF of the domain A of the session history in the communication system according to the first embodiment of the present invention.

Referring to FIGS. 4A and 4B, the client A 400 of the domain A transmits an INVITE message to the CS A 410 to create a one-to-one session with the client B 460 of the domain B (step 401). The CS A 410 transmits the INVITE message received to the CS B 450 of the domain B (step 403). The CS B 450 transmits the INVITE message received by the client B 460 (step 405). The client B 460 transmits a 200 OK message to the CS B 450 in response to the received INVITE message (step 407). The CS B 450 transmits the 200 OK message received by the CS A 410 (step 409). The CS A 410 transmits the 200 OK message received by the client A 400 (step 411). A one-to-one session is created between the client A 400 and the client B 460 through steps 401 through 411.

The client A 400 transmits and receives an INVITE w / replaces message and a 200 OK message to the CS A 410 and the CF A 420 to change the one-to-one session with the client B 460 to a group session 413 Step 419).

The CF A 420 transmits a MESSAGE message to the CS A 410 (step 421). The MESSAGE message requests a one-to-one session history, and has the following form.

MESSAGE sip: CPMServerA@home.net SIP / 2.0

Via: SIP / 2.0 / UDP cpmserver.home.net:5060

To: <sip: CPMServerA@home.net>

From: <sip: conference1@example.com>; tag = 2837302775

Call-ID: 563b4c76366712

CSeq: 2030485 MESSAGE

Contact: < sip: conference1 @ example.com >

Content-Length: XXX

Content-Type: application / OnetoOneSessionHistoryRequest + xml

<xml version = "1.0">

<OnetoOneSessionHistoryRequest version = "1.0">

<OnetoOneSessionID> </ OnetoOneSessionID>

<RequestDeviceID> </ RequestDeviceID>

</ OnetoOneSessionHistoryRequest>

Upon receiving the MESSAGE message, the CS A 410 transmits a 200 OK message to the CF A 420 indicating that it has received the MESSAGE message in step 423, To the CF A 420, a MESSAGE message indicating that the one-to-one session history management unit 450 manages the one-to-one session history (Step 425). The CF A 420 transmits a 200 OK message indicating that the MESSAGE message is received in step 425 to the CS A 410 in step 427. Here, the MESSAGE message in step 425 has the following form.

MESSAGE sip: conference1@example.com SIP / 2.0

Via: SIP / 2.0 / UDP cpmserver.home.net:5060

To: <sip: conference1@example.com>; tag = 2837302775

From: <sip: CPMServerA@home.net>; tag = 1928301774

Call-ID: 563b4c76366712

CSeq: 2030485 MESSAGE

Contact: < sip: CPMServerA@cs.home.net >

Content-Length: XXX

Content-Type: application / OnetoOneSessionHistoryResponse + xml

<xml version = "1.0">

<OnetoOneSessionHistoryResponse version = "1.0">

<OnetoOneSessionID> </ OnetoOneSessionID>

<GroupSessionID> </ GroupSessionID>

<HistoryManagementServerInfo>

<ServerType> </ ServerType>

<ServerAddr> </ ServerAddr>

                <CHFEnable> </ CHFEnable>

                <CHFID> </ CHFID>

        </ HistoryManagementServerInfo>

<MMSInfo>

<M & MSAddr> </ M & MSAddr>

<MailboxID> </ MailboxID>

</ MMSInfo>

</ OnetoOneSessionHistoryResponse>

The CF A 420 transmits and receives an INVITE w / replaces message and a 200 OK message to the CS A 410 and the CF A 420 to change the one-to-one session with the client B 460 to a group session 429 Step 435).

The CF A 420 transmits a MESSAGE message indicating a one-to-one session history request to the CS B 450, which is the subject of the session history management, in step 437. The type of the MESSAGE message used at this time is the same as the MESSAGE message used in step 421 above. However, only the difference is that 'To: <sip: CPMServerA@home.net>' corresponding to the destination address is changed to 'To: <sip: CPMServerB@home.net'.

That is, the OnetoOneSessionHistoryRequest of the Content-Type of the MESSAGE message used in steps 421 and 437 indicates a message requesting session history related information. The OnetoOne SessionID is specified in the body part of the MESSAGE message to display the identifier of the one-to-one session.

Upon receiving the MESSAGE message, the CS B 450 transmits a 200 OK message indicating that the MESSAGE message has been received to the CF A 420 in step 439. In addition, the CS B 450 transmits a MESSAGE message including the one-to-one session history to the CF A 420 (step 441). The type of the MESSAGE message used at this time is the same as the MESSAGE message used in step 425 above.

That is, the OnetoOneSessionHistoryResponse is displayed in the Content-Type of the MESSAGE message used in steps 425 and 441, indicating that the message is one-to-one session history related information. OnetoOneSessionID, GroupSessionID, HistoryManagementServerInfo, and M & MSInfo of the body part represent session history related information. The OnetoOneSessionID indicates the dialog information (i.e., the identifier information) of the existing one-to-one session, and the GroupSessionID indicates the dialog information of the group session. Displays the information of the server managing the session history and related information of the managing CPM CHF in HistoryManagemenServerInfo. Also, specify the type of server to be managed in ServerType. Specify 'ConversationServer' if the server is a CS or 'ControllingFunction' if it is a CF. Then, information of the SIP Uniform Resource Identifier (URI) of the server is displayed on the ServerAddr.

If you want to store the group session history on the server, specify "True" in CHFEnable. If the group session history is not stored and managed, "False" is specified in CHFEnable. Then, it sends the information of the managed server by specifying the unique ID of the Conversation History Function managing the group session history in the server. If the session history of the group session is managed by the M & MS A 430, the address of the corresponding M & MS A 430 and the mailbox address of the session history are specified in the M & MSAddr and the MailboxID, respectively. On the other hand, if the M & MS A 430 does not manage the session history of the group session, then null is specified.

Upon receiving the MESSAGE message, the CF A 420 transmits a 200 OK message to the CS B 450 indicating that the MESSAGE message has been received (step 435).

Thereafter, the CF A 420 transmits an INVITE w / replaces message to the CS C 470 to invite the client C 480 of the domain C to the group session (step 437). The CS C 470 having received the INVITE w / replaces message transmits the INVITE w / replaces message received by the client C 480 in step 439. The client C 480 transmits a 200 OK message to the CS C 470 in response to the INVITE w / replaces message, and the CS C 470 transmits the received 200 OK message to the CF A 420. (Steps 441 and 442). After step 443 is completed, a group session in which the clients A 400, B 460, and C 480 participate is created.

5 is a diagram illustrating a process in which a CS B transmits a group session history to a CF A in a communication system according to a second embodiment of the present invention.

5, in a state where a group session is created between the clients 500, 560 and 580 existing in the respective domains A, B and C, the client C 580 transmits a MESSAGE message to the CS C 570 Thereby requesting a group session history (step 501). The MESSAGE message used in the group session history request in step 501 has the following form.

MESSAGE sip: conference1@example.com SIP / 2.0

Via: SIP / 2.0 / UDP cpmserver.home.net:5060

To: < sip: CPMServerC@home.net >

From: <sip: CPM-ClientC@homeC.net>; tag = 19237234

Call-ID: 563b4c76366712

CSeq: 2030485 MESSAGE

Contact: <sip: CPM-ClientC@pc.homeC.net>

Content-Length: XXX

Content-Type: application / GroupSessionHistoryRequest + xml

<xml version = "1.0">

<GroupSessionHistoryRequest version = "1.0">

<GroupSessionID> </ GroupSessionID>

<RequestDeviceID> </ RequestDeviceID>

</ GroupSessionHistoryRequest>

The Content-Type ClientGroupSessionHistoryRequest of the MESSAGE message indicates that the MESSAGE message is a group session history transmission request message. In the body part, a GroupSessionID is specified to configure a subscriber's session history transmission request message. That is, the GroupSessionID corresponding to the identifier of the group session indicates the information of the group session by displaying the dialog information of the group session.

The CS C 570 transmits a 200 OK message indicating that the client C 580 recognizes the group session history request (step 503).

The CS C 570 requests the CF A 520 from the group session history (step 505). The CF A 520 transmits a 200 OK message indicating that the request is acknowledged to the CS C 570 (step 507). The CF A 520 knows that the CS B 550 manages the group session history through steps 429 through 435 of FIG. Accordingly, the CF A 520 transmits a MESSAGE message to the CS C 570 indicating that the CS B 550 manages the group session history (step 509). Here, the MESSAGE message in step 509 has the following form.

MESSAGE sip: CPMServerC@home.net SIP / 2.0

Via: SIP / 2.0 / UDP cpmserver.home.net:5060

To: <sip: CPMServerC@home.net>; tag = 19237234

From: <sip: conference1@example.com>; tag = 2837302775

Call-ID: 563b4c76366712

CSeq: 2030485 MESSAGE

Contact: < sip: conference1 @ example.com >

Content-Length: XXX

Content-Type: application / GroupSessionHistoryResponse + xml

<xml version = "1.0">

<GroupSessionHistoryResponse version = "1.0">

<OnetoOneSessionID> </ OnetoOneSessionID>

<GroupSessionID> </ GroupSessionID>

<HistoryManagementServerInfo>

<ServerType> </ ServerType>

<ServerAddr> </ ServerAddr>

                <CHFEnable> </ CHFEnable>

                <CHFID> </ CHFID>

        </ HistoryManagementServerInfo>

<MMSInfo>

<M & MSAddr> </ M & MSAddr>

<MailboxID> </ MailboxID>

</ MMSInfo>

</ GroupSessionHistoryResponse>

In step 511, the CS C 570 transmits a 200 OK message to the CF A 520 in response to the received MESSAGE message. Upon receiving the MESSAGE message in step 509, the CS C 570 recognizes that the group session history is stored in the M & MS B 540, and requests the group session history through the IMAP interface with the M & MS B 540 (Steps 513 to 519). At this time, the messages transmitted and received between the CS C 570 and the M & MS B 540 include an IMAP SELECT mailbix message, an IMAP OK SELECT message, an IMAP FETCH 1 body message, and an IMAP OK FETCH message in step 513.

The CS C 570 that has acquired the group session history transmits the group session history acquired using the MSRP protocol to the client C 580 (steps 521 to 525).

6 is a diagram illustrating a process in which a client C obtains a group session history in a communication system according to a third embodiment of the present invention.

Referring to FIG. 6, the client C 680 of the domain C transmits a MESSAGE message to the CS C 670 to request the group session history (step 601). The CS C 670 requests the CF A 620 for a group session history using the MESSAGE message (step 603). The CF A 620 transmits a 200 OK message indicating that the MESSAGE message has been received to the CS C 670 (step 605). The CS C 670 transmits a 200 OK message to the client C 680 indicating that the MESSAGE message has been received in step 601 (step 607).

Thereafter, the CF A 620 transmits a MESSAGE message to the CS C 670 (step 609). The MESSAGE message in step 609 includes access information for the CS B 650 and the M & MS B 640, which manage and store the group session history. The CS C 670 transmits access information on the group session history to the client C 680 using the MESSAGE message received from the CF A 620 in operation 611. The client C 680 transmits a 200 OK message indicating that the MESSAGE message has been received to the CS C 670 in step 613 and the CS C 670 transmits a 200 OK message to the CF A 620. [ (Step 615).

In step 617, the client C 680 transmits an AUTHENTICATE GSSAPI message to the M & MS B 640 in which the group session history is stored according to the acquired access information. The AUTHENTICATE GSSAPI message is a message necessary for the client C 680 to log into the M & MS B 640. The M & MS B 640 transmits an OK GSSAPI message to the client C 680 indicating that the client C 680 is logged in step 619. The client C 680 logged into the M & MS B 640 obtains the group session history from the M & MS B 640 (steps 621 through 627), similar to steps 513 through 519 of FIG.

7 is a diagram illustrating a process in which a client C obtains a group session history in a communication system according to a fourth embodiment of the present invention.

Referring to FIG. 7, since steps 701 to 707 are the same as steps 601 to 607 of FIG. 6, detailed description will be omitted.

The CF A 720 of the domain A requests the group session history using the MESSAGE message to the CS B 750 in step 709. The CS B 750 transmits a 200 OK message indicating that the MESSAGE message has been received to the CF A 720 in step 711. Here, the MESSAGE message in step 709 has the following form.

MESSAGE sip: conference1@example.com SIP / 2.0

Via: SIP / 2.0 / UDP cpmserver.home.net:5060

To: <sip: conference1@example.com>; tag = 2837302775

From: <sip: CPMServerB@home.net>; tag = 1852424756

Call-ID: 563b4c76366712

CSeq: 2030485 MESSAGE

Contact: < sip: CPM-ServerB@cs.homeB.net >

Content-Length: XXX

Content-Type: application / GroupSessionHistorySendRequest + xml

<xml version = "1.0">

<GroupSessionHistoryRequest version = "1.0">

<GroupSessionID> </ GroupSessionID>

<SendingDeviceID> </ SendingDeviceID>

</ GroupSessionHistoryRequest>

The Content-Type of the MESSAGE message indicates that the group session history is to be transmitted to a specific client by displaying the GroupSessionHistorySendRequest. The body part includes OnetoOneSessionID, GroupSessionID, and SendingDeviceID. The OnetoOne Session ID indicates dialog information of an existing one-to-one session. The GroupSessionID indicates information about the group session by displaying dialog information of the group session. Both OnetoOneSessionID and GroupSessionID can be used to fetch both session history or one-to-one session history and group session history. Also, by specifying the host information of the client C 780 of the domain C in the SendingDeviceID, the CF A 720 requests the client C 780 to transmit the session history managed by the CS 750 of the domain B to the client C 780.

The CS B 750 obtains the group session history by communicating using the IMAP protocol with the M & MS B 740 in which the group session history is stored (steps 713 to 719). Steps 713 through 719 are similar to steps 513 through 519 of FIG. The CS B 750 transmits the group session history acquired by the CF A 720 using the MSRP SEND message (step 721).

The CF A 720 transmits the group session history acquired from the CS B 750 to the CS C 770 using an MSRP SEND message (step 723). The CS C 770 transmits an MSRP SEND message including the group session history to the client C 780 (step 725). The client C 780 transmits an MSRP 200 OK message indicating that the MSRP SEND message has been received to the CS C 770 (step 727). The CS C 770 transmits an MSRP 200 OK message informing the CS A 710 that it has received the MSRP SEND message in step 723 (step 729). The CF A 720 transmits an MSRP 200 OK message indicating that the MSRP SEND message is received in step 721 to the CS B 750 in step 731.

Meanwhile, the client C 780 transmits an MSRP REPORT message indicating that the group session history has been acquired to the CS C 770 (step 733). The CS C 770 transmits the received MSRP REPORT message to the CF A 720 in step 735 and the CF A 720 transmits the received MSRP REPORT message to the CS B 750 (Step 737).

8A and 8B are diagrams illustrating a process in which a CS C transmits a group session history to a client C in a communication system according to a fifth embodiment of the present invention.

Referring to FIGS. 8A and 8B, the client C 880 requests the CS C 870 for a group session history using the MESSAGE message (step 801). The CS C 870 transmits a 200 OK message indicating that the MESSAGE message has been received to the client C 880 (step 803). The CS C 870 requests the CF A 820 for a group session history using the MESSAGE message (Step 805). The CF A 820 transmits a 200 OK message to the CS C 870 informing that the MESSAGE message in step 805 has been received (step 807).

The CFA 820 requests a group session history from the CS A 810 and receives a response thereto (steps 809 to 815). If the CS A 810 is managing the group session history information, it transmits a MESSAGE message including the group session history to the CF A 820. On the other hand, if the CS A 810 does not manage the group session history, a MESSAGE message containing no contents in the body part of the MESSAGE message or a MESSAGE message indicating the subject managing the group session history is transmitted to the CF A (820).

The CF A 820 transmits a MESSAGE message requesting the group session history to the CS B 850 managing the group session history (step 817). The CS B 850 transmits a 200 OK message indicating that the MESSAGE message is received in step 817 to the CF A 820 in step 819. In step 821, the CS B 850 transmits a MESSAGE message indicating that the group session history is stored in the M & MS B 840 in the CF A 820. The CF A 820 transmits a 200 OK message indicating that the MESSAGE message is received in step 821 to the CS B 850 (step 823). In addition, the CF A 820 transmits a MESSAGE message requesting the group session history to the CS C 870 (step 825). The CS C 870 transmits a 200 OK message indicating that the MESSAGE message is received in step 825 to the CF A 820 in step 827.

The CS C 870 then obtains a group session history by communicating with the M & MS B 840 using the IMAP protocol (steps 829 through 835). The CS C 870 that has acquired the group session history transmits the group session history acquired by the client C 880 using the MSRP protocol and receives a response thereto (steps 837 to 841).

9A and 9B are diagrams illustrating a process in which a client C obtains a group session history from an M & MS B in a communication system according to a sixth embodiment of the present invention.

Referring to FIGS. 9A and 9B, steps 901 to 907 are the same as steps 701 to 707 of FIG. 7, and steps 909 to 925 are the same as steps 809 to 825 of FIG. 8, .

The CS C 970 transmits access information for the M & MS B 940 in which the group session history is stored to the client C 980 using the MESSAGE message in step 927. The client C 980 transmits a 200 OK message to the CS C 970 in response to the MESSAGE message (step 929). The CS C 970 transmits a 200 OK message to the CF A 920 in response to the MESSAGE message in step 925 (step 931).

Thereafter, the client C 980 acquires a group session history by transmitting and receiving a series of messages with the M & MS B 940 (steps 933 through 943). Steps 933 through 943 are the same as steps 617 through 627 of FIG.

10A and 10B are views showing a process in which a client C acquires a group session history in a communication system according to a seventh embodiment of the present invention.

Referring to FIGS. 10A and 10B, since steps 1001 to 1023 are the same as steps 901 to 923 of FIG. 9, detailed description thereof will be omitted.

CF A 1020 causes the CS B 1050 to send a group session history to CF A 1020 by sending a MESSAGE message to CS B 1050 (step 1025). In step 1027, the CS B 1050 transmits a 200 OK message to the CF A 1010 in response to the MESSAGE message. Then, the CS B 1050 acquires a group session history by communicating with the M & MS B 1040 in which the group session history is stored using the IMAP protocol (steps 1029 to 1035).

The CS B 1050 transmits the acquired group session history to the CF A 1020 using an MSRP SEND message (step 1037). The CF A 1020 transmits the group session history acquired from the CS B 1050 to the CS C 1070 (step 1039). The CS C 1070 transmits an MSRP SEND message including the group session history to the client C 1080 (step 1041). The client C 1080 transmits an MSRP 200 OK message to the CS C 1070 in response to the MSRP SEND message in step 1041 (step 1043). In step 1045, the CS C 1070 transmits an MSRP 200 OK message to the CF A 1020 in response to the MSRP SEND message received in step 1039.

In step 1047, the CF A 1020 transmits an MSRP 200 OK message to the CS B 1050 in response to the MSRP SEND message in step 1037. Meanwhile, the client C 1080 transmits an MSRP REPORT message indicating that the group session history has been acquired to the CS C 1070 (step 1049). The CS C 1070 transmits an MSRP REPORT message received from the client C 1080 to the CF A 1020 in step 1051. The CF A 1020 transmits the received MSRP REPORT message to the CS B 1020 (Step 1053).

11A and 11B illustrate a process of transmitting a session history until a group session is created in a one-to-one session in a communication system according to an eighth embodiment of the present invention.

Referring to FIGS. 11A and 11B, a one-to-one session is created between the client A 1100 and the client B 1160. Then, the client A 1100 transmits an INVITE w / replaces message to the CS A 1110 to create a group session (step 1101). The CS A 1110 transmits and receives INVITE w / replaces and 200 OK messages to the CF A 1120 (steps 1103 and 1105). The CS A 1110 transmits a 200 OK message to the client A 1100 in response to the INVITE w / replaces in step 1101 (step 1107).

Thereafter, the CS A 1110 receives a MESSAGE message from the CF A 1120 (step 1109). The MESSAGE message has the following form.

MESSAGE sip: CPM-ClientA@example.com SIP / 2.0

Via: SIP / 2.0 / UDP cpmserver.home.net:5060

To: <sip: conference1@example.com>; tag = 2837302775

From: <sip: CPMServerA@home.net>; tag = 1928301774

Call-ID: 563b4c76366712

CSeq: 2030485 MESSAGE

Contact: < sip: conference1@example.com >

Content-Length: XXX

Content-Type: application / UserNotifiaction + xml

<xml version = "1.0">

<UserNotification version = "1.0">

<ManagementServerMsg> </ ManagementServerMsg>

</ UserNotifiaction>

The MESSAGE message is used in the following steps 1111, 1139, 1141, 1163, and 1165 as well. A UserNotification indicating that data to be exchanged for session history management is stored is displayed in the Content-Type of the MESSAGE. In the body part, ManagementServerMsg indicating that the CF A 1120 manages the session history is displayed.

The CS A 1110 transmits the MESSAGE message to the client A 1100 in step 1111 and receives the 200 OK message from the client A 1100 in step 1113. The CS A 1110 receives a 200 OK message in response to the MESSAGE message in step 1109 (step 1115).

Thereafter, the CF A 1120 obtains a session history by communicating with the CS A 1110 (steps 1117 to 1129). The CF A 1120 that has acquired the session history acquires the session history from the CS B 1150 through a series of processes and generates a group session with the client B 1160 and the C 1180 (steps 1131 to 1169 step).

12 is a diagram illustrating a process in which a CF A, which manages session history according to a ninth embodiment of the present invention, transmits a session history to a client C.

Referring to FIG. 12, the client C 1280 transmits a MESSAGE message requesting the group session history to the CS C 1270 (step 1201). The CS C 1270 transmits the MESSAGE message to the CF A 1220 (step 1203). The CFA 1220 transmits a 200 OK message indicating that the MESSAGE message has been received to the CS C 1270 (Step 1205). The CS C 1270 transmits the 200 OK message to the client C 1280 (step 1207).

The CFA 1220 obtains the group session history by communicating with the M & MS B 1240 (steps 1209-1215). The CFA 1220 transmits the acquired group session history to the CS C 1270 using an MSRP SEND message (step 1217). The CS C 1270 transmits the group session history received by the client C 1280 and receives a response thereto (steps 1219 and 1221). In step 1223, the CS C 1270 transmits an MSRP 200 OK message to the CF A 1220 in response to the MSRP SEND message in step 1217. Thereafter, the client C 1280 notifies the CS C 1270 that it has acquired the group session history by transmitting an MSRP REPORT message (operation 1225). The CS C 1270 transmits the MSRP REPORT message to the CF A 1220 (step 1227).

While the present invention has been described in connection with what is presently considered to be practical exemplary embodiments, it is to be understood that the invention is not limited to the disclosed embodiments. Therefore, the scope of the present invention should not be limited by the illustrated embodiments, but should be determined by the scope of the appended claims and equivalents thereof.

400: Client A 410: CSA
420: CFA 430: M & MS A
440: M & MS B 450: CS B
460: Client B 470: CS C
480: Client C

Claims (13)

A method for receiving session history of a control function (CF) in a communication system,
Forming a one-to-one session between a client terminal belonging to the first domain and a client terminal belonging to the second domain;
Transmitting a first message requesting session history to a Conversation Server (CS) belonging to the first domain, the CF belonging to the first domain, in order to change the formed one-to-one session into a group session;
Receiving, by the CF, a second message identifying the device managing the session history from the CS belonging to the first domain if the CS belonging to the first domain does not have a session history;
Receiving, by the CF, a third message including access information for a CS belonging to the second domain holding the session history from a CS belonging to the first domain;
Sending, by the CF, a fourth message requesting the session history to a CS belonging to the second domain holding the session history, based on the access information;
Receiving, by the CF, a fifth message including the session history from a CS belonging to the second domain,
Each of the third message and the fifth message includes an address of a CS belonging to the first domain or a CS belonging to the second domain, a content-type indicating a response to a session history request, information on a one- Information about an identifier, and information about a server managing the session history,
The process of forming the one-to-
Transmitting an invitation message to a client terminal belonging to the first domain to a client terminal belonging to the second domain;
Receiving a response message in response to the transmitted invitation message from a client terminal belonging to the second domain.
A method for transmitting and receiving a group session history in a communication system in which a group session is created between at least two client terminals,
Receiving from a client terminal belonging to the first domain a first message requesting a group session history by a conversation server (CS) belonging to a first domain;
If the CS belonging to the first domain does not have the group session history, a second message identifying a device managing the session history is sent to a control function (CF) belonging to the first domain Transmitting;
Receiving a third message including access information on a storage area in which the group session history is stored from a CF belonging to a second domain;
The CS reading the group session history in the storage area based on the access information;
And transmitting, by the CS, the read group session history to the client terminal,
The third message includes an address of a CS belonging to the first domain or a CS belonging to the second domain, a content-type indicating a response to a session history request, information on a one-to-one session identifier, information on a group session identifier, A method of transmitting and receiving a group session history including information about a server managing session history.
3. The method of claim 2,
Wherein the protocol used to read the group session history is Internet Message Access Protocol (IMAP).
3. The method of claim 2,
Wherein the protocol used to transmit the group session history to a client terminal belonging to the first domain is a message session relay protocol (MSRP).
3. The method of claim 2,
Wherein the first message and the third message are MESSAGE messages based on SIP (Session Initiation Protocol).
3. The method of claim 2,
Wherein the CS further comprises transmitting a fourth message requesting the group session history to the CF belonging to the second domain.
The method according to claim 6,
Wherein the first message to the third message is a Session Initiation Protocol (SIP) -based MESSAGE message.
The method according to claim 6,
Wherein the CF belonging to the second domain and the CS belonging to the first domain transmit the group session history using a message based on MSRP (Message Session Relay Protocol) protocol.
3. The method of claim 2,
And informing that a client terminal belonging to the first domain has acquired a group session history with a CS belonging to the first domain.
A method for transmitting and receiving a group session history in a communication system in which a group session is created between at least two client terminals,
Receiving from a client terminal belonging to the first domain a first message requesting a group session history by a conversation server (CS) belonging to a first domain;
If the CS belonging to the first domain is managing the group session history, the CS responds to the first message by sending a requested session history to a control function (CF) belonging to the first domain, ;
If the CS belonging to the first domain does not manage the group session history, the CS belonging to the first domain identifies a device managing the group session history with a CF belonging to the first domain Transmitting;
Transmitting, by the CS belonging to the first domain, a third message requesting the group session history to a CF belonging to a second domain;
Wherein the CF belonging to the first domain receives the group session history from a CF belonging to the second domain, the CF belonging to the second domain obtains the group session history from a storage area in which the group session history is stored - and;
And transmitting, by a CS belonging to the first domain, the group session history to a client terminal belonging to the first domain,
In the process of receiving the group session history,
The CS includes an address of a CS belonging to the first domain or a CS belonging to the second domain, a content-type indicating a response to a session history request, information on a one-to-one session identifier, And receiving a fourth message including information on an identifier and information on a server managing the session history.
11. The method of claim 10,
Wherein the first message and the second message are MESSAGE messages based on SIP (Session Initiation Protocol).
11. The method of claim 10,
Wherein a CF belonging to the second domain obtains the group session history from the storage area using a message based on an IMAP (Internet Message Access Protocol) protocol.
11. The method of claim 10,
Wherein the CS of the first domain transmits the group session history using a message based on a Message Session Relay Protocol (MSRP) protocol.

Images