RAN and Packet Core Evolution – 3GPP

MSC
NodeB BSC SGSN Gateway
eNodeB RNC MME
Serving PDN
BSC Gb
GERAN S7
S4 Gateway
Rx+
RNC
UTRAN IuPS S3 SGs Operator
S5/S8 SGi
Services
S1-U S11
S1-MME S6b
Internet
LTE Corporate
S6a Services
S2c
(e.g. IMS)
Non 3GPP and Internet)
WiMax
ePDG
WLAN Untrusted Non-3GPP IP Access S2b
CDMA200 Control plane
PSTN
Trusted Non-3GPP IP Access S2a User plane
IP Based Protocols for User, Control, Management and Synchronization Plane

Lower transport cost and easier planning & configuration

Uu S1-MME
NAS

RRC RRC
S1-AP S1-AP

X2 Inter-enodeB PDCP PDCP

X2 RLC RLC SCTP SCTP

X2-AP X2-AP MAC MAC IP IP

(U/C-Plane)
SCTP SCTP PHY PHY L1/L2 L1/L2

IP IP

L1/L2 L1/L2
eNB 2 C-Plane UE eNB MME

MME
GTP-U GTP-U

UDP UDP
S-Plane
IP IP Master Clock
L1/L2 L1/L2
IP (optional)
eNB eNB U-Plane

Uu SAE-GW S1-U
User IP

M-Plane PDCP PDCP GTP-U GTP-U

RLC RLC UDP UDP

eNB1 MAC MAC IP IP

OSS PHY PHY L1/L2 L1/L2

UE eNB S-GW
 X2 interface – TS 36.420

Handover over X2 - Principle

X2 Handover - Capacity

30…50ms radio link interruption during HO

