1、 ETSI TS 133 185 V15.0.0 (2018-07) LTE; 5G; Security aspect for LTE support of Vehicle-to-Everything (V2X) services (3GPP TS 33.185 version 15.0.0 Release 15) TECHNICAL SPECIFICATION ETSI ETSI TS 133 185 V15.0.0 (2018-07)13GPP TS 33.185 version 15.0.0 Release 15Reference RTS/TSGS-0333185vf00 Keyword
2、s 5G,LTE,SECURITY 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 (06) N 7803/88 Important notice The present document can be d
3、ownloaded 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 without the prior written authorization of ETSI. In case of any exi
4、sting 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 su
5、bject to revision or change of status. Information on the current status of this and other ETSI documents is available at https:/portal.etsi.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
6、/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 content of the PDF version shall not be modified without
7、the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. ETSI 2018. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI registered for the benefit of its Members. 3GPPTM and LTETMare trademarks of ETSI re
8、gistered for the benefit of its Members and of the 3GPP Organizational Partners. oneM2M logo is protected for the benefit of its Members. GSMand the GSM logo are trademarks registered and owned by the GSM Association. ETSI ETSI TS 133 185 V15.0.0 (2018-07)23GPP TS 33.185 version 15.0.0 Release 15Int
9、ellectual Property Rights Essential patents IPRs essential or potentially essential to normative deliverables 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: “Inte
10、llectual 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, incl
11、uding 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. Trademarks The present document may include
12、trademarks and/or tradenames which are asserted and/or registered by their owners. ETSI claims no ownership of these except for any which are indicated 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 d
13、ocument does not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks. Foreword This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or re
14、ports 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 http:/webapp.etsi.org/key/queryform.asp. Modal verbs termin
15、ology 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
16、ETSI deliverables except when used in direct citation. ETSI ETSI TS 133 185 V15.0.0 (2018-07)33GPP TS 33.185 version 15.0.0 Release 15Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 6g33.1 De
17、finitions 6g33.2 Abbreviations . 6g34 V2X security architecture . 6g35 V2X security requirements . 6g35.1 General . 6g35.2 Interfaces between network elements . 6g35.3 Interface between UE and V2X control function (V3) . 7g35.4 Interface between external provider and 3GPP network (MB2) 7g35.5 Securi
18、ty requirements of V2X application data 7g35.6 Privacy related requirements 7g35.7 Security requirement for V2X Entities Secure Environment . 7g36 V2X security solutions . 8g36.1 General . 8g36.2 V2X communication between network elements . 8g36.2.1 General 8g36.2.2 Security procedures. 8g36.3 V2X c
19、ommunication between UE and V2X Control Function (V3) 8g36.3.1 General 8g36.3.2 Security procedures for configuration transfer to the UICC . 8g36.3.3 Security procedures for data transfer to the UE 8g36.4 Interface between V2X application server and 3GPP network (MB2) . 9g36.5 Security of V2X applic
20、ation data . 9g36.5.1 General 9g36.5.2 Security procedures. 9g36.6 Privacy in V2X services . 9g36.6.1 General 9g36.6.2 Privacy procedures related to PC5 transmissions . 10g3Annex A (informative): Change history . 11g3History 12g3ETSI ETSI TS 133 185 V15.0.0 (2018-07)43GPP TS 33.185 version 15.0.0 Re
21、lease 15Foreword This Technical Specification has been produced by the 3rd 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 documen
22、t, 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
23、. 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 ETSI TS 133 185 V15.0.0 (2018-07)53GPP TS 33.185 version 15.0.0 Release
24、151 Scope The present document specifies the security aspects of V2X features in LTE, including security architecture, security requirements on the network entities that are used to support V2X services, as well as the procedures and solutions which are provided to meet those requirements. 2 Referen
25、ces 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 revi
26、sions 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: “
27、Vocabulary for 3GPP Specifications“. 2 3GPP TS 22.185: “Service requirements for V2X services“. 3 3GPP TS 23 285: “Architecture enhancements for V2X services (Release 14)“. 4 3GPP TS 33.210: “3G security; Network Domain Security (NDS); IP network layer security“. 5 3GPP TS 33.310: “Network Domain Se
28、curity (NDS); Authentication Framework (AF)“. 6 ETSI TS 102 225: “Smart Cards; Secured packet structure for UICC based applications“. 7 ETSI TS 102 226: “Smart cards; Remote APDU structure for UICC based applications“. 8 3GPP TS 31.115: “Secured packet structure for (Universal) Subscriber Identity M
29、odule (U)SIM Toolkit applications“. 9 3GPP TS 31.116: “Remote APDU Structure for (U)SIM Toolkit applications “. 10 3GPP TS 33.303: “Proximity-based Services (ProSe); Security aspects“. 11 3GPP TS 29.368: “Tsp interface protocol between the MTC Interworking Function (MTC-IWF) and Service Capability S
30、erver (SCS)“. 12 3GPP TS 33.401: “3GPP System Architecture Evolution (SAE): Security Architecture“. 13 3GPP TS 33.223: “Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA) Push function“. 14 3GPP TS 23.468: “Group Communication System Enablers for LTE (GCSE_LTE); Stag
31、e 2“. 15 3GPP TS 33.246: “3G Security; Security of Multimedia Broadcast/Multicast Service (MBMS)“. 16 IEEE Std 1609.2-2016: “IEEE Standard for Wireless Access in Vehicular Environments (WAVE)Security Services for Applications and Management Messages“. 17 ETSI TS 102 940: “Intelligent Transport Syste
32、ms (ITS); Security; ITS communications security architecture and security management“ (V1.2.1; 2016-11). 18 3GPP TS 33.402: “3GPP System Architecture Evolution; Security aspects of non-3GPP accesses“. ETSI ETSI TS 133 185 V15.0.0 (2018-07)63GPP TS 33.185 version 15.0.0 Release 153 Definitions and ab
33、breviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in 3GPP 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 3GPP TR 21.905 1. 3.2 Abbreviations For the purp
34、oses of the present document, the abbreviations given in 3GPP 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 3GPP TR 21.905 1. AS Application Server BSF Bootstrapping Server Function GBA G
35、eneric Bootstrapping Architecture GCS Group Communication System ITS Intelligent Transportation System LTE-V LTE V2X NAF Network Application Function ProSe Proximity-based Services V2I Vehicle-to-InfrastructureV2N Vehicle-to-Network V2P Vehicle-to-Pedestrian V2V Vehicle-to-Vehicle V2X Vehicle-to-Eve
36、rythingVCF V2X Control Function 4 V2X security architecture V2X service contains three types of vehicular communication services V2V (vehicle to vehicle), V2I (vehicle to infrastructure), V2N (vehicle to network), and V2P (vehicle to pedestrian) for both safety and non-safety aspects. The overall ar
37、chitecture describing LTE enhancements for V2X services is given in TS 23.285 3. Both LTE-Uu based architecture (e.g. eMBMS) and PC5 based architecture are used for supporting V2X services, but they may be used by a UE independently for transmission and reception, e.g. a UE can use eMBMS for recepti
38、on without using LTE-Uu for transmission. The security for interfaces given in the overall architecture (TS 23.285 3) is provided in clause 6, in detail these are the interfaces between network entities (clause 6.2), between UE and V2X Control Function (clause 6.3), and between V2X AS and 3GPP syste
39、m (clause 6.4). Clause 6.5 discusses security of V2X application data. Clause 6.6 is providing details to privacy in V2X services. Note: The V2 interface is not specified in 3GPP TS 23.285 3, thus out of scope also in the present document. 5 V2X security requirements 5.1 General The service requirem
40、ents for V2X services are specified in 3GPP TS 22.185 2. This clause contains the security requirements for V2X. 5.2 Interfaces between network elements The V2X network entities shall be able to authenticate the source of the received data communications. The transmission of data between V2X network
41、 entities shall be integrity protected. ETSI ETSI TS 133 185 V15.0.0 (2018-07)73GPP TS 33.185 version 15.0.0 Release 15The transmission of data between V2X network entities shall be confidentiality protected. The transmission of data between V2X network entities shall be protected from replays. 5.3
42、Interface between UE and V2X control function (V3) The V2X enabled UE and its HPLMN V2X Control Function shall mutually authenticate each other. The transmission of configuration data between the V2X Control Function and the UE shall be integrity protected. The transmission of configuration data bet
43、ween the V2X Control Function and the UE shall be confidentiality protected. The transmission of configuration data between the V2X Control Function and the UE shall be protected from replays. The transmission of UE identity should be confidentiality protected on the V3 interface. 5.4 Interface betw
44、een external provider and 3GPP network (MB2) V2X services use the MB2 interface for GCSE. The requirements to MB2 as listed in Annex N.1.2 of 3GPP TS 33.246 shall apply. 5.5 Security requirements of V2X application data The V2X system entities should be able to authenticate and verify that the sende
45、r of the received data communications was authorized to send the data. The transmission of data between different V2X entities in the V2X system should be integrity protected. The transmission of data between different V2X entities in the V2X system should be protected from replays. The transmission
46、 of data between two different V2X entities in the V2X system should be confidentiality protected if needed for the V2X application. NOTE: Transmission of data includes but is not limited to multicast, broadcast, unicast, or geocast. 5.6 Privacy related requirements As specified in 3GPP TS 22.185 2
47、the following PC5 privacy related requirements apply: Subject to regional regulatory requirements and/or operator policy for a V2X application, the data sent in the PC5 transmission should not allow UE identity to be tracked or identified by any other UE or non-V2X entity beyond a certain short time
48、-period required by the V2X application. Subject to regional regulatory requirements and/or operator policy for a V2V/V2I application, the data sent in the PC5 transmission should not allow a single party (operator or third party) to track a UE identity in that region. In addition, the following PC5
49、 related requirements are given in the present specification: The identifiers in the V2X messages should minimize the risk of leaking the UE or user permanent identities. UE pseudonymity should be provided to conceal personal data from attackers. The application layer UE identity in the V2X messages should be protected from eavesdropping. 5.7 Security requirement for V2X Entities Secure Environment For V2X services relying on access networks within the scope of TS 33.401 12, the 3GPP authentication, key agreem
