Department of Informatics and Telecommunications

University of Peloponnese - Greece

Network slicing for V2X communications

Professor Alexandros Kaloxylos
Email: kaloxyl@uop.gr

Network Slicing World Summit

Berlin 23-10-2018
 Contents
 Network slicing
 Vehicle to Everything (V2X) communications
• What is it?
• How to support it?
 Does a V2X slice requires any differential treatment from a typical URLLC slice?
• Examples of existing V2X solutions and potential alterations
• Discuss how a V2X slice may differ from any other slice type at a network
function level
 Conclusions
Goal of the presentation:

Address the question - “Do only 3 slice types (eMBB, URLLC, mMTC) fit all use cases”?
 5G Architecture- Network Slicing
AF
Service Provider Service
N5 Requirements

CN Control Plane Slice i

NEF NRF PCF UDM

CSMF

NSI Management
NSSF

Slice
AUSF AMF SMF UDR Management Requirements
Orchestration
of NSIs
NSFM
N3IWF

Data
UE RAN UPF network
Untrusted
non-3GPP
Access

3GPP - TS 23.501: “System Architecture for the 5G System”

Network slice: A logical network that provides specific network capabilities and network characteristics.
Network Slice Instance: A set of NF instances and the required resources (compute, storage and networking)
 Classification System for automated vehicles
(National Highway Safety Administration - NHTSA and Society of Automotive Engineers - SAE)

LoA: Level of automation

 V2X use cases investigated in 3GPP

- Vehicles Platooning: coordinate multiple

autonomous vehicles into convoys Types of messages
- Advanced Driving: semi/fully automated 1. Periodic CAM message
driving by sharing perception data and driving 2. Emergency DENM
intentions messages
- Extended Sensors: raw/processed data, live 3. Session based (trajectory
video images shared among vehicles, RSUs, exchange, video, high
V2X servers
definition maps etc.)
- Remote Driving: operate a vehicle remotely

Source: 3GPP 22.186, Enhancement of 3GPP support for V2X scenarios

 Performance Requirements: (e.g., Advanced driving)
Communication scenario description Max end- Minimum
Tx rate Data
Payload to-end Reliability required
(Message/ rate
Scenario Degree (Bytes) latency (%) communication
Sec) (Mbps)
(ms) range (meters)
Lowest degree of
300-400 30 25 90
automation
Cooperative driving for vehicle Low
6500 50 20 350
platooning degree of automation
Information exchange between a group Highest degree of 10
of UEs supporting V2X application. 50-1200 30 99.99 80
automation
High
20 65 180
degree of automation
Reporting needed for platooning
between UEs supporting V2X
N/A 50-1200 2 500
application and between a UE
supporting V2X application and RSU.
Lower
6000 50 20 350
Information sharing for platooning degree of automation
between UE supporting V2X application
Higher degree of
and RSU. 20 50 180
automation

Source: 3GPP 37.885, Study on the evaluation methodology of the new V2X use cases for LTE
Cellular network support for V2X communications

V2X Application Server

V2
SGi

EPC
V2X Control
Function V1
S1

V3
E-UTRAN eNB Uu
Uu
eNB

PC5
V2X Application V2X Application
V5
Source: 3GPP 23.285, Architecture enhancements for V2X services
 V2X application layer functional model

Source: 3GPP 23.795, Study on application layer support for V2X services
 V2X application layer functional model

 Most of the issues seem to be covered by a URLLC slice and existing network functions

 Still, not all issues are yet solved or some of them may be addressed in a suboptimal way
 What may differentiate a V2X slice?
0. Fast moving terminals
1. User plane traffic has usually local significance
2. The geography of the streets is fixed and well known
3. The maximum number of vehicles inside a cell is known
4. The path of the vehicles may be known beforehand!
5. Different modes of communication and fast dynamic group management are needed

Taking advantage of V2X contextual information may improve KPIs and simplify network functions
 Taking advantage of contextual information

1. User plane traffic has usually local significance Session management, MBMS

2. The geography of the streets is fixed and well known Session management, MBMS

3. The maximum number of vehicles inside a cell is known Traffic Engineering

