1、 ETSI TR 1Minimum ReMCPTT Service(3GPP TR 24.9TECHNICAL REPORT 124 980 V13.0.1 (2016LTE; Requirements for support of e over the Gm reference poin.980 version 13.0.1 Release 1316-05) f oint 13) ETSI ETSI TR 124 980 V13.0.1 (2016-05)13GPP TR 24.980 version 13.0.1 Release 13Reference DTR/TSGC-0124980vd
2、01 Keywords LTE 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 Grasse (06) N 7803/88 Important notice The present document can be dow
3、nloaded 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 without the prior written authorization of ETSI. In case of any exist
4、ing 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 the present document should be aware that the document may be subj
5、ect to revision or change of status. Information on the current status 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/Comm
6、iteeSupportStaff.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. The content of the PDF version shall not be modified without the written
7、authorization of ETSI. The copyright and the foregoing restriction extend 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 an
8、d LTE are Trade Marks of ETSI registered for the benefit of its Members 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 980 V13.0.1 (2016-05)23GPP TR 24.980 version 13.0.1 Release 13Intellectual Property Righ
9、ts IPRs essential or potentially essential to the present document 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,
10、 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.org/). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by
11、 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 present document. Foreword This Technical Report (TR) has been produced by ETSI 3rd Generation Partnershi
12、p 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 being references to the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identit
13、ies can be found under 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
14、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 980 V13.0.1 (2016-05)33GPP TR 24.980 version 13.0.1 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Fo
15、reword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions, symbols and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 7g34 Support of generic functions over the Gm reference point 7g34.1 General . 7g34.1.1 MCPTT UE . 7g34.1.2 SIP core. 8g34.1.3 EPC. 8g34.2 Registration procedur
16、es 8g34.2.1 MCPTT UE . 8g34.2.2 SIP core . 8g34.3 Authentication procedures 8g34.3.1 MCPTT UE. 8g34.3.2 SIP core . 8g34.4 Session establishment procedures 8g34.4.1 General 8g34.5 Integration of resource management and SIP . 8g34.5.1 MCPTT UE . 8g34.5.1.1 Loss of PDN connectivity . 8g34.5.1.2 Loss of
17、 media bearer and Radio Connection . 9g34.5.2 SIP core. 9g34.5.2.1 Loss of PDN connectivity . 9g34.5.2.2 Loss of media bearer and Radio Connection . 9g35 RTP and SDP considerations to support MCPTT over the Gm reference point 9g35.1 General . 9g35.1.1 MCPTT UE . 9g35.1.2 SIP core. 9g35.2 Data transp
18、ort . 10g35.2.1 MCPTT UE . 10g35.2.2 SIP core. 10g35.3 RTCP usage 10g35.3.1 General 10g36 Bearer management 10g36.1 General . 10g36.1.1 MCPTT UE . 10g36.2 EPS bearer considerations for SIP signalling and MCPTT sessions 10g36.2.1 MCPTT UE . 10g36.2.2 EPS . 10g36.3 P-CSCF discovery 11g36.3.1 MCPTT UE
19、. 11g36.3.2 SIP core. 11g36.3.3 EPC. 11g37 Common functionalities . 11g3ETSI ETSI TR 124 980 V13.0.1 (2016-05)43GPP TR 24.980 version 13.0.1 Release 137.1 IP version 11g37.1.1 MCPTT UE . 11g37.1.2 SIP core. 12g3Annex A: Change history 13g3History 14g3ETSI ETSI TR 124 980 V13.0.1 (2016-05)53GPP TR 24
20、.980 version 13.0.1 Release 13Foreword 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 following formal TSG approval. Should the TSG modify the contents of the p
21、resent 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 to TSG for approval; 3 or greater indicates TSG approved document under
22、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 document. Introduction 3GPP TS 23.179 2 defines that the SIP-1 reference
23、point between the MCPTT UE and the SIP core uses the 3GPP Gm reference point (with necessary enhancements to support MCPTT requirements and profiled to meet the minimum requirements for support of MCPTT). 3GPP TS 24.229 4 and 3GPP TS 24.301 5 contain several options or alternatives for the MCPTT UE
24、and network for support of procedures on the Gm reference point in order to obtain IMS services. In order to ensure interoperability it is necessary to define recommendations that if adhered to by both MCPTT UE and network will ensure that the MCPTT UE can obtain access to the MCPTT service. The pre
25、sent document makes recommendations for the P-CSCF and S-CSCF entities defined in 3GPP TS 23.228 6, however if the SIP core for MCPTT does not internally comply with the architecture of 3GPP TS 23.228 6 these recommendations apply generically to whatever SIP core entity provides the equivalent funct
26、ionality to the P-CCSF and S-CSCF. The MCPTT UE and SIP core adhere to the procedures on the Gm reference point defined in 3GPP TS 24.229 4, 3GPP TS 24.301 5 and 3GPP TS 24.379 3. The present document cross-references and aligns with GSMA PRD IR.92 12, which profiles Voice and SMS over LTE (VoLTE).
27、ETSI ETSI TR 124 980 V13.0.1 (2016-05)63GPP TR 24.980 version 13.0.1 Release 131 Scope The present document describes a minimum IMS profile of the Gm reference point for SIP core implementation to guide interoperable implementation of MCPTT solutions. In order to support procedures over the SIP-1 re
28、ference point defined in 3GPP TS 23.179 2 and 3GPP TS 24.379 3, and which exists between the MCPTT UE Signaling User Agent and the SIP core for obtaining access to MCPTT service and supporting MCPTT sessions, the Gm reference point is profiled to meet the minimum requirements to support MCPTT. The G
29、m reference point contains many options which are not necessarily applicable for support of MCPTT or options which are alternative mechanisms (e.g. P-CSCF discovery) where if the same option is not supported by both the MCPTT UE and the network interoperability cannot be achieved. The present docume
30、nt describes the following: - Where options exist in 3GPP TS 24.229 4 related to provision of IMS based services over the Gm reference point, those options which need to be supported to ensure interoperable MCPTT service will be identified. - Where options exist in 3GPP TS 24.301 5 and stage 2 funct
31、ionality that are needed to provide MCPTT service over IMS, those options which need to be supported to ensure interoperable MCPTT service will be identified. - Where optional features of MCPTT are defined that require additional options on the Gm reference point to be supported, these options will
32、also be identified as recommended to be supported to ensure interoperability of the optional feature. The present document will only cover on-network unicast operation. The present document covers EPC aspects that are required by MCPTT to establish MCPTT sessions. 2 References The following document
33、s 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
34、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 3GPP TR 21.905: “Vocabulary for 3GPP Specif
35、ications“. 2 3GPP TS 23.179: “Functional architecture and information flows to support mission critical communication; Stage 2“. 3 3GPP TS 24.379: “Mission Critical Push To Talk (MCPTT) call control protocol specification“. 4 3GPP TS 24.229: “IP multimedia call control protocol based on Session Init
36、iation Protocol (SIP) and Session Description Protocol (SDP); Stage 3“. 5 3GPP TS 24.301: “Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3“. 6 3GPP TS 23.228: “IP Multimedia Subsystem (IMS); Stage 2“. 7 3GPP TS 33.203: “3G security; Access security for IP-based services“.
37、8 3GPP TS 26.114: “IP Multimedia Subsystem (IMS); Multimedia telephony; Media handling and interaction“. ETSI ETSI TR 124 980 V13.0.1 (2016-05)73GPP TR 24.980 version 13.0.1 Release 139 3GPP TS 23.203: “Policy and charging control architecture“. 10 3GPP TS 36.331: “Evolved Universal Terrestrial Radi
38、o Access (E-UTRA); Radio Resource Control (RRC); Protocol specification“. 11 3GPP TS 26.179: “Mission Critical Push To Talk; Codecs and media handling“. 12 GSMA PRD IR.92 (V9.0): “IMS Profile for Voice and SMS“ (http:/ 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the
39、present document, the terms and definitions given in 3GPP TR 21.905 1 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 1. MCPTT service: A Push To Talk communication service supporting applications for Mi
40、ssion Critical Organizations and mission critical applications for other businesses and organizations (e.g., utilities, railways) with fast setup times, high availability, reliability and priority handling. MCPTT related APN: An APN utilised by the MCPTT service including the MCPTT service APN for t
41、he SIP-1 reference point, an MC common core services APN for the HTTP-1 reference point and a MC identity management service APN for the CSC-1 reference point. MCPTT UE: A UE that enables an MCPTT user to participate in MCPTT service. 3.2 Abbreviations For the purposes of the present document, the a
42、bbreviations given in 3GPP TR 21.905 1 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 1. EPC Evolved Packet Core MCPTT Mission Critical Push To Talk over LTE P-CSCF Proxy Call Session C
43、ontrol Function UM Unacknowledged Mode 4 Support of generic functions over the Gm reference point 4.1 General 4.1.1 MCPTT UE All of the mandatory capabilities for an E-UTRAN capable UE and EPS defined in 3GPP TS 24.229 4 are assumed as a baseline to be supported by the MCPTT UE for this profile. All
44、 of the mandatory capabilities for the UE defined in 3GPP TS 24.301 5 are assumed as a baseline to be supported by the MCPTT UE for this profile. ETSI ETSI TR 124 980 V13.0.1 (2016-05)83GPP TR 24.980 version 13.0.1 Release 134.1.2 SIP core All the mandatory capabilities for the P-CSCF and S-CSCF for
45、 the messages sent and received on the Gm reference point defined in 3GPP TS 24.229 4 are assumed as a baseline to be supported for this profile. 4.1.3 EPC All the mandatory capabilities for the MME defined in 3GPP TS 24.301 5 are assumed as a baseline to be supported for this profile. 4.2 Registrat
46、ion procedures 4.2.1 MCPTT UE The MCPTT UE follows the SIP registration procedures defined in 3GPP TS 24.229 4. In addition, when the conditions for performing IMS registration in bullets 2, 3, 4, 5 and 6 in subclause L.3.1.2 of 3GPP TS 24.229 4 evaluate to true, the MCPTT UE registers with the IMS.
47、 4.2.2 SIP core The SIP core follows the SIP registration procedures defined in 3GPP TS 24.229 4. The SIP core supports network-initiated de-registration as defined in 3GPP TS 24.229 4. 4.3 Authentication procedures 4.3.1 MCPTT UE The MCPTT UE follows the procedures defined in 3GPP TS 24.229 4 and 3
48、GPP TS 33.203 7 for authentication with IMS Authentication and Key Agreement (IMS-AKA), Sec-Agree and IPSec. The MCPTT UE supports integrity protection. 4.3.2 SIP core The SIP core follows the procedures defined in 3GPP TS 24.229 4 and 3GPP TS 33.203 7 for authentication with IMS-AKA, Sec-Agree and
49、IPSec. The SIP core supports integrity protection. 4.4 Session establishment procedures 4.4.1 General Session establishment procedures are described in 3GPP TS 24.229 4 and 3GPP TS 24.379 3. 4.5 Integration of resource management and SIP 4.5.1 MCPTT UE 4.5.1.1 Loss of PDN connectivity In accordance with GSMA PRD IR.92 12 section 2.4.2.1, if the MCPTT UE discovers (for example during a TAU procedure) that PDN connectivity had been lo
