Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TR 22.885  Word version:  14.0.0

Top   Top   None   None   Next
0…   5…

 

0  IntroductionWord‑p. 7

This document covers use cases and potential requirements for LTE support for vehicular communications services (represented by the term, Vehicle-to-Everything (V2X) Services). The TR on LTE support for V2X services contains three types of V2X (V2V (vehicle to vehicle), V2I (vehicle to infrastructure/network), and V2P (vehicle to pedestrian)) and both safety and non-safety aspects.

1  ScopeWord‑p. 8

The objective of this TR is to identify use cases and associated potential requirements for LTE support of V2X services taking into account V2X Services and parameters defined in other SDOs (e.g. GSMA Connected Living, ETSI ITS (Intelligent Transportation System), US SAE) or related governmental agency (e.g. C-ITS project in Korean Ministry of Land, Infrastructure and Transport). The essential use cases for LTE V2X (V2V, V2I, and V2P) to be studied and requirements identified are as follows;
  • V2V: covering LTE-based communication between vehicles.
  • V2P: covering LTE-based communication between a vehicle and a device carried by an individual (e.g. handheld terminal carried by a pedestrian, cyclist, driver or passenger).
  • V2I: covering LTE-based communication between a vehicle and a roadside unit.
This TR includes safety and non-safety aspects.
Up

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 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]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
ETSI TR 102 638 V1.1.1: "Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Definitions"
[3]
ETSI TS 102 637-1 V1.1.1: "Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Part 1: Functional Requirements"
Up

3  Definitions and abbreviations

3.1  Definitions

For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply.
A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
Road Side Unit:
An entity supporting V2I Service that can transmit to, and receive from a UE using V2I application. RSU is implemented in an eNB or a stationary UE.
V2I Service:
A type of V2X Service, where one party is a UE and the other party is an RSU both using V2I application.
V2N Service:
A type of V2X Service, where one party is a UE and the other party is a serving entity, both using V2N applications and communicating with each other via LTE network entities.
V2P Service:
A type of V2X Service, where both parties of the communication are UEs using V2P application.
V2V Service:
A type of V2X Service, where both parties of the communication are UEs using V2V application.
V2X Service:
A type of communication service that involves a transmitting or receiving UE using V2V application via 3GPP transport. Based on the other party involved in the communication, it can be further divided into V2V Service, V2I Service, V2P Service, and V2N Service.
Up

3.2  AbbreviationsWord‑p. 9

For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply.
An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
CACC
Corporative Adaptive Cruise Control
HV
Host Vehicle
ITS
Intelligent Transport Systems
RV
Remote Vehicle
RSU
Road Side Unit
TTC
Time to Collision
V2I
Vehicle-to-Infrastructure
V2N
Vehicle-to-Network
V2P
Vehicle-to-Pedestrian
V2V
Vehicle-to-Vehicle
V2X
Vehicle-to-Everything
VRU
Vulnerable Road User
Up

4  Overview

4.1  Types of V2X

The vehicular communication in this TR, referred to as Vehicle-to-Everything (V2X), contains the following three different types:
  • Vehicle-to-Vehicle (V2V) Communications
  • Vehicle-to-Infrastructure (V2I) Communications
  • Vehicle-to-Pedestrian (V2P) Communications
(not reproduced yet)
Figure 4.1-1: Types of V2X (V2V, V2P, and V2I).
Up
Three basic classes of applications for providing ITS services: road safety, traffic efficiency, and other applications can be found in e.g., [2],[3].
Up

4.2  Vehicle-to-Vehicle (V2V)Word‑p. 10

E-UTRAN allows such UEs that are in proximity of each other to exchange V2V-related information using E-UTRA(N) when permission, authorisation and proximity criteria are fulfilled. The proximity criteria can be configured by the MNO. However, UEs supporting V2V Service can exchange such information when served by or not served by E-UTRAN which supports V2X Service.
The UE supporting V2V applications transmits application layer information (e.g. about its location, dynamics, and attributes as part of the V2V Service). The V2V payload must be flexible in order to accommodate different information contents, and the information can be transmitted periodically according to a configuration provided by the MNO.
V2V is predominantly broadcast-based; V2V includes the exchange of V2V-related application information between distinct UEs directly and/or, due to the limited direct communication range of V2V, the exchange of V2V-related application information between distinct UEs via infrastructure supporting V2X Service, e.g., RSU, application server, etc.
Up

4.3  Vehicle-to-Infrastructure (V2I)

The UE supporting V2I applications sends application layer information to RSU. RSU sends application layer information to a group of UEs or a UE supporting V2I applications.
V2N is also introduced where one party is a UE and the other party is a serving entity, both supporting V2N applications and communicating with each other via LTE network.

4.4  Vehicle-to-Pedestrian (V2P)

E-UTRAN allows such UEs that are in proximity of each other to exchange V2P-related information using E-UTRAN when permission, authorisation and proximity criteria are fulfilled. The proximity criteria can be configured by the MNO. However, UEs supporting V2P Service can exchange such information even when not served by E-UTRAN which supports V2X Service.
The UE supporting V2P applications transmits application layer information. Such information can be broadcast by a vehicle with UE supporting V2X Service (e.g., warning to pedestrian), and/or by a pedestrian with UE supporting V2X Service (e.g., warning to vehicle).
V2P includes the exchange of V2P-related application information between distinct UEs (one for vehicle and the other for pedestrian) directly and/or, due to the limited direct communication range of V2P, the exchange of V2P-related application information between distinct UEs via infrastructure supporting V2X Service, e.g., RSU, application server, etc.
Up

Up   Top   ToC