3GPP Telecommunication Systems

Long Term Evolution (LTE)

Gert-Jan van Lieshout

Samsung Electronics Research Institute
Deventer, The Netherlands
[email protected]

2012-06-05

Mobile and Wireless; 23-10-2014

 Outline

Outline
!   Introduction [4]-[9]
!   3rd Generation Partnership Project (3GPP)
!   Start of LTE
!   Overall LTE architecture

!   LTE RAN: “E-UTRAN” [11]-[34]

!   E-UTRAN Release-8
!   E-UTRAN architecture
!   User Plane protocol Stack
!   Control Plane protocol Stack
!   Specific Features:
!   Quality of Service
!   Mobility
!   E-UTRAN after Release-8

!   LTE Core Network: “EPC” [36]-[54]

!   Core Network Architecture
!   Signalling Sequence Examples
!   PS CN evolution
!   Interworking with non-3GPP accesses

!   Summary [56]

2
Mobile and Wireless; 23-10-2014
 I Introduction

Mobile and Wireless; 23-10-2014

 3GPP structure

3rd Generation Partnership Project (3GPP) (Europe) (USA)

(China) (Korea)

(Japan) (Japan)

www.
3gpp.org

4
Mobile and Wireless; 23-10-2014
 Why LTE ?

Competition situation around 2006:

!   GSM did not have any serious competition a decade
!   Even today, still the unchallenged nr. 1 in number of mobile phones

!   UMTS had competition from the beginning but won

!   CDMA-2000 (3GPP2 evolution “UMB” on side-track)

!   More data centric solutions are standardised by IEEE:

!   802.16
!   Mainly backhaul broadband wireless (OFDM, nomadic)
!   802.16e (“WiMax”)
!   Broadband wireless access to end-users (OFDM, with mobility support)
!   Large group of supporters (Samsung, Intel, ….)
!   Flatter architecture (2 nodes) => Cheaper
!   802.20
!   Also based on OFDM with mobility support

!   Can HSDPA/EDCH meet the WiMax competition ? (=> Yes)

!   3GPP answer: “Long Term Evolution” (LTE)

5
Mobile and Wireless; 23-10-2014
 Why LTE ?

LTE & EPC

!   Around 2006, 3GPP RAN groups start to work on LTE “Long Term
Evolution”. In parallel SA2 started to work on the EPS ‘Evolved Packet System’
started.
!   Main objectives:
!   Ensure competitiveness in the next 10 years and behond
!   Enhanced capability of 3GPP system to cope with rapid growth of IP data traffic
!   Support for (seamless) mobility between heterogeneous access networks
!   Important parts of such a long-term evolution included:
!   Reduced latency, higher user data rates, improved system capacity and coverage,
and reduced overall cost for the operator
!   “flat IP Architecture”
!   LTE/SAE system was to be packet only system
!   Migration aspects were to be taken into account for the above, i.e. how
to migrate from the existing architecture
!   Resulted in 2 new main architecture documents:
!   23.401: GPRS enhancements for E-UTRAN
!   23.402: Architecture enhancements for non-3GPP accesses

6
Mobile and Wireless; 23-10-2014
 LTE: Overall architecture

Overall network architecture (non roaming)

Source: TS23.401
7
Mobile and Wireless; 23-10-2014
 LTE: Basic principle

Uu (radio) interface: Terminal to Network

UE
Uu Network / “Infrastructure side”

8
Mobile and Wireless; 23-10-2014
 LTE: Basic principle

S1 interface: Separates RAN from CN

Non-Access Stratum (NAS) functionality

- no radio specific functionality

Access Stratum (AS), Radio Network functionality

- all radio specific functionality
- no user service specific functionality

UE E-UTRAN CN
Uu S1

9
Mobile and Wireless; 23-10-2014
 II E-UTRAN
E-UTRAN Release-8
•  E-UTRAN architecture
•  User Plane protocol Stack
•  Control Plane protocol Stack
•  Specific Features:
•  Quality of Service
•  Mobility

E-UTRAN beyond Release-8

•  Release-10: Carrier Aggregation
•  Release-11
•  Release-12…

Mobile and Wireless; 23-10-2014

 E-UTRAN architecture

E-UTRAN Architecture

!   E-UTRAN consists of eNBs

!   flat architecture (no RNC or BSC as in UTRAN
and GERAN) for reduced latency and delays

!   eNBs are interconnected with each MME / S-GW MME / S-GW

other by means of the X2 interface

!   can be a logical connection via CN elements

S1

S1
S1

S1
!   eNBs are also connected to the Evolved X2 E-UTRAN
Packet Core (EPC) eNB eNB

!   eNBs are connected to the Mobility

X2

X2
Management Entity (MME) via the
S1-C (control) interface eNB