Location Management,
4. The path of the vehicles may be known beforehand! Handover, Traffic Engineering,
Scheduling, Session
Radio Resource control, Pre-
5. Different mode of communications and fast dynamic group management configuration of NFs, pre-
allocation of IDs or even
resources, multi-operator
communication
Example 1: Mobility Management (MM)

Existing MM schemes
Typical Schemes (Tracking area list, smart paging)

RNA: RAN based Notification Area (RRC Inactive State)

However, for several vehicles their path will be

known beforehand
A Context Enhanced Mobility management scheme (CEMOB)
V2X Application Server

2. Provide Path (coordinates, timestamps)

NG-CP
NEF

1. Destination/Path 3. Provide Path (involved gNBs, timestamps)

5. Pre configure tunnel (UE, timestamps)

AMF SMF

4. Context transfer (UE, timestamps)

6. Pre configure tunnel (UE, timestamps)

UE gNB NG-UP

Source: P. Spapis, C Zhou, A. Kaloxylos, On V2X network slicing: using context information to improve mobility management, ICDT 2017
 Performance evaluation for CEMOB
Paging cost
120

Signaling Reduction gain %

100

80

Paging 60 RAN vs CN

CEMOB vs CN
40
CEMOB vs RAN
20

0
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Number of gNBs
Inversely proportional to the
space headway

Location
Update

Calculations assume that every 30 sec the 20% of the vehicles will request a path update
 Example 2: Session management (SM)

Existing SM schemes
Typical communication over the Uu interface and the
core network components

Local break-out schemes (e.g., SIPTO)

However,
a) not all traffic needs to pass pass through the CN.
b) existing breakout schemes are designed for enterprise local
networks and low mobility
 The Local IP V2V Access (LIVA) scheme

Key Points:
1. No S-GW or P-GW are used for local
traffic
2. V2V GW is the UP termination point
3. The V2V GW knows which eNB serves
each street
4. The V2V GW can be considered as a
merged L-GW, S-GW, MBMS server
5. V2V GWs communicate directly through
a new interface (V2V-X2)

Source: A. Kaloxylos, LIVA: An efficient local breakout scheme for V2V communication, PCI 2017
 Performance Analysis for LIVA
Delay LIVA SIPTO LTE/EPC
UE processing delay 3msec 3msec 3msec
Uu transfer delay 5msec 5msec 5msec
S1-U transfer delay 1 msec 7,5msec 7,5msec
S5 transfer delay - - 1msec
(SGW, PGW) Delay
SGW, PGW - 1msec 3msec
processing delay
LIVA processing 1msec - -
delay
SIPTO processing - 1msec -
delay
Total delay 10msec 17,5msec 19,5msec SIPTO -LIVA (20Km/h) LTE/EPC-LIVA (20Km/h) SIPTO -LIVA (30Km/h)

NUMBER OD ADDITIONAL
LTE/EPC-LIVA (30Km/h) SIPTO -LIVA (45Km/h) LTE/EPC-LIVA (45Km/h)
450000

MESSAGES
400000
350000
300000
250000
200000
150000
Signaling 100000
50000
0
4.5 9 13.5 18 22.5
AVERAGE SPACE HEADWAY
 What may be different in a V2X slice?
E2E service management and
AF orchestrator
BM-SC

NG-CP

NEF NRF PCF UDM

MANO

AUSF AMF SMF UDR

TE NMS

AF
BM-SC

EMS
Inter slice RRM SM NEF
RRC
PDCP
RLC
Data
UE MAC NG-UP network
PHY

NG-RAN
 Conclusions

• Current work for V2X slicing is progressing rapidly

• A V2X slice could be treated simply as a URLLC slice but
Available contextual information may not really be exploited
Fine-tuning of several network functions may not be possible to the fullest extent
• V2X communications have specific characteristics that may require some
further investigations on a number of topics e.g.,
Localized session management
(Localized) Multicast/Broadcast communication
Optimizing handover, mobility management, traffic engineering solutions
Radio resource management for ultra-reliable communication for highly moving
terminals
Multi-operator communication that meets the strict delay requirements