4. Work Status

March, 2016

SungDuck CHUN

LG Electronics

3GPP Activities on ITS

Copyright 2016. LG Electronics Inc. All rights reserved

1. History

3GPP started feasibility study of 3GPP support of V2X communication from 1Q 2015

– Discussion started from 3GPP RAN in 2Q 2014, and RAN sent request to define service requirement to SA1 in 4Q 2014.

– First SI/WI for V2X was created in 1Q 2015 at SA1 and completed in 4Q 2015.

– Technical Report for V2X (TR 22.885) was approved in 4Q 2015.

– Technical specification for V2X (TS 22.185) has been sent for SA approval in 1Q 2016.

– First stage-3 level TS for V2X will be available in 3Q 2016.

2

SA

RAN

First discussion on LTE V2X

‘14.06

RAN SI completion &WI for other V2X aspects may start

‘16.06

SA1 SI approval

‘15.02

SA1 WI approval

‘15.09

SA1 SI completion

‘15.12

SA1 WI completion

‘16.03

‘15.06

RAN SI approval

RAN WI on D2D-based V2V

approval

‘15.12 ‘16.09

RAN WI on D2D-based

V2V completion

Overall Timeline


1. History

The ongoing progress for release 14 in Working Groups SA1, SA2, SA3, RAN1, RAN2, RAN3 and RAN4.

3

SA1

RANOverall ‘16.06

‘15.03 ‘15.09 ‘15.12 ‘16.03

‘15.06

V2X SI D2D-based V2V

‘15.12

‘16.06

Estimate

‘16.09

Detailed Target Schedule

SA2

SA3‘16.09

SI approval SI completion WI Approval WI completion

Estimate

D2D-based V2VV2X SI Estimate

RAN1

RAN2

RAN3

RAN4

Study Item/TR Work Item/ TS

‘16.03

‘17.03

(Stage-1)

(Stage-2)

(Stage-3)


2. Scope

Standardization activity for V2X in 3GPP includes the transport layer aspects, but does not include V2X application-layer aspects.

– In overview section of TS 22.185:

These intelligent transportation services and the associated message 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. The message transport expectations are described in requirements defined in this specification.

The related references and the related SDOs:

– ETSI TR 102 638 V1.1.1: "Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Definitions".

– ETSI TS 102 637-1 V1.1.1, "Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Part 1: Functional Requirements“

– GSMA Connected Living, ETSI ITS (Intelligent Transportation System), US SAE, C-ITS project in Korean Ministry of Land, Infrastructure and Transport, IEEE, SAE-China, C-ITS, WWRF, C2C-CC, ACEA, ERTICO, ACEM, etc

4

General


2. Scope

The following four types of V2X are considered:

– V2V: Vehicle-to-Vehicle

– V2P: Vehicle-to-Pedestrian (e.g., handheld terminal carried by a pedestrian, cyclist, driver or passenger)

– V2I: Vehicle-to-Infrastructure application, where infrastructure is RSU (Roadside Unit). RSU is a transportation infrastructure entity implemented in an eNB or a stationary UE

– V2N: Vehicle-to-Network, where Network means application service/server which is out of 3GPP scope

To support these V2X applications, 3GPP considers both WAN based communication and D2D (device-to-device) direct communication.

5

Types


2. Scope

In 3GPP, RSU is:

– A stationary infrastructure entity supporting V2X applications that can exchange messages with other entities supporting V2X applications.

– 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).

UE-type RSU is beneficial in areas where cellular coverage cannot be provided (e.g. deep in the mountain area).

The following figures show the possible example of RSU implementations.

6

RSUs

UE A(Vehicle)

V2X Application

UE B(Stationary)

V2X Application

PC5

V5

RSU

UE A(Vehicle)

V2X Application

eNB

V2X Application

Uu

V1

RSU

L-GW

UE-type RSU eNB-type RSU


2. Scope

For V2X, the respective WGs are working on the following aspects:

7

Per WG objective/scope

3GPP

SA

RAN

RAN1

RAN2

RAN3

RAN4

SA3

SA2

SA1

Specify enhancment to physical layer structure, procedures (e.g. resource allocation, synchronization, etc)

Specify enhancment to radio protocols and RRC Signalling.Specifiy mechanisms to e.g. spectum access control, switching between interfaces PC5/Uu

