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

《ETSI TR 133 919-2016 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE 3G Security Generic Authentication Architecture (GA.pdf》由会员分享，可在线阅读，更多相关《ETSI TR 133 919-2016 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE 3G Security Generic Authentication Architecture (GA.pdf（19页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TR 1Digital cellular telecoUniversal Mobile TelGeneric AutheSy(3GPP TR 33.9TECHNICAL REPORT 133 919 V13.0.0 (2016communications system (Phaelecommunications System (LTE; 3G Security; hentication Architecture (GAAstem description .919 version 13.0.0 Release 1316-01) hase 2+); (UMTS); A); 13) ET

2、SI ETSI TR 133 919 V13.0.0 (2016-01)13GPP TR 33.919 version 13.0.0 Release 13Reference RTR/TSGS-0333919vd00 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 Associat

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

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

5、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 ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find er

6、rors 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 ex

7、cept 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. European Telecommunications Standards Institute 2016. All rights reserved

8、. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM 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

9、 GSM Association. ETSI ETSI TR 133 919 V13.0.0 (2016-01)23GPP TR 33.919 version 13.0.0 Release 13Intellectual Property 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 availa

10、ble 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 available on the ETSI Web server

11、 (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 are, or may be, or may become,

12、 essential to the present document. 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 interpret

13、ed as 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 “shall“, “shall not“, “should“, “should not“, “may“, “need not“,

14、“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 expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TR 133 919 V13.0.0 (2016-01)33

15、GPP TR 33.919 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g3Introduction 4g31 Scope 6g32 References 6g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 8g34 Generic Authentication Architecture 8g34.

16、1 GAA overview . 8g34.2 Authentication using shared secret . 8g34.3 Authentication based on (public, private) key pairs and certificates 9g35 Issuing authentication credentials 9g35.1 Schematic overview . 9g35.2 GBA: Mechanism to issue shared secret 9g35.3 SSC: Mechanism to issue subscriber certific

17、ates . 10g36 GAA building blocks 10g36.1 GAA structural overview . 10g36.2 GAA . 10g36.3 GBA . 11g36.4 SSC . 11g36.5 Access to Network Application Functions using HTTPS 12g36.5.1 HTTPS with Authentication Proxy . 12g36.5.2 HTTPS without Authentication Proxy 12g36.5.3 Pre-Shared Key TLS . 12g37 Appli

18、cation guidelines to use GAA 12g37.0 Overview on Application Authentication . 12g37.1 Use of shared secrets and GBA 14g37.2 Use of certificates . 14g37.3 NAF Recommendations . 14g37.3.1 Overview 14g37.3.2 Key Lifetime Management . 14g37.3.3 User Identity Validation 14g37.4 Event Monitoring Principle

19、s for GAA . 14g38 Usage of GBA 15g38.1 GAA and Trusted Open Platforms . 15g38.2 2G GBA . 15g38.3 Key Establishment between UICC and a Terminal 15g38.4 Liberty Alliance and GBA 15g38.5 MBMS Security 16g3Annex A: Change history 17g3History 18g3ETSI ETSI TR 133 919 V13.0.0 (2016-01)43GPP TR 33.919 vers

20、ion 13.0.0 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 present do

21、cument, 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 change co

22、ntrol. 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 This section provides an introduction on the context of GAA

23、 and some clarification of why this TR was written (with some reference to related 3GPP Technical Specifications and Technical Reports). 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 b

24、efore further communication can take place. Examples include (but are not limited to) communication between a client and a presence server (possibly via an authentication proxy), communication with a PKI portal where a client requests a digital certificate, communication with a Mobile Broadcast / Mu

25、lticast Service (MBMS) content server, a BM-SC, etc. Since a lot of applications share this common need for a peer authentication mechanism, it has been considered useful to specify a Generic Authentication Architecture (GAA). This GAA describes a generic architecture for peer authentication that ca

26、n a priori serve for any (present and future) application. This TR can be considered as a framework document for the generic authentication 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 Rele

27、ase 6 and they are specified each in a separate TS. Later on, many additions were made to accommodate specific needs for various use cases. NEGBA HTTPS and AP Certificates HSS UE GAA ETSI ETSI TR 133 919 V13.0.0 (2016-01)53GPP TR 33.919 version 13.0.0 Release 13How the different GAA and GBA related

28、specifications and technical reports fit together in GAA is explained in this document. ETSI ETSI TR 133 919 V13.0.0 (2016-01)63GPP TR 33.919 version 13.0.0 Release 131 Scope This 3GPP Technical Report aims to give an overview of the different mechanisms that mobile applications can rely upon for au

29、thentication 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 application. To this end the TR puts the different 3GPP GAA related specifications, into perspective.

30、 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. The heart of GAA consists out of the Generic Bootstrapping Architecture (GBA): The GBA core sp

31、ecifications 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: Relationships between GBA core specifications and the protocols used by GBA interfaces GBA in turn i

32、s 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 provisions of the present document. References are either specific (identified by date of pub

33、lication, 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 refers

34、 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 Security; Security architecture“. 2 3GPP TS 33.220: “3rd Generation Partnership Project; Technical

35、 Specification Group Services and System Aspects; 3G Security; Generic Authentication Architecture (GAA); Generic bootstrapping architecture“. 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 / Zn ZhHT

36、TP Digest AKARFC 3310HTTPRFC 2616Diameter Base ProtocolRFC 3588TCP SCTPIPETSI ETSI TR 133 919 V13.0.0 (2016-01)73GPP TR 33.919 version 13.0.0 Release 133 3GPP TS 33.221: “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Generic Authenticatio

37、n Architecture (GAA); Support for subscriber certificates“. 4 3GPP TS 33.222: “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Generic Authentication Architecture (GAA); Access to network application functions using secure hypertext transfe

38、r 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 and Zn Interfaces based on the Diameter protocol; Protocol details“. 7 3GPP TS 24.109: “3rd Generati

39、on 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 Services Description Language (WSDL) Version 2.0 Part 0: Primer“, http:/www.w3.org/TR/2005/WD-wsdl20-prime

40、r-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 System Aspects; 3G Security; Security of Multimedia Broadcast / Multicast Services. 13 3GPP TR 33.90

41、5: 3rdGeneration Partnership Project, Technical Specification Group Services and System Aspects; Recommendations for Trusted Open Platforms. 14 3GPP TR 33.920: 3rdGeneration Partnership Project, Technical Specification Group Services and System Aspects; SIM card based GBA Generic Bootstrapping Archi

42、tecture; 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 Terminal. 16 3GPP TR 33.980: 3rd Generation Partnership Project; Technical Specification Group Services and S

43、ystem Aspects; Liberty Alliance and 3GPP security interworking; Interworking of Liberty Alliance Identity Federation Framework (ID-FF), Identity Web Services Framework (ID-WSF) and Generic Authentication Architecture (GAA). 3 Definitions and abbreviations 3.1 Definitions For the purposes of the pres

44、ent 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 the subscribers own public key and possibly other information such as the subscribers identity in some form. E

45、TSI ETSI TR 133 919 V13.0.0 (2016-01)83GPP TR 33.919 version 13.0.0 Release 133.2 Abbreviations For the purposes of the present document, the following abbreviations apply: AKA Authentication and Key Agreement AP Authentication ProxyAS Application ServerBSF Bootstrapping Server Function GAA Generic

46、Authentication Architecture GBA Generic Bootstrapping ArchitectureHSS Home Subscriber System NAF Network Application Function NE Network Element PKI Public Key Infrastructure SSC Support for Subscriber Certificates UE User Equipment 4 Generic Authentication Architecture 4.1 GAA overview There are ge

47、nerally 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 certificates. Also in GAA these are the two options that are a priori available for mobile applications as is

48、 illustrated in Figure 3. GAA Shared Secret GBA TS33.220 Certificates SSC TS33.221 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

49、 Digest, Pre-Shared Key TLS, IKE with pre-shared secret and a priori any mechanism based on username and password. The main problem with these mechanisms is how to agree on this pre-shared secret. Clause 5.2 and GBA TS 33.220 2 describe how in a mobile context an AKA based mechanism can be used to provide both communicating entities with a pre-shared secret. ETSI ETSI TR 133 919 V13.0.0 (2016-01)93GPP TR 33.919 version 13.0.0 Release 134.3 Authentication based on (public, private) key pairs and certificates An alterna