|
TECHNICAL SPECIFICATION
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 13.0.0 Release 13)
---------------------- Page: 1 ----------------------
3GPP TS 33.187 version 13.0.0 Release 13 1 ETSI TS 133 187 V13.0.0 (2016-03)
Reference
RTS/TSGS-0333187vd00
Keywords
GSM,LTE,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 lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
The present document can be downloaded from:
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 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 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
If you find errors in the present document, please send your comment to one of the following services:
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 written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 2016.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP 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
---------------------- Page: 2 ----------------------
3GPP TS 33.187 version 13.0.0 Release 13 2 ETSI TS 133 187 V13.0.0 (2016-03)
Intellectual 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 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 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 (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 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, 3GPP and ETSI identities can be found under
.
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 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
---------------------- Page: 3 ----------------------
3GPP TS 33.187 version 13.0.0 Release 13 3 ETSI TS 133 187 V13.0.0 (2016-03)
Contents
Intellectual Property Rights . 2
Foreword . 2
Modal verbs terminology . 2
Foreword . 4
1 Scope . 5
2 References . 5
3 Definitions and abbreviations . 6
3.1 Definitions . 6
3.2 Void . 6
3.3 Abbreviations . 6
4 Security Requirements . 6
4.1 Requirements on SCEF – 3GPP Network Entity reference point. 6
4.2 Requirements on Service Capability Exposure Function (SCEF) . 7
4.3 Requirements on SCEF – Interworking SCEF reference point . 7
4.1 Requirements on MTC . 7
4.2 Requirements on Tsp reference point . 7
4.3 Requirements on MTC-IWF. 7
5 General security procedures . 8
5.1 Security procedures for Tsp interface security . 8
5.2 Security procedures for reference point SCEF – 3GPP Network Entity . 8
5.2.0 Introduction. 8
5.2.1 SCEF is considered as a 3GPP network function . 8
5.2.2 SCEF is not considered as a 3GPP network function . 8
5.3 Security procedures for reference point Application – 3GPP Network Entity . 8
5.4 Security procedures for reference point SCEF – Interworking SCEF . 8
6 Security procedures for Device Triggering . 9
6.1 Network based solution for filtering SMS-delivered device trigger messages . 9
7 Security procedures for secure connection . 10
7.1 Introduction . 10
7.2 UE initiated secure connection . 10
7.3 Network initiated secure connection . 11
8 Security procedures for restricting the USIM to specific UEs . 11
8.1 UE-based procedure with USAT application pairing . 11
8.1.1 General . 11
8.1.2 Security procedure . 11
Annex A (informative): Change history . 13
History . 14
ETSI
---------------------- Page: 4 ----------------------
3GPP TS 33.187 version 13.0.0 Release 13 4 ETSI TS 133 187 V13.0.0 (2016-03)
Foreword
rd
This Technical Specification has been produced by the 3 Generation 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 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 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.
ETSI
---------------------- Page: 5 ----------------------
3GPP TS 33.187 version 13.0.0 Release 13 5 ETSI TS 133 187 V13.0.0 (2016-03)
1 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 Communications 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 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 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 (MTC)".
[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 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 Bootstrapping
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) Subscriber 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) Application 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
---------------------- Page: 6 ----------------------
3GPP TS 33.187 version 13.0.0 Release 13 6 ETSI TS 133 187 V13.0.0 (2016-03)
3 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.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 Communications
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
rd
controlling the Network Entity or by a 3 party, 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 authentication 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 operator’s
domain);
- the 3GPP 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 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 mechanism 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
---------------------- Page: 7 ----------------------
3GPP TS 33.187 version 13.0.0 Release 13 7 ETSI TS 133 187 V13.0.0 (2016-03)
4.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 Entity reference point in clause 4.x;
- 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 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 decision 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 requirements
from clause 4.x 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.1 Requirements on MTC
The security requirements for MTC include the following:
- MTC optimizations shall not degrade security compared to non-MTC communications 3GPP TS 22.368 [2]
4.2 Requirements on Tsp reference point
The Tsp reference point shall fulfil the following requirements:
- integrity protection, replay protection, confidentiality protection and privacy protection for 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 [4];
- integrity protection and replay protection shall be used;
- confidentiality protection should be used;
- privacy shall be provided (e.g. IMS
...