!   eNBs are connected to the to the Serving Uu

Gateway (S-GW) by means of the S1-U (user
data) interface

11
Mobile and Wireless; 23-10-2014
 E-UTRAN architecture

E-UTRAN Functions

!   Main functions hosted by eNB include

!   Functions for Radio Resource Management:
!   Connection Mobility Control, eNB

!   Radio Bearer Control, Inter Cell RRM

!   Radio Admission Control, RB Control

!   Dynamic allocation of resources Connection Mobility Cont.

MME
to UEs in both uplink and Radio Admission Control
downlink (scheduling) NAS Security
eNB Measurement

!   IP header compression and Configuration & Provision

Idle State Mobility

encryption of user data stream

Handling
Dynamic Resource
Allocation (Scheduler)

!   Routing of User Plane data RRC

EPS Bearer Control

towards Serving Gateway PDCP

!   Scheduling and transmission RLC
S-GW P-GW

of paging messages MAC

Mobility
Anchoring
UE IP address
allocation
(originated from the MME); S1
PHY Packet Filtering
!   Scheduling and transmission of internet

broadcast information (originated E-UTRAN EPC

from the MME or O&M)

12
Mobile and Wireless; 23-10-2014
 E-UTRAN protocol stack: User Plane

UE eNB

User Plane protocol stack (1) PDCP PDCP

RLC RLC

!   PDCP (Packet Data Convergence Protocol) – 36.323

MAC MAC

PHY PHY
!   ciphering
!   timer-based discard and header compression using the RoHC protocol
!   in-sequence delivery, retransmission and duplicate detection of PDCP SDUs at handover

Radio Bearers
!   RLC (Radio Link Control) – 36.322 ROHC ROHC
!   reliability increase through retransmissions PDCP
Security Security
!   segmentation and concatenation of SDUs for the
same radio bearer
!   in-sequence delivery RLC
Segm.
...
Segm.
ARQ etc ARQ etc

!   MAC (Media Access Control) – 36.321 Logical Channels

!   multiplexing/demultiplexing of RLC PDUs Scheduling / Priority Handling

!   scheduling information reporting

MAC
!   error correction through HARQ Multiplexing

!   logical channel prioritisation

HARQ

Transport Channels

UL-SCH

13
Mobile and Wireless; 23-10-2014
 E-UTRAN protocol stack: User Plane

User Plane protocol stack (2)

IP PDU#1 IP PDU#2 IP PDU#2

Radio Bearer 1 Radio Bearer 1 Radio Bearer 2

Header IP Payload Header IP Payload Header IP Payload

H H H
PDCP

SN PDCP SDU SN PDCP SDU SN PDCP SDU

RLC SDU RLC SDU RLC SDU

RLC

H H H
RLC PDU RLC PDU
MAC

H MAC SDU MAC SDU

Multiplexing
PHY

Transport Block CRC

14
Mobile and Wireless; 23-10-2014
 E-UTRAN protocol stack: Control Plane

Control Plane protocol stack (1)

!   RRC (Radio Resource Control) – 36.331

!   Broadcast of system information, paging, RRC connection management,
RB control, mobility functions, UE measurement reporting and control

!   PDCP (Packet Data Convergence Protocol) – 36.323

!   Ciphering and integrity protection

UE eNB MME

NAS NAS

RRC RRC

PDCP PDCP

RLC RLC

MAC MAC

PHY PHY

15
Mobile and Wireless; 23-10-2014
 E-UTRAN protocol stack: Control Plane

Control Plane protocol stack (2)

!   Only two RRC states

!   IDLE and CONNECTED
!   (Compare to IDLE, CELL_PCH, CELL_FACH, CELL_DCH in UMTS)

!   Idle mode
!   UE known in EPC, not in EUTRAN
!   UE has an IP address and its location known on Tracking Area level
!   UE-based cell-selection and tracking area update to EPC
!   MME initiates paging in the whole tracking areas indicated by the UE

!   Connected mode
!   Unicast data communication possible
!   UE known in E-UTRAN and its location known on Cell level
!   Mobility is UE-assisted, network-controlled
!   Discontinuous Data Reception (DRX) supported for power saving

16
Mobile and Wireless; 23-10-2014
 E-UTRAN Mobility

Control Plane protocol stack (3)

UE1 -> UE2 ->

S1-Conn. Y Core Network TA 403

S1 S1
S1-connection Y
eNB TA 403
(Tracking Area)

UE1 ->
Cell X
= Data
record RRC-connection

X
Cells TA 403
(Tracking Area)

Uu (the “radio interface”)

UE 1, Connected
C
h
4
a
n
n
s e
l
a a
C q s k
h
4
a
n w l d
n s
s e e d j
l a a
a a s f f
q k
q s k l r l
w d

UE 2, Idle mode
ö

