Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TR 24.930  Word version:  17.0.0

Top   Top   None   None   Next
1…   5…

 

1  Scopep. 5

The present document 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.

2  Referencesp. 5

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
  • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
  • For a specific reference, subsequent revisions do not apply.
  • For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TS 24.229: "IP Multimedia Call Control Protocol based on SIP and SDP; Stage 3".
[2]
TS 24.228: Release 5: "Signalling flows for the IP multimedia call control based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP) - Stage 3".
[3]
TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".
[4]
RFC 3261:  "SIP: Session Initiation Protocol".
[5]
RFC 3312:  "Integration of Resource Management and Session Initiation Protocol (SIP)".
[6]
RFC 3262:  "Reliability of Provisional Responses in Session Initiation Protocol (SIP)".
[7]
RFC 3311:  "The Session Initiation Protocol (SIP) UPDATE Method".
[8]
RFC 3264:  "An Offer/Answer Model with Session Description Protocol (SDP)".
[9]
RFC 4032  (March 2005): "Update to the Session Initiation Protocol (SIP) Preconditions Framework".
[10]
draft-ietf-mmusic-sdp-capability-negotiation-08  (December 2007) "SDP Capability Negotiation".
Up

3  Definitions, symbols and abbreviationsp. 5

3.1  Definitionsp. 5

For the purposes of the present document, the [following] terms and definitions [given in ... and the following] apply.

3.2  Symbolsp. 5

For the purposes of the present document, the following symbols apply:

3.3  Abbreviationsp. 6

For the purposes of the present document, the following abbreviations apply:
AMR
Adaptive Multi-Rate
AS
Application Server
CN
Core Network
CSCF
Call Session Control Function
DSL
Digital Subscriber Line
FQDN
Fully Qualified Domain Name
HSS
Home Subscriber Server
HTTP
Hyper Text Transfer Protocol
I-CSCF
Interrogating CSCF
IM
IP Multimedia
IMS
IP Multimedia CN subsystem
IP
Internet Protocol
IP-CAN
IP-Connectivity Access Network
MGCF
Media Gateway Control Function
MRFC
Multimedia Resource Function Controller
MRFP
Multimedia Resource Function Processor
NGN
Next Generation Network
PCRF
Policy and Charging Rules Function
P-CSCF
Proxy CSCF
PSI
Public Service Identity
S-CSCF
Serving CSCF
SDP
Session Description Protocol
SIP
Session Initiation Protocol
UE
User Equipment
Up

4  Methodologyp. 6

4.1  Generalp. 6

The signalling flows provided in this document follow the methodology developed in TS 24.228. The following additional considerations apply:
  1. 3GPP 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 the present document;
  2. 3GPP 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".
Up

4.2  Key required to interpret signalling flowsp. 6

The key to interpret signalling flows specified in TS 24.228, subclause 4.1 applies.subclause 4.2 applies.
Each signalling flow table contains descriptions for headers where the content of the header is new to that signalling flow, as is already performed in TS 24.228.
However, TS 24.228 includes extensive descriptions for the contents of various headers following each of the tables representing the contents of the signalling flows. Where the operation of the header is identical to that shown in TS 24.228, then such text is not reproduced in the present document.
Additional text may also be found on the contents of headers within TS 24.228 in addition to the material shown in the present document.
In order to differentiate between messages for SIP and media, the notation in Figure 4.1-1 is used.
Copy of original 3GPP image for 3GPP TS 24.930, Fig. 4.1-1: Signalling flow notation
Figure 4.1-1: Signalling flow notation
(⇒ copy of original 3GPP image)
Up

Up   Top   ToC