WO2010090465A2 - Procédé de réception et d'envoi d'historique de session dans un système de communication - Google Patents

Procédé de réception et d'envoi d'historique de session dans un système de communication Download PDF

Info

Publication number
WO2010090465A2
WO2010090465A2 PCT/KR2010/000697 KR2010000697W WO2010090465A2 WO 2010090465 A2 WO2010090465 A2 WO 2010090465A2 KR 2010000697 W KR2010000697 W KR 2010000697W WO 2010090465 A2 WO2010090465 A2 WO 2010090465A2
Authority
WO
WIPO (PCT)
Prior art keywords
message
domain
belonging
session history
group session
Prior art date
Application number
PCT/KR2010/000697
Other languages
English (en)
Korean (ko)
Other versions
WO2010090465A3 (fr
Inventor
박성진
이승용
이경탁
엄현상
Original Assignee
삼성전자 주식회사
서울대학교산학협력단
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 삼성전자 주식회사, 서울대학교산학협력단 filed Critical 삼성전자 주식회사
Priority to US13/148,234 priority Critical patent/US9444649B2/en
Priority to GB1115278.2A priority patent/GB2480203B/en
Publication of WO2010090465A2 publication Critical patent/WO2010090465A2/fr
Publication of WO2010090465A3 publication Critical patent/WO2010090465A3/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/1813—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast for computer conferences, e.g. chat rooms
    • H04L12/1831—Tracking arrangements for later retrieval, e.g. recording contents, participants activities or behavior, network status
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/21—Monitoring or handling of messages
    • H04L51/216—Handling conversation history, e.g. grouping of messages in sessions or threads
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/56—Unified messaging, e.g. interactions between e-mail, instant messaging or converged IP messaging [CPM]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1046—Call controllers; Call servers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1063—Application servers providing network services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1069—Session establishment or de-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1083—In-session procedures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H04L65/1104—Session initiation protocol [SIP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H04L65/403—Arrangements for multi-party communication, e.g. for conferences
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/535—Tracking the activity of the user

Definitions

  • the present invention relates to a communication system, and more particularly, to a method for transmitting and receiving session history in a communication system.
  • a terminal is being prepared to perform services that were only available in a wired environment in a wireless environment.
  • the services should be able to be provided in an all IP (Internet Protocol) based wired and wireless network.
  • IP Internet Protocol
  • OMA Open Mobile Alliance
  • CCM Converged IP Messaging
  • protocols used for providing integrated services include Session Initiation Protocol (SIP), Message Session Relay Protocol (MSRP), and Real Time Transfer Protocol (RTP). Protocol).
  • SIP Session Initiation Protocol
  • MSRP Message Session Relay Protocol
  • RTP Real Time Transfer Protocol
  • SIP is defined in the IETF Request for Comment (RFC) 3261 document, and application level signaling for establishing, modifying and terminating sessions for multimedia communication such as video and voice.
  • the SIP transmits and receives messages in a request / response manner by using a protocol existing on a user datagram protocol (UDP) / transmission control protocol (TCP) / IP layer.
  • the SIP-based request message may include an invite (INVITE: invite to attend session), an ACK (ACK: approve the invitation request), a buy (BYE: end session), and a register (REGISTER: user) as defined in RFC 3261.
  • the SIP-based response messages include 1xx (information response), 2xx (successful response), 3xx (redirect response), 4xx (client error), 5xx (server error), and 6xx (global error) as status codes. .
  • the MSRP is a standard defined in the IETF RFC 4975 document and is used to transmit text data in a session.
  • the MSRP is designed to compensate for the disadvantage that the existing text data transmission method using the SIP-based MESSAGE message does not consider any relations between the messages, and the message of SEND (message transmission) and REPORT (message transmission confirmation) Is present.
  • FIG. 1 is a diagram illustrating a structure of a general CPM system.
  • the CPM system includes a CPM Client 100, a CPM Conversation Server (hereinafter referred to as CS) 110, and a CPM Controlling Function (CF). 120, application control function 130, interworking selection function 140, interworking function 150, messages and media Message and Media Storage Client 160 and Message and Media Storage Server (hereinafter referred to as M & MS) 170.
  • the M & MS 170 may exist as a separate component or may exist in a form included in the CS 110.
  • the CPM Client 100 is a service requester, creates a session with another CPM Client and receives a service through the CS 110.
  • the M & MS 170 stores data transmitted and received through a session created between CPM clients. Whether the CPM session data is stored is determined by a user preference and a service provider policy.
  • the CF 120 creates and manages a session between the CPM Client 100 and the CS 110. That is, the CF 120 generates a session between the CPM Client 100 and the CS 110 and the CF 120 of the corresponding user domain when the group session is created. 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. In this case, the domain is divided by a service provider.
  • the session history is managed by a CPM Conversation History Function (not shown) in the CS 110 and may be stored in the M & MS 170 or the CPM Conversation History function in the CS 110. have.
  • the session history of the current one-to-one session is managed by 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 the CS 110.
  • the session history of the one-to-one session may be managed separately for each CS of the domain, and may not be stored by user preference and service provider policy.
  • U.S. Patent Application Publication No. US 20070100908 'Method and apparatus for tracking history information of a group session' discloses the tracking of histo information about the group session.
  • session history tracking of the group in the jain must be preceded by group selection.
  • the jain does not describe the details of the process of creating a group session and the process of sending and receiving a session history.
  • the present invention proposes a specific method for generating a session history in a communication system and managing and transmitting the generated session history.
  • CF control function
  • CS conversation server
  • a client belonging to the first domain is connected to a chat server (CS) belonging to the same domain.
  • CS chat server
  • Transmitting a first message requesting a history, and the CS receiving the first message communicates with a control function (CF) belonging to a second domain in a memory in which the group session history is stored from the CF.
  • a method of transmitting and receiving a group session history in a communication system in which a group session is created between at least two clients, a method of transmitting and receiving a group session history, wherein a client belonging to the first domain is connected to a chat server (CS) belonging to the same domain. Transmitting a first message requesting a history, and the CS receiving the first message communicates with a control function (CF) belonging to a second domain in a memory in which the group session history is stored from the CF. Receiving a second message including access information about the client; transmitting, by the CS, the acquired access information to a client belonging to the first domain; and receiving a access information from the client belonging to the first domain And reading the group session history from the memory by using the received access information.
  • CS chat server
  • a fourth method of the present invention is 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 or more clients, wherein a client belonging to the first domain is connected to a chat server (CS) belonging to the same domain. Transmitting a first message requesting a history; and a CS belonging to the first domain receiving the first message requests a group session history to a control function unit belonging to a second domain. Transmitting a third message for requesting the group session history to a CS belonging to a third domain, and transmitting the third message to the CS belonging to a third domain from a memory in which the group session history is stored.
  • CS chat server
  • the CF belonging to the second domain receives the group session history, 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.
  • clients belonging to the first domain may be grouped to a chat server (CS) belonging to the same domain. Transmitting a first message requesting a session history; and a CS belonging to the first domain receiving the first message requests a group session history to a control function unit belonging to a second domain.
  • CS chat server
  • the CF belonging to the process of transmitting the message and the second domain receiving the second message acquires access information of the CS belonging to the third domain managing the memory in which the group session history is stored, and the third Receiving access information about the memory in which the group session history is stored from the CS belonging to the domain, and the CF belonging to the second domain Transmitting the acquired access information to the CS belonging to the first domain, and the CS belonging to the first domain receives the access information, and obtains the group session history from the memory using the received access information. And transmitting the obtained group session history to a client belonging to the first domain.
  • a sixth method of the present invention in a communication system in which a group session is created between at least two or more clients, in the group session history transmission / reception method, clients belonging to the first domain are grouped to a chat server (CS) belonging to the same domain. Transmitting a first message requesting a session history; and a CS belonging to the first domain receiving the first message requests a group session history to a control function unit belonging to a second domain.
  • CS chat server
  • the CF belonging to the process of transmitting the message and the second domain receiving the second message acquires access information of the CS belonging to the third domain managing the memory in which the group session history is stored, and the third Receiving access information about the memory in which the group session history is stored from the CS belonging to the domain, and the CF belonging to the second domain Transmitting previously obtained access information to a CS belonging to the first domain, and 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 receiving, by the client, belonging to the first domain, and obtaining the group session history from the memory by using the received access information.
  • a seventh method of the present invention in a communication system in which a group session is created between at least two or more clients, in the group session history transmission / reception method, clients belonging to the first domain are grouped to a chat server (CS) belonging to the same domain. Transmitting a first message requesting a session history; and a CS belonging to the first domain receiving the first message requests a group session history to a control function unit belonging to a second domain. Transmitting a message, and receiving the second message, the CF belonging to the second domain may request the group session history to the CS belonging to a third domain managing a memory in which the group session history is stored.
  • CS chat server
  • Transmitting the message, and the CS belonging to the third domain receiving the third message obtains the group session history from the memory And transmitting the obtained group session history to the CF belonging to the second domain, and the CF belonging to the second domain receives the group session history from the CS belonging to the third domain, and receives the received group session history.
  • Is transmitted to the CS belonging to the first domain, and the CS belonging to the first domain includes receiving the group session history and transmitting the received group session history to the client belonging to the same domain. .
  • clients belonging to the first domain are grouped to a chat server (CS) belonging to the same domain.
  • CS chat server
  • the CF belonging to the second domain after transmitting the message and transmitting the second message acquires the group session history from a memory in which the group session history is stored, and obtains the obtained group session history to the first domain.
  • Transmitting to the belonging CS, and the CS belonging to the first domain receives the group session history and receives the received group session. Transmitting a history to a client belonging to the first domain.
  • the present invention has an advantage of providing an improved service in data communication between users by providing a specific method for efficiently transmitting and receiving session history in a communication system.
  • FIG. 2 is a diagram illustrating a communication system structure when a CS manages session history in the present invention.
  • FIG. 3 is a diagram illustrating a communication system structure when a CF manages session history in the present invention.
  • FIG. 4 and 5 illustrate a process in which a CS of a domain B informs a CF of a domain A of session history in a communication system according to a first embodiment of the present invention
  • FIG. 6 is a diagram illustrating a process in which a CS B transmits a group session history to CF A in a communication system according to a second embodiment of the present invention.
  • FIG. 7 is a diagram illustrating a process in which a client C acquires a group session history in a communication system according to a third embodiment of the present invention.
  • FIG. 8 is a diagram illustrating a process of acquiring group session history by client C in a communication system according to a fourth embodiment of the present invention.
  • FIGS. 9 and 10 illustrate 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.
  • 11 and 12 illustrate 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.
  • FIG. 13 and 14 illustrate 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.
  • 15 and 16 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.
  • FIG. 17 illustrates a process in which CF A managing session history transmits session history to client C according to the ninth embodiment of the present invention.
  • the present invention proposes a specific method for generating a session history in a communication system and managing and transmitting and receiving the generated session history.
  • the present invention will be divided into a case of managing the session history in the CS and the case of managing in the CF will be described.
  • the session history includes both one-to-one session history and group session history.
  • FIG. 2 is a diagram illustrating a system structure when a CS manages session history in the present invention.
  • Client A 212 in Domain A and Client B 222 in Domain B create a one-to-one session and have a conversation
  • Client C in Domain C 232 is requested by Client A 212.
  • each client 212, 232 in domains A and C requests and receives the group session history directly or via a different path from the CS 221 in domain B to know the group session history.
  • the group session history may be stored in the CS 221 or the M & MS 223.
  • the CS 221 does not receive data related to the conversation transmitted and received in the group session, and thus cannot manage the group session history. do. In this case, there is a need to manage the group session history in the CF 200.
  • 3 illustrates a case where the CF 200 manages the group session history.
  • FIG. 3 is a diagram illustrating a system structure when a CF manages session history in the present invention.
  • the CF 300 should include a Conversation History Function (CHF) defined in CS, and the group session history through the M & MS 313 and the Internet Message Access Protocol (IMAP) interface. Can manage.
  • CHF Conversation History Function
  • IMAP Internet Message Access Protocol
  • 4 and 5 illustrate 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.
  • client A 400 in domain A transmits an INVITE message to CS A 410 to create a one-to-one session with client B 460 in 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 to 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 to the CS A 410 (step 409).
  • the CS A 410 transmits the 200 OK message received to the client A 400 (step 411).
  • Steps 401 to 411 generate a one-to-one session between the client A 400 and the client B 460.
  • the client A 400 transmits and receives an INVITE w / replaces message and a 200 OK message with the CS A 410 and the CF A 420 to change the one-to-one session with the client B 460 into a group session (413). Steps 419).
  • the CF A 420 transmits a MESSAGE message to the CS A 410 (step 421).
  • the MESSAGE message requests one-to-one session history, and has a form as follows.
  • the CS A 410 Upon receiving the MESSAGE message, the CS A 410 transmits a 200 OK message to the CF A 420 indicating that the MESSAGE message has been received (step 423), and then does not manage one-to-one session history.
  • a MESSAGE message indicating that 450 manages the one-to-one session history is transmitted to CF A 420 (step 425).
  • the CF A 420 transmits a 200 OK message indicating that the MESSAGE message has been received in step 425 to the CS A 410 (step 427).
  • the MESSAGE message in step 425 has a form as follows.
  • the CF A 420 transmits and receives an INVITE w / replaces message and a 200 OK message with the CS A 410 and the CF A 420 to change the one-to-one session with the client B 460 into 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 a session history management entity (step 437).
  • the MESSAGE message used in this case has the same form as the MESSAGE message used in step 421. The only difference is that 'To: ⁇ sip: CPMServerA@home.net>' corresponding to the destination address is changed to 'To: ⁇ sip: CPMServerB@home.net'.
  • the OnetoOneSessionHistoryRequest of Content-Type of the MESSAGE message used in steps 421 and 437 indicates that the message is for requesting session history related information.
  • OnetoOneSessionID is specified to indicate an identifier of a one-to-one session.
  • the CS B 450 Upon receiving the MESSAGE message, the CS B 450 transmits a 200 OK message to the CF A 420 indicating that the MESSAGE message has been received (step 439). In addition, the CS B 450 transmits a MESSAGE message including a one-to-one session history to the CF A 420 (step 441).
  • the MESSAGE message used in this case has the same form as the MESSAGE message used in step 425.
  • OnetoOneSessionHistoryResponse is displayed in the Content-Type of the MESSAGE message used in steps 425 and 441, indicating that the message transmits one-to-one session history related information.
  • OnetoOneSessionID, GroupSessionID, HistoryManagementServerInfo, and M & MSInfo of the body part represent session history related information.
  • OnetoOneSessionID displays dialog information (ie, identifier information) of an existing one-to-one session
  • GroupSessionID displays dialog information of a group session.
  • Information on the server that manages the session history and related information of the managed CPM CHF is displayed in HistoryManagemenServerInfo.
  • the type of server to be managed is specified in ServerType.
  • server CS In case of server CS, 'ConversationServer' is specified. In case of CF, 'ControllingFunction' is specified. In addition, information on the SIP Uniform Resource Identifier (URI) of the corresponding server is displayed in ServerAddr.
  • URI Uniform Resource Identifier
  • the server sends the information of the managed server by specifying the unique ID of the Conversation History Function that manages the group session history. If the session history of the group session is managed by the M & MS A 430, the address of the M & MS A 430 and the mailbox address of the session history are specified in M & MSAddr and MailboxID, respectively. On the other hand, if the session history of the group session is not managed by the M & MS A 430, null is specified.
  • the CF A 420 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).
  • 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 transmits the received INVITE w / replaces message to the client C 480 (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 sends the received 200 OK message to the CF A 420.
  • Step 441 and 442 As the step 443 ends, a group session in which the client A 400, the B 460, and the C 480 participates is created.
  • FIG. 6 is a diagram illustrating a process in which a CS B transmits a group session history to CF A in a communication system according to a second embodiment of the present invention.
  • step 501 a group session history is requested.
  • the MESSAGE message used for the group session history request in step 501 has a form as follows.
  • ClientGroupSessionHistoryRequest of Content-Type of the MESSAGE message indicates that the MESSAGE message is a group session history transfer request message.
  • the GroupSessionID is specified to configure the subscriber's session history transmission request message. That is, GroupSessionID corresponding to the identifier of the group session indicates the group session information by displaying the dialog information of the group session.
  • the CS C 570 transmits a 200 OK message to the client C 580 indicating that the group session history request has been acknowledged (step 503).
  • the CS C 570 requests the CF A 520 for the group session history (step 505).
  • the CF A 520 transmits a 200 OK message to the CS C 570 indicating that the request has been acknowledged (step 507).
  • the CF A 520 knows that the CS B 550 manages the group session history through steps 429 to 435 of FIG. 6. 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).
  • the MESSAGE message in step 509 has the following form.
  • the CS C 570 transmits a 200 OK message to the CF A 520 in response to the received MESSAGE message (step 511).
  • the CS C 570 Upon receipt of 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. And receive (steps 513 to 519).
  • 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 having obtained the group session history transmits the group session history acquired using the MSRP protocol to the client C 580 (steps 521 to 525).
  • FIG. 7 is a diagram illustrating a process in which a client C acquires a group session history in a communication system according to a third embodiment of the present invention.
  • client C 680 of domain C transmits a MESSAGE message to CS C 670 to request group session history (step 601).
  • the CS C 670 requests the group session history from the CF A 620 using the MESSAGE message (step 603).
  • the CF A 620 transmits a 200 OK message to the CS C 670 indicating that the MESSAGE message has been received (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).
  • 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 that manage and store the group session history.
  • the CS C 670 transmits access information about the group session history to the client C 680 using the MESSAGE message received from the CF A 620 (step 611).
  • the client C 680 transmits a 200 OK message indicating that the MESSAGE message has been received to the CS C 670 (step 613), and the CS C 670 also sends a 200 OK message to the CF A 620. (Step 615).
  • 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 obtained access information (step 617).
  • the AUTHENTICATE GSSAPI message is a message required for the client C 680 to log in to 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 in to the M & MS B 640 obtains a group session history from the M & MS B 640 similarly to steps 513 to 519 of FIG. 6 (steps 621 to 627).
  • FIG. 8 is a diagram illustrating a process of acquiring group session history by client C in a communication system according to a fourth embodiment of the present invention.
  • steps 701 to 707 are the same as steps 601 to 607 of FIG. 7, a detailed description thereof will be omitted.
  • the CF A 720 of the domain A requests the group session history to the CS B 750 using the MESSAGE message (step 709).
  • the CS B 750 transmits a 200 OK message indicating that the MESSAGE message has been received to the CF A 720 (step 711).
  • the MESSAGE message in step 709 has the following form.
  • the Content-Type of the MESSAGE message indicates GroupSessionHistorySendRequest to indicate that the group session history is transmitted to a specific client.
  • the body part contains OnetoOneSessionID, GroupSessionID, and SendingDeviceID.
  • the OnetoOneSessionID indicates dialog information of an existing one-to-one session.
  • GroupSessionID represents information about a group session by displaying dialog information of the group session.
  • OnetoOneSessionID and GroupSessionID can be used to get individual session history or both one-to-one session history and group session history.
  • the CF A 720 requests the client C 780 to transmit a session history managed by the CS 750 of domain B.
  • the CS B 750 acquires the group session history by communicating with the M & MS B 740 in which the group session history is stored using the IMAP protocol (steps 713 to 719). Steps 713 to 719 are similar to steps 513 to 519 of FIG. 6.
  • the CS B 750 transmits the group session history obtained to the CF A 720 using an MSRP SEND message (step 721).
  • the CF A 720 transmits the group session history obtained 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 to the CS C 770 indicating that the MSRP SEND message has been received (step 727).
  • the CS C 770 transmits an MSRP 200 OK message indicating that the MSRP SEND message is received in step 723 to the CS A 710 (step 729).
  • the CF A 720 transmits an MSRP 200 OK message to the CS B 750 indicating that the MSRP SEND message has been received in step 721 (step 731).
  • 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 (step 735), and the CF A 720 transmits the received MSRP REPORT message to the CS B 750. (Step 737).
  • FIGS. 9 and 10 illustrate 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.
  • the client C 880 requests the group session history to the CS C 870 using the MESSAGE message (step 801).
  • the CS C 870 transmits a 200 OK message to the client C 880 indicating that the MESSAGE message has been received (step 803).
  • the CS C 870 requests the group session history to the CF A 820 using the MESSAGE message (step 805).
  • the CF A 820 transmits a 200 OK message to the CS C 870 indicating that the MESSAGE message has been received in step 805 (step 807).
  • the CF A 820 requests the group session history to the CS A 810 and receives a response thereto (steps 809 to 815). If the CS A 810 manages group session history information, the CS A 810 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, the MESSAGE message containing no content in the body portion of the MESSAGE message or the MESSAGE message specifying the subject managing the group session history CF A Transmit to 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 has been received in step 817 to the CF A 820 (step 819).
  • the CS B 850 transmits a MESSAGE message indicating that the group session history is stored in the M & MS B 840 to the CF A 820 (step 821).
  • the CF A 820 transmits a 200 OK message to the CS B 850 indicating that the MESSAGE message has been received in step 821 (step 823).
  • 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 to the CF A 820 indicating that the MESSAGE message has been received in step 825 (step 827).
  • the CS C 870 acquires the group session history by communicating with the M & MS B 840 using the IMAP protocol (steps 829 to 835).
  • the CS C 870 acquiring the group session history transmits the group session history acquired to the client C 880 using the MSRP protocol and receives a response thereto (steps 837 to 841).
  • 11 and 12 illustrate a process in which a client C acquires a group session history from an M & MS B in a communication system according to a sixth embodiment of the present invention.
  • steps 901 to 907 are the same as steps 701 to 707 of FIG. 8, and steps 909 to 925 are the same as steps 809 to 825 of FIG. 9, and thus a detailed description thereof is omitted. Let's do it.
  • the CS C 970 transmits the access information about the M & MS B 940 in which the group session history is stored, to the client C 980 using the MESSAGE message (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).
  • Steps 933 to 943 are the same as steps 617 to 627 of FIG. 7.
  • FIG. 13 and 14 illustrate 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.
  • steps 1001 to 1023 are the same as steps 901 to 923 of FIG. 11, a detailed description thereof will be omitted.
  • the CF A 1020 transmits a MESSAGE message to the CS B 1050 so that the CS B 1050 transmits a group session history to the CF A 1020 (step 1025).
  • the CS B 1050 transmits a 200 OK message to the CF A 1010 in response to the MESSAGE message (step 1027).
  • the CS B 1050 acquires the group session history by communicating with the M & MS B 1040 having the group session history stored using the IMAP protocol (steps 1029 to 1035).
  • the CS B 1050 transmits the obtained group session history to the CF A 1020 using an MSRP SEND message (step 1037).
  • the CF A 1020 transmits the group session history obtained 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).
  • 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 (step 1045).
  • 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 (step 1047).
  • 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 the MSRP REPORT message received from the client C 1080 to the CF A 1020 (step 1051), and the CF A 1020 sends the received MSRP REPORT message to the CS B. Transmit to step 1050 (step 1053).
  • 15 and 16 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.
  • a one-to-one session is created between the client A 1100 and the client B 1160.
  • the client A 1100 then sends an INVITE w / replaces message to the CS A 1110 to create a group session (step 1101).
  • the CS A 1110 transmits and receives an INVITE w / replaces and 200 OK message with 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).
  • the CS A 1110 receives a MESSAGE message from the CF A 1120 (step 1109).
  • the MESSAGE message has the following form.
  • the MESSAGE message is subsequently used in steps 1111, 1139, 1141, 1163, and 1165.
  • a UserNotification indicating that data transmitted and received for managing session history is stored.
  • the body portion also displays ManagementServerMsg indicating that the CF A 1120 will manage session history.
  • the CS A 1110 transmits the MESSAGE message to the client A 1100 (step 1111), and receives a 200 OK message from the client A 1100 in response thereto (step 1113).
  • the CS A 1110 receives a 200 OK message in response to the MESSAGE message in step 1109 (step 1115).
  • the CF A 1120 acquires a session history by communicating with the CS A 1110 (steps 1117 to 1129).
  • the CF A 1120 acquiring the session history acquires the session history from the CS B 1150 through a series of processes, and creates a group session with the client B 1160 and the C 1180 (steps 1131 to 1169). step).
  • FIG. 17 is a diagram illustrating a process of CF A managing session history, transmitting session history to client C, according to the ninth embodiment of the present invention.
  • client C 1280 transmits a MESSAGE message requesting group session history to CS C 1270 (step 1201).
  • the CS C 1270 transmits the MESSAGE message to the CF A 1220 (step 1203).
  • the CF A 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 CF A 1220 acquires a group session history by communicating with the M & MS B 1240 (steps 1209 to 1215).
  • the CF A 1220 transmits the obtained 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 to the client C 1280 and receives a response thereto (steps 1219 and 1221).
  • 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 (step 1223).
  • the client C 1280 notifies that the group session history has been acquired by sending an MSRP REPORT message to the CS C 1270 (step 1225).
  • the CS C 1270 transmits the MSRP REPORT message to the CF A 1220 (step 1227).

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • General Engineering & Computer Science (AREA)
  • Telephonic Communication Services (AREA)
  • Computer And Data Communications (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne un système de communication. Un procédé de réception de l'historique de session d'une unité fonctionnelle de commande (fonction de commande: CF) comprend: un procédé dans lequel un CF appartenant à un premier domaine envoie un premier message de demande d'historique de session à un serveur de conversation (CS) appartenant au premier domaine; un procédé dans lequel, si le CS appartenant au premier domaine ne présente pas d'historique de session, un deuxième message contenant des informations d'accès relatives à un CS appartenant à un second domaine qui ne présente pas d'historique de session est reçu en provenance du CS appartenant au premier domaine; un procédé dans lequel un troisième message de demande d'historique de session est envoyé au CS appartenant au second domaine qui ne présente pas l'historique de session conformément aux informations d'accès; et un procédé dans lequel un quatrième message contenant l'historique de session est reçu en provenance du CS appartenant au second domaine.
PCT/KR2010/000697 2009-02-05 2010-02-04 Procédé de réception et d'envoi d'historique de session dans un système de communication WO2010090465A2 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US13/148,234 US9444649B2 (en) 2009-02-05 2010-02-04 Method for sending and receiving session history in a communications system
GB1115278.2A GB2480203B (en) 2009-02-05 2010-02-04 Method for sending and receiving session history in a communications system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR10-2009-0009376 2009-02-05
KR1020090009376A KR101773183B1 (ko) 2009-02-05 2009-02-05 통신 시스템에서 세션 히스토리 송수신 방법

Publications (2)

Publication Number Publication Date
WO2010090465A2 true WO2010090465A2 (fr) 2010-08-12
WO2010090465A3 WO2010090465A3 (fr) 2010-10-28

Family

ID=42542519

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2010/000697 WO2010090465A2 (fr) 2009-02-05 2010-02-04 Procédé de réception et d'envoi d'historique de session dans un système de communication

Country Status (4)

Country Link
US (1) US9444649B2 (fr)
KR (1) KR101773183B1 (fr)
GB (1) GB2480203B (fr)
WO (1) WO2010090465A2 (fr)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101581674B1 (ko) * 2009-05-15 2015-12-31 삼성전자주식회사 통합메시징 서비스 시스템에서 사용자의 요청에 따라 컨버세이션을 저장하기 위한 방법 및 그 시스템
KR101199401B1 (ko) * 2010-06-23 2012-11-09 엘지전자 주식회사 Ｃｐｍ 서비스 메시지의 전달 및 저장 방법 및 그 서버
US20150032828A1 (en) * 2013-07-26 2015-01-29 Blackberry Limited Friendly Names for Stored CPM Conversation Histories
US20190104402A1 (en) * 2017-10-03 2019-04-04 Motorola Solutions, Inc Managing access to group communication history for multiple services

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040015548A1 (en) * 2002-07-17 2004-01-22 Lee Jin Woo Method and system for displaying group chat sessions on wireless mobile terminals
KR20060026409A (ko) * 2003-05-16 2006-03-23 피카사 인코퍼레이티드 네트워크된 챗과 미디어 공유 시스템 및 방법
US20070100908A1 (en) * 2005-11-01 2007-05-03 Neeraj Jain Method and apparatus for tracking history information of a group session

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2000016209A1 (fr) * 1998-09-15 2000-03-23 Local2Me.Com, Inc. Correspondance dynamiquetm des utilisateurs pour la communication en groupe
US7441045B2 (en) * 1999-12-13 2008-10-21 F5 Networks, Inc. Method and system for balancing load distribution on a wide area network
US7360164B2 (en) * 2003-03-03 2008-04-15 Sap Ag Collaboration launchpad
US20140143852A1 (en) * 2008-08-21 2014-05-22 Ntrepid Corporation Secure network privacy system
US20050138137A1 (en) * 2003-12-19 2005-06-23 Microsoft Corporation Using parameterized URLs for retrieving resource content items
US8832247B2 (en) * 2006-03-24 2014-09-09 Blue Coat Systems, Inc. Methods and systems for caching content at multiple levels
US7984066B1 (en) * 2006-03-30 2011-07-19 Emc Corporation Mandatory access control list for managed content
JP4561671B2 (ja) * 2006-03-30 2010-10-13 株式会社日立製作所 データ通信方法およびシステム
CN101227418B (zh) * 2007-01-19 2012-04-04 华为技术有限公司 一种实现融合ip消息的方法、装置及系统
CN101282330B (zh) * 2007-04-04 2013-08-28 华为技术有限公司 网络存储访问权限管理方法及装置、网络存储访问控制方法
US8494520B2 (en) * 2007-07-20 2013-07-23 Bridgewater Systems Corp. Systems and methods for providing centralized subscriber session state information
WO2010082803A2 (fr) * 2009-01-19 2010-07-22 Lg Electronics Inc. Procédé pour délivrer un message sur la base d'un service cpm, et serveur correspondant

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040015548A1 (en) * 2002-07-17 2004-01-22 Lee Jin Woo Method and system for displaying group chat sessions on wireless mobile terminals
KR20060026409A (ko) * 2003-05-16 2006-03-23 피카사 인코퍼레이티드 네트워크된 챗과 미디어 공유 시스템 및 방법
US20070100908A1 (en) * 2005-11-01 2007-05-03 Neeraj Jain Method and apparatus for tracking history information of a group session

Also Published As

Publication number Publication date
US9444649B2 (en) 2016-09-13
GB201115278D0 (en) 2011-10-19
WO2010090465A3 (fr) 2010-10-28
GB2480203A (en) 2011-11-09
KR101773183B1 (ko) 2017-09-12
GB2480203A8 (en) 2013-07-31
KR20100090089A (ko) 2010-08-13
GB2480203B (en) 2013-11-27
US20110295965A1 (en) 2011-12-01

Similar Documents

Publication Publication Date Title
WO2016080808A1 (fr) Procédé et dispositif de partage d'informations enrichies associées à un appel
WO2010019022A2 (fr) Système et procédé d'émission et de réception d'un appel sur un réseau domestique
WO2014010992A1 (fr) Procédé de communication entre un demandeur de contenu et un fournisseur de contenu pour fournir un contenu et diffuser en continu, en temps réel, un contenu dans un réseau centré sur le contenu et basé sur un nom de contenu
WO2014107045A1 (fr) Procédé de partage de contenu au moyen d'un dispositif informatique en nuage personnel, dispositif électronique et système informatique en nuage personnel l'utilisant
WO2016047983A1 (fr) Procédé et dispositif pour une communication sans fil entre des terminaux de communication
WO2015046960A1 (fr) Procédé de délivrance d'un message de notification dans un système m2m et dispositifs associés
WO2016200145A1 (fr) Technique pour partager des informations de profil d'utilisateur dans un système de communication mobile
WO2011056034A2 (fr) Procédé de commande de session et serveur utilisant celui-ci
WO2010062139A2 (fr) Procédé et appareil pour commander une session d'interfonctionnement dans un service de messagerie ip convergent et système associé
WO2021167277A1 (fr) Dispositif et procédé pour fournir un service selon un type de réseau de communication sans fil dans un système informatique périphérique
WO2018066965A1 (fr) Procédé et appareil servant à transmettre un message de données critiques dans un système de communication
WO2017135787A1 (fr) Dispositif électronique permettant de prendre en charge un appel de profil et procédé d'appel de profil
JP2010124431A (ja) 呼制御装置、中継装置、呼制御方法及びコンピュータプログラム
WO2012124985A2 (fr) Procédé et appareil de synchronisation d'informations personnelles
WO2012030067A2 (fr) Système de communication, réseau à commutation de paquets, dispositif de contrôle de services supplémentaires et procédé de fourniture de services supplémentaires
WO2010064866A2 (fr) Procédé et système de fourniture de services iptv pour dispositifs fixes et mobiles
WO2010143903A2 (fr) Procédé et système pour conserver l'ordre de messages de type supports discrets dans une session cpm
WO2019156506A1 (fr) Système et procédé de fourniture de contenus conversationnels
WO2017082657A1 (fr) Procédé pour prendre en charge des appels vocaux dans un terminal de communication
WO2010090465A2 (fr) Procédé de réception et d'envoi d'historique de session dans un système de communication
WO2015041469A1 (fr) Procédé et système pour intégrer une visualisation de contenu et une communication dans une session de centre social immersif
WO2022075690A1 (fr) Systèmes et procédés pour la gestion d'un service stratégique dans un système de communication sans fil
US20070206745A1 (en) Communication system and transfer control method together with telphone device, communication device, and program used for same
WO2012099425A9 (fr) Procédé et système permettant d'obtenir une meilleure notification d'événement dans un environnement de réseau domestique de type prêt à l'emploi universel
WO2011002163A2 (fr) Procédé de transfert d'équipement inter-utilisateur

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 10738749

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 13148234

Country of ref document: US

ENP Entry into the national phase

Ref document number: 1115278

Country of ref document: GB

Kind code of ref document: A

Free format text: PCT FILING DATE = 20100204

WWE Wipo information: entry into national phase

Ref document number: 1115278.2

Country of ref document: GB

122 Ep: pct application non-entry in european phase

Ref document number: 10738749

Country of ref document: EP

Kind code of ref document: A2