mode
w l d s e d r ö
s j
e d j f t a
a a a a f
f f k r l i d l
q s k q s
l r l l d r ö ö u a
w d w
d r ö ö j t a o ö d
s e j e d
f t a f f i d l l k
a a f
k i d l l u a d k s
q s r l r
d ö u a ö ö o ö d k d f
w l r ö r
j t a o ö d t a l k l j
e d
f f i d l l k i d l d k s c
l u a d k s u a k d f
r
ö ö o ö d k d f o ö d l j .
r
t a l k l j l k c
i d l d k s c d k s
u a k d f k d f .
o ö d l j . l j
l k c c
d k s
k d f . .
l j
c

17
Mobile and Wireless; 23-10-2014
 E-UTRAN QOS

End-to-End QOS
E-UTRAN EPC Internet

UE eNB S-GW P-GW Peer

Entity

End-to-end Service

EPS Bearer External Bearer

E-RAB S5/S8 Bearer

Radio Bearer S1 Bearer

Radio S1 S5/S8 Gi

!   E-UTRAN is responsible for Radio Bearer management and therefore

ensuring QoS over the radio
!   one-to-one mapping between EPS bearer, E-RAB and Radio Bearer

18
Mobile and Wireless; 23-10-2014
 E-UTRAN QOS

Radio Bearer QOS Compare UMTS:

Traffic class
Maximum bitrate
Delivery order
!   RB  establishment  based  on  QoS  parameters  from  MME   Maximum SDU size
S SDU format
!   QoS  Class  Iden-fier  (QCI)  per  bearer:     e s t to A information
u
 scalar  value  which  iden@fies  a  par@cular   NAS req
SDU error ratio
Residual bit error ratio
 service  in  terms  of  resource  type,  priority,     Delivery of erroneous
SDUs
 packet  delay  budget  and  packet  error  rate  [23.203]   Transfer delay
Guaranteed bit rate
!   Guaranteed  Bit  Rate  (GBR)  per  bearer   Traffic handling priority
Allocation/ Retention
!   Maximum  Bit  Rate  (MBR)  per  bearer   priority
Source statistics
!   Aggregate  Maximum  Bit  Rate  (AMBR)  per  group  of  bearers   descriptor

!   RB  Scheduling  based  on  QoS  parameters  from  MME  and  scheduling    

informa@on  from  UE  
!   Channel  Quality  Indica@on  
!   Buffer  Status  Report  
!   Power  Headroom  Report  

!   Scheduling  for  downlink  is  eNB  implementa@on  specific  

!   Scheduling  for  uplink  is  only  par@ally  specified  
!   Logical  channel  priori@za@on  and  avoid  starva@on  [36.321]  
19
Mobile and Wireless; 23-10-2014
 E-UTRAN QOS

QOS: Reliability

!   L1  applies  24  bit  CRC  protec@on  to  transport  blocks  (MAC  PDUs)  
!   erroneous  transport  blocks  are  discarded  on  L1  

!   Hybrid  ARQ  (HARQ)  protocol  in  MAC  +  ARQ  protocol  in  RLC  
!   high  reliability  and  radio  efficiency  
!   HARQ  feedback  sent  on  L1/L2  control  channel  
!   Single,  un-­‐coded  bit  (low  overhead)  
!   Sent  for  each  scheduled  subframe  (fast)  
!   Retransmissions  are  so\-­‐combined  with  previous  a]empt  (efficient)  
!   ARQ  status  report  sent  as  MAC  data  
!   RLC  Status  is  sent  on  demand  (poll,  @mer,  gap  detec@on)  
!   protected  by  CRC  and  HARQ  retransmissions  

!   Both  HARQ  and  ARQ  protocols  operate  between  the  eNB  and  UE  
!   fast  handling  of  residual  HARQ  errors  

!   Ensures  low  latency  and  high  reliability  

20
Mobile and Wireless; 23-10-2014
 E-UTRAN QOS

Retransmissions: comparison to GSM/ UMTS

GPRS
Appl
IP GTP: GPRS Tunneling Protocol
SNDCP SNDCP GTP-U GTP-U E.g.
L2TP
LLC LLC UDP UDP or SNDCP: SubNetwork Dependent
RLC RLC IP
BSSGP BSSGP tunnel Convergence Protocol
MAC MAC IP IP IP a.o.: header/payload compression
GSM GSM L2 L2 L2 L2 L2 L2 L2
RF RF
L1 L1 L1 L1 L1 L1 L1 LLC: Logical Link Control
RLC (GPRS): Radio Link Control
MT Um BTS Abis BSS Gb SGSN Gn GGSN Gi

