TS 22.186 V1.0.1 (2017-03) Enhancement of 3GPP Support for V2X Scenarios

《TS 22.186 V1.0.1 (2017-03) Enhancement of 3GPP Support for V2X Scenarios》由會(huì)員分享，可在線閱讀，更多相關(guān)《TS 22.186 V1.0.1 (2017-03) Enhancement of 3GPP Support for V2X Scenarios（16頁珍藏版）》請(qǐng)?jiān)谘b配圖網(wǎng)上搜索。

3GPP TS 22.186 V1.0.1 (2017-03) Technical Specification 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Enhancement of 3GPP Support for V2X Scenarios; Stage 1 (Release 15) The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP.. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organizational Partners Publications Offices. 3GPP TS 22.186 V1.0.1 (2017-03) 16 Release 15 Keywords Vehicle-to-Everything, V2X, eV2X, Vehicular communication 3GPP Postal address 3GPP support office address 650 Route des Lucioles - Sophia Antipolis Valbonne - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Internet http://www.3gpp.org Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. 2017, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). All rights reserved. UMTS? is a Trade Mark of ETSI registered for the benefit of its members 3GPP? is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners LTE? is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners GSM and the GSM logo are registered and owned by the GSM Association Contents Foreword 4 1 Scope 5 2 References 5 3 Definitions, symbols and abbreviations 5 3.1 Definitions 5 3.2 Abbreviations 6 4 Overview 6 4.1 Categories of requirements to support eV2X scenarios 6 5 Requirements 7 5.1 General Requirements 7 5.2 Requirements to support Vehicles Platooning 8 5.3 Requirements to support Advanced Driving 10 5.4 Requirements to support Extended Sensors 11 5.5 Requirements to support Remote Driving 11 Annex A (informative): Background information on service Requirements 12 Annex B (informative): Relation between TS 22.185 and this TS 14 Annex C (informative): Relationship between V2X applications and V2X requirements 15 Annex D (informative): Change history 17 Foreword 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 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. 1 Scope The present document specifies service requirements to enhance 3GPP support for V2X scenarios in the 3GPP systems (i.e. EPS, 5G). It includes transport layer support for both safety and non-safety V2X scenarios: - Safety-related V2X scenarios: e.g. automated driving, vehicle platooning - Non-safety-related V2X scenarios: e.g., mobile high data rate entertainment, mobile hotspot/office/home, dynamic digital map update 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 nonspecific. - 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] 3GPPTR21.905: "Vocabulary for 3GPP Specifications". [2] 3GPPTS 22.261: "Service requirements for the 5G system". [3] 3GPPTS 22.185: "Service requirements for V2X services". [4] SAE International, "AUTOMATED DRIVING LEVELS OF DRIVING AUTOMATION ARE DEFINED IN NEW SAE INTERNATIONAL STANDARD J3016", December 2016, https://www.sae.org/misc/pdfs/automated_driving.pdf 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in 3GPP TR21.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 TR21.905[1]. End-to-end latency: Time it takes to transfer a given piece of information from a source to a destination, measured at the application level, from the moment it is transmitted by the source to the moment it is received at the destination. Reliability (%): The success probability of transmitting X bytes within a certain delay, which is the time it takes to deliver a small data packet from the radio protocol layer 2/3 SDU ingress point to the radio protocol layer 2/3 SDU egress point of the radio interface. 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 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). 3.2 Abbreviations For the purposes of the present document, the abbreviations given in 3GPP TR21.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 TR21.905[1]. LoA Level of Automation RSU Road Side Unit 4 Overview 4.1 Categories of requirements to support eV2X scenarios Different V2X scenarios require the transport of V2X messages with different performance requirements for the 3GPP system. This Technical Specification specifies service requirements to enhance 3GPP support for V2X scenarios in the following five areas: - General Aspects: interworking, communication-related requirements valid for all V2X scenarios - Vehicle Platooning - Advanced Driving - Extended Sensors - Remote Driving Vehicles Platooning enables the vehicles to dynamically form a group travelling together. All the vehicles in the platoon receive periodic data from the leading vehicle, in order to carry on platoon operations. This information allows the the distance between vehicles to become extremely small, i.e., the gap distance translated to time can be very low (sub second). Platooning applications may allow the vehicles following to be autonomously driven. Advanced Driving enables semi-automated or fully-automated driving. Longer inter-vehicle distance is assumed. Each vehicle and/or RSU shares data obtained from its local sensors with vehicles in proximity, thus allowing vehicles to coordinate their trajectories or maneuvers. In addition, each vehicle shares its driving intention with vehicles in proximity. The benefits of this use case group are safer traveling, collision avoidance, and improved traffic efficiency. Extended Sensors enables the exchange of raw or processed data gathered through local sensors or live video data among vehicles, Road Site Units, devices of pedestrians and V2X application servers. The vehicles can enhance the perception of their environment beyond what their own sensors can detect and have a more holistic view of the local situation. Remote Driving enables a remote driver or a V2X application to operate a remote vehicle for those passengers who cannot drive themselves or a remote vehicle located in dangerous environments. For a case where variation is limited and routes are predictable, such as public transportation, driving based on cloud computing can be used. In addition, access to cloud-based back-end service platform can be considered for this use case group. 4.2 Level of Automation A relevant aspect of advanced V2X applications is the Level of Automation (LoA), which reflects the functional aspects of the technology and affects the system performance requirements. In accordance with the levels from SAE [4], the LoA are: 0 – No Automation, 1 – Driver Assistance, 2 – Partial Automation, 3 – Conditional Automation, 4 – High Automation, 5 – Full Automation. A distinction is drawn between lower levels and higher levels based on whether the human operator or the automated system is primarily responsible for monitoring the driving environment. The 3GPP system provides the performances expected for all levels of automation 5 Requirements 5.1 General Requirements [R.5.1-001] The 3GPP system shall be able to control the communication range for a message based on the characteristic of the messages transmitted by a UE supporting V2X application. [R.5.1-002] The 3GPP system shall be able to optimize the communication between UEs supporting V2X application belonging to the same group and in proximity. [R.5.1-003] The 3GPP system shall be able to support the message transfer for group management operations as requested by the application layer. NOTE 1: The determination of group membership may be done at the upper layers and/or lower layers (application and/or Layer 2). [R.5.1-004] The 3GPP system shall be able to support message transfer among a group of UEs supporting V2X application. [R.5.1-005] The 3GPP system shall be able to support message transfer between two UEs belonging to the same group of UEs supporting V2X application. [R.5.1-006] The 3GPP system shall be able to support confidentiality and integrity of message transfer among a group of UEs supporting V2X application. [R.5.1-007] The 3GPP system shall support relative lateral position accuracy of 0.1 m between UEs supporting V2X application. [R.5.1-008] The 3GPP system shall support high connection density for congested traffic. NOTE 2: Example estimate is for worst case US Freeway scenario that does not include arterial roads (i.e. onramps): 5 lanes in each direction or 10 lanes total per highway, for up to 3 highways intersecting = 3,100 to 4,300 cars per square kilometer [R.5.1-009] The 3GPP system shall support efficient coordination of radio resources used for transport of messages to maximize the utilization of the available spectrum and to ensure the required reliability. [R.5.1-010] The 3GPP system shall be able to control the UL and DL reliability of transport of V2X communications, depending on the requirement of V2X application [R.5.1-011] Impact to E-UTRA(N) by UE supporting only NR based V2X communication shall be minimized. [R.5.1-012] Impact to NR by UE supporting only E-UTRA based V2X communication shall be minimized. [R.5.1-013] The 3GPP system shall be able to support message transfer between UEs or between a UE and a UE-type RSU, regardless of whether or not they are subscribers of the same PLMN supporting V2X communications. In case they are subscribers to different PLMNs, there shall be no service degradation of the message transfer. [R.5.1-014] The 3GPP system shall enable discovery and communication between UEs supporting the same V2X application. [R.5.1-015] The 3GPP system shall be able to support the operators to select which 3GPP RAT to use for a V2X application. Editor’s note: The meaning of V2X application needs further clarification [R.5.1-016] The 3GPP system shall enable a UE supporting a V2X application to obtain network access via another UE supporting V2X application. [R.5.1-017] The 3GPP system shall enable a UE supporting a V2X application to discover another UE supporting V2X application that can offer access to the network. [R.5.1-018] The 3GPP system shall support switching between direct 3GPP connection and indirect 3GPP connection via a UE supporting a V2X application, for a UE supporting a V2X application. [R.5.1-019] The 3GPP system should be able to support confidentiality and integrity of message transfer between a UE supporting a V2X application and network, when the UE is using an indirect 3GPP connection. [R.5.1-020] The 3GPP system shall allow UEs supporting V2X application to use NR for direct communication when the UEs are not served by a RAN using NR. [R.5.1-021] The 3GPP system shall allow UEs supporting V2X application to use E-UTRA for direct communication when the UEs are not served by a RAN using E-UTRA. [R.5.1-022] An RSU shall be able to communicate with up to 200 UEs supporting a V2X application. NOTE 3: This requirement specifies the number of UEs that RSU should be capable of handling. The requirement is not applied to the number of UE in a platoon. NOTE 4: This requirement does not applied to UE type RSU. [R.5.1-023] The 3GPP system shall be able to support confidentiality and integrity of message transfer between a UE supporting V2X application and a V2X application server. 5.2 Requirements to support Vehicles Platooning [R.5.2-001] The 3GPP system shall be able to support up to 5 UEs for a group of UEs supporting V2X application. [R.5.2-002] For Vehicle Platooning, the 3GPP system shall be able to support reliable V2V communications between a specific UE supporting V2X applications and up to 19 other UEs supporting V2X applications. NOTE 1: For group of heavy goods vehicle platooning, the number of UEs in a platoon can be smaller, due to communication range, the length of truck, inter-truck distance, etc. [R.5.2-003] The 3GPP system shall support relative longitudinal position accuracy of less than 0.5 m for UEs supporting V2X application for platooning in proximity. Table 5.2-1 Performance requirements for Vehicles Platooning Communication scenario description Req # Payload (Bytes) Tx rate (Message/ Sec) Max end-to-end latency (ms) Reliability (%) (NOTE 4) Data rate (Mbps) Min required communication range (meters) (NOTE 6) Scenario Degree Cooperative driving for vehicle platooning Information exchange between a group of UEs supporting V2X application. Lowest degree of automation [R.5.2-004] 300-400 (NOTE 1) 30 25 90 Low degree of automation [R.5.2-005] 6500 (NOTE 2) 50 20 350m Highest degree of automation [R.5.2-006] 50-1200 (NOTE 3) 30 10 99.99 80 High degree of automation [R.5.2-007] 20 [65] (NOTE 2) 180m Reporting needed for platooning between UEs supporting V2X application and between a UE supporting V2X application and RSU. N/A [R.5.2-008] 50-1200 2 500 Information sharing for platooning between UE supporting V2X application and RSU. Lower degree of automation [R.5.2-009] 6000 (NOTE 2) 50 20 350m Higher degree of automation [R.5.2-0010] 20 [50] (NOTE 2) 180m NOTE 1: This value is applicable for both triggered and periodic transmission of data packets. NOTE 2: The data that is considered in this V2X scenario includes both cooperative manoeuvres and cooperative perception data that could be exchanged using two separate messages within the same period of time (e.g., required latency 20ms). NOTE 3: This value does not including security related messages component. NOTE 4: Sufficient reliability should be provided even for cells having no value in this table NOTE 5: The naming used in column degree is specific to the scenario. NOTE 6: This is obtained considering UE speed of 130km/h 5.3 Requirements to support Advanced Driving Table 5.3-1 Performance requirements for advanced driving Communication scenario description Req # Payload (Bytes) Tx rate (Message/Sec) Max end-to-end latency (ms) Reliability (%) (NOTE3) Data rate (Mbps) Min required Communication range (meters) Scenario Degree Cooperative collision avoidance between UEs supporting V2X applications. [R.5.3-001] 2000 10 99.99 10 Information sharing for automated driving between UEs supporting V2X application. Lower degree of automation [R.5.3-002] 6500 (NOTE 1) 10 100 [700] Higher degree of automation [R.5.3-003] 100 53 (NOTE 1) [360] Information sharing for automated driving between the UE supporting V2X application and the RSU Lower degree of automation [R.5.3-004] 6000 (NOTE 1) 10 100 [700] Higher degree of automation [R.5.3-005] 100 50 (NOTE 1) [360] Emergency trajectory alignment between UEs supporting V2X application. [R.5.3-006] 2000 3 99.999 30 500 Intersection safety information between RSU and UE supporting V2X application. [R.5.3-007] 450 50 DL: 0.5 UL: 50 (NOTE 2) Cooperative lane change between UEs supporting V2X applications. Lower degree of automation [R.5.3-008] 300-400 25 90 Higher degree of automation [R.5.3-009] 12000 10 99.99 Video sharing between a UE supporting V2X application and a V2X application server. [R.5.3-010] UL: 10 NOTE 1: This includes both cooperative manoeuvers and cooperative perception data that could be exchanged using two separate messages within the same period of time (e.g., required latency 100ms). NOTE 2: This value is referring to a maximum number of 200 UEs. The data rate per UE is DL: 250Kbps and UL: 2.5Kbps. NOTE 3: Sufficient reliability should be provided even for cells having no values in this table Editor’s note: The KPI values of minimum required communication range in requirement [R.5.3-002] [R.5.3-003] [R.5.3-004] [R.5.3-005] need update based on further study. 5.4 Requirements to support Extended Sensors Table 5.4-1 Performance requirements for extended sensors Communication scenario description Req # Payload (Bytes) Tx rate (Message /Sec) Max end-to-end latency (ms) Reliability (%) Data rate (Mbps) Min required communication range (meters) Scenario Degree Sensor information sharing between UEs supporting V2X application Lower degree of automation [R.5.4-001] [1600] 10 100 99 1000 Higher degree of automation [R.5.4-002] 10 95 [25] (NOTE 1) [R.5.4-003] 3 99.999 [50] 200 [R.5.4-004] 10 99.99 [25] 500 [R.5.4-005] 50 99 [10] 1000 [R.5.4-006] (NOTE 2) 10 99.99 1000 50 Video sharing between UEs supporting V2X application Lower degree of automation [R.5.4-007] [50] 90 [10] [100] Higher degree of automation [R.5.4-008] [10] 99.99 [700] [500] NOTE 1: This is peak data rate. NOTE 2: This is for imminent collision scenario. Editor’s note: The KPI values (e.g. data rate, minimum required communication range) in requirement [R.5.4-008] need update based on further study. 5.5 Requirements to support Remote Driving [R.5.5-001] The 3GPP system shall support message exchange between a UE supporting V2X application and V2X application server for an absolute speed of up to 250 km/h. Table 5.5-1 Performance requirements for remote driving Communication scenario description Req # Max end-to-end latency (ms) Reliability (%) Data rate (Mbps) Information exchange between a UE supporting V2X application and a V2X Application Server [R.5.5-002] 5 [99.999] UL: 25 DL: 1 Annex A (informative): Background information on service Requirements For each requirement in this specification, Table A-1 indicates reference to the consolidated potential requirements in TR 22.8