Specify enhancment to radio access network protocol

Specify UE RF TX/RX requirements up to 6 Ghz and RRM/ demodulation requirementsEvaluation for adjacent coexistence at licensed/unlicensed band

Identify secuirty requirement for V2X, and specify enhancement to existing 3GPP security functionalities to support the requirements.

Specify enhancment to existing 3GPP architecture and functionalities to support V2X

Specify service requirements for transport layer support of V2X communication, for both safety-related and non-safety aspects.


3. Enablers

3GPP did not begin standardization work for V2X from scratch, but fully utilizes and enhances the existing framework as much as possible:

– This will expedite the standardization processof V2X communication in 3GPP

The following enablers/functions are mainly considered for the bases of V2X:

– MBMS (Multimedia Broadcast Multicast Service)3GPP functionality to provide efficient delivery of broadcast and multicast services. This functionality can be used for various purposes such as group call session, live TV broadcasting, public warning message delivery, etc.

– ProSe (Proximity-based services) or D2D (Device to Device) communication:D2D communications refers to the communications of users in cellular networks without base station (BS) intervention or with reduced BS intervention.

8

UE2UE3UE1

D2DUE1UE2UE1

WAN

ProSEMBMS


4. Work Status

Following the completion of the feasibility study (LTE support of V2X services), Technical Report 22.885 was published in December 2015

Technical specification 22.185 will include service requirements of 3GPP transport service for V2X application.

– Upon the approval by 3GPP SA Plenary in Mar.2016, TS 22.185 will be available at ftp://ftp.3gpp.org/Specs/archive/22_series/22.185/

In TS 22.185, service requirements are classified as follow:

9

SA1 – Service Requirement

OverallReq.

SpecificReq.

Message Size

Frequency

Latency/Reliability

Support up to 10 messages transfer per second per UE

Support Max relative velocity up to 280 km/h, absolute velocity 160 km/h

50~300 bytes for periodic, 1200 bytes for event-triggered (except security)

Max 100ms latency for V2V/P/I, Max 1000ms latency for V2N

Configurability/ Inter-PLMN/ Prioritization/ Area control. etc

SecurityReq.

Range

Speed

Support communication range sufficient to give driver ample response time (4 second)

Authorization / Anonimity / Integrity protection / Privacy


4. Work Status

SA2 has made two architectual assumption on PC5-based and eMBMS-based V2X, respectively.

The architectural assumption for PC5 based V2X:

– V2X Control Function:the logical function used for networkrelated actions for V2X

The latest TR 23.785 developed by SA2 is available at ftp://ftp.3gpp.org/Specs/archive/23_series/23.785/

10

SA2 – Architecture

E-UTRAN

UE A(Vehicle)

UE D(stationary)

UE B(Vehicle)

V2X Application

V2X Application

V2X Application

V2X Control FunctionPLMN A

LTE-Uu

LTE-Uu

V5

V1

V5

V3

V2

V3

PC5

PC5

PC5

UE C(pedestrian)

V2X Application

V5

MME

HSS

S/P-GW

S1

S6a

V3

V4

V2X Application

Server V3

V2X Control FunctionPLMN B

V2X Control FunctionPLMN n

.

.

.

V2

V2

Figure 4.1.1-1: Reference architecture for V2X (PC5 based)


4. Work Status

The following architectural assumption for eMBMS-based V2X:

– V2X AS (Application Server): the logical function that is used for network related actions required for V2X.

Based on the following key issues identified, SA2 is working on solutions:– Service Authorization

– V2X message transmission/reception for V2V and V2P

– Policy/Parameter provisioning for V2V/V2P/V2I

– V2X message prioritization for V2V / V2P

– V2X message transmission/reception for Vehicle and RSU for V2I

– Latency improvement for eMBMS for V2X

– QoS for V2X

11

SA2 – Architecture


4. Work Status

As of Febuary 2016, SA3 identified three key issues to resolve and some resulting requirements for the security in 3GPP support of V2X:

– V2X communication security The transmission of data between different entities should be integrity protected.

The transmission of data between different entities should be protected from replays.

UE pseudo-anonymity should be provided to conceal personal data from attackers

– Authorization for LTE-V2X radio resources If many malicious UEs may attempt to request radio resources at the same time from the MNO network, it

would lead to an exhaustion of network radio resources. Legal vehicle UEs can not get available radio resourcers for LTE-V2X communications.