UMTS
Appl
IP PDCP: Packet Data Convergence
PDCP GTP-U
PDCP GTP-U GTP-U GTP-U E.g. Protocol
L2TP a.o.: header compression
RLC
MAC
RLC
MAC
REL-99 UDP
UDP UDP UDP or
IP
tunnel RLC (UMTS): Radio Link Control
MAC-hs MAC-hs FP
UMTS
MAC-e
RF
UMTS
MAC-e
RF ATM
REL-5/6ATM FP IP
ATM
IP
ATM
IP
L2
IP
L2
IP
L2
UMTS UMTS
RF RF L1 L1 L1 L1 L1 L1 L1
UE Uu Node-B Iub SRNC Iu SGSN Gn GGSN Gi
LTE
UE eNB

PDCP PDCP
LTE:
RLC RLC
•  MAC: performs retransmissions to obtain loss rate of around E-2
MAC MAC •  RLC: retransmissions up to loss rate of around E-6 or lower
•  PDCP: retransmissions at intra-LTE handover
PHY PHY

21
Mobile and Wireless; 23-10-2014
 E-UTRAN QOS

QOS: Latency

!   User Plane Latency < 10ms [36.912]

!   One way latency
!   Between 5ms and 10ms depending on HARQ operating point and
TDD configuration

!   Control Plane Latency : 50ms

!   Transition time from Idle to Connected mode

!   Handover: 12ms interruption time

!   For intra - E-UTRAN handover

22
Mobile and Wireless; 23-10-2014
 E-UTRAN Mobility

Mobility
!   IDLE: Cell Reselection
!   UE controlled cell reselection
!   UE decides when to change cell, influenced by network steering parameters

!   CONNECTED: Handover
!   UE-assisted :
!   Measurements are made and reported by the UE to the network
!   Network-controlled :
!   Target cell is selected by the network, not by the UE and Handover control in E-UTRAN (not
in packet core)
!   Lossless:
!   Packets are forwarded from the source to the target
!   Late path switch:
!   Only once the handover is successful, the packet core is involved
!   Two handover approaches:
!   S1-handover (“normal handover“ conform GSM/UMTS; no inter-eNB connection required)
!   X2-handover (see next slides)
23
Mobile and Wireless; 23-10-2014
 E-UTRAN Mobility: Handover

Mobility: X2-Handover(1)

MME !   Source  eNB  configures  UE  

S-GW measurements  
!   target  frequency  and  triggers  

S1-MME S1-U !   Source  eNB  receives  UE    

measurement  reports  

Source
eNB
Target
eNB
!   HO  decision  is  made  and    
X2 target  eNB  is  selected  by  the  
source  eNB  
measurements

control plane UE
user plane
user data
control plane signalling

24
Mobile and Wireless; 23-10-2014
 E-UTRAN Mobility: Handover

Mobility: X2-Handover(2)

MME !   HO  request  sent  from  source  

S-GW eNB  to  target  eNB  

!   Target  eNB  performs    

S1-MME S1-U admission  control  and  accepts  
the  HO  request  
HO request
Source
eNB
Target
eNB
!   HO  Ack  sent  to  source  eNB    
HO Request Ack from  target  eNB  
measurements

control plane UE
user plane
user data
control plane signalling

25
Mobile and Wireless; 23-10-2014
 E-UTRAN Mobility: Handover

Mobility: X2-Handover(3)

MME !   HO  command  is  sent  to  the  UE  

S-GW !   RRCConnec'onReconfigura'on  
message  including  the    
mobilityControlInfo  

S1-MME S1-U
!   Data  forwarding  ini@ated  
towards  the  target  eNB    
Source Target
eNB eNB
X2

HO command

control plane UE
user plane
user data
control plane signalling

26
Mobile and Wireless; 23-10-2014
 E-UTRAN Mobility: Handover

Mobility: X2-Handover(3)

MME !   UE  accesses  the  target  eNB  

S-GW and  confirms  the  HO  
!   RACH  procedure  is  ini@ated  
!   RRCConnec'onReconfigura'onComplete  
is  sent  
S1-MME S1-U

Source Target
eNB eNB
X2

HO confirm

control plane UE
user plane
user data
control plane signalling

27
Mobile and Wireless; 23-10-2014
 E-UTRAN Mobility: Handover

Mobility: X2-Handover(4)

MME
!   Target  eNB  requests  EPC  to  switch  
the  data  path  
S-GW !   eNB  →  MME  :  path  switch  request    

!   MME  →  S-­‐GW  :  modify  bearer  request  

!   S-­‐GW  →  MME  :  modify  bearer  response  

Source Target !   MME  →  eNB  :  path  switch  request  ACK  

eNB eNB
X2
!   Target  eNB  no@fies  the  source  eNB  
that  UE  resources  can  be  released  

control plane UE
user plane
user data
control plane signalling

28
Mobile and Wireless; 23-10-2014
 E-UTRAN Mobility: Handover

