ETSI TR 133 919-2018 Digital cellular telecommunications system (Phase 2+) (GSM) Universal Mobile Telecommunications System (UMTS) LTE 3G Security Generic Authentication Architectu.pdf

1、 ETSI TR 133 919 V15.0.0 (2018-07) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; 3G Security; Generic Authentication Architecture (GAA); System description (3GPP TR 33.919 version 15.0.0 Release 15) TECHNICAL REPORT ETSI ETSI TR

2、133 919 V15.0.0 (2018-07)13GPP TR 33.919 version 15.0.0 Release 15Reference RTR/TSGS-0333919vf00 Keywords GSM,LTE,SECURITY,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

3、 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 in electronic versions and/or in print. The content of any electronic and/or print versions of

4、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 prevailing document is the print of the Portable Document Format (PDF) version kept on a specific ne

5、twork 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 ETSI documents is available at https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find err

6、ors 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 in any form or by any means, electronic or mechanical, including photocopying and microfilm exc

7、ept 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 reproduction in all media. ETSI 2018. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI lo

8、go 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 is protected for the benefit of its Members. GSMand the GSM logo are trademarks registered and ow

9、ned by the GSM Association. ETSI ETSI TR 133 919 V15.0.0 (2018-07)23GPP TR 33.919 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 IP

10、Rs, 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 standards“, which is available from the ETSI Secretariat. Latest updates are av

11、ailable 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 referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which

12、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 no ownership of these except for any which are indicated as being the property of ETSI, and con

13、veys 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 associated with those trademarks. Foreword This Technical Report (TR) has been produced by ETSI 3rd

14、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 being references to the corresponding ETSI deliverables. The cross reference between GSM, UMTS,

15、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“ and “cannot“ are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal f

16、orms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TR 133 919 V15.0.0 (2018-07)33GPP TR 33.919 version 15.0.0 Release 15Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3For

17、eword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 7g34 Generic Authentication Architecture 7g34.1 GAA overview . 7g34.2 Authentication using shared secret . 7g34.3 Authentication based on (public, private) key pairs and

18、certificates 8g35 Issuing authentication credentials 8g35.1 Schematic overview . 8g35.2 GBA: Mechanism to issue shared secret 8g35.3 SSC: Mechanism to issue subscriber certificates . 8g36 GAA building blocks 9g36.1 GAA structural overview . 9g36.2 GAA . 9g36.3 GBA . 9g36.4 SSC . 10g36.5 Access to Ne

19、twork Application Functions using HTTPS 10g36.5.1 HTTPS with Authentication Proxy . 10g36.5.2 HTTPS without Authentication Proxy 10g36.5.3 Pre-Shared Key TLS . 11g37 Application guidelines to use GAA 11g37.0 Overview on Application Authentication . 11g37.1 Use of shared secrets and GBA 12g37.2 Use o

20、f certificates . 12g37.3 NAF Recommendations . 12g37.3.1 Overview 12g37.3.2 Key Lifetime Management . 13g37.3.3 User Identity Validation 13g37.4 Event Monitoring Principles for GAA . 13g38 Usage of GBA 13g38.1 GAA and Trusted Open Platforms . 13g38.2 2G GBA . 13g38.3 Key Establishment between UICC a

21、nd a Terminal 14g38.4 Liberty Alliance and GBA 14g38.5 MBMS Security 14g3Annex A: Change history 15g3History 16g3ETSI ETSI TR 133 919 V15.0.0 (2018-07)43GPP TR 33.919 version 15.0.0 Release 15Foreword This Technical Report has been produced by the 3rdGeneration Partnership Project (3GPP). The conten

22、ts 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 and an increase in version number as follows

23、: 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 enhancements, corrections, updates, etc. z

24、the third digit is incremented when editorial only changes have been incorporated in the document. Introduction This section provides an introduction on the context of GAA and some clarification of why this TR was written (with some reference to related 3GPP Technical Specifications and Technical Re

25、ports). Figure 1: Schematic illustration of GAA A number of applications share a need for mutual authentication between a client (i.e. the UE ) and an application server before further communication can take place. Examples include (but are not limited to) communication between a client and a presen

26、ce server (possibly via an authentication proxy), communication with a PKI portal where a client requests a digital certificate, communication with a Mobile Broadcast / Multicast Service (MBMS) content server, a BM-SC, etc. Since a lot of applications share this common need for a peer authentication

27、 mechanism, it has been considered useful to specify a Generic Authentication Architecture (GAA). This GAA describes a generic architecture for peer authentication that can a priori serve for any (present and future) application. This TR can be considered as a framework document for the generic auth

28、entication architecture as is illustrated in Figure 1. GBA, HTTPS and the Authentication Proxy (AP), and Certificates are the basic building blocks of the GAA in 3GPP Release 6 and they are specified each in a separate TS. Later on, many additions were made to accommodate specific needs for various

29、use cases. How the different GAA and GBA related specifications and technical reports fit together in GAA is explained in this document. NE GBA HTTPS and AP Certificates HSS UE GAA ETSI ETSI TR 133 919 V15.0.0 (2018-07)53GPP TR 33.919 version 15.0.0 Release 151 Scope This 3GPP Technical Report aims

30、to give an overview of the different mechanisms that mobile applications can rely upon for authentication between server and client (i.e. the UE). Additionally it provides guidelines related to the use of GAA and to the choice of authentication mechanism in a given situation and for a given applicat