– V2X Entities secure environment The attacker may manipulate the information from measuring instruments, generating false V2X messages/

warnings which may mislead surrounding V2X entities to take wrong actions and possibly cause accidents.

The attacker may manipulate the data processing in V2X entities, leading to false V2X messages

The attacker may modify the security materials or vital configuration data in eNB-type RSU

The latest TR33.885 is available at ftp://ftp.3gpp.org/Specs/archive/33_series/33.885/

12

SA3 – Security


4. Work Status

RAN1 has finished evaluation of performance for PC5 based V2V communication:

– Simulation results shows that PC5 interface transport for V2V communication is feasible and can meet requirements

– Study result is avaialble at ftp://ftp.3gpp.org/Specs/archive/36_series/36.885/

Based on this, RAN1 is working on PC5 interface enhancement in areas such as:

– Enhancement to PC5 interface resource allocation (resource pool, selection, etc)

– Enhancement to physical layer structures such as DMRS (Demodulation Reference Symblol) to handle high doppler

– Synchronization procedure (i.g. source of synchronization such as GNSS, eNB, etc)

Progress will be made on other than PC5-based V2V:

– Possibility of extending PC5 design for V2V to V2I/V2P communication

– Enhancements to MBMS for Uu based V2V/I/P communication

– Enhancements to physical layer structure or procedure for Uu based V2V/I/P

13

RAN1 – Physical Layer


4. Work Status

RAN2 has mainly focused on evaluation of latency and capacity for V2V service:

– Latency requirement can be met for PC5-based V2V communication with relevant resource configuration.

– Latency requirement can be met for Uu-based V2V communication only in limited cases which could demand almost 100% of the resources for V2V services e.g. when short UL/DL scheduling periods are configured for all Ues in Urban scenario.

– Given that we cannot assume that 100% of the resources are available for V2V services, some UL enhancements can be considered.

– Unicast based mechanism is not suitable to meet DL capacity requirement. Focus will be on enhancement based on broadcast mechanism.

RAN2 will do further enhancement study on following areas:

– UL SPS enhancement based on traffic characteristic

– Latency improvement on DL broadcast

– DL broadcast on the basis of UE geographical location

– Support for the inter-operator deployment

– QoS support for Uu based or PC5 based mechanism

14

RAN2 – L2/L3


4. Work Status

RAN3 formally started work on V2X from 1Q 2016. It made progress by agreeing following way forward:

– For the D2D based V2X WI, confirms that only V2V over PC5 is supported and RSU is not discussed.

Following is captured in TR 36.885:

– Local breakout architecture (i.e, putting V2X application closer to the edge of Radio Network edge) is considered to better fulfil the stringenet V2X latency requirements

V2x server, connected through SIPTO@LN with stand-alone GW

V2x server, connected through SIPTO@LN with co-located L-GW

V2x server co-located in the eNB

– The small and variable areas in V2X could be managed via MBSFN and/or SC-PTM

– Localized MBMS should be considered.

15

RAN3 – Radio Access Network

SC-PTMMBSFN


4. Work Status

RAN4 started work on V2X from 1Q 2016. It made progress by agreeing following way forward:

– Define operating band for PC5 based V2V:

For licensed band, current commercially available band willl be considerd.

For unlicensed band, band 46 reuse or new band will be considered.

– Coexistence scenario and simulation parameter in adjacent channel:

Licensed band (Aggressor-to-Victim):

• V2V UE-to-LTE eNB and LTE UE-to-V2V UE in 2GHz band

Unlicensed band (Aggressor-to-Victim):

• FFS, consider V2V-to-LAA or V2V-to-ITS for legacy system protection

16

RAN4 – RF


5. Performance

Potential benefit of LTE-based V2X is:

Existing LTE infrastructure can be reused.

– Reduces the cost for V2I/N deployment and maintenance

– Controls and authorizes V2X devices via infrastructure

Not only for WAN but also for D2D

– Various operation scenarios are possible especially using RSUs

For example, cellular links can be used as backup of D2D link

Larger coverage is provided.

– High transmit power and antenna height of base stations in WAN-based solutions.

– FDM of transmissions from multiple UEs within a carrier to increase the multiplexing capacity

– Use of multiple antennas, turbo code.

– Carrier frequency, numerology, and sensitivity of LTE.