Mobility: X2-Handover(5)

MME !   Path  is  switched  

S-GW

!   Source  eNB  finishes  forwarding  

packets  
S1-MME S1-U !   once  completed  UE  context  can  be  
cleared  and  resources  freed  

Source Target !   HO  is  completed  

eNB eNB
X2

control plane UE
user plane
user data
control plane signalling

29
Mobile and Wireless; 23-10-2014
 E-UTRAN: Beyond Release-8

Release-10

!   Main goal of Rel-10 was to fulfil the IMT-Advanced requirements

!   up to 1Gbps in downlink and 500Mbps in uplink [36.913]
!   took 2 years of efforts in 3GPP
!   Release-10 Features:
!   Carrier Aggregation: increase the bit rate and reach IMT-A requirements [WID]
!   eICIC: to efficiently support highly increasingly complex network deployment scena
rios with unbalanced transmit power nodes sharing the same frequency [WID]
!   Relay Nodes: to improve the coverage of high data rates, cell-edge throughput
and ease temporary network deployments [WID]
!   Minimisation of Drive Tests / SON Enhancements: enhanced and combined effort
to optimize the performance of the network aiming to automate the collection of
UE measurements and thus minimize the need for operators to rely on manual
drive-tests [WID] [WID]
!   MBMS enhancements: to enable the network to know the reception status of Ues
receiving a given MBMS service in connected mode… [WID]
!   Machine Type Communication: protect the core network from signalling
congestion & overload [WID]

30
Mobile and Wireless; 23-10-2014
 E-UTRAN: Beyond Release-8

Release-10: Carrier Aggregation(1)

!   Goal of Carrier aggregation is to aggregate Rel-8 compatible carriers

to increase peak data rate

!   up to 5 carriers can be aggregated in DL for a maximum BW of 100 MHz

LTE-Advanced maximum bandwidth

Rel’8 BW Rel’8 BW Rel’8 BW Rel’8 BW Rel’8 BW

Carrier 1 Carrier 2 Carrier 3 Carrier 4 Carrier 5

!   non-contiguous carriers can also be aggregated in DL for increased flexibility

31
Mobile and Wireless; 23-10-2014
 E-UTRAN: Behond Release-8

Release-10: Carrier Aggregation(2)

!   Basic Concept
!   When CA is configured, the UE only has one PCC PCell  
RRC connection with the network
SCC SCell  
!   At RRC connection establishment, one serving
cell provides the NAS mobility information SCC SCell  
(e.g. TAI) / security input: Primary Cell (PCell)
!   In the downlink, the carrier corresponding to the
PCell is the Downlink Primary Component Carrier
(DL PCC) while in the uplink it is the Uplink Primary
Component Carrier (UL PCC)

!   Depending on UE capabilities, Secondary Cells (SCells) can be configured to form

together with the PCell a set of serving cells (“helper cells/resources”)
!   In the downlink, the carrier corresponding to an SCell is a Downlink Secondary
Component Carrier (DL SCC) while in the uplink it is an Uplink Secondary
Component Carrier (UL SCC)

!   The configured set of serving cells for a UE therefore always consists of one Pcell
and one or more SCells
32
Mobile and Wireless; 23-10-2014
 E-UTRAN: Beyond Release-8

Release-10: Carrier Aggregation(3)

!   Impact on L2 Architecture (nwk side)

Radio Bearers

ROHC ... ROHC ROHC ... ROHC

PDCP ...
Security ... Security Security ... Security There is one PDCP and RLC per
Radio Bearer. Not visible from
RLC on how many CCs the PHY
layer transmission is conducted.
Segm. Segm. Segm. Segm. Segm. Segm.
... ... ...
RLC ARQ etc ARQ etc ARQ etc ARQ etc
CCCH BCCH PCCH
MCCH MTCH
Logical Channels

Unicast Scheduling / Priority Handling Dynamic L2 packet scheduling

MBMS Scheduling
across multiple CCs supported

Multiplexing UE1 ... Multiplexing UEn Multiplexing

MAC

Independent HARQ per CC.

HARQ retransmissions shall be
HARQ ... HARQ HARQ ... HARQ sent on the same CC as the CC
of the original transmission
Transport Channels

DL-SCH DL-SCH DL-SCH BCH PCH MCH

on CC1 on CCx on CC1 Separate TrCH per CC

33
Mobile and Wireless; 23-10-2014
 E-UTRAN: Beyond Release-8

Example features in later releases

!   Release 11 (specifications completed March 2013)
!   Coordinate MultiPoint Transmission (COMP)

!   Release-12 (specifications to be completed March 2015)

