1、 ETSI TS 1Digital cellular telecoUniversal Mobile TelKey establishmenand(3GPP TS 33.2TECHNICAL SPECIFICATION133 259 V13.0.0 (2016communications system (Phaelecommunications System (LTE; ent between a UICC hosting dend a remote device .259 version 13.0.0 Release 1316-01) hase 2+); (UMTS); vice ) ETSI
2、 ETSI TS 133 259 V13.0.0 (2016-01)13GPP TS 33.259 version 13.0.0 Release 13Reference RTS/TSGS-0333259vd00 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 Associatio
3、n 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 ver
4、sions 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 sp
5、ecific 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 erro
6、rs 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 exce
7、pt 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 G
9、SM Association. ETSI ETSI TS 133 259 V13.0.0 (2016-01)23GPP TS 33.259 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 availabl
10、e 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, e
12、ssential to the present document. Foreword This Technical Specification (TS) 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 inte
13、rpreted 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 n
14、ot“, “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 TS 133 259 V13.0.0 (2016-
15、01)33GPP TS 33.259 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 8g34 Key Establishment between a UICC Hos
16、ting Device and a Remote Device . 8g34.1 Reference model . 8g34.2 Network elements . 9g34.2.1 General 9g34.2.2 NAF Key Centre . 9g34.3 Key establishment architecture and reference points . 9g34.3.1 General 9g34.3.2 Reference point Ub . 9g34.3.3 Reference point Ua . 9g34.3.4 Reference point Local int
17、erface 10g34.4 Requirements and principles for key establishment between a UICC Hosting Device and a Remote Device 10g34.4.1 General requirements 10g34.4.2 Requirements on the Remote Device 10g34.4.3 Requirements on the UICC Hosting Device . 10g34.4.4 Requirements on the UICC . 11g34.4.5 Requirement
18、s on the NAF Key Centre . 11g34.4.6 Requirements on Ks_local_device key and associated parameters handling in Remote Device 11g34.4.7 Requirements on Ks_local_device key and associated parameters handling in UICC Hosting Device . 12g34.5 Procedures 12g34.5.1 Initiation of key establishment between a
19、 UICC Hosting Device and a Remote Device . 12g34.5.2 Key establishment procedure 13g3Annex A (normative): Key Derivation Function definition 17g3A.1 Platform specific key (Ks_local_device): Ks_local_device key derivation in key establishment . 17g3A.2 Input parameters for Ks_local_device key derivat
20、ion 17g3Annex B (normative): HTTP based key request procedure . 18g3B.1 Introduction 18g3B.2 Key request procedure 18g3B.2.1 Key request . 18g3B.2.2 Error situations . 19g3Annex C (informative): Signalling flows for key request procedure . 20g3C.1 Introduction 20g3C.2 Signalling flow demonstrating a
21、 successful key request procedure . 20g3Annex D (normative): XML schema for Key Request and Key Response . 23g3ETSI ETSI TS 133 259 V13.0.0 (2016-01)43GPP TS 33.259 version 13.0.0 Release 13D.1 Introduction 23g3D.2 Key Request Format . 23g3D.2.1 Data Format 23g3D.2.2 Example 23g3D.3 Key Response For
22、mat 24g3D.3.1 Data Format 24g3D.3.2 Example 24g3Annex E (normative): TLS profiles 25g3Annex F (informative): Application specific key (Ks_local_device_appl) 26g3F.1 Example of Ks_local_device_appl key derivation in key establishment . 26g3Annex G (informative): Application specific key (Ks_local_dev
23、ice_appl): Key Derivation Function definition . 27g3G.1 Ks_local_device_appl key derivation in key establishment . 27g3G.2 Input parameters for Ks_local_device_appl key derivation . 27g3Annex H (informative): Change history . 28g3History 29g3ETSI ETSI TS 133 259 V13.0.0 (2016-01)53GPP TS 33.259 vers
24、ion 13.0.0 Release 13Foreword 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 change following formal TSG approval. Should the TSG modify the contents of the pre
25、sent 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 ch
26、ange 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 The need to establish a secure channel between a UIC
27、C Hosting Device and a Remote Device connected via a local interface has been identified by the Personal Network Management work (see TS 22.259 4), in order to protect the communication between the UICC Hosting Device and the Remote Device. This document describes key establishment between a UICC Ho
28、sting Device and a Remote Device. ETSI ETSI TS 133 259 V13.0.0 (2016-01)63GPP TS 33.259 version 13.0.0 Release 131 Scope The present document describes the security features and mechanisms to provision a shared key between a UICC Hosting Device and a Remote Device connected via a local interface. Th
29、e shared secret is then intended to be used to secure the interface between the Remote Device and the UICC hosting device. Candidate applications to use this key establishment mechanism include but are not restricted to Personal Network Management (see TS 22.259 4). The scope of this specification i
30、ncludes an architecture overview and the detailed procedure how to establish the shared key between the UICC Hosting Device and the Remote Device. This is different from the Technical Specification TS 33.110 5 that describes an architecture overview and the detailed procedure how to establish the sh
31、ared key between the UICC itself and the terminal hosting the UICC. The use cases utilizing the mechanisms described in this specification are seen to be different to the use cases where “Key establishment between a UICC and a terminal“, PSK TLS as specified in TS 33.310 19, is utilized. The solutio
32、n described in this document is built on the existing infrastructure defined in “GBA“, TS 33.220 3. 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 publ
33、ication, 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 TR 21.905: “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Vocabulary for 3GPP Specifications“. 2 3GPP TS 31.101: “3rd Generation Partnership Project; Technical
35、Specification Group Terminals; UICC-terminal interface; Physical and logical characteristics“. 3 3GPP TS 33.220: “Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture“. 4 3GPP TS 22.259: “Service Requirements for Personal Network Management; Stage 1“. 5 3GPP TS 33.110: “Tech
36、nical Specification Group Services and System Aspects; Key establishment between a UICC and a terminal“. 6 Void. 7 Void. 8 Void. 9 3GPP TS 29.109: “Generic Authentication Architecture (GAA); Zh and Zn Interfaces based on the Diameter protocol; Stage 3“. 10 3GPP TR 33.905: “3rd Generation Partnership
37、 Project; Technical Specification Group Services and System Aspects; Recommendations for trusted open platforms“. 11 3GPP TS 24.008: “Mobile radio interface Layer 3 specification; Core network protocols; Stage 3“. 12 NIST, FIPS PUB 180-2: “Secure Hash Standard (SHS)“. 13 IETF RFC 4634 (2006): US Sec
38、ure Hash Algorithms (SHA and HMAC-SHA). ETSI ETSI TS 133 259 V13.0.0 (2016-01)73GPP TS 33.259 version 13.0.0 Release 1314 IETF RFC 2104 (1997): “HMAC: Keyed-Hashing for Message Authentication“. 15 TCG Mobile Phone Specifications, https:/www.trustedcomputinggroup.org/specs/mobilephone. 16 TCG Trusted
39、 Network Connect (TNC) Specifications, https:/www.trustedcomputinggroup.org/specs/TNC. 17 IETF RFC 2616 (1999): “Hypertext Transfer Protocol - HTTP/1.1“. 18 Void. 19 3GPP TS 33.310: “ Network Domain Security (NDS); Authentication Framework (AF)“. 3 Definitions and abbreviations 3.1 Definitions For t
40、he purposes of the present document, the terms and definitions given in 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 TR 21.905 1. NAF Key Centre: Dedicated NAF in charge of performing the key establishme
41、nt between a UICC Hosting Device and a Remote Device. UICC Hosting Device: The entity, which is physically connected to the UICC used for key establishment between UICC Hosting Device and Remote Device. The UICC Hosting Device may be the MT or the ME. Remote Device: A Remote Device is physically sep
42、arated from the UICC Hosting Device (e.g. PNE as defined in TS 22.259 4). The Remote Device may host a UICC by itself but this UICC is not involved in the key establishment between the UICC Hosting Device and the Remote Device. For the purposes of the present document, the term Remote Device denotes
43、 a trusted device that can establish a shared key with a UICC Hosting Device. NOTE 1: The definition of trusted devices is out of the scope of the present document. It is assumed that the home network can decide whether a Remote Device is trusted or not. Device_ID: It identifies uniquely the Remote
44、Device. The Device_ID of a ME or MT is the IMEI and shall be encoded using BCD coding as defined in section 10.5.1.4 of TS 24.008 11. NOTE 2: In case that the Remote Device is not a ME or MT the definition of the type of Device_IDs is out of the scope of the present document. Local interface: The in
45、terface between the Remote Device and the UICC Hosting Device is named the local interface. Appl_ID: It uniquely identifies an application in the UICC Hosting Device and Remote Device. The Appl_ID is an octet string. ETSI ETSI TS 133 259 V13.0.0 (2016-01)83GPP TS 33.259 version 13.0.0 Release 133.2
46、Abbreviations For the purposes of the present document, the abbreviations given in 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 TR 21.905 1. B-TID Bootstrapping Transaction Identifier BS
47、F Bootstrapping Server Function GBA Generic Bootstrapping Architecture GBA_ME ME-based GBA GBA_U GBA with UICC-based enhancements HSS Home Subscriber System KDF Key Derivation Function Ks_ext_NAF Derived key in GBA_U Ks_NAF Derived key in GBA_ME Ks_(ext)_NAF Combined abbreviation denoting Ks_NAF in
48、case of GBA_ME and Ks_ext_NAF in case of GBA_U Ks_local_device Derived key, which is shared between a UICC hosting device and a Remote Device Ks_local_device_appl Derived key, which is shared between an application residing in the UICC hosting device and the Remote Device MAC Message Authentication
49、Code NAF Network Application FunctionPNE Personal Network Element SLF Subscriber Locator Function USS User Security Setting 4 Key Establishment between a UICC Hosting Device and a Remote Device 4.1 Reference model A Remote Device, which for example could be a PNE as defined in TS 22.259 4 or any other Remote Device containing a Ua application according to this specification, is connected to a UICC Hosting Device, via a local interface. The communication over the local interface could take place via for exa
