Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.333  Word version:  18.1.0

Top   Top   Up   Prev   Next
1…   4   5…   5.8…   5.12…   5.14…   5.20…   5.24…   6…   6.1.8…   6.2…   6.2.3…   6.2.4…   6.2.5   6.2.6…   6.2.7…   6.2.8…   6.2.9…   6.2.10…   6.2.10.2.7   6.2.10.3…   6.2.11…   6.2.13…   6.2.13.2.6…   6.2.14…   6.2.15…   6.2.16…   6.2.18…   6.2.19…   6.2.19.3…   6.2.20…   6.2.21…   6.2.22…   6.2.23   6.2.24…   7   8…   8.11…   8.20   8.21   8.22   8.23…   8.30…   8.39…   8.45…   8.56… 
6.2.20 TCP bearer connection control  6.2.20.1 TCP connection establishment  6.2.20.2 TCP connection establishment Failure Indication 
...

 

6.2.20  TCP bearer connection control |R12|  p. 137

6.2.20.1  TCP connection establishment  p. 137

Figure 6.2.20.1.1 shows an example call flow for a MSRP session set-up procedure, where the UE wants to join a messaging conference.
Copy of original 3GPP image for 3GPP TS 23.333, Fig. 6.2.20.1.1: UE connecting into a messaging conference
Figure 6.2.20.1.1: UE connecting into a messaging conference
(⇒ copy of original 3GPP image)
Up
The IMS UE-A and the MRFC perform an IMS conference session set-up according to TS 23.228, TS 24.247 and TS 24.147. The procedure in the Figure 6.2.20.1.1 is described step-by-step with an emphasis on the additional aspects for the MRFC and the MRFP of the TCP connection establishment.
Step 1.
The IMS UE-A wants to join a messaging conference. For this purpose the IMS UE-A assigns a local TCP port number for the MSRP communication and builds an SDP offer containing the "a=setup:actpass" SDP attribute specified in RFC 4145.
The IMS UE-A sends the SIP INVITE request with the SDP offer.
Step 2. - 4.
Upon reception of the SIP INVITE request with the SDP offer containing a media stream that uses "TCP/MSRP" transport protocol, the MRFC uses the "Reserve And Configure IMS resources" procedure to request a termination for "TCP/MSRP" media. The MRFC provides an IP address and TCP port received from the IMS UE-A as part of a remote descriptor, requests the MRFP to allocate a local IP address and TCP port and includes a Notify TCP connection establishment Failure Event information element to request the MRFP to report an unsuccessful TCP connection set-up. In accordance to the information in the "a=setup" SDP attribute that will be sent in an SDP answer the MFRC requests the MRFP to start a TCP connection establishment.
Step 5.
The MRFP sends a TCP SYN message towards the IMS UE-A to establish a TCP connection. The IMS UE-A answers with a TCP SYN ACK message and the MRFP replies with a TCP ACK message, completing the TCP connection establishment.
Step 6.
The MRFC builds the SDP answer containing the "a=setup:active" SDP attribute and inserts the IP address and TCP port received from the MRFP.
Step 7.
The MRFC sends the 200 (OK) final response (or 18x provisional response) to the SIP INVITE request with the SDP answer for the MSRP session towards the IMS UE-A.
Up

6.2.20.2  TCP connection establishment Failure Indication  p. 139

The MRFP shall use a Notify TCP connection establishment Failure Indication procedure to report TCP connection establishment related failures.
The Figure 6.2.20.2.1 shows the message sequence chart example when the MRFP reports an unsuccessful TCP connection set-up to the MRFC.
Copy of original 3GPP image for 3GPP TS 23.333, Fig. 6.2.20.2.1: TCP connection establishment Failure Indication
Figure 6.2.20.2.1: TCP connection establishment Failure Indication
(⇒ copy of original 3GPP image)
Up

Up   Top   ToC