!   LTE Device to Device Proximity Services
!   UEs can “discover” each other directly, when in network coverage
!   UEs can “communicate” directly, when in and out of coverage (Public Safety)
!   Also heavy CN impact
!   Dual Connectivity for LTE
!   One UE served by a “Main eNB” and “Secondary eNB”

!   Release-13 (work started)

!   Licensed-Assisted Access using LTE
!   CA with LTE in licensed + unlicensed spectrum
!   Physical layer enhancements for Low cost Machine Type Communication
!   Internet Of Things
!   Full dimension MIMO
34
Mobile and Wireless; 23-10-2014
 III Enhanced Packet Core (EPC)
•  Core Network Architecture
•  Example Signalling Sequences

•  PS CN evolution

•  Interworking with non-3GPP accesses

Mobile and Wireless; 23-10-2014

 CN Architecture

GSM/UMTS network architecture

BSS MSC PSTN/

A CS-domain ISDN

Gb

HLR

Iu
UTRAN IP
Uu GSN Gi
Iu PS-domain
CN
Two CN domains:
- Circuit-Switched (CS) domain
- Packet-Switched (PS) domain
36
Mobile and Wireless; 23-10-2014
 CN Architecture

LTE EPC architecture

!   Two User Plane Gateways (which can be merged):

!   Serving SAE GW
!   Local mobility Anchor for inter-eNB handover / inter-3GPP mobility
!   PDN SAE GW
!   Policy enforcement, per user packet filtering, charging
!   Mobility anchor for non-3GPP mobility

!   One Control Plane Node

!   Mobility Management Entity (MME)
!   NAS control protocol between UE and MME (24.301)
!   Mobility in IDLE mode
UE eNB MME
!   EPS bearer management NAS NAS

RRC RRC

PDCP PDCP

!   Only 1 CN domain
RLC RLC

MAC MAC

!   GSM/UMTS: CS & PS
PHY PHY

!   LTE: Only PS
!   Resulting in large simplication of procedures
!   UMTS UE always registered in Location Area (CS: MSC) and Routing Area (PS: SGSN)
!   LTE UE only registered in Tracking Area (MME)
Source: TS23.401
37
Mobile and Wireless; 23-10-2014
 Signalling Sequence Example: Connection Establishment

RRC Connection establishment (AS)

UE E-UTRAN

RRC CONNECTION REQUEST

RRC CONNECTION SETUP

GW MME
CN

RRC CONNECTION SETUP COMPLETE

RRC Connection (C-plane)

E-RAB
S1-connection (C-plane)
E-Radio Access Bearer Service

INITIAL UE MSG

E-RAB (U-plane)
E-UTRAN

E-UTRAN

SRB
Radio Bearer Service

RRC CONNECTION SETUP

(CCCH)
RRC CONNECTION SETUP
COMPLETE
RRC CONNECTION (DCCH)
REQUEST
RB
UE

(CCCH)

UE E-UTRAN Radio Access Bearer (E-RAB)

Signalling Radio Bearer (SRB)
Radio Bearer (RB)

38
Mobile and Wireless; 23-10-2014
 Signalling Sequence Example: Bearer Establishment

Dedicated Bearer Activation Procedure (NAS)

UE eNodeB MME Serving GW PDN GW PCRF

1. Session Modification
(A)
 
2. Create Bearer Request

3. Create Bearer Request

4. Bearer Setup Request
(NAS: Activate dedicated EPS bearer context request)

5. RRC Connection Reconfiguration

(NAS: Activate dedicated EPS bearer context request)
6. RRC Connection Reconfiguration
7. Bearer Setup Response
8. UL Direct Transfer
(NAS: Activate default EPS bearer context accept)
9. Uplink NAS transport
(NAS: Activate default EPS bearer context accept)
10. Create Bearer Response
11. Create Bearer Response
12. Session Modification
(B)  

IP
RB GPRS GPRS
Network
Tunnel Tunnel IP-packets

39
Mobile and Wireless; 23-10-2014
 PS evolution: IMS

PS-CN evolution
!   Normally uses dynamic IP addresses, only allocated to the UE
when the UE establishes a PDP context;
!   Results in “pull-based” approach (dial-up approach);
!   Very limited support for “push-based” services;
!   No standardised way for establishing sessions with other users
!   How to establish a video session, audio session with somebody on the Internet ?
E.g. user wants to start chess game with peer user ? What
signalling to use ?
!   Network convergence (removal of CS CN)
!   Operator could leave choice to user:
!   Multitude of different solutions
!   Less control
!   Charging might be complicated
!   Need a protocol that is suitable for session establishment,
modification and release, and that addresses the “pull limitation”.

40
Mobile and Wireless; 23-10-2014
 PS evolution: IMS

IP Multimedia Core Network Subsystem (IMS)

!   IP Multimedia Core Network Subsystem (IMS) is part of 3GPP Rel-5