31、ion. To this end the TR puts the different 3GPP GAA related specifications, into perspective. It clarifies the logic for having the technical specifications and technical reports, sketches their content and explains the inter-relation between these 3GPP TSs and TRs and their relation with this TR. T

32、he heart of GAA consists out of the Generic Bootstrapping Architecture (GBA): The GBA core specifications consist out of TS 33.220, TS 24.109 and TS 29.109. Figure 2 depicts protocols used over the GBA core interfaces and the relationships between different GBA core specifications. Figure 2: Relatio

33、nships between GBA core specifications and the protocols used by GBA interfaces GBA in turn is then used by many other TSs and TRs to enable specific usages e.g. HTTPS, subscriber certificates. 2 References The following documents contain provisions which, through reference in this text, constitute

34、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 of a

35、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 33.102: “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G

36、 Security; Security architecture“. 2 3GPP TS 33.220: “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Generic Authentication Architecture (GAA); Generic bootstrapping architecture“. 3 3GPP TS 33.221: “3rd Generation Partnership Project; Tec

37、hnical Specification Group Services and System Aspects; 3G Security; Generic Authentication Architecture (GAA); Support for subscriber certificates“. TS 33.220 GBATS 24.109Ub UaWSDL/ SOAP b a se d Web Se r v i ce 1 0 E.g. HTTP Digest RFC 2617IMS Cx Diameter message definitionsTS 29.229TS 29.109Zn /

38、Zn ZhHTTP Digest AKARFC 3310HTTPRFC 2616Diameter Base ProtocolRFC 3588TCP SCTPIPETSI ETSI TR 133 919 V15.0.0 (2018-07)63GPP TR 33.919 version 15.0.0 Release 154 3GPP TS 33.222: “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Generic Authen

39、tication Architecture (GAA); Access to network application functions using secure hypertext transfer protocol (HTTPS)“. 5 IETF RFC 2818: “HTTP Over TLS“. 6 3GPP TS 29.109: “3rd Generation Partnership Project; Technical Specification Group Core Network; Generic Authentication Architecture (GAA); Zh a

40、nd Zn Interfaces based on the Diameter protocol; Protocol details“. 7 3GPP TS 24.109: “3rd Generation Partnership Project; Technical Specification Group Core Network; Bootstrapping interface (Ub) and Network application function interface (Ua); Protocol details“. 8 Void. 9 Void. 10 W3C: “Web Service

41、s Description Language (WSDL) Version 2.0 Part 0: Primer“, http:/www.w3.org/TR/2005/WD-wsdl20-primer-20050803/. 11 IETF RFC 4279 (2005) “Pre-Shared Key Ciphersuites for Transport Layer Security (TLS)“. 12 3GPP TS 33.246: “3rdGeneration Partnership Project, Technical Specification Group Services and

42、System Aspects; 3G Security; Security of Multimedia Broadcast / Multicast Services”. 13 3GPP TR 33.905: “3rdGeneration Partnership Project, Technical Specification Group Services and System Aspects; Recommendations for Trusted Open Platforms”. 14 3GPP TR 33.920: “3rdGeneration Partnership Project, T

43、echnical Specification Group Services and System Aspects; SIM card based GBA Generic Bootstrapping Architecture; Early Implementation Feature”. 15 3GPP TS 33.110: “3rdGeneration Partnership Project, Technical Specification Group Services and System Aspects; Key Establishment between a UICC and a Ter

44、minal”. 16 3GPP TR 33.980: “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Liberty Alliance and 3GPP security interworking; Interworking of Liberty Alliance Identity Federation Framework (ID-FF), Identity Web Services Framework (ID-WSF) and Generic Aut

45、hentication Architecture (GAA)”. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply. Subscriber certificate: a certificate issued by a mobile network operator to a subscriber based on his/her subscription. It contains t

46、he subscribers own public key and possibly other information such as the subscribers identity in some form. ETSI ETSI TR 133 919 V15.0.0 (2018-07)73GPP TR 33.919 version 15.0.0 Release 153.2 Abbreviations For the purposes of the present document, the following abbreviations apply: AKA Authentication

47、 and Key Agreement AP Authentication ProxyAS Application ServerBSF Bootstrapping Server Function GAA Generic Authentication Architecture GBA Generic Bootstrapping ArchitectureHSS Home Subscriber System NAF Network Application Function NE Network Element PKI Public Key Infrastructure SSC Support for

48、Subscriber Certificates UE User Equipment 4 Generic Authentication Architecture 4.1 GAA overview There are generally speaking two types of authentication mechanisms. One is based on a secret shared between the communicating entities, the other one is based on (public, private) key pairs and digital

49、certificates. Also in GAA these are the two options that are a priori available for mobile applications as is illustrated in Figure 3. GAA g54g75g68g85g72g71g3g54g72g70g85g72g87g3g42g37g36g3g55g54g22g22g17g21g21g19 g38g72g85g87g76g73g76g70g68g87g72g86g3g54g54g38g3g55g54g22g22g17g21g21g20 Figure 3: GAA schematic overview 4.2 Authentication using shared secret There are several authentication protocols that rely on a pre-shared secret between the two communicating entities. Popular examples include HTTP Digest, Pre-Shared Key TLS, IKE wit