1、 ETSI TS 122 185 V14.3.0 (2017-03) LTE; Service requirements for V2X services (3GPP TS 22.185 version 14.3.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 122 185 V14.3.0 (2017-03)13GPP TS 22.185 version 14.3.0 Release 14Reference DTS/TSGS-0122185ve30 Keywords LTE ETSI 650 Route des Lucioles F-06
2、921 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 downloaded from: http:/www.etsi.org/standards-searc
3、h 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
4、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
5、 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/People/CommiteeSupportStaff.aspx Copyright Notifi
6、cation 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 a
7、nd the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2017. All rights reserved. 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 register
8、ed 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 122 185 V14.3.0 (2017-03)23GPP TS 22.185 version 14.3.0 Release 14Intellectual Property Rights IPRs essential or potentially essen
9、tial 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 notifi
10、ed 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
11、 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 The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities o
12、r 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 terminology In the present document “shall“, “shall not“,
13、“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 citatio
14、n. ETSI ETSI TS 122 185 V14.3.0 (2017-03)33GPP TS 22.185 version 14.3.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 5g34 Overview on V2
15、X (informative) 6g34.1 Types of V2X application support in 3GPP . 6g34.1.1 General 6g34.1.2 Vehicle-to-Vehicle (V2V) application 6g34.1.3 Vehicle-to-Infrastructure (V2I) application 7g34.1.4 Vehicle-to-Network (V2N) application 7g34.1.5 Vehicle-to-Pedestrian (V2P) application 7g34.2 Relative priorit
16、y of V2X communication . 8g35 Requirements 8g35.1 Overall Requirements . 8g35.2 Specific Service Requirements . 9g35.2.1 Latency/ Reliability Requirements . 9g35.2.2 Message Size Requirements . 9g35.2.3 Frequency Requirements 9g35.2.4 Range Requirements . 9g35.2.5 Speed Requirements . 9g35.3 Securit
17、y Requirements . 10g3Annex A (informative): Background Information on Service Requirement 11g3Annex B (informative): Change history . 14g3History 15g3ETSI ETSI TS 122 185 V14.3.0 (2017-03)43GPP TS 22.185 version 14.3.0 Release 14Foreword This Technical Specification (TS) has been produced by ETSI 3r
18、d 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 releas
19、e 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. te
20、chnical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TS 122 185 V14.3.0 (2017-03)53GPP TS 22.185 version 14.3.0 Release 141 Scope The present document provides 3GPP support for V2X service requ
21、irements to be supported by LTE transport. These requirements are identified by taking into account the V2X service requirements defined in other SDOs, e.g. ETSI ITS, US SAE. The specification includes requirements of safety and non-safety aspects. 2 References The following documents contain provis
22、ions which, through reference in this text, constitute provisions of the present document.- 1 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TR 22.885: “Study on LTE Support for V2X Services“. 3 ETSI TR 102 638 V1.1.1: “Intelligent Transport Systems (ITS); Vehicular Communications; Bas
23、ic Set of Applications; Definitions“. 3 Definitions and abbreviations 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, i
24、f any, in 3GPP TR 21.905 1. Road Side Unit: A stationary infrastructure entity supporting V2X applications that can exchange messages with other entities supporting V2X applications. NOTE: RSU is a term frequently used in existing ITS specifications, and the reason for introducing the term in the 3G
25、PP specifications is to make the documents easier to read for the ITS industry. RSU is a logical entity that combines V2X application logic with the functionality of an eNB (referred to as eNB-type RSU) or UE (referred to as UE-type RSU). Pseudonymity: The condition when the processing of personally
26、 identifiable information is such the data can no longer be attributed to a specific subscriber without the use of additional information, as long as such additional information is kept separately and subject to technical and organisational measures to ensure non-attribution to an identified or iden
27、tifiable subscriber. 3.2 Abbreviations For the purposes 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. RSU Road S
28、ide Unit V2I Vehicle-to-Infrastructure V2N Vehicle-to-Network V2P Vehicle-to-Pedestrian V2V Vehicle-to-Vehicle V2X Vehicle-to-EverythingETSI ETSI TS 122 185 V14.3.0 (2017-03)63GPP TS 22.185 version 14.3.0 Release 144 Overview on V2X (informative) 4.1 Types of V2X application support in 3GPP 4.1.1 Ge
29、neral The V2X applications in the present specification, referred to as Vehicle-to-Everything (V2X), contain the following four different types: - Vehicle-to-Vehicle (V2V) - Vehicle-to-Infrastructure (V2I) - Vehicle-to-Network (V2N) - Vehicle-to-Pedestrian (V2P) Figure 4.1.1-1: Types of V2X applicat
30、ions (V2V, V2P, V2N and V2I) These four types of V2X applications can use g256co-operative awarenessg257 to provide more intelligent services for end-users. This means that entities, such as vehicles, roadside infrastructure, application server and pedestrians, can collect knowledge of their local e
31、nvironment (e.g., information received from other vehicles or sensor equipment in proximity) to process and share that knowledge in order to provide more intelligent services, such as cooperative collision warning or autonomous driving. These intelligent transportation services and the associated me
32、ssage sets have been defined in automotive SDOs outside 3GPP. Three basic classes of applications for providing ITS services: road safety, traffic efficiency, and other applications can be found in e.g., 3. 3GPP only handles the transport of these messages to support different types of V2X applicati
33、ons. The message transport expectations are described in requirements defined in this specification. 4.1.2 Vehicle-to-Vehicle (V2V) application V2V applications expect UEs that are in proximity of each other to exchange V2V application information. 3GPP transport of messages containing V2V applicati
34、on information requires the UE to have a valid subscription and authorization from a network operator. Transport for a valid subscriber is provided whether the UE is served or not served by E-UTRAN. The UE supporting V2V applications transmits messages containing V2V application information (e.g. lo
35、cation, dynamics, and attributes). The message payloads may be flexible in order to accommodate varying amount of information. ETSI ETSI TS 122 185 V14.3.0 (2017-03)73GPP TS 22.185 version 14.3.0 Release 143GPP transport of message containing V2V application information is predominantly broadcast-ba
36、sed as illustrated in Figure 4.1-2. Such 3GPP transport includes the transport between UEs directly and/or, due to the limited direct communication range, the transport between UEs via infrastructure supporting V2X communication, e.g., RSU, application server, etc. Tx UECommunication rangeMessagebro
37、adcastingRx UERx UERx UEFigure 4.1.2-1: Broadcast-based V2V communications 4.1.3 Vehicle-to-Infrastructure (V2I) application The UE supporting V2I applications transmits messages containing V2I application information to an RSU or locally relevant application server. The RSU and/or the locally relev
38、ant application server transmit messages containing V2I application information to one or more UEs supporting V2I applications. A locally relevant application server serves a particular geographic area. There can be multiple application servers serving overlapping areas, providing the same or differ
39、ent applications. 4.1.4 Vehicle-to-Network (V2N) application The UE supporting V2N applications communicates with an application server supporting V2N applications. Both parties communicate with each other via EPS. 4.1.5 Vehicle-to-Pedestrian (V2P) application V2P applications expect UEs that are in
40、 proximity of each other to exchange V2P application information. 3GPP transport of messages containing V2P application information requires the UE to have a valid subscription and authorization from a network operator. Transport for a valid subscriber is provided whether the UE is served or not ser
41、ved by E-UTRAN. The UE supporting V2P applications transmits messages containing V2P application information. It is expected that V2P application information can be transmitted either by a UE supporting V2X application in a vehicle (e.g., warning to pedestrian), or by a UE supporting V2X application
42、 associated with a vulnerable road user (e.g., warning to vehicle). 3GPP transport of messages containing V2P application information includes the transport between UEs directly and/or, due to the limited direct communication range, the transport between UEs via infrastructure supporting V2X communi
43、cation, e.g., RSU, application server, etc. NOTE: The main difference between 3GPP transport of messages with V2P and V2V application information is due to the properties of the UE. A UE supporting V2P applications used by pedestrian might, for example, have lower battery capacity, the radio sensiti
44、vity might be limited, e.g. due to antenna design, and therefore it may not be able to send messages with the same periodicity as UEs supporting V2V application, and/or receive messages. ETSI ETSI TS 122 185 V14.3.0 (2017-03)83GPP TS 22.185 version 14.3.0 Release 144.2 Relative priority of V2X commu
45、nication Subject to regional/national regulatory requirements and operator policies, certain mission critical services (e.g. Public Safety, MPS) can be relatively prioritized over transport of V2X application information. Transport of safety-related V2X application information can be prioritized ove
46、r transport of non-safety-related V2X application information. However, in general, it is expected that operator can control relative priorities of different services. 5 Requirements 5.1 Overall Requirements R-5.1-001 The message transmission shall be under control of the 3GPP network when the trans
47、mitting UE is served by the E-UTRAN. R-5.1-002 A UE supporting V2X application shall be able to be pre-configured by the 3GPP network with parameters to be used for the transmission and reception of messages when not served by E-UTRAN supporting V2X communication. R-5.1-003 A UE supporting V2X appli
48、cation shall be able to transmit and receive messages when served or not served by E-UTRAN supporting V2X communication. R-5.1-004 An RSU shall be able to transmit/receive messages to/from a UE supporting V2X application. R-5.1-005 The 3GPP system shall be able to support message transfer between UE
49、s when served or not served by the same PLMN supporting V2X communications. R-5.1-006 The 3GPP system shall be able to provide means to prioritize message transmission among UEs supporting V2X application R-5.1-007 The 3GPP system shall be able to provide means to prioritize transmission of messages according to their type (e.g. safety vs. non-safety). R-5.1-008 The 3GPP system shall be able to vary the transmission rate and range of the V2X communication based on service conditions (e.g., UE speed, UE density). R-5.1-009 The 3GPP system sha