!   Uses SIP (Session Initiation Protocol) as the protocol for session
management
!   SIP is standardised by IETF (RFC-3261)
!   Main SIP functionality:
!   Setup, Modify and Tear down of multi-media Sessions
!   Request and deliver presence information
!   Instant messaging
!   Works with URI’s “Uniform Resource Indicators”, which might be location
independent
!   User related URI, also called AOR “Address of Record”
!   This you store in your address book
!   Device URI
!   Associated to a user for a shorter period of time

41
Mobile and Wireless; 23-10-2014
 PS evolution: IMS

SIP: Simple signalling example (no proxy)

Irma Erik
INVITE sip:[email protected] SIP/2.0
INVITE
Via: SIP/2.0/UDP server1.kpn.nl:5060; branch=d987fsdjhff
Max-Forwards: 70
180 Ringing To: Erik <sip: [email protected]>
From: Irma <sip: [email protected]>; tag=98774
200 OK Call-ID: 123456789”server1.kpn.nl
Cseq: 1 INVITE
Subject: When do we meet ?
ACK Contact: [email protected]
Content-Type: application/SDP
Media Session Content-Length: 158

SDP content………
BYE

200 OK

!   Peer-to-Peer
!   Text based
!   Transport can use UDP, TCP or SCTP
!   Without Proxy, IP address of peer user needs to be known

42
Mobile and Wireless; 23-10-2014
 PS evolution: IMS

SIP: Signalling example (with proxy)

Irma SIP Proxy Erik
INVITE
INVITE
-  User related URI Irma (from)
-  User related URI Irma (from)
-  User related URI Erik (to) 180 Ringing
180 Ringing -  User related URI Erik (to)
-  Device URI Irma (contact)
-  Device URI Erik (contact)
200 OK
200 OK

ACK

Media Session

BYE

200 OK

!  Irma does not know where Erik is:

!  DNS lookup on Erik’s URI domain name (idols.nl)
!  DNS lookup returns IP address of the proxy server
!  INVITE is sent to this address
!  Proxy server:
!  looks up the SIP URI in the request URI “sip: [email protected]” in its DB, and determines the current IP address
where Erik can be reached;
!  Forwards INVITE to that address
!  If Erik is temporarily reachable via another node, he could sent a REGISTER message
to a REGISTRAR server, to inform it about the new node. This information can then be
used by a SIP Proxy.
43
Mobile and Wireless; 23-10-2014
 PS evolution: IMS

IMS architecture (1)

S-CSCF
SIP signalling
C
h
4
a

a
q
s
n
n

s
a
e
l

l
k
P-CSCF I-CSCF
w d
s
e d j
a a
s f f
q k
w l d r l
d r ö ö
s e j
f t a
a a f
k r l i d l
q s
l d r ö ö u a
w ö
d j t a o d
e
f f i d l l k
l u a d k s
r
ö ö o ö d k d f
r
t a l k l j

User Traffic
i d l d k s c
u a k d f
o ö d l j .
l k c
d k s
k d f .
l j
c

GPRS/UMTS
IP Multimedia CN Subsystem
Access

!   P-CSCF (Proxy-Call Session Control Function)

!   is the first contact point within the IMS for the subscriber.
!   interfaces to PCRF for RAN/EPC resource control
!   I-CSCF (Interrogating-CSCF)
!   is the contact point within an operator's network for all connections destined to a
subscriber of that network operator, or a roaming subscriber currently located within
that network operator's service area.
!   S-CSCF (Serving-CSCF)
!   performs the session control services for the subscriber. It also acts as a SIP Registrar.
Source: RFC 3574 44
Mobile and Wireless; 23-10-2014
 PS evolution: IMS

IMS architecture (2): Routing of INVITE

Source: Luis Angel 45

Mobile and Wireless; 23-10-2014 Galindo
 PS evolution: IMS

IMS Outgoing call example: SIP signalling [1]

Visited P-CSCF Home S-CSCF Home P-CSCF Called
Caller
INVITE SIP request messages
INVITE ACK:
INVITE
100 Trying INVITE Acknowledge final responses to
100 Trying
100 Trying INVITE requests
183
183 INVITE:
183 Establish session
183
PRACK:
PRACK Ack for reliable transported
PRACK PRACK
PRACK provisional response

UPDATE:
200 OK Update session without changing
200 OK State of dialog
200 OK
200 OK SIP Response messages
100 Trying:
UPDATE hop-by-hop progress indication
UPDATE
UPDATE
UPDATE
180:
Alerting is taking place
200 OK
200 OK 183:
200 OK 180 End-to-end progess (e.g. establi
200 OK 180 sh one-way media for ring tone,
180 200 OK busy tone or announcement “you
180 200 OK call is being diverted”))
200 OK
200 OK 200 OK:
1) Accept session invitation
ACK 2) General confirmation stopping
ACK
ACK retransmissions
ACK
Media Session

