ETSI TS 133 187-2018 Digital cellular telecommunications system (Phase 2+) (GSM) Universal Mobile Telecommunications System (UMTS) LTE Security aspects of Machine-Type Communicatio.pdf

《ETSI TS 133 187-2018 Digital cellular telecommunications system (Phase 2+) (GSM) Universal Mobile Telecommunications System (UMTS) LTE Security aspects of Machine-Type Communicatio.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 133 187-2018 Digital cellular telecommunications system (Phase 2+) (GSM) Universal Mobile Telecommunications System (UMTS) LTE Security aspects of Machine-Type Communicatio.pdf（15页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 133 187 V14.1.0 (2018-01) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Security aspects of Machine-Type Communications (MTC) and other mobile data applications communications enhancements (3GPP TS 33.187 version 14.1.0

2、Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 133 187 V14.1.0 (2018-01)13GPP TS 33.187 version 14.1.0 Release 14Reference RTS/TSGS-0333187ve10 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

3、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 downloaded from: http:/www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The co

4、ntent 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 existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Do

5、cument 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 subject to revision or change of status. Information on the current status of this and other ETSI documents is available at https:/portal.etsi.

6、org/TB/ETSIDeliverableStatus.aspx If you find errors 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 mec

7、hanical, 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 authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. ETSI 2018. All rights res

8、erved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are 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. GSM

9、and the GSM logo are trademarks registered and owned by the GSM Association. ETSI ETSI TS 133 187 V14.1.0 (2018-01)23GPP TS 33.187 version 14.1.0 Release 14Intellectual Property Rights Essential patents IPRs essential or potentially essential to the present document may have been declared to ETSI. T

10、he 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, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available f

11、rom 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 ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314

12、 (or the updates on the ETSI Web server) which 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 i

13、ndicated as being the property of ETSI, and conveys 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 Techn

14、ical 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 interpreted as being references to the corresponding ETSI

15、 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“, “will“, “will not“, “can“ and “cannot“ are to be

16、 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 187 V14.1.0 (2018-01)33GPP TS 33.187 version 14.1.0 Release 14Contents

17、Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Void 6g33.3 Abbreviations . 6g34 Security Requirements . 6g34.1 Requirements on SCEF 3GPP Network Entity reference point. 6g34

18、.2 Requirements on Service Capability Exposure Function (SCEF) 7g34.3 Requirements on SCEF Interworking SCEF reference point 7g34.4 Requirements on MTC . 7g34.5 Requirements on Tsp reference point . 7g34.6 Requirements on MTC-IWF. 7g35 General security procedures . 8g35.1 Security procedures for Tsp

19、 interface security . 8g35.2 Security procedures for reference point SCEF 3GPP Network Entity 8g35.2.0 Introduction. 8g35.2.1 SCEF is considered as a 3GPP network function . 8g35.2.2 SCEF is not considered as a 3GPP network function . 8g35.3 Security procedures for reference point Application 3GPP N

20、etwork Entity . 8g35.4 Security procedures for reference point SCEF Interworking SCEF 8g36 Security procedures for Device Triggering 9g36.1 Network based solution for filtering SMS-delivered device trigger messages . 9g37 Security procedures for secure connection . 10g37.1 Introduction 10g37.2 UE in

21、itiated secure connection . 10g37.3 Network initiated secure connection 11g38 Security procedures for restricting the USIM to specific UEs . 11g38.1 UE-based procedure with USAT application pairing . 11g38.1.1 General 11g38.1.2 Security procedure 11g3Annex A (informative): Change history . 13g3Histo

22、ry 14g3ETSI ETSI TS 133 187 V14.1.0 (2018-01)43GPP TS 33.187 version 14.1.0 Release 14Foreword 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 f

23、ormal 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: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG fo

24、r 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 third digit is incremented when editorial only changes have been incorporated in the document.

25、ETSI ETSI TS 133 187 V14.1.0 (2018-01)53GPP TS 33.187 version 14.1.0 Release 141 Scope The present document specifies the security architecture enhancements (i.e., enhancements to the security features and the security mechanisms) to facilitate Machine-Type and other mobile data applications Communi

26、cations enhancements (MTCe) as per the use cases and service requirements defined in 3GPP TS 22.368 2 and the architecture enhancements and procedures defined in 3GPP TS 23.682 3. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of

27、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 reference to a

28、 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 Specifications“. 2 3GPP TS 22.368: “Service Requirements for Machine-Type Communications (M

29、TC)“. 3 3GPP TS 23.682: “Architecture Enhancements to facilitate communications with Packet Data Networks and Applications“. 4 3GPP TS 29.368: “Tsp interface protocol between the MTC Interworking Function (MTC-IWF) and Service Capability Server (SCS)“. 5 3GPP TS 23.040: “Technical realization of the

30、 Short Message Service (SMS)“. 6 3GPP TS 23.142: “Value-added Services for SMS (VAS4SMS); Interface and signalling flow“. 7 3GPP TS 33.220: “Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA)“. 8 3GPP TS 33.223: “Generic Authentication Architecture (GAA); Generic Boo

