TR 24.930
CT1
★
Signalling Flows
for the Session Setup in the IMS
based on SIP and SDP
use "3GPP‑Page" to get the Word version
use "ETSI‑search" to get the PDF version
for a better overview, the Table of Contents (ToC) is reproduced
use "ETSI‑search" to get the PDF version
for a better overview, the Table of Contents (ToC) is reproduced
V15.0.0 (PDF)
2018/06 160 p.
V14.0.0
2017/03 161 p.
V13.0.0
2015/12 162 p.
V12.1.0
2015/03 162 p.
V11.0.0
2012/09 169 p.
V10.1.0
2011/12 169 p.
V9.1.0
2011/12 169 p.
V8.3.0
2011/12 169 p.
V7.6.0
2011/12 155 p.
Rapporteur: Mr. Leis, Peter
This TR gives examples of the session setup in the IM CN subsystem based on SIP and SDP. These signalling flows provide detailed signalling flows, which expand on the overview information flows provided in TS 23.228. The flows focus on a basic session setup, i.e. no flows will be provided for topology hiding, for sessions with IBCF involved or for sessions having certain features.
The signalling flows provided in this TR follow the methodology developed in TS 24.228. The following additional considerations apply:
- TS 24.228 shows separate signalling flows with no configuration hiding between networks, and with configuration hiding between networks. Separate signalling flows are not shown in this TR;
- TS 24.228 breaks down the functionality of the various CSCFs. The functionality of the S-CSCF and I-CSCF is not relevant for the session setup procedure. Therefore S-CSCFs and I-CSCFs are collapsed into a single entity labelled "Intermediate IM CN subsystem entities".
full Table of Contents for TR 24.930 Word version: 15.0.0
1 Scope Word-p. 5
2 References
3 Definitions, symbols and abbreviations
4 Methodology
5 Signalling flows for session initiation Word-p. 7
5.1 Establishing a session when UE#1 and UE#2 do not have required resources available 
A Change history Word-p. 159
5.1.1 Introduction
5.1.2 UE initiated IP-CAN bearer setup
5.2 Establishing a session when UE#1 does not have required resources available while UE#2 has resources already available Word-p. 63
5.1.2.1 Introduction
5.1.2.2 SDP capability negotiation not supported by UE#1
5.1.2.3 SDP capability negotiation supported by UE#1 and UE#2 Word-p. 21
5.1.2.4 SDP capability negotiation only supported by UE#1 Word-p. 35
5.1.3 Network initiated IP-CAN bearer setup Word-p. 49
5.2.1 Introduction
5.2.2 Signalling flow with UPDATE request Word-p. 64
5.2.3 Signalling flow without UPDATE request Word-p. 77
5.3 Establishing a session when UE#1 has resources available while UE#2 does not have required resources available Word-p. 89
5.3.1 Introduction
5.3.2 Signalling Flow (with SDP answer in 200 (OK) response for INVITE request)
5.3.3 Signalling Flow (with SDP answer in reliable 180 Ringing) response Word-p. 96
5.3.4 Signalling Flow with SDP answer in reliable 183 Session Progress response for INVITE request when the IP-CAN performs resource reservation for UE#2 Word-p. 104
5.4 Establishing a session when UE#1 does not have required resources available and UE#2 is non-IMS Word-p. 113
5.4.1 Introduction
5.4.2 Signalling Flow
5.4.3 Signalling flow (preconditions used, SDP capability negotiation not supported by UE#1, 2nd SDP offer offering AVP transport for video) Word-p. 118
5.4.4 Signalling Flow (preconditions not supported by SIP UA#2, SDP capability negotiation not supported by UE#1, 2nd SDP offer offering AVP transport for video) Word-p. 134
5.5 Establishing a session when UE#1 is non-IMS and UE#2 does not have required resources available Word-p. 142
5.6 Establishing a session when UE#1 and UE#2 have resources already available Word-p. 146
