1、 ETSI TS 124 322 V15.0.0 (2018-06) Universal Mobile Telecommunications System (UMTS); LTE; Tunnelling of IP Multimedia Subsystem (IMS) services over restrictive access networks; Stage 3 (3GPP TS 24.322 version 15.0.0 Release 15) TECHNICAL SPECIFICATION ETSI ETSI TS 124 322 V15.0.0 (2018-06)13GPP TS
2、24.322 version 15.0.0 Release 15Reference RTS/TSGC-0124322vf00 Keywords LTE,UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - 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 Grass
3、e (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 in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified with
4、out 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 prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. Users of t
5、he 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 ETSI documents is available at https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your c
6、omment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI
7、. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. ETSI 2018. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI registered for the be
8、nefit of its Members. 3GPPTM and LTETMare trademarks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. oneM2M logo is protected for the benefit of its Members. GSMand the GSM logo are trademarks registered and owned by the GSM Association. ETSI ETSI TS 124 32
9、2 V15.0.0 (2018-06)23GPP TS 24.322 version 15.0.0 Release 15Intellectual Property Rights Essential patents IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI memb
10、ers 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 standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (https:/ipr.etsi
11、.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 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
12、 present document. Trademarks The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners. ETSI claims 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
13、 and/or tradename. Mention of those trademarks in the present document does not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks. Foreword This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). T
14、he present document may refer to technical specifications 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 un
15、der http:/webapp.etsi.org/key/queryform.asp. Modal verbs 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 expre
16、ssion of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 124 322 V15.0.0 (2018-06)33GPP TS 24.322 version 15.0.0 Release 15Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g31 Scope
17、 6g32 References 6g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 7g34 UE network protocols 7g34.1 General . 7g35 FTT-IMS protocol 8g35.1 General . 8g35.2 UE requested FTT-IMS establishment procedure 8g35.2.1 General 8g35.2.2 UE procedures 8g35.2.2.1 UE requested FTT-IM
18、S establishment procedure initiation 8g35.2.2.2 UE requested FTT-IMS establishment procedure initiation via restrictive non-3GPP access network type I . 8g35.2.2.3 UE requested FTT-IMS establishment procedure initiation via restrictive non-3GPP access network type II 8g35.2.2.4 UE requested FTT-IMS
19、establishment procedure accepted 8g35.2.3 EFTF procedures 8g35.3 IP packet transport FTT-IMS procedure 9g35.3.1 General 9g35.3.2 UE procedures 9g35.3.2.1 IP packet sending 9g35.3.2.2 IP packet receiving 9g35.3.3 EFTF procedures 9g35.3.3.1 IP packet sending 9g35.3.3.2 IP packet receiving 9g35.4 UE re
20、quested FTT-IMS release procedure . 10g35.4.1 General 10g35.4.2 UE procedures 10g35.4.3 EFTF procedures 10g35.5 EFTF requested FTT-IMS release procedure . 10g35.5.1 General 10g35.5.2 EFTF procedures 10g35.5.3 UE procedures 10g35.6 Procedure for unknown FTT-IMS envelope types . 10g35.6.1 General 10g3
21、5.6.2 UE procedures 10g35.6.3 EFTF procedures 10g36 IP roles and IP based procedures 10g36.1 General . 10g36.2 IP roles . 11g36.2.1 UE procedures 11g36.2.2 EFTF procedures 11g36.3 Inner IP address assignment procedure 11g36.3.1 UE procedures 11g36.3.2 EFTF procedures 11g37 PDUs and parameters . 12g3
22、ETSI ETSI TS 124 322 V15.0.0 (2018-06)43GPP TS 24.322 version 15.0.0 Release 157.1 PDUs and parameters specific to FTT-IMS protocol . 12g37.1.1 General 12g37.1.2 Message types of FTT-IMS messages 12g37.1.2.1 Generic FTT-IMS envelope 12g37.1.2.2 IP packet envelope 12g3Annex A (informative): Change hi
23、story . 14g3History 15g3ETSI ETSI TS 124 322 V15.0.0 (2018-06)53GPP TS 24.322 version 15.0.0 Release 15Foreword This Technical Specification 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 c
24、hange 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 and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 pr
25、esented 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 enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated
26、in the document. ETSI ETSI TS 124 322 V15.0.0 (2018-06)63GPP TS 24.322 version 15.0.0 Release 151 Scope The present document specifies procedures and protocol elements for tunnelling of IMS traffic over restrictive access networks, specifically procedures and protocol elements for establishing, main
27、taining, and sending traffic via a firewall traversal tunnel between the UE and an enhanced firewall traversal function (EFTF) in the network. The present document is applicable to UE and EFTF. The present document applies only to the case when the IMS traffic is not routed via EPC of a PLMN. Proced
28、ures for tunnelling of IMS traffic that is routed via EPC are specified in 3GPP TS 24.302 3 annex F. 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 p
29、ublication, 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
30、refers to the latest version of that document in the same Release as the present document. 1 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS 24.229: “IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3“. 3 3GP
31、P TS 24.302: “Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3“. 4 3GPP TS 33.203: “3G security; Access security for IP-based services“. 5 IETF RFC 791 (September 1981): “Internet Protocol“. 6 IETF RFC 2131 (March 1997): “Dynamic Host Configuration Protocol“. 7 IETF
32、 RFC 2460 (December 1998): “Internet Protocol, Version 6 (IPv6) Specification“. 8 IETF RFC 2817 (May 2000): “Upgrading to TLS Within HTTP/1.1“. 9 IETF RFC 3736 (April 2004): “Stateless Dynamic Host Configuration Protocol (DHCP) Service for IPv6“. 10 IETF RFC 4291 (February 2006): “IP Version 6 Addre
33、ssing Architecture“. 11 IETF RFC 4862 (September 2007): “IPv6 Stateless Address Autoconfiguration“. 12 Void. 13 Void. 14 3GPP TS 33.310: “Network Domain Security (NDS); Authentication Framework (AF)“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms
34、 and definitions given in 3GPP TR 21.905 1 and the following apply. ETSI ETSI TS 124 322 V15.0.0 (2018-06)73GPP TS 24.322 version 15.0.0 Release 15A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 1. Firewall traversal tunnel to I
35、P network of IMS: a TCP connection with TLS connection enabling passing of envelopes between UE in restrictive non-3GPP access network and EFTF, established in order to reach IP network of IP multimedia core network subsystem. For the purposes of the present document, the following terms and definit
36、ions given in 3GPP TS 24.229 2 apply: IP multimedia core network subsystem For the purposes of the present document, the following terms and definitions given in 3GPP TS 24.302 3 apply: Restrictive non-3GPP access network type I Restrictive non-3GPP access network type II Restrictive non-3GPP access
37、 network For the purposes of the present document, the following terms and definitions given in 3GPP TS 33.203 4 apply: Enhanced firewall traversal function 3.2 Abbreviations For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 1 and the following apply. An abbreviatio
38、n defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 1. EFTF Enhanced firewall traversal function FTT-IMS Firewall traversal tunnel to IP network of IMS HTTP Hypertext transfer protocol IMS IP multimedia core network subsystem TCP
39、 Transmission control protocol TLS Transport layer security URI Uniform resource identifier 4 UE network protocols 4.1 General In order to access to IMS via restrictive non-3GPP access network, the UE and the EFTF shall establish a firewall traversal tunnel to IP network of IMS (FTT-IMS) using the U
40、E requested FTT-IMS establishment procedure according to subclause 5.2. The UE and the EFTF shall send the IP packets using the IP packet transport FTT-IMS procedure according to subclause 5.3. The UE and the EFTF shall use the IP protocol according to clause 6. When FTT-IMS is no longer needed (e.g
41、. if the UE deregistered from IMS), the UE shall perform the UE requested FTT-IMS release procedure according to subclause 5.4. When FTT-IMS is no longer needed, the EFTF can perform the EFTF requested FTT-IMS release procedure according to subclause 5.5. NOTE: Keep-alive functionality is not define
42、d in this document. Keep-alive functionality defined in 3GPP TS 24.229 2 can be used to maintain the FTT-IMS between the UE and the EFTF. ETSI ETSI TS 124 322 V15.0.0 (2018-06)83GPP TS 24.322 version 15.0.0 Release 155 FTT-IMS protocol 5.1 General The FTT-IMS protocol consists of the UE requested FT
43、T-IMS establishment procedure, the IP packet transport FTT-IMS procedure, the UE requested FTT-IMS release procedure and the EFTF requested FTT-IMS release procedure. 5.2 UE requested FTT-IMS establishment procedure 5.2.1 General The purpose of the UE requested FTT-IMS establishment procedure is to
44、establish an FTT-IMS between the UE and the EFTF. 5.2.2 UE procedures 5.2.2.1 UE requested FTT-IMS establishment procedure initiation If the UE is not configured with an HTTP proxy address, the UE shall follow the procedures in subclause 5.2.2.2. If the UE is configured with an HTTP proxy address, t
45、he UE shall follow the procedures in subclause 5.2.2.3. NOTE: UE configuration of an HTTP proxy address is out of scope of 3GPP. 5.2.2.2 UE requested FTT-IMS establishment procedure initiation via restrictive non-3GPP access network type I In order to establish an FTT-IMS, the UE shall establish a T
46、CP connection to the EFTF address and destination port 443. If the TCP connection establishment is successful, the UE shall establish a TLS connection over the TCP connection according to the TLS profile specified in 3GPP TS 33.310 14 annex E. If the EFTF address is a FQDN, the UE shall include a TL
47、S extension of type “server_name“ in the TLS client hello message according to the TLS profile specified in 3GPP TS 33.310 14 annex E. 5.2.2.3 UE requested FTT-IMS establishment procedure initiation via restrictive non-3GPP access network type II If the UE is configured with HTTP proxy address, in o
48、rder to establish an FTT-IMS, the UE shall send HTTP CONNECT request to the HTTP proxy address according to IETF RFC 2817 8. The UE shall populate Request-URI of the HTTP CONNECT request with the EFTF address and port 443. Upon receiving HTTP 2xx response to HTTP CONNECT request, the UE shall establ
49、ish TLS connection according to the TLS profile specified in 3GPP TS 33.310 14 annex E over the TCP connection used for the HTTP CONNECT request transport. If the EFTF address is a FQDN, the UE shall include a TLS extension of type “server_name“ in the TLS client hello message according to the TLS profile specified in 3GPP TS 33.310 14 annex E. 5.2.2.4 UE requested FTT-IMS establishment procedure accepted When valid TLS Finished message is received over the TCP connection, the UE shall use the connection as the FTT-IM