31、tstrapping Architecture (GBA) Push function“. 9 3GPP TS 23.204: “Support of Short Message Service (SMS) over generic 3GPP Internet Protocol (IP) access; Stage 2“. 10 3GPP TS 31.115: “Remote APDU Structure for (U)SIM Toolkit applications“. 11 3GPP TS 31.116: “Remote APDU Structure for (Universal) Sub

32、scriber Identity Module (U)SIM Toolkit applications“. 12 ETSI TS 102 225: “Smart Cards; Secured packet structure for UICC based applications”. 13 ETSI TS 102 226: “Smart cards; Remote APDU structure for UICC based applications”. 14 3GPP TS 31.111: “Universal Subscriber Identity Module (USIM) Applica

33、tion Toolkit (USAT)“. 15 3GPP TS 33.210: “3G security; Network Domain Security (NDS); IP network layer security “. 16 3GPP TS 33.246: “MBMS Security“. 17 3GPP TS 33.310: “3G security; Network Domain Security (NDS); Authentication Framework (AF) “. ETSI ETSI TS 133 187 V14.1.0 (2018-01)63GPP TS 33.18

34、7 version 14.1.0 Release 143 Definitions and abbreviations 3.1 Definitions For the 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.

35、905 1. 3.2 Void 3.3 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. MTC Machine-Type Communic

36、ations MTC-IWF MTC Interworking Function SCEF Service Capability Exposure Function 4 Security Requirements 4.1 Requirements on SCEF 3GPP Network Entity reference point The SCEF is controlled by the 3GPP operator or a business partner e.g. by another operator than the 3GPP operator controlling the Ne

37、twork Entity or by a 3rdparty, the SCEF 3GPP Network Entity reference point shall fulfil the following requirements: - integrity protection, replay protection, confidentiality protection and privacy protection for communication between the SCEF and 3GPP Network Entity shall be supported; - mutual au

38、thentication between 3GPP Network Entity and SCEF shall be supported; - integrity protection and replay protection shall be used; - confidentiality protection should be used; - privacy of the 3GPP user shall be provided (e.g. IMSI/IMPI shall not be sent outside the 3GPP operators domain); - the 3GPP

39、 Network Entity shall be able to determine whether the SCEF is authorized to send requests to the 3GPP Network Entity; - the 3GPP Network Entity may be able to determine whether authorization shall be per UE, or optionally per service per UE. NOTE: How to achieve authorization per UE or per service

40、per UE is specific to application and network configuration. For example, if the SCEF 3GPP Network Entity reference point does not support such authorization, the SCEF may need to contact HSS before forwarding the request to the 3GPP Network Entity (or to the IWK-SCEF in case of roaming). The mechan

41、ism of such authorization is not specified in 3GPP standards. The same security requirements apply also when applications operating in the trust domain access network entities (e.g. PCRF), wherever the required 3GPP interface(s) are made available, directly without going through the SCEF. ETSI ETSI

42、TS 133 187 V14.1.0 (2018-01)73GPP TS 33.187 version 14.1.0 Release 144.2 Requirements on Service Capability Exposure Function (SCEF) The functionality of the Service Capability Exposure Function (SCEF) includes the following: - support ability to satisfy security requirements on SCEF 3GPP Network En

43、tity reference point in clause 4. 1; - it shall be able to determine whether the Application is authorized to send requests for the 3GPP Network Entity, where authorization shall be per UE or optionally per service per UE. NOTE: SCEF may include authentication, authorization, and access control list

44、 management functionality or it may rely on the authorization decisions made by the 3GPP Network Entity via reference point SCEF 3GPP Network Entity. The mechanism of such authorization performed by the SCEF is not specified in 3GPP standards. However, the mechanisms for asking authorization decisio

45、n from the HSS by the SCEF are in the scope of 3GPP. 4.3 Requirements on SCEF Interworking SCEF reference point The requirements for the SCEF Interworking SCEF reference point include the following: - the same integrity protection, replay protection, confidentiality protection and privacy protection

46、 requirements from clause 4. 1 apply for the interface T7 between the SCEF and IWK-SCEF. - the IWK-SCEF shall be able to determine whether the SCEF in the HPLMN is authorized to send requests for the 3GPP Network Entity. 4.4 Requirements on MTC The security requirements for MTC include the following

47、: - MTC optimizations shall not degrade security compared to non-MTC communications 3GPP TS 22.368 2 4.5 Requirements on Tsp reference point The Tsp reference point shall fulfil the following requirements: - integrity protection, replay protection, confidentiality protection and privacy protection f

48、or communication between the MTC-IWF and SCS shall be supported: - mutual authentication between two directly communicating entities in the security domains, in which MTC-IWF and SCS respectively reside, shall be supported; - the use of mutual authentication shall follow the provisions in TS 29.368

49、4; - integrity protection and replay protection shall be used; - confidentiality protection should be used; - privacy shall be provided (e.g. IMSI shall not be sent outside the 3GPP operator domain). 4.6 Requirements on MTC-IWF The functionality of the MTC-IWF includes the following: - support ability to satisfy security requirements on Tsp reference point in clause 4. 5. ETSI ETSI TS 133 187 V14.1.0 (2018-01)83GPP TS 33.187 version 14.1.0 Release 145 General security procedures 5.1 Security procedures