A better multi-carrier/channel operation can be provided.

– Sharper out-band emission property which reduces interference to adjacent carriers.

– Efficient operation based on the LTE carrier aggregation framework

Services can be optimized for pedestrian UEs.

– It is expected that pedestrian UE is always equipped with LTE.

– Battery saving based on LTE power saving mechanism

17

Benefit


5. Performance

Better to meet End-to-end latency

– Some safety services (e.g. pre-crash warning) requires very tight latency which Uu-based V2X can not meet without potential enhancement.

– Multi-hop operation using UL + DL might be difficult to meet the requirements with no enhancement.

Support operation even when outside of network coverage

– 100% WAN coverage cannot be guaranteed and is challenging even with current cellular deployment.

– The safety services should be provided regardless of vehicle location

18

Comparision between Uu / PC5

* PC5 is the interface used for D2D type communication, Uu is the interface for WAN (Wide Area Network) type communication.

Easy to use various cellular network features/merits such as:

– Attractive for V2I/N services which requires long range communication due to better coverage than PC5-based mechanism (e.g. high power and antenna height of eNB can be utilized)

– Intereference coordination

Can provide V2X communication even for UE without D2D capability

– Can minimize UE implementation cost.

Better battery performance for Pedestrian UE

PC5-based V2X Uu-based V2X


6. Operational consideration

V2X operations under consideration in 3GPP

– Scenario 1: Multiple operators share V2X spectrum

– Scenario 2: Multiple operators manage different V2X spectrum

– Scenario 3: There is only one operator in a region.

– Scenario 4: There is no network coverage in a region. D2D is the only option for this scenario.

19

Spectrum

Spectrum for WAN(Operator 1)


Spectrum for D2D(Operator 1&2)

Coverage

Spec

tru

m



Spectrum for D2D(Operator 2)

CoverageSp

ectr

um


Can be the same spectrum




Coverage

Spec

tru

m


Spectrum for D2D

Scenario 1

Scenario 2

Scenario 3Scenario 4


6. Operational consideration

20

Deploy

E-UTRAN

SL

Scenario 1: Only D2D

E-UTRAN

ULDL

Scenario 2: Only WAN

DLUL

SL

UE (RSU)

E-UTRAN

ULDL

SL

UE (RSU)

E-UTRAN

Scenario 3: Combination of D2D and WAN

V2X operations under consideration in 3GPP


7. Forward Looking

Further enhancement on 3GPP support for V2X will be likely to start in 2Q 2016:

– Work on 5G communication system started in 3GPP 2Q 2015.

– In SA1, use case scenario and service requirements for 5G system are being studied.

– Due to area overlap between 5G study item and Rel-14 V2X study item, study on the support of V2X & Connected Car in 5G has been suspended and will resume in 2Q 2016.

– Candidate topics are:

Further 3GPP enhancement to support autonomous driving

Further 3GPP enhancement to support car platooning

Inter-3GPP RAT interworking to support communication between UEs of different RATs

Etc.

21

Overall


7. Forward Looking

5G performance will be evolution of 4G performance.

22

5G target

User Experienced

Data Rate [Mbps]Peak Data Rate

[Gbps]

Spectrum

Efficiency

Mobility

[km/h]

Connection Density

[#/km2]

Latency

[ms]

Area Traffic

Capacity

[Mbps/m2]

Network Energy

Efficiency

20 100

3x

500

1106

100x

100.1

1

1x

1x

10

350

10105

IMT-Adv.

IMT-2020

Enhanced Mobile Broadband

Massive Machine Type Communications

Ultra-reliable and Low Latency Communications

3D video, UHD screens

Smart City

Industry automation

Gigabytes in a second

Self Driving Car

Augmented reality

Smart Home/Building

Work and play in the cloud

Voice Mission critical application,

e.g. e-health

Future IMT

IMT2020 Use Cases IMT2020 Key Capabilities


7. Forward Looking

Performance evolution as a result of 5G will benefit V2X / Connected car.

Thus, evolution of V2X technologies will be continued in 3GPP

– New air interface can be optimized for V2X communication from the beginning.

Lower latency & Higher reliability

Higher data rate

– Characteristics of vehicles can be defined as a new device type

Large volume, Sufficient power, More antennas, etc.

23

5G target

Documents

4. Work Status