1、 ETSI TR 124 930 V15.0.0 (2018-06) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Signalling flows for the session setup in the IP Multimedia core network Subsystem (IMS) based on Session Initiation Protocol (SIP) and Session Desc
2、ription Protocol (SDP); Stage 3 (3GPP TR 24.930 version 15.0.0 Release 15) TECHNICAL REPORT ETSI ETSI TR 124 930 V15.0.0 (2018-06)13GPP TR 24.930 version 15.0.0 Release 15Reference RTR/TSGC-0124930vf00 Keywords GSM,LTE,UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +3
3、3 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 may be made available
4、 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 print, the only prev
5、ailing 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 of this and other ETS
6、I documents is available at https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx 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 or utilized
7、 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 extend to repro
8、duction in all media. ETSI 2018. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI registered for the benefit of its Members. 3GPPTM and LTETMare trademarks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. oneM2M logo i
9、s protected for the benefit of its Members. GSMand the GSM logo are trademarks registered and owned by the GSM Association. ETSI ETSI TR 124 930 V15.0.0 (2018-06)23GPP TR 24.930 version 15.0.0 Release 15Intellectual Property Rights Essential patents IPRs essential or potentially essential to normati
10、ve deliverables may 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
11、 respect of ETSI standards“, 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 existenc
12、e of other IPRs not 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. Trademarks The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners. ETSI claims
13、 no ownership of these except for any which are indicated as being the property of ETSI, and conveys no right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does not constitute an endorsement by ETSI of products, services or organizations asso
14、ciated with those trademarks. Foreword This Technical Report (TR) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as
15、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 verbs terminology In the present document “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ an
16、d “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 allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TR 124 930 V15.0.0 (2018-06)33GPP TR 24.930 version 15.0.0
17、 Release 15Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g31 Scope 5g32 References 5g33 Definitions, symbols and abbreviations . 5g33.1 Definitions 5g33.2 Symbols 5g33.3 Abbreviations . 6g34 Methodology 6g34.1 General . 6g34.2 Key required to interpret
18、 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 Introduction. 7g35.1.2 UE initiated IP-CAN bearer setup 7g35.1.2.1 Introduction . 7g35.1.2.2 SDP capability negotiation not supported by
19、 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-CAN bearer setup 49g35.2 Establishing a session when UE#1 does not have required resources available while UE#2 has resources already
20、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 when UE#1 has resources available while UE#2 does not have required resources available . 89g35.3.1 Introduction. 89g35.3.2 Signalling F
21、low (with SDP answer in 200 (OK) response for INVITE request) . 89g35.3.3 Signalling Flow (with SDP answer in reliable 180 Ringing) response . 95g35.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
22、 . 103g35.4 Establishing a session when UE#1 does not have required resources available and UE#2 is non-IMS . 112g35.4.1 Introduction. 112g35.4.2 Signalling Flow . 112g35.4.3 Signalling flow (preconditions used, SDP capability negotiation not supported by UE#1, 2nd SDP offer offering AVP transport f
23、or video) 117g35.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) 133g35.5 Establishing a session when UE#1 is non-IMS and UE#2 does not have required resources available . 141g35.5.1 Intro
24、duction. 141g35.5.2 Signalling Flow . 141g35.6 Establishing a session when UE#1 and UE#2 have resources already available 145g35.6.1 Introduction. 145g35.6.2 Signalling Flow (preconditions are not used) . 145g35.6.3 Signalling Flow (preconditions are used) . 149g3Annex A (informative): Change histor
25、y . 157g3History 159g3ETSI ETSI TR 124 930 V15.0.0 (2018-06)43GPP TR 24.930 version 15.0.0 Release 15Foreword This Technical Report has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change fol
26、lowing 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 and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented t
27、o 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 enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the do
28、cument. ETSI ETSI TR 124 930 V15.0.0 (2018-06)53GPP TR 24.930 version 15.0.0 Release 151 Scope 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 flow
29、s 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 sessions having certain features. 2 References The following documents contain provisions which, through reference in this text, consti
30、tute 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
31、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 3GPP TS 24.229: “IP Multimedia Call Control Protocol based on SIP and SDP; Stage 3“. 2 3GPP TS 24.228 Release
32、 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 Multimedia Subsystem (IMS); Stage 2“. 4 IETF RFC 3261: “SIP: Session Initiation Protocol“. 5 IETF RFC 3312: “Integration of Res
33、ource Management and Session Initiation Protocol (SIP)“. 6 IETF RFC 3262: “Reliability of Provisional Responses in Session Initiation Protocol (SIP)“. 7 IETF RFC 3311: “The Session Initiation Protocol (SIP) UPDATE Method“. 8 IETF RFC 3264: “An Offer/Answer Model with Session Description Protocol (SD
34、P)“. 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“. Editors note: The above document cannot be formally referenced until it is published as an RFC. 3
35、 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 Symbols For the purposes of the present document, the following symbols apply: ETSI ETSI TR 124 930 V15.0.0 (2018-06)63GPP TR
36、24.930 version 15.0.0 Release 153.3 Abbreviations For the purposes of the present document, the following abbreviations apply: AMR Adaptive Multi-Rate AS Application ServerCN Core NetworkCSCF Call Session Control Function DSL Digital Subscriber Line FQDN Fully Qualified Domain Name HSS Home Subscrib
37、er 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 Network MGCF Media Gateway Control Function MRFC Multimedia Resource Function Controller MRFP Multimedia Resource Function Processor
38、 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 4 Methodology 4.1 General The signalling flows provided in this document follow th
39、e 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 between networks, and with configuration hiding between networks. Separate signalling flows are not shown in the present docume
40、nt; 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. Therefore S-CSCFs and I-CSCFs are collapsed into a single entity labelled “Intermediate IM CN subsystem entities“. 4.2 Key required
41、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 descriptions for headers where the content of the header is new to that signalling flow, as is already performed in 3GPP TS 24.228 2.
42、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. 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 pres
43、ent 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 differentiate between messages for SIP and media, the notation in figure 4.1-1 is used. ETSI ETSI TR 124 930 V15.0.0 (2018-06)73GP
44、P TR 24.930 version 15.0.0 Release 15INVITESIP messageMedia over a PS connectionFigure 4.1-1: Signalling flow notation 5 Signalling flows for session initiation 5.1 Establishing a session when UE#1 and UE#2 do not have required resources available 5.1.1 Introduction The following flows show the esta
45、blishment 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 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
46、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 subsystem entities“ stands for the combination of I-CSCF/S-CSCF on the originating and on the terminating side. Routing of messa
47、ges 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 where UE#1 and UE#2 need to reserve local resources. In subclause 5.1.2.3 the SDP capability negotiations 10 mechanism is used a
48、nd 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 V15.0.0 (2018-06)83GPP TR 24.930 version 15.0.0 Release 15uni0049uni006Euni0074uni0065uni0072uni006Duni0065uni0064uni0069uni0061uni
49、0074uni0065uni0020uni0049uni004Duni0020uni0043uni004Euni0020uni0073uni0075uni0062uni0073uni0079uni0073uni0074uni0065uni006Duni0020uni0065uni006Euni0074uni0069uni0074uni0069uni0065uni0073uni0055uni0045uni0023uni0031uni0031uni002Euni0020uni0049uni004Euni0056uni0049uni0054uni0045uni0055uni0045uni0023uni0032uni0033uni002Euni0020uni0049uni004Euni0056uni0049uni0054uni0045uni0034uni002Euni0020uni0031uni0030uni0030uni002Euni0020uni0054uni0072uni0079uni0069uni006Euni0067uni0032uni0031uni002Euni0020uni0032uni0030uni0030uni0020uni004Funi004Bun
