ETSI TS 133 246-2016 Universal Mobile Telecommunications System (UMTS) LTE 3G Security Security of Multimedia Broadcast Multicast Service (MBMS) (V13 1 0 3GPP TS 33 246 version 13 .pdf

1、 ETSI TS 1Universal Mobile TelSecurity of Multimedia(3GPP TS 33.2TECHNICAL SPECIFICATION133 246 V13.1.0 (2016elecommunications System (LTE; 3G Security; ia Broadcast/Multicast Servic.246 version 13.1.0 Release 1316-01) (UMTS); ice (MBMS) 13) ETSI ETSI TS 133 246 V13.1.0 (2016-01)13GPP TS 33.246 vers

2、ion 13.1.0 Release 13Reference RTS/TSGS-0333246vd10 Keywords 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 lucratif enregistre la Sous-Prfecture de Grasse

3、(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 the present document shall not be modified withou

4、t 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

5、 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 errors in the present document, please send your comment to on

6、e 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 except as authorized by written permission of ETSI. The conten

7、t 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. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Mar

8、ks 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 GSM Association. ETSI ETSI TS 133 246 V13.1.0 (2016-01)23GP

9、P TS 33.246 version 13.1.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 available for ETSI members and non-members, and can be found in ET

10、SI 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

11、 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

12、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 deli

13、verables. 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 inte

14、rpreted 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 246 V13.1.0 (2016-01)33GPP TS 33.246 version 13.1.0 Release 13Contents Intel

15、lectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 7g3Introduction 7g31 Scope 8g32 References 8g33 Definitions, abbreviations, symbols and conventions 10g33.1 Definitions 10g33.2 Abbreviations . 10g33.3 Symbols 11g33.4 Conventions 11g34 MBMS security overview 11g34.1 MBMS

16、 security architecture. 11g34.1.1 General 11g34.1.2 BM-SC sub-functions . 13g34.1.3 UE security architecture 14g34.1A Granularity of MBMS security . 15g34.2 Key management overview 15g35 MBMS security functions 16g35.1 Authenticating and authorizing the user . 16g35.2 Key derivation, management and

17、distribution 17g35.3 Protection of the transmitted traffic 17g36 Security mechanisms 18g36.1 Using GBA for MBMS 18g36.2 Authentication and authorisation of a user . 19g36.2.1 Authentication and authorisation in HTTP procedures . 19g36.2.1.1 General 19g36.2.1.2 Bootstrapping 19g36.2.1.3 HTTP digest a

18、uthentication . 19g36.2.2 Authentication and authorisation in MBMS bearer establishment . 20g36.2.3 Void 20g36.2.4 Void 20g36.3 Key management procedures . 20g36.3.1 General 20g36.3.2 MSK procedures . 20g36.3.2.1 MSK identification 20g36.3.2.1A MBMS User Service Registration procedure 21g36.3.2.1B M

19、BMS User Service Deregistration procedure . 24g36.3.2.2 MSK request procedures . 25g36.3.2.2.1 Basic MSK request procedure . 25g36.3.2.2.2 Void . 26g36.3.2.2.3 Missed key update procedure 26g36.3.2.2.4 BM-SC solicited pull procedure 26g36.3.2.3 MSK delivery procedures . 27g36.3.2.3.1 Pushing the MSK

20、 to the UE 27g36.3.2.3.2 Void . 27g36.3.2.4 Handling of multiple status codes within one response message 27g36.3.3 MTK procedures. 28g36.3.3.1 MTK identification 28g36.3.3.2 MTK update procedure . 29g3ETSI ETSI TS 133 246 V13.1.0 (2016-01)43GPP TS 33.246 version 13.1.0 Release 136.3.3.2.1 MTK deliv

21、ery in download . 29g36.3.3.2.2 MTK delivery in streaming . 29g36.3.4 Multiple BM-SC deployments 29g36.3.4.1 General 29g36.3.4.2 Service announcement coordination . 29g36.3.X.3 MSK key management anchor point . 29g36.3.4.4 MSK coordination . 29g36.3.4.5 MTK coordination . 30g36.3.4.6 MIKEY MTK times

22、tamp coordination . 30g36.4 MIKEY message creation and processing in the ME . 30g36.4.1 General 30g36.4.2 MIKEY common header . 31g36.4.3 Replay protection 31g36.4.4 General extension payload 31g36.4.5 MIKEY message structure 32g36.4.5.1 MSK message structure. 32g36.4.5.2 MSK Verification message st

23、ructure 34g36.4.5.3 MTK message structure 34g36.4.6 Processing of received messages in the ME . 35g36.4.6.1 MSK MIKEY Message Reception 35g36.4.6.2 MTK MIKEY Message Reception 35g36.5 Validation and key derivation functions in MGV-F . 36g36.5.1 General 36g36.5.2 Usage of MUK 36g36.5.3 MSK processing

24、 36g36.5.4 MTK processing . 36g36.6 Protection of the transmitted traffic 37g36.6.1 General 37g36.6.2 Protection of streaming data . 38g36.6.2.1 Usage of SRTP 38g36.6.2.1A Usage of SRTCP . 38g36.6.2.2 Packet processing in the UE 39g36.6.3 Protection of download data . 39g36.6.3.1 General 39g36.6.3.2

25、 Usage of OMA DRM DCF . 39g36.7 Confidentiality protection of associated delivery procedures . 40g36.7.1 General 40g36.7.2 TLS Profile . 40g36.7.3 HTTP server authentication 41g36.7.4 Authentication of the UE 41g3Annex A (informative): Trust model 42g3Annex B (informative): Security threats 43g3B.1

26、Threats associated with attacks on the radio interface . 43g3B.1.1 Unauthorised access to MBMS User Service data . 43g3B.1.2 Threats to integrity . 43g3B.1.3 Denial of service attacks . 43g3B.1.4 Unauthorised access to MBMS User Services . 43g3B.1.5 Privacy violation 44g3B.2 Threats associated with

27、attacks on other parts of the system . 44g3B.2.1 Unauthorised access to data 44g3B.2.2 Threats to integrity . 44g3B.2.3 Denial of service . 44g3B.2.4 A malicious UE generating MTKs for malicious use later on 44g3B.2.5 Unauthorised insertion of MBMS user data and key management data . 45g3Annex C (no

28、rmative): MBMS security requirements . 46g3C.1 Requirements on security service access 46g3C.1.1 Requirements on secure service access 46g3ETSI ETSI TS 133 246 V13.1.0 (2016-01)53GPP TS 33.246 version 13.1.0 Release 13C.1.2 Requirements on secure service provision . 46g3C.2 Requirements on MBMS Tran

29、sport Service signalling protection 46g3C.3 Requirements on Privacy 46g3C.4 Requirements on MBMS Key Management 47g3C.5 Requirements on integrity protection of MBMS User Service data . 47g3C.6 Requirements on confidentiality protection of MBMS User Service data . 48g3C.7 Requirements on content prov

30、ider to BM-SC reference point . 48g3Annex D (normative): UICC-ME interface . 49g3D.1 MSK Update Procedure 49g3D.2 Void 49g3D.3 MTK generation and validation . 49g3D.4 MSK deletion procedure 50g3D.5 MUK deletion procedure 50g3Annex E (Informative): MIKEY features not used in MBMS 51g3Annex F (normati

31、ve): MRK key derivation for ME based MBMS key management . 52g3Annex G (normative): HTTP based key management messages . 53g3G.1 Introduction 53g3G.2 Key management procedures . 53g3G.2.1 MBMS User Service Registration 53g3G.2.2 MBMS User Service Deregistration . 54g3G.2.3 MSK request . 54g3G.2.4 Er

32、ror situations . 55g3Annex H (informative): Signalling flows for MSK procedures 57g3H.1 Scope of signalling flows . 57g3H.2 Signalling flows demonstrating a successful MSK request procedure . 57g3H.2.1 Successful MSK request procedure 57g3Annex I (informative): Example of using MSKs and MTKs in MBMS

33、 . 61g3Annex J (informative): Mapping the MBMS security requirements into security functions and mechanism . 62g3J.1 Consistency check 62g3J.1.1 Requirements on secure service access . 62g3J.1.2 Requirements on MBMS transport Service signalling protection. 62g3J.1.3 Requirements on Privacy 63g3J.1.4

34、 Requirements on MBMS Key Management . 63g3J.1.5 Requirements on integrity protection of MBMS User Service data . 64g3J.1.6 Requirements on confidentiality protection of MBMS User Service data 64g3J.1.7 Requirements on content provider to BM-SC reference point 65g3J.2 Conclusions 65g3Annex K (Inform

35、ative): SRTP features not used in MBMS 66g3Annex L (Normative): Multicasting MBMS user data on Iub 67g3Annex M (informative): Relation to IMS based MBMS user services . 68g3Annex N (normative): GCSE security aspects . 69g3ETSI ETSI TS 133 246 V13.1.0 (2016-01)63GPP TS 33.246 version 13.1.0 Release 1

36、3N.0 GCSE architecture and requirements . 69g3N.1 GCSE security requirements 69g3N.1.1 General . 69g3N.1.2 GCSE Broadcast Delivery specific security requirements . 69g3N.2 Security solution for MB2-C interface . 69g3N.3 Security solution for MB2-U interface . 70g3Annex O (informative): Change histor

37、y . 71g3History 75g3ETSI ETSI TS 133 246 V13.1.0 (2016-01)73GPP TS 33.246 version 13.1.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 chang

38、e 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 presen

39、ted 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 t

40、he document. Introduction The security of MBMS provides different challenges compared to the security of services delivered over point-to-point services. In addition to the normal threat of eavesdropping, there is also the threat that it may not be assumed that valid subscribers have any interest in

41、 maintaining the privacy and confidentiality of the communications, and they may therefore conspire to circumvent the security solution (for example one subscriber may publish the decryption keys enabling non-subscribers to view broadcast content). Countering this threat requires the decryption keys

42、 to be updated frequently in a manner that may not be predicted by subscribers while making efficient use of the radio network. The stage 1 requirements for MBMS are specified in TS 22.146 2. ETSI ETSI TS 133 246 V13.1.0 (2016-01)83GPP TS 33.246 version 13.1.0 Release 131 Scope The Technical Specifi

43、cation covers the security procedures of the Multimedia Broadcast/Multicast Service (MBMS) for 3GPP systems (UTRAN, GERAN and E-UTRAN). MBMS is a 3GPP system network bearer service over which many different applications could be carried. The actual method of protection may vary depending on the type

44、 of MBMS application. 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 specifi

45、c 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 doc

46、ument. 1 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS 22.146: “Multimedia Broadcast/Multicast Service; Stage 1“. 3 3GPP TS 23.246: “Multimedia Broadcast/Multicast Service (MBMS); Architecture and Functional Description“. 4 3GPP TS 33.102: “3G Security; Security Architecture“. 5 3G

47、PP TS 22.246: “MBMS User Services“. 6 3GPP TS 33.220: “Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture“. 7 3GPP TS 31.102: “Characteristics of the USIM application“. 8 IETF RFC 2617 “HTTP Digest Authentication“. 9 IETF RFC 3830 “MIKEY: Multimedia Internet KEYing“ 10 IET

48、F RFC 1982 “Serial Number Arithmetic“. 11 IETF RFC 3711 “Secure Real-time Transport Protocol“. 12 3GPP TS 43.020: “Security related network functions“. 13 3GPP TS 26.346: “Multimedia Broadcast/Multicast Service; Protocols and Codecs“. 14 3GPP TS 33.210: “Network domain security; IP network layer sec

49、urity“. 15 OMA-DRM-DCF-v2_0: “OMA DRM Content Format“, www.openmobilealliance.org 16 IETF RFC 4563 “The Key ID Information Type for the General Extension Payload in Multimedia Internet KEYing (MIKEY)“. 17 Port numbers at IANA, http:/www.iana.org/assignments/port-numbers. 18 3GPP TS 24.109: “3rd Generation Partnership Project; Technical Specification Group Core Network; Bootstrapping interface (Ub) and network application function interface (Ua); Protocol details“. 19 IETF RFC 2616 “ Hypertext Transfer Protocol - HTTP/1.1“. ETSI ET