1、 ETSI TR 1Digital cellular telecoUniversal Mobile TelSignalling flows for the snetwork SuSession and Session(3GPP TR 24.9TECHNICAL REPORT 124 930 V13.0.0 (2016communications system (Phaelecommunications System (LTE; e session setup in the IP MultiSubsystem (IMS) based on n Initiation Protocol (SIP)
2、o Description Protocol (SDP)Stage 3 .930 version 13.0.0 Release 1316-01) hase 2+); (UMTS); ltimedia core P); 13) ETSI ETSI TR 124 930 V13.0.0 (2016-01)13GPP TR 24.930 version 13.0.0 Release 13Reference RTR/TSGC-0124930vd00 Keywords GSM,LTE,UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Ce
3、dex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The present document
4、may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in
5、 print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status
6、of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced
7、or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing restriction exte
8、nd to reproduction in all media. European Telecommunications Standards Institute 2016. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members
9、 and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TR 124 930 V13.0.0 (2016-01)23GPP TR 24.930 version 13.0.0 Release 13Intellectual Property Rights IPRs essential or potentially essential to the present document may
10、have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI sta
11、ndards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (https:/ipr.etsi.org/). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not
12、referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Report (TR) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifica
13、tions or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. Modal v
14、erbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT
15、allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TR 124 930 V13.0.0 (2016-01)33GPP TR 24.930 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g31 Scope 5g32 References 5g33 Definitions, symbols and abbre
16、viations . 5g33.1 Definitions 5g33.2 Symbols 5g33.3 Abbreviations . 6g34 Methodology 6g34.1 General . 6g34.2 Key required to interpret signalling flows 6g35 Signalling flows for session initiation 7g35.1 Establishing a session when UE#1 and UE#2 do not have required resources available . 7g35.1.1 In
17、troduction. 7g35.1.2 UE initiated IP-CAN bearer setup 7g35.1.2.1 Introduction . 7g35.1.2.2 SDP capability negotiation not supported by UE#1 7g35.1.2.3 SDP capability negotiation supported by UE#1 and UE#2 . 21g35.1.2.4 SDP capability negotiation only supported by UE#1 35g35.1.3 Network initiated IP-
18、CAN bearer setup 49g35.2 Establishing a session when UE#1 does not have required resources available while UE#2 has resources already available . 63g35.2.1 Introduction. 63g35.2.2 Signalling flow with UPDATE request 64g35.2.3 Signalling flow without UPDATE request . 77g35.3 Establishing a session wh
19、en UE#1 has resources available while UE#2 does not have required resources available . 89g35.3.1 Introduction. 89g35.3.2 Signalling Flow (with SDP answer in 200 (OK) response for INVITE request) . 89g35.3.3 Signalling Flow (with SDP answer in reliable 180 Ringing) response . 96g35.3.4 Signalling Fl
20、ow with SDP answer in reliable 183 Session Progress response for INVITE request when the IP-CAN performs resource reservation for UE#2 . 104g35.4 Establishing a session when UE#1 does not have required resources available and UE#2 is non-IMS . 113g35.4.1 Introduction. 113g35.4.2 Signalling Flow . 11
21、3g35.4.3 Signalling flow (preconditions used, SDP capability negotiation not supported by UE#1, 2nd SDP offer offering AVP transport for video) 118g35.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
22、for video) 134g35.5 Establishing a session when UE#1 is non-IMS and UE#2 does not have required resources available . 142g35.5.1 Introduction. 142g35.5.2 Signalling Flow . 142g35.6 Establishing a session when UE#1 and UE#2 have resources already available 146g35.6.1 Introduction. 146g35.6.2 Signalli
23、ng Flow (preconditions are not used) . 146g35.6.3 Signalling Flow (preconditions are used) . 150g3Annex A (informative): Change history . 159g3History 161 ETSI ETSI TR 124 930 V13.0.0 (2016-01)43GPP TR 24.930 version 13.0.0 Release 13Foreword This Technical Report has been produced by the 3rdGenerat
24、ion Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date an
25、d an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical e
26、nhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TR 124 930 V13.0.0 (2016-01)53GPP TR 24.930 version 13.0.0 Release 131 Scope The present document gives examples of the session setup in the IM CN su
27、bsystem based on SIP and SDP. These signalling flows provide detailed signalling flows, which expand on the overview information flows provided in 3GPP TS 23.228 2. 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 se
28、ssions having certain features. 2 References 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
29、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 pr
30、esent document. 1 3GPP TS 24.229: “IP Multimedia Call Control Protocol based on SIP and SDP; Stage 3“. 2 3GPP 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 3GPP TS 23.228: “IP
31、Multimedia Subsystem (IMS); Stage 2“. 4 IETF RFC 3261: “SIP: Session Initiation Protocol“. 5 IETF RFC 3312: “Integration of Resource Management and Session Initiation Protocol (SIP)“. 6 IETF RFC 3262: “Reliability of Provisional Responses in Session Initiation Protocol (SIP)“. 7 IETF RFC 3311: “The
32、Session Initiation Protocol (SIP) UPDATE Method“. 8 IETF 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):
33、“SDP Capability Negotiation“. Editors note: The above document cannot be formally referenced until it is published as an RFC. 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions given in . and the following apply. 3.2
34、 Symbols For the purposes of the present document, the following symbols apply: ETSI ETSI TR 124 930 V13.0.0 (2016-01)63GPP TR 24.930 version 13.0.0 Release 133.3 Abbreviations For the purposes of the present document, the following abbreviations apply: AMR Adaptive Multi-Rate AS Application ServerC
35、N Core NetworkCSCF 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 MultimediaIMS IP Multimedia CN subsystem IP Internet Protocol IP-CAN IP-Connectivity Access Netwo
36、rk 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 S
37、ession Initiation Protocol UE User Equipment 4 Methodology 4.1 General The signalling flows provided in this document follow the methodology developed in 3GPP TS 24.228 2. The following additional considerations apply: a) 3GPP TS 24.228 2 shows separate signalling flows with no configuration hiding
38、between networks, and with configuration hiding between networks. Separate signalling flows are not shown in the present document; b) 3GPP TS 24.228 2 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. There
39、fore S-CSCFs and I-CSCFs are collapsed into a single entity labelled “Intermediate IM CN subsystem entities“. 4.2 Key required to interpret signalling flows The key to interpret signalling flows specified in 3GPP TS 24.228 2 subclauses 4.1 and 4.2 applies. Each signalling flow table contains descrip
40、tions for headers where the content of the header is new to that signalling flow, as is already performed in 3GPP TS 24.228 2. However, 3GPP TS 24.228 3 includes extensive descriptions for the contents of various headers following each of the tables representing the contents of the signalling flows.
41、 Where the operation of the header is identical to that shown in 3GPP TS 24.228 2, then such text is not reproduced in the present document. Additional text may also be found on the contents of headers within 3GPP TS 24.228 2 in addition to the material shown in the present document. In order to dif
42、ferentiate between messages for SIP and media, the notation in figure 4.1-1 is used. ETSI ETSI TR 124 930 V13.0.0 (2016-01)73GPP TR 24.930 version 13.0.0 Release 13INVITESIP messageMedia over a PS connectionFigure 4.1-1: Signalling flow notation 5 Signalling flows for session initiation 5.1 Establis
43、hing a session when UE#1 and UE#2 do not have required resources available 5.1.1 Introduction The following flows show the establishment of a session where UE#1 and UE#2 do not yet have the required local resources available and need to perform resource reservation. In subclause 5.1.2 both UEs will
44、initiate the IP-CAN bearer setup. In subclause 5.1.3 the network will initiate the IP-CAN bearer setup for UE#1. It is assumed that both the originating UE and terminating UE are using a dedicated IP-CAN bearer for SIP signalling and a dedicated IP-CAN bearer for media. The box “Intermediate IM CN s
45、ubsystem entities“ stands for the combination of I-CSCF/S-CSCF on the originating and on the terminating side. Routing of messages between those nodes is not described in the flow below. 5.1.2 UE initiated IP-CAN bearer setup 5.1.2.1 Introduction This subclause shows the establishment of a session w
46、here UE#1 and UE#2 need to reserve local resources. In subclause 5.1.2.3 the SDP capability negotiations 10 mechanism is used and supported by both UE#1 and UE#2. In sublcause 5.1.2.4 only UE#1 supports the mechanism. 5.1.2.2 SDP capability negotiation not supported by UE#1 ETSI ETSI TR 124 930 V13.
47、0.0 (2016-01)83GPP TR 24.930 version 13.0.0 Release 13Figure 5.1.2.2-1: IMS session setup, resource reservation on both sides NOTE: Support for SDP capability negotiation is only optional for 3GPP release 7 and release 8 UEs and non-IMS UEs. The details of the signalling flows are as follows: 1. INV
48、ITE request (UE#1 to P-CSCF#1) see example in table 5.1.2.2-1 For this example, it is assumed that UE#1 is willing to establish a multimedia session comprising a video stream and an audio stream. The video stream supports two codecs, either H.263 or MPEG-4 Visual. The audio stream supports the AMR c
49、odec. For the video stream AVPF is offered and for the audio stream AVP is offered. ETSI ETSI TR 124 930 V13.0.0 (2016-01)93GPP TR 24.930 version 13.0.0 Release 13UE#1indicates that it supports precondition and it indicates that it supports reliable provisional responses. However, it does not use the “Require header for these capabilities. UE#1 does not have available the resources that are necessary to transport the media. UE#2 supports both AVP and AVPF and supports SDP capability negotiation and since only AVPF is being o