46
Mobile and Wireless; 23-10-2014
 PS evolution: IMS

IMS Outgoing call example: Overview originating side [2]

UE E-UTRAN MME P-GW P-CSCF I-CSCF S-CSCF

1) RRC Connection establishment

2) Attach (establish MM context)

3) Activate Default EPS bearer context

- UE IP address
- P-CSCF IP address 4) Service Registration (SIP Register)

5) INVITE

6) SDP negotiation

7) Activated Dedicated EPS bearer context

8) Session Confirmation (200OK & ACK)

9) Session in Progress

47
Mobile and Wireless; 23-10-2014
 PS evolution: IMS

Signalling and Traffic paths

Source: award solutions

48
Mobile and Wireless; 23-10-2014
 Long Term Evolution

Logical architecture (non roaming)

Source: TS23.401
49
Mobile and Wireless; 23-10-2014
 Long Term Evolution; non-3GPP accesses

Inter-working with non-3GPP accesses

!   SAE supports both host-based and network-based mobility management solutions

!   Dual-Stack MIPv6 (host-based)
!   Proxy MIPv6 and MIPv4 in Foreign Agent mode (network-based)

!   PDN GW works as MIP/PMIP Home Agent

!   When connected to a 3GPP access the UE can be assumed to be at home in MIP sense
!   Mobility within 3GPP accesses (E-UTRAN, UTRAN and GERAN) is managed in a
network-based fashion using 3GPP-specific protocols

!   SAE distinguishes between “trusted” and “untrusted” non 3GPP accesses

!   It is up to the operator to decide if a non 3GPP access is trusted or untrusted
!   The decision is not based just on the access network technology but may depend
also on business considerations
!   Interworking with an untrusted access is performed via an evolved PDG (ePDG)
!   the ePDG is similar to a VPN concentrator
!   the UE has to establish an IPsec tunnel with the ePDG to access operator’s services
!   the ePDG may implement IP mobility protocols (e.g. PMIPv6)
!   Interworking with a trusted access is performed using a more lightweight procedure
!   The UE does not need to establish an IPsec tunnel with the ePDG in advance
!   MIP or PMIP protocols can be used directly between the non 3GPP access network and
the EPC

50
Mobile and Wireless; 23-10-2014
 Long Term Evolution; non-3GPP accesses

Inter-working with non-3GPP accesses

51
Mobile and Wireless; 23-10-2014
 Long Term Evolution; non-3GPP accesses

Example: Handover to trusted non-3GPP access (1)

HA: Home Agent (MIP/PMIP)

MAG: Mobility Access Gateway (PMIP)
AGW: Access GateWay
ePDG: evolved Packet Data Gateway
Source: IST Mobile Wireless
52
Mobile and Wireless; 23-10-2014
 Long Term Evolution; non-3GPP accesses

Example: Handover to trusted non-3GPP access (2)

Source: IST Mobile Wireless

53
Mobile and Wireless; 23-10-2014
 Long Term Evolution; non-3GPP accesses

Example: Handover to trusted non-3GPP access (3)

54
Mobile and Wireless; 23-10-2014
 IV Summary

Mobile and Wireless; 23-10-2014

 Summary

Summary

!   3rd Generation Partnership Project (3GPP)

!   Long History of Successful standardisation
!   GSM, UMTS, UMTS-HSDPA/HSUPA, LTE, LTE-A (CA),…..

!   Access Stratum <-> Non Access Stratum (AS ó NAS)

!   Required to introduce LTE in RAN/CN network architecture

!   E-UTRAN
!   LTE RAN brings a new flat RAN architecture with high throughput/capacity

!   PS CN evolution
!   Enhanced Packet Core (EPC) / IP Multimedia Core Network System (IMS)

!   Interesting new topics

!   Dual-Connectivity (Rel-12)
!   Direct Discovery/Direct Communication (Rel-12)
!   Licensed-Assisted Access (Rel-13)
!   Internet of Things IoT (Rel-12/13)
!   …..

56
Mobile and Wireless; 23-10-2014
 V Backup Slides

Mobile and Wireless; 23-10-2014

 Long Term Evolution

UMTS<-> LTE comparison: Radio technology

HSDPA/E-DCH 3GPP LTE Rel-8

Radio Technology W-CDMA OFDM

(better suited for higher BW)

Peak Data Rates Lower Spectrum 100Mbps/50Mbps

(DL/UL) efficiency in 20Mhz

Flexible Bandwidth 5Mhz / 1.25 , …, 20Mhz /

N * 5Mhz N * (1.25 , …, 20Mhz)

User plane latency ± 50ms ± 10ms

58
Mobile and Wireless; 23-10-2014