1、 ETSI TS 1Mission Critical Push TProt(3GPP TS 24.3TECHNICAL SPECIFICATION124 382 V13.0.1 (2016LTE; To Talk (MCPTT) identity manrotocol specification .382 version 13.0.1 Release 1316-05) anagement; 13) ETSI ETSI TS 124 382 V13.0.1 (2016-05)13GPP TS 24.382 version 13.0.1 Release 13Reference DTS/TSGC-0
2、124382vd01 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 ca
3、n 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 without the prior written authorization of ETSI. In case of a
4、ny 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 the present document should be aware that the document may
5、 be subject 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/Peo
6、ple/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. The content of the PDF version shall not be modified without the
7、written 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. 3
8、GPPTM and 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 TS 124 382 V13.0.1 (2016-05)23GPP TS 24.382 version 13.0.1 Release 13Intellectual Prope
9、rty Rights 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); Es
10、sential, 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 carrie
11、d 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 present document. Foreword This Technical Specification (TS) has been produced by ETSI 3rd Genera
12、tion 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 being references to the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP a
13、nd ETSI identities 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
14、 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 TS 124 382 V13.0.1 (2016-05)33GPP TS 24.382 version 13.0.1 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs te
15、rminology 2g3Foreword . 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 6g34 General . 6g34.1 Identity management 6g35 Entities 7g35.1 Identity management client 7g35.2 Identity management server . 7g35.3 MCPTT client . 7g35.4 HTTP proxy 7g36
16、 Authentication procedures 8g36.1 General . 8g36.2 Identity management client procedures 8g36.2.1 User authentication . 8g36.3 Identity management server procedures . 9g36.3.1 User authentication . 9g37 Inter/intra domain interface security 10g3Annex A (normative): HTTP entities . 11g3A.1 Scope 11g3
17、A.2 Procedures 11g3A.2.1 HTTP client 11g3A.2.1.1 General 11g3A.2.1.2 HTTP client in UE 11g3A.2.1.3 HTTP client in network entity 12g3A.2.2 HTTP proxy 12g3A.2.2.1 General 12g3A.2.2.2 HTTP request method from HTTP client in UE . 12g3A.2.2.3 HTTP request method from HTTP client in network entity within
18、 trust domain . 12g3A.2.3 HTTP server . 13g3Annex B (informative): Change history . 14g3History 15g3ETSI ETSI TS 124 382 V13.0.1 (2016-05)43GPP TS 24.382 version 13.0.1 Release 13Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of
19、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 and an increase in version number as follows: Vers
20、ion 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 enhancements, corrections, updates, etc. z the th
21、ird digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TS 124 382 V13.0.1 (2016-05)53GPP TS 24.382 version 13.0.1 Release 131 Scope This document specifies the identity management and authentication protocols needed to support Mission Critical Push To
22、Talk (MCPTT). Identity management applies only to on-network operation. Mission critical communication services are services that require preferential handling compared to normal telecommunication services, e.g. in support of police or fire brigade. The MCPTT service can be used for public safety ap
23、plications and also for general commercial applications (e.g., utility companies and railways). This document is applicable to User Equipment (UE) supporting the identity management client functionality, and to application servers supporting the identity management server functionality. 2 References
24、 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 revisio
25、ns 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 3GPP TR 21.905: “Voc
26、abulary for 3GPP Specifications“. 2 3GPP TS 33.179: “Security of Mission Critical Push-To-Talk (MCPTT)“. 3 3GPP TS 22.179: “Mission Critical Push To Talk (MCPTT) over LTE“. 4 IETF RFC 2616: “Hypertext Transfer Protocol - HTTP/1.1“. 5 IETF RFC 6749: “The OAuth 2.0 Authorization Framework“. 6 “OpenID
27、Connect Core 1.0 incorporating errata set 1“. 7 W3C.REC-html401-19991224: “HTML 4.01 Specification. 8 3GPP TS 23.179: “Functional architecture and information flows to support mission critical communication services“. 9 3GPP TS 23.179: “Functional architecture and information flows to support missio
28、n critical communication services; Stage 2“. 10 IETF RFC 2818: “HTTP Over TLS“. 11 3GPP TS 24.383: “Mission Critical Push To Talk (MCPTT) Management Object (MO)“. 12 3GPP TS 24.379: “Mission Critical Push To Talk (MCPTT) call control Protocol specification“. ETSI ETSI TS 124 382 V13.0.1 (2016-05)63G
29、PP TS 24.382 version 13.0.1 Release 133 Definitions and abbreviations 3.1 Definitions For the purposes of the 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, i
30、f any, in 3GPP TR 21.905 1. IdM client id: The client_id as specified in 3GPP TS 33.179 2 which is used to identify the IdM client to the IdM server. For the purposes of the present document, the following terms and definitions given in 3GPP TS 22.179 3 apply: MCPTT UE 3.2 Abbreviations For the purp
31、oses of the present document, the abbreviations 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. HTTP Hypertext Transfer Protocol IdM Identity Management LTE
32、Long Term Evolution MC ID Mission Critical User Identity MCPTT Mission Critical Push To Talk OIDC OpenID Connect TLS Transport Layer Security UE User Equipment 4 General 4.1 Identity management The Identity Management functional model for MCPTT is shown in figure 4.1-1 below and consists of the iden
33、tity management server located in the MCPTT common services core and the identity management client located in the MCPTT UE. The IdM server and the IdM client in the MCPTT UE establish the foundation for MCPTT user authentication and user authorisation. CSC-1Common services coreIdentity management s
34、erverMCPTT UEIdentity management clientFigure 4.1-1: Functional model for MCPTT identity management ETSI ETSI TS 124 382 V13.0.1 (2016-05)73GPP TS 24.382 version 13.0.1 Release 13The CSC-1 reference point, between the MCPTT IdM client in the UE and the Identity Management server, provides the interf
35、ace for user authentication. CSC-1 uses the HTTP-1 reference point and supports OpenID Connect Core 1.0 6 and IETF RFC 6749 5. The OpenID Connect profile for MCPTT is implemented as described in 3GPP TS 33.179 2. The MCPTT user authentication, the MCPTT user authorisation, the OpenID Connect Core 1.
36、0 6 and the OpenID Connect profile described in 3GPP TS 33.179 2 for MCPTT forms the basis of the MCPTT identity management architecture. Subclause 6.3 describes the procedures for the MCPTT user authentication. OIDC is flexible with respect to the user authentication mechanism used. As 3GPP TS 33.1
37、79 2 has indicated that username and password authentication is mandatory to support, that mechanism is included in subclause 6.3, although other mechanisms are possible. When the MCPTT user is authenticated, the procedure will provide an id token, an access token and a refresh token, which are all
38、described in 3GPP TS 33.179 2. The access token is scoped to the services the MCPTT user is authorised for, e.g., group management services, key management services and MCPTT services. The access token will be utilized for MCPTT service authorisation, the procedure which is documented in 3GPP TS 24.
39、379 12. 5 Entities 5.1 Identity management client The identity management client acts as the application user agent for MC ID transactions. It interacts with the identity management server. The identity management client: - shall support identity management registration to the identity management se
40、rver; - shall support the MCPTT user authentication framework as specified in 3GPP TS 33.179 2; - shall support a username and password method of authentication as specified in 3GPP TS 33.179 2; and - may support additional methods of authentication. 5.2 Identity management server The identity manag
41、ement server is a functional entity that is capable of authenticating the MC ID. It contains the knowledge and means to do authentication by verifying the credentials supplied by the user. The identity management server: - shall support identity management registration of the identity management cli
42、ent; - shall support the MCPTT user authentication framework as specified in 3GPP TS 33.179 2; - shall support a username and password method of authentication as specified in 3GPP TS 33.179 2; and - may support additional methods of authentication. 5.3 MCPTT client The MCPTT client shall interact w
43、ith the IdM client as specified in subclause 6.2: - to trigger initiation of the user authentication procedure; and - to receive the credentials obtained from the IdM server. 5.4 HTTP proxy The HTTP proxy acts as the proxy for all hypertext transactions between the HTTP client and the HTTP server. T
44、he HTTP proxy terminates the TLS session with the HTTP client of the MCPTT UE in order to allow the HTTP client to ETSI ETSI TS 124 382 V13.0.1 (2016-05)83GPP TS 24.382 version 13.0.1 Release 13establish a single TLS session for hypertext transactions with multiple HTTP servers as specified in 3GPP
45、TS 23.179 9. NOTE: The HTTP proxy is in the same trust domain as the HTTP servers that are located within a MCPTT service provider“s network. 6 Authentication procedures 6.1 General 6.2 Identity management client procedures 6.2.1 User authentication Upon an indication from the MCPTT client to initia
46、te MCPTT user authentication, the IdM client shall perform the user authentication procedure according to 3GPP TS 33.179 2 with the following clarifications: 1) shall establish a TLS tunnel to the HTTP proxy as specified in 3GPP TS 33.179 2 using the configured URL of the HTTP proxy specified in 3GP
47、P TS 24.383 11 and the clarifications in Annex A; Editors Note CT1#96, C1-161228: While 3GPP TS 33.179 indicates that the interface from IdM client to IdM server is CSC-1 and CSC-1 uses HTTP-1, there is a question as to whether the TLS session should terminate on the HTTP proxy or be end-to-end from
48、 IdM client to IdM server. This is the only interface where the MCPTT user exposes primary credentials and thus the security concerns are heightened, and IETF RFC 6749 specifies the use of TLS as MUST. 2) shall generate an OIDC Authentication Request message as specified in the OpenID Connect 1.0 6
49、and IETF RFC 6749 5 with the following clarifications: a) shall generate an HTTP GET request method according to IETF RFC 2616 4; b) shall include the configured parameter IdM client id as the client_id parameter specified in 3GPP TS 33.179 2 in the query component of the authorization endpoint“s URI using the “application/x-www-form-urlencoded“ format as specified in W3C.REC-html401-19991224 7; and NOTE 1: The configuration of client_id is specified in 3GPP TS 24.383 11. c) shall include the