X2 latency should be less or equal than radio link interruption provisioning of extra capacity may only be justified for sites
time for optimum performance` where high HO performance is required
L2 Mobile Backhaul Network with E-Line
http://metroethernetforum.org/

Mobile Backhaul Backbone

eNB Group Network Network
eNB 11 UNI
EVC 11 (E-Line)
UNI

MME
eNB 12 UNI
EVC 12 (E-Line)
UNI

eNB 21 UNI
EVC 21 (E-Line)
UNI

eNB 22 UNI SAE-GW

EVC 22 (E-Line)
UNI

X2 routing between eNBs within one group

and between eNB groups
L2 Mobile Backhaul Network with E-LAN
http://metroethernetforum.org/carrier-
ethernet/mobile-backhaul

eNB Group Mobile Backhaul Backbone

Network Network
eNB 11 UNI

UNI
EVC 1 (E-LAN)
eNB 12
UNI MME

E-Line / E-Tree
–Simpler Traffic Engineering
–Easier troubleshooting
eNB 21 UNI ▪Connectivity checking (L2 or L3) between eNBs
not required
–Impact of DoS attacks is limited to one eNB
UNI
EVC 2 (E-LAN)
eNB 22 UNI
SAE-GW

X2 switching between eNBs of one group X2 routing between eNB groups

L2 Mobile Backhaul Network with E-Tree
eNB Group Mobile Backhaul Core
Network Network
eNB 11 UNI

UNI
EVC 1 (E-Tree)
eNB 12
UNI MME

Perceived advantages are questionable

Marginal backhaul traffic savings
X2 traffic <5%
X2 latency optimization
eNB 21 UNI S1 transport should be designed for low
latency anyhow
UNI
EVC 2 (E-Tree)
eNB 22 UNI
SAE-GW
X2 routing between eNBs within one group and
between eNB groups
Carrier Ethernet Transport for Backhaul, IP/MPLS for Core
Access Network Aggregation Backbone
Network Network
enodeB 11

enodeB 12
MME

VLAN
Eth
VLAN VLAN
PW
Eth Eth
MPLS
enodeB 21 Eth

enodeB 22
SAE-GW

Carrier Ethernet Transport IP/MPLS

eNB / eNB group identification with VLAN

EPS Bearers
  QCI (QoS Class Identifier 5-9)
EPS Bearers 

ARP (allocation Retention Priority)
UE-AMBR (UE aggregate Maximun Bit Rate)
 APN-AMBR (APN Aggregate Maximum Bit Rate)

 TFT (Traffic Flow Template)

GBR and Non-GBR Bearers

 QCI (QoS Class Identifier 1-4)
 ARP (allocation Retention Priority)
 MBR (Maximun Bit Rate)
 GBR (Guranteed Bit Rate)
QCI (QoS Class Identifier)

3GPP : TS 23.203
End-to-End QoS Principles
Radio and Transport QoS are closely related
• Scarce resources • Scarce resources • Fair resources
• Strict control (RRM) • Strict control (Transport) • Less strict control • No control
• Reservation for GBR • Reservation (CIR) • Reservation (MPLS TE)
• Controlled overbooking • Controlled overbooking with • Overbooking with
with prioritization prioritization (802.1p) prioritization (DiffServ)
for non-GBR
QoS features

• Radio & Transport CAC

• Flow & (CIR for GBR, EIR for non-GBR)
congestion • Radio scheduling per UE (UL+DL)
control (TCP)
• Transport UL policing and shaping
• Traffic marking • DL policing and • DL policing and shaping • Flow &
per eNB
shaping per per UE congestion
enodeB control (TCP)

Ethernet IP IP
Internet
SAE-GW
Server
Access Aggregation Internet
Service
quality

Core
Guaranteed
Operator
Best effort Server
E2E QoS: Mapping Radio QoS onto Transport QoS
U-Plane C/M/S-Plane
LTE Radio domain LTE Transport domain
Resource DiffServ Ethernet
LTE Traffic Class QCI DSCP
Type PHB p-bits
Conversational Voice 1 S-Plane(ToP) 46 EF 5
Conversational Video 2 26 AF31 3
GBR
Real Time Gaming 3 46 EF 5
Non-conversational Video 4 28 AF32 3
IMS signaling 5 C-Plane 34 AF41 4
Voice, video, interactive
6 18 AF21 2
gaming
Video (buffered streaming) 7 non-GBR 20 AF22 2

TCP-based (e.g. www, e- 8 10 AF11 1

mail, ftp, p2p file sharing,
etc. 9 0 BE 0

Exemplary configuration
LTE/Wi-Fi Multipath Aggregation
LTE/Wi-Fi Multipath Aggregation
LTE/Wi-Fi Multipath Aggregation

Better performance: using both LTE and Wi-Fi links simultaneously

Mobile Network Architecture for 5G
C-RAN (Centralized/Cloud RAN) Architecture and Distributed 5G Core

Many predict 5G, compared to 4G, will give:

 1. Ultra-high radio speed (20Gbps/UE) - New RAT, mmWave, massive MIMO, massive
Aggregation
 2. Ultra-low latency (E2E few msec) - Tactile Internet, autonomous driving, remote
controlled machine
 3. Massive connectivity (hundreds of millions of IoT devices)
Mobile Network Architecture for 5G
1. Ultra-High Radio Speed ⇒ Enormous traffic at fronthaul ⇒ New C-RAN/Fronthaul

(2T2R)
Mobile Network Architecture for 5G
1. Ultra-High Radio Speed ⇒ Enormous traffic at fronthaul ⇒ New C-RAN/Fronthaul

(2T2R)
Mobile Network Architecture for 5G
2. Ultra-High Radio Speed ⇒ Enormous traffic converging into the Core ⇒ Distributed 5G Core
Mobile Network Architecture for 5G
2. Ultra-High Radio Speed ⇒ Enormous traffic converging into the Core ⇒ Distributed 5G Core
Mobile Network Architecture for 5G
3. Ultra-low latency ⇒ Distributed 5G Core
Many agree that massive IoT and mission-critical IoT are the biggest difference between 4G and 5G.
Mission-critical IoT (Ultra-reliable and low latency communications) applications include remote controlled
machine, autonomous driving (self-driving), etc. These types of ultra-real-time services require radio latency
of less than 1ms, and end-to-end latency of less than a few ms.

The best way to achieve minimal end-to-end latency in terms of network architecture would be to eliminate
backhaul delay by distributing 5G core closest to mobile devices, and placing application servers right next to
it. Distribution of 5G core that we have just discussed above will naturally give us the same effect.
Network slicing: Why do we need it?
How do we implement E2E network slices?
Current Network (with dedicated equipment)

Creating virtualized network

How do we implement E2E network slices?
Network Slicing: Creating multiple virtual networks (by cutting network horizontally)

In the figure, Core

indicates user plane

Commercial server Commercial server

E2E network slicing
Example of 5G C-RAN network slicing by ITU
5G network slices illustrated by NGMN
Cloudification of 5G RAN and 5G Core
5G

4G
Mobile Network Architecture for 5G RAN and 5G Core
5G
2015 2020

4G
 5G

2015 2020

4G

Mobile Network Architecture for 5G RAN and 5G Core

Thanks.