1、 ETSI TS 122 185 V14.4.0 (2018-07) LTE; Service requirements for V2X services (3GPP TS 22.185 version 14.4.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 122 185 V14.4.0 (2018-07)13GPP TS 22.185 version 14.4.0 Release 14Reference RTS/TSGS-0122185ve40 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. 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 registered for the benefit of its Members and of the
8、 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 122 185 V14.4.0 (2018-07)23GPP TS 22.185 version 14.4.0 Release 14Intellectual Property Rights Essential patents IPRs e
9、ssential 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: “Intellectual Property Rights (IPRs); Essential, or pot
10、entially 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.
11、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 trademarks and/or tradenames which are asserted an
12、d/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 document does not constitute an endorsement by ETSI
13、 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 reports using their 3GPP identities, UMTS identities
14、 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 terminology In the present document “shall“, “shall not“
15、, “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 citat
16、ion. ETSI ETSI TS 122 185 V14.4.0 (2018-07)33GPP TS 22.185 version 14.4.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
17、V2X (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 prior
18、ity 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 Secur
19、ity Requirements . 9g3Annex A (informative): Background Information on Service Requirement . 11g3Annex B (informative): Change history . 14g3History 15g3ETSI ETSI TS 122 185 V14.4.0 (2018-07)43GPP TS 22.185 version 14.4.0 Release 14Foreword This Technical Specification has been produced by the 3rdGe
20、neration 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 da
21、te 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. techni
22、cal 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.4.0 (2018-07)53GPP TS 22.185 version 14.4.0 Release 141 Scope The present document provides 3GPP support for V2X service requirem
23、ents 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 provisions
24、 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; Basic S
25、et 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, if an
26、y, 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 3GPP s
27、pecifications is to make the documents easier to read for the ITS industry. RSU is a logical entity that supports V2X application logic using the functionality provided by either a 3GPP network or an UE (referred to as UE-type RSU). Pseudonymity: The condition when the processing of personally ident
28、ifiable 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 identifiab
29、le 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 Side Un
30、it 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.4.0 (2018-07)63GPP TS 22.185 version 14.4.0 Release 144 Overview on V2X (informative) 4.1 Types of V2X application support in 3GPP 4.1.1 General
31、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 applications (
32、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 environ
33、ment (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 message
34、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 applications. T
35、he 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 application inf
36、ormation 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. location
37、, dynamics, and attributes). The message payloads may be flexible in order to accommodate varying amount of information. ETSI ETSI TS 122 185 V14.4.0 (2018-07)73GPP TS 22.185 version 14.4.0 Release 143GPP transport of message containing V2V application information is predominantly broadcast-based as
38、 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. Figure 4.1.2-1: Broadcast-based V2V comm
39、unications 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 relevant application server transmit messages containing V2I applicat
40、ion 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 different applications. 4.1.4 Vehicle-to-Network (V2N) application The
41、 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 proximity of each other to exchange V2P application information
42、. 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 served by E-UTRAN. The UE supporting V2P applications transmits mes
43、sages 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 associated with a vulnerable road user (e.g., warning to vehicl
44、e). 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 communication, e.g., RSU, application server, etc. NOTE: The main diffe
45、rence 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 sensitivity might be limited, e.g. due to antenna design, and therefore
46、 it may not be able to send messages with the same periodicity as UEs supporting V2V application, and/or receive messages. uni0054uni0078uni0020uni0055uni0045uni0043uni006Funi006Duni006Duni0075uni006Euni0069uni0063uni0061uni0074uni0069uni006Funi006Euni0020uni0072uni0061uni006Euni0067uni0065uni004Dun
47、i0065uni0073uni0073uni0061uni0067uni0065uni0062uni0072uni006Funi0061uni0064uni0063uni0061uni0073uni0074uni0069uni006Euni0067uni0052uni0078uni0020uni0055uni0045uni0052uni0078uni0020uni0055uni0045uni0052uni0078uni0020uni0055uni0045ETSI ETSI TS 122 185 V14.4.0 (2018-07)83GPP TS 22.185 version 14.4.0 Re
48、lease 144.2 Relative priority of V2X communication 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 appl
49、ication information can be prioritized over 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 transmitting 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 ser