EPC Presentation Final

EPC Session
Content
LTE Overview
Architecture , Interface and Protocols
Functional Description
LTE Bearers and QoS
LTE Identifiers
Call Flows
2 | Videocon Mobile Services | 2010

Mobile Broadband Landscape
Cellular Wireless Law of Speed vs. Decade
1T
100G
5G
10G
?
Mobile device Cell size shrinks Cel
4G for everything count increases
Gbps 3G 50
16
Mbps 2G
4
kbps 1G 1
bps AMPS
40 Years
1980 1990 2000 2010 2020 Time
Page 3
The Rise of Mobile Broadband
To enable x10 (speed) x10 (devices) x10 (industries)
Connected Devices
Tablet and Smartphone
Laptop and Cellphone
Anything that can be connected

will be connected
Key Technical Challenges
Low Latency <20ms
Affordable
100 Mbps ( 1Gbps ??)
anytime, anywhere
Full Mobility 350km/h Seamless Coverage
High Data Rate
5
The Beauties of LTE
OFDM
tim
e
Fast Link
64QAM Multi-layer transmission
Adaptatio frequency
n Modulation
due to
channel
behaviou
r
scalable Short TTI = 1
ms
Transmission
time interval
HARQ
Hybrid
Automatic
DL: OFDMA
Repeat Request
UL: SC-FDMA

3GPP Releases
7 | Videocon Mobile Services | 2010 Page7

3GPP Evolution in Release 5 Release 8
Long term
evolution (LTE)
Basic HSDPA+HSUPA HSPA evolution +
Further HSPA
evolution
HSPA
HSPAR5
R5 HSPA
HSPAR6
R6 HSPA
HSPAR7
R7 3GPP
3GPPR8
R8
HSDPA 14 HSUPA 5.76 Enhanced FACH LTE: New PS only
Mbps Mbps Continuous radio
MBMS packet Further HSPA
connectivity evolution
L2 optimization
Flat architecture
MIMO
Higher order
modulation
VoIP capacity
MBMS evolution

HSPA Peak Data Rate Evolution
HSPA downlink data rate increases with 2x2 MIMO and 64QAM up to 42 Mbps
and uplink data rate with 16QAM up to 11 Mbps
LTE further increases the data rate beyond 100 Mbps with larger bandwidth of
20 MHz
3GPP R5 3GPP R6 3GPP R71 3GPP R8

k rate LTE: 300
k p ea
Downlin Mbps
HSPA: 42
28 Mbps1 Mbps 2
14 Mbps LTE: 75 Mbps
14 Mbps 11 Mbps
5.7 Mbps
0.4 Mbps
p ea k rate
Uplin k
With 2x2 MIMO and 16QAM
1
With 2x2 MIMO and 64QAM likely for R8

2

What is new in LTE?

Presentation / Author / Date
Main LTE Requirements [3GPP TS25.913]
Peak data rates of uplink/downlink 50/100 Mbps
Reduced Latency:
Enables round trip time <10 ms
Ensure good level of mobility and security
Optimized for low mobile speed but also support high mobile speed
Frequency flexibility and bandwidth scalability:
with 1.4, 3, 5, 10, 15 and 20 MHz allocations
Improved Spectrum Efficiency:
Capacity 2-4 times higher than with Release 6 HSPA
Efficient support of the various types of services, especially from the PS
domain
Packet switched optimized
Operation in FDD and TDD modes
Improved terminal power efficiency
Support for inter-working with existing 3G system and non-3GPP specified
systems

System Performance Requirements for LTE-Advanced
Peak data rate

1 Gbps data rate will be achieved by 4-by-4 MIMO and transmission bandwidth wider
than approximately 70 MHz
Peak spectrum efficiency
DL: Rel. 8 LTE satisfies IMT-Advanced requirement
UL: Need to double from Release 8 to satisfy IMT-Advanced requirement
14
14| Videocon Mobile Services | 2010
LTE-Release 8 User Equipment Categories
15
15| Videocon Mobile Services | 2010
LTE/LTE-A Frequency Bands (FDD/TDD)
Uplink (UL) operating band Downlink (DL) operating band
EUTRA Uplink (UL) operating
Downlink (DL) operating band
Operating EUTRA band
Band FUL_low FUL_high [MHz] FDL_low FDL_high [MHz] Operating
Band
FUL_low FUL_high [MHz] FDL_low FDL_high [MHz]
1 1920 1980 2110 2170
2 1850 1910 1930 1990
33 1900 1920 1900 1920
3 1710 1785 1805 1880
34 2010 2025 2010 2025
4 1710 1755 2110 2155
5 824 849 869 894 35 1850 1910 1850 1910
6 830 840 875 885
36 1930 1990 1930 1990
7 2500 2570 2620 2690
37 1910 1930 1910 1930
8 880 915 925 960
9 1749.9 1784.9 1844.9 1879.9 38 2570 2620 2570 2620
10 1710 1770 2110 2170
39 1880 1920 1880 1920
11 1427.9 1452.9 1475.9 1500.9
40 2300 2400 2300 2400
12 698 716 728 746
13 777 787 746 756
14 788 798 758 768
17 704 716 734 746
18 815 830 860 875
19 830 845 875 890
20 832 - 862 791 - 821
21 1447.9 - 1462.9 1495.9 - 1510.9
22 3410 - 3500 3510 - 3600

Downlink Peak Bit Rate
2x2 MIMO (2 antennas for TX, 2 Antennas for RX)
64QAM
Control overhead 7.1%
Reference symbol overhead 7.7%
172 Mbps in 20 MHz and 86 Mbps in 10 MHz

Uplink Peak Bit Rate
Single stream transmission with 64QAM assumed
Reference symbol overhead 14.3%
One resource block for Physical Uplink Control Channel (PUCCH)
85 Mbps in 20 MHz and 42 Mbps in 10 MHz

Multiple Access Methods
TDMA FDMA CDMA OFDMA
Time Division Frequency Division Code Division Frequency Division

Orthogonal subcarriers
f f f f
es
d
t t co t t
f f f f
User 1 User 2 User 3 User ..

Signal in Time and Frequency Domain

OFDM Basics
Transmits hundreds or even thousands of separately modulated radio signals

using orthogonal subcarriers spread across a wideband channel
Total transmission bandwidth
f 1 / Tu
Orthogonality:
The peak ( centre

frequency) of one
subcarrier
intercepts the
nulls of the
neighbouring
subcarriers

Orthogonality between subcarriers
Orthogonality between subcarriers
The orthogonality between subcarriers is due to the specific frequency

domain structure of each subcarrier and the specific choice of
f 1 / Tu
Orthogonality in Radio Environment
Orthogonality is maintained if the subcarriers are not distorted during the
integration time period.
Subcarriers in the same radio path are orthogonal to each other
Subcarriers from radio paths with different time delay are not orthogonal

Doppler in OFDM and Loss of Orthogonality
Doppler effect (shift): Change in frequency of a wave due to the relative motion of
source and receiver.
Symbols are distorted in the time domain

Frequency shifts make symbol detection inaccurate
MCS schemes with high number of bits per subcarrier (high data rates) are not
suitable for MSs
moving at high speed
Doppler only impacts SINRs at the higher range i.e. > 20dB
It reduces orthogonality
The frequency domain
subcarriers are shifted
causing inter-carrier
interference (ICI)

Cyclic Prefix (CP) and Guard Time
Multipath causes Inter Symbol Interference ( ISI) which affects the subcarrier orthogonality
due to phase distortion
Solution to avoid ISI is to introduce a Guard Period (Tg) after the pulse
To make use of that Tg (no transmission) Cyclic Prefix is transmitted
Orthogonality between subcarriers from different radio paths can be maintained if the
delay difference is less than Tg or TCP
total symbol time T(s)
Guard Time
t
CP symbol Useful
T(g) time Tu

Determining Basic OFDM Parameters
TCP: in principle the higher is the multipath delay spreading for the interesting radio
environment, the larger is this time.
Tu: TCP is an overhead regarding time and Tx power. The overhead is given by TCP /
(TCP + Tu). Hence, to minimize the CP overhead, large Tu is preferred.
f: f = 1/Tu. Though large Tu is preferred, it also means small subcarrier spacing in

frequency domain. However, a too small subcarrier spacing increases the sensitivity of
the OFDM transmission to Doppler spread and different kinds of frequency
inaccuracies.
In LTE
f = 15 KHz, Tu = 66.7 s
2 CP options are defined
Normal CP: for small cells or with short multipath delay spread
Extended CP: designed for use with large cells or those with long delay
profiles
OFDM symbol duration including CP is approx. 71.4 s
Long duration when compared with 3.69s for GSM and 0.26s for WCDMA allowing a good CP
duration

26 | Videocon Robust for mobile
Mobile Services | 2010 radio channel with the use of guard internal/cyclic prefix
Peak-to-Average Power Ratio in OFDMA
The transmitted power is the sum of the
powers of all the subcarriers.
Due to large number of subcarriers, the

peak to average power ratio (PAPR)
tends to have a large range
The higher the peaks, the greater the

range of power levels over which the
power amplifier is required to work
Having a UE with such a PA that works

over a big range of powers would be
expensive
Not best suited for use with mobile

( battery-powered) devices

OFDMA Transmitter Structure Transmitted frequency spectrum:
Total channel bandwidth

a0( m ) f0
Modulation
Mapping a1( m ) Subcarrier
f1 CP
e.g. QPSK S/P IFFT P/S
(m) Mapping Insertion
symbols a N c 1 f N c 1
j 2f t
e 0
a0( m ) x0 (t )

e j 2f1t x(t )
a0( m) , a1( m) .......a N( mc)1 x1 (t )

(m)
a 1

S/P N c 1 N c 1
e
j 2f N 1t
c x(t ) xk (t ) ak (m)e j 2kft
a N c 1 x N c 1 (t ) k 0 k 0
f k kf

Figure valid for time interval mTu t (m 1)Tu

OFDMA Received Structure Received frequency spectrum:
Subcarrier
CP FFT De- Demodulati
S/P P/S on
Removal mapping
j 2f t
e 0 a (m 1)Tu
( m)
mTu
a0
r (t ) e j 2f1t
(m 1)Tu
S/P a
1
( m)
mTu
f k kf e
j 2f N 1t
c
(m 1)Tu ( m)
a
Nc 1
mTu

Transmitted frequency spectrum
SC-FDMA Transmitter Structure
0 Total channel bandwidth

0
0
Modulation f0
IFFT
Mapping DFT Subcarrier . CP
e.g. QPSK S/P . (Size P/S
(Size M) mapping . Insertion
symbols fM 1
N)
0
0
j 2f t
e 0 0
a0( m ) x0 (t )

e j 2f1t x(t )
a0(m) , a1(m) .......a N(m)1 x1 (t )

(m)
a 1

S/P N 1 N 1
e j 2f N 1t
x(t ) xk (t ) ak ( m)e j 2kft
k 0 k 0
f k kf ( m)
aN x N 1 (t )

1

Transmitted frequency spectrum
SC-FDMA Receiver Structure
IFFT Subcarrier
CP IDFT
S/P (Size De- P/S Demodulation
Removal
N) mapping (Size M)
j 2f t
e 0 a (m 1)Tu
( m)
mTu
a0
r (t ) e j 2f1t
(m 1)Tu
S/P a
1
( m)
mTu
f k kf e j 2f N 1t
(m 1)Tu ( m)
aN 1
mTu

Downlink - OFDM
Subchannels (each 15 kHz)
1.4 MHz = 72 Subcarriers 20 MHz = 1200 Subcarriers
User 1
User 2
User 3
User ..
e
tim
1 TTI
= 1ms
1 PRB = 2 Slots = 2 * 0.5 ms
1 PRB (Physical Resource Block) = 12 Subcarriers = 180 kHz

Uplink Single Carrier FDMA
Subchannels (each 15 kHz)
User 1 1.4 MHz = 72 subcarriers 20 MHz = 1200 Subcarriers
User 2
User 3
User ..
e
tim
1 TTI
= 1ms
1 PRB = 2 Slots = 2 * 0.5 ms
1 PRB (Physical Resource Block) = 12 Subcarriers = 180 kHz
SC-FDMA: PRBs are grouped to bring down Peak to Average Power Ratio (PAPR)
> better power efficiency at the terminal
Comparing OFDMA and SC-FDMA QPSK example using
M=4 subcarriers
The following graphs show how a
sequence of eight QPSK symbols is 1, 1 -1,-1 -1, 1 1, -1 -1,-1 1,1 1, -1 -1,1
represented in frequency and time
Q Time
-1,1 1,1
-1,-1 1,-1
V V
bo A
m M
sy -FD
l
SC
CP
CP
e
e
m
bo A
m A
m M
Ti
Ti
sy DM
sy -FD
l
l
bo
F
SC
O
Frequency 60 kHz Frequency

fc 15 kHz fc
OFDMA SC-FDMA
Data symbols occupy 15 kHz for Data symbols occupy M*15 kHz for
one OFDMA symbol period 1/M SC-FDMA symbol periods
OFDMA Parameters

LTE Frame Structure

Downlink CP Parameters

Resource Block and Resource Element
Physical Resource Block or Resource Block ( PRB or RB):

12 subcarriers in frequency domain x 1 slot period in time domain.
Subcarrier 1 0 1 2 3 4 5 6 0 1 2 3 4 5 6 Capacity allocation is based

0 1 2 3 4 5 6 0 1 2 3 4 5 6 on Resource Blocks
0 1 2 3 4 5 6 0 1 2 3 4 5 6 Resource Element ( RE):
0 1 2 3 4 5 6 0 1 2 3 4 5 6 1 subcarrier x 1 symbol
0 1 2 3 4 5 6 0 1 2 3 4 5 6
period
B
180 KHz
0 1 2 3 4 5 6 0 1 2 3 4 5 6
Theoretical minimum
R
0 1 2 3 4 5 6 0 1 2 3 4 5 6
0 1 2 3 4 5 6 0 1 2 3 4 5 6
capacity allocation unit
1 RE is the equivalent of 1
0 1 2 3 4 5 6 0 1 2 3 4 5 6
0 1 2 3 4 5 6 0 1 2 3 4 5 6
modulation symbol on a
0 1 2 3 4 5 6 0 1 2 3 4 5 6 subcarrier, i.e. 2 bits for
Subcarrier 12 0 1 2 3 4 5 6 0 1 2 3 4 5 6 QPSK, 4 bits for 16QAM and
1 slot 1 slot 6 bits for 64QAM.
Resource
1 ms subframe Element

Resource Block and Resource Element
# PRBs with 20 MHz spectrum 100
# Subcarriers/PRB 12
# Total Subcarriers 100 x 12 = 1200
# Time Slots/Subframe 2
# OFDM symbols/ Time Slot 7
# Total OFDM symbols per Subframe 2 x 7 =14
# Resource Elements per Subframe 14 x 1200 = 16800
# Data Symbols per Resource Element 2 (QPSK), 4 (16 QAM) and

6 (64 QAM)
# Total Data Symbols with 64 QAM 16800 x 6 = 100800
# Transmission Layers with 4 x4 MIMO 4
# Total Data Symbols with 4 Transmission 100800 x 4 = 403200

Layers
# Code rate ( No redundancy) 1
# Overhead 14.8%
# Peak Bit Rate
(1- 14.8%) * 403200/
Subframe duration (1ms)
MIMO Concept
Up Link Down Link

2x2 MIMO 2x2 MIMO
Multiple antenna transmit multiple antenna receive higher peak rate

MIMO exploit multi-path to create parallel streams
Easy to install and maintain antennas Conventional x-pol antenna
Lower operational cost
MIMO works in all environments urban, suburban, rural
MIMO designed for mobility
40
Shannon Theory and MIMO
CSISO=Wlog2(1+SNR)
CMIMO=mWlog2(1+SNR/m
)
41
Combined OFDM and MIMO
Achieves Highest Throughput
LTE allows dynamic

switching the MIMO Modes
to achieve superior MIMO
performance
MIMO Better spectral efficiency Spatial Multiplexing

Matrix
Better coverage Transmit Diversity
LTE down link MIMO profile can be adapted dynamically to deliver

optimized user throughput
42
LTE/SAE Network Architecture Subsystems
LTE/SAE architecture is driven by the goal to optimize the system for packet data
transfer.
No circuit switched components
New approach in the inter-connection between radio access network and core
network
The EPS architecture is made up of an IMS/PDN

EPC (Packet Core Network, also referred
as SAE) and an eUTRAN Radio Access
Network (also referred as LTE)
EPC
The CN provides access to external
packet IP networks and performs a
number of CN related functions (e.g.
QoS, security, mobility and terminal eUTRAN EPS
context management) for idle (camped)
and active terminals
The RAN performs all radio interface LTE-UE
related functions

Packet Core Evolution in 3GPP
network
Direct tunnel I-HSPA LTE/SAE
HSPA R6 HSPA R7 HSPA R7 LTE R8
GGSN GGSN GGSN SAE GW/

GGSN
SGSN SGSN SGSN MME/

SGSN
Control User
RNC RNC plane plane
Node-B Node-B Node-B eNode-B
Direct Tunnel is mandatory in 3GPP R8

SAE GW comprises SGW and PGW

LTE/SAE Network Interfaces
LTE Radio Interface and the X2 Interface
LTE-Uu
.. Air interface of EUTRAN
Based on OFDMA in downlink and SC-FDMA in
uplink
FDD and TDD duplex methods
eNB Scalable bandwidth 1.4MHz to currently 20 MHz
Data rates up to 100 Mbps in DL
MIMO (Multiple Input Multiple Output) is a major
LTE-Uu component although optional.
X2
Inter eNB interface
X2 Handover coordination without involving the EPC
X2AP: special signalling protocol
During HO, Source eNB can use the X2 interface
to forward downlink packets still buffered or
arriving from the serving gateway to the target
eNB.
This will avoid loss of a huge amount of packets
during inter-eNB handover.
eNB
S1-MME & S1-U Interfaces
MM
S1-MME E
Control interface between eNB and MME
S1flex allows 1 eNB to connect to several MME
MME and UE will exchange non-access stratum
signaling via eNB through this interface.
E.g.: if a UE performs a tracking area update the
TRACKING AREA UPDATE REQUEST
message will be sent from UE to eNB and the eNB
eNB will forward the message via S1-MME to
the MME. SG
W
S1AP:S1 Application Protocol
S1-U
User plane interface between eNB and serving
gateway.
It is a pure user data interface (U=User plane).
S1flex-U also supported: a single eNB can
connect to several Serving GWs.
Which Serving GW a users SAE bearer will
have to use is signaled from the MME of this
user.
S10 & S6a Interfaces
MM HSS
E MM
E
S10 S6a
Interface between different MMEs Interface between the MME and the HSS
Used during inter-MME tracking area updates The MME uses it to retrieve subscription
The new MME can contact the old MME the information from HSS (handover/tracking area
user had been registered before to retrieve data restrictions, external PDN allowed, QoS, etc.)
about identity (IMSI), security information during attaches and updates
(security context, authentication vectors) and The HSS can during these procedures also
active SAE bearers (PDN gateways to contact, store the users current MME address in its
QoS, etc.) database.
Obviously S10 is a pure signaling interface, no
user data runs on it.
S11 & S5/S8 Interfaces S5/S8
MM
E Interface between Serving GW and PDN GW
S11 S5: If Serving GW and PDN GW belong to the
Interface between MME and a same network (non-roaming case). Provides
Serving GW user plane tunneling and tunnel management
A single MME can handle between Serving GW and PDN GW..
multiple Serving GW each one S8:Roaming variant of S5 interface with SGW
with its own S11 interface in the visiting network and PGW in the home
network. Inter-PLMN reference point providing
Used to coordinate the user and control plane between the Serving
establishment of SAE bearers GW in the VPLMN and the PDN GW in the
within the EPC HPLMN.
EPS bearer setup can be S5/S8 can be implemented either by reuse of
started by the MME (default the GTP protocol from 2G/3G or by using
EPS bearer) or by the PDN Mobile IPv6 with some IETF enhancements.
Gateway.
SGi PDN
SG PG
W W
S7 & SGi Interfaces
PC
R F
PDN
PG
W
S7 SGi
Interface between PDN GW and PCRF Interface used by the PDN GW to send and receive
(Policy and Charging Rule Function) data to and from the external data network
It allows: It is typically either IPv4 or IPv6 based
- the PCRF to request the setup of a Downlink data coming from the external PDN must
EPS bearer with appropriate QoS be assigned to the right SAE bearer of the right user
- allows the PDN GW to ask for the by analysis of the incoming packets IP addresses,
QoS of an EPS bearer to setup port numbers, etc.
- to indicate EPC status changes to This interface corresponds to the Gi interface in
the PCRF to apply a new policy rule. 2G/3G networks
Rx+ Interface
PC
R F
S7
SGi
PDN
PG
W
Rx+
Interface between PCRF(Policy & Charging Rules
Function) and the external PDN
network/operators IMS
Standardized in 3GPP TS 23.203.
SAE/LTE Interworking with 2G/3G Networks
S3 & S4 Interfaces
SG
W
SGSN
MM
E
S3/S4
Interfaces between EPC and 2G/3G packet switched core network domain
They allow inter-system mobility between LTE and 2G/3G.
The S3 is a pure signaling interface located between SGSN and MME and enables user and
bearer information exchange for inter 3GPP access network mobility in idle and/or active state.
The S4 is located between SGSN and SGW and provides related control and mobility support
between GPRS Core and the 3GPP Anchor function of SGW. In addition, if Direct Tunnel is not
established, it provides the user plane tunneling.
SAE/LTE Interworking with 3G - Alternative
S12 Interface
UTRAN
SG
W
S12
Interfaces between EPC and 3G Radio access network
It would allow inter-system changes between SAE and 3G
The S12 is the user plane interface used for tunneling user data directly between the Serving
SAE GW and the UTRAN.
This would allow to forward packet data from 3G RAN to Serving SAE GW to PDN GW.
It is based on the Gn interface between the SGSN and the GGSN and so uses the GTP-U
protocol.
Control Plane Protocol Stack
User Plane Protocol Stack
LTE/SAE Roaming Architecture Case 1
Case 1:
Home Routed Traffic
By connecting Serving
GW in vPLMN to PDN
GW in hPLMN
GTP tunnel and MIPv6
options over the S8
interface
Also called Remote
Breakout.
LTE/SAE Roaming Architecture Case 2
Case 2: Local Breakout
UE can access the PDN network directly from
the vPLMN rather than traffic being routed
through the hPLMN.
Breakout should depend on the service:
i.e.:internet accesslocal breakout
i.e.:access to corporate VPNremote breakout
S9: PCRF-to-PCRF interface: roaming
controlled by hPLMN policies
S9 Interface
hPCRF vPCRF
S9
Interfaces between the hPCRF and the vPCRF used in roaming cases.
It is used enforcement in the VPLMN of dynamic control polices from the HPLMN.
LTE/SAE Interworking with Non-3GPP Access
Common GW for all accesses

Generic support for any non-3GPP
access (e.g. WLAN, Fixed)
Session Mobility using Mobile IP
Policy control supported for non-
3GPP accesses
Access authentication for non-
3GPP
accesses using Authentication,
Authorization and accounting (AAA)
mechanisms
Security support for non-trusted
accesses
Charging Architecture
Charging for LTE/SAE is performed on a per IP bearer basis.

The network elements involved in LTE/SAE charging are:
The PCRF for charging rule instructions
The PDN GWs Policy & Charging Enforcement Function (PCEF)
with its collection and credit control client functions,
The Serving GW with its collection functions for inter-operator
charging.
The Charging Gateway Function (CGF), collecting CDR for offline
charging.
The Online Charging Function (OCS), containing credit information
for online charging.
The Billing System (BS)
Charging Architecture Different Scenarios
Non-Roaming
Roaming, home routed traffic
Roaming with local breakout
3GPP Non-Roaming PCC Architecture for EPS
65
1 - Charging when Non-Roaming
Offline Charging the PDN GW generates a CDR based on the charging

rules received from the PCRF.
The PDN GW forwards the so called enhanced G-CDR via Gz interface
with protocol GTP' to the Charging Gateway Function (CGF)
CGF collects CDRs from all local network entities involved in billing the
call and forwards them to the Billing System (BS).
Online Charging the PDN GW forwards usage information and receives

credit information to/from the Online Charging System (OCS) in real time
via Gy interface with DIAMETER based credit control application protocol
(DCCA).
At session start the OCS authorizes the user session.
During the session granted and used volume, time or unit quotas are
exchanged. The used quotas are the basis of cost calculation in OCS.
If the user runs out of credits the OCS can terminate the user session
immediately.
SAE/LTE Charging Architecture Non Roaming
2 - Charging when Roaming, Home Routed Traffic
The Offline Charging Function in Serving GW is necessary for the roaming case
with home routed traffic.
In this case the PDN GW is located in home network
The Serving GW generates a CDR with access and bearer information.
The Serving GW forwards the so-called S-CDR via Ga interface with protocol
GTP' to the CGF and further to the BS of the visited operator.
The subscriber's bill is always calculated in the home located BS.
In roaming cases the visited operator generates a TAP3 Record based on S-CDR
or if available an eG-CDR for request of the roaming charge to the home
operator.
Online Charging the OCS is always home located.

In the non-roaming and roaming with home routed traffic scenarios the PDN GW,
and consequently the credit control client are home located.
The PCRF sends a set of charging rules to the PCEF located in the PDN GW via
S7 interface with DIAMETER based policy and charging rule application protocol,
whenever a new bearer is established.
In those cases the PCRF is home located (no inter-operator S7 interface) and
consequently the policy and charging rules are defined by the home operator.
SAE/LTE Charging Architecture Roaming with Home
Routed Traffic
3 - Charging when Roaming with Local Breakout
In this case the PCRF is located in the VPLMN and the policy and charging rules
have to be based on the roaming agreements between the operators.
The NSN standard proposal is to use one single charge, represented by a
standardized rating group, which in essence provides flat rate local breakout.
Dynamic transfer of charging rules from HPLMN to VPLMN would not be needed.
If such transfer were required, this would use the S9 interface (between the
HPCRF and the VPCRF).
The charging rules may be preconfigured in visited PDN GW, according to
roaming agreements. Consequently there would be no requirements for VPLMN
to interpret HPLMN specific IP flow & rating information.
Offline Charging
The subscriber's bill is always calculated in the home located BS.
In roaming cases the visited operator generates a TAP3 Record based on S-CDR
or if available an eG-CDR for request of the roaming charge to the home operator.
Online Charging
The OCS is always home located.
In the roaming with local breakout scenario the PDN GW is located in the visited
network and consequently an inter-operator Gy interface to OCS is necessary.
SAE/LTE Charging Architecture Roaming with Local
Breakout
Evolved Node B (eNB)
eNB Functions
Inter-cell RRM: HO, load balancing between cells Only network element defined as
part of e-UTRAN
Radio Bearer Control: setup , modifications and
release of Radio Resources
Replaces the old Node B / RNC
combination from 3G.
Connection Mgt. Control: UE State Management, Provides all radio management
MME-UE Connection
functions
Radio Admission Control To enable efficient inter-cell radio
eNode B Meas. collection and evaluation management for cells not attached to
the same eNB, there is a inter-eNB
Dynamic Resource Allocation (Scheduler) interface X2 specified. It will allow to
IP Header Compression/ de-compression
coordinate inter-eNB handovers
without direct involvement of EPC
Access Layer Security: ciphering and integrity
protection on the radio interface
during this process.
MME Selection at Attach of the UE

User Data Routing to the S-GW/ P-GW
Transmission of Paging Msg coming from MME
Transmission of Broadcast Info (e.g. System info,

MBMS)
Mobility Management Entity (MME)
MME Functions
Control plane NE in EPC

It is a pure signaling entity inside the
Non-Access-Stratum (NAS)
EPC. Security (Authentication,
integrity Protection)
SAE uses tracking areas to track the Idle State Mobility Handling
position of idle UEs. The basic principle
Tracking Area updates
is identical to location or routing areas
from 2G/3G. Subscriber attach/detach
MME handles attaches and detaches to Signalling coordination for

EPS Bearer Setup/Release
the SAE system, as well as tracking area
Radio Security Control
updates
Trigger and distribution of
Therefore it possesses an interface Paging Messages to eNB
towards the HSS (home subscriber Roaming Control (S6a interface

server) which stores the subscription to HSS)
relevant information and the currently Inter-CN Node Signaling

(S10 interface), allows efficient
assigned MME in its permanent data inter-MME tracking area updates
and attaches
base.
A second functionality of the MME is the
Serving Gateway
The serving gateway is a network Serving Gateway Functions
element that manages the user data Local mobility anchor point:
Switching the user plane path to a
path (EPS bearers) within EPC. new eNB in case of Handover
It therefore connects via the S1-U Mobility anchoring for inter-3GPP
interface towards eNB and receives mobility. This is sometimes referred

to as the 3GPP Anchor function
uplink packet data from here and Idle Mode Packet Buffering and
transmits downlink packet data on it. notification to MME
Thus the serving gateway is some kind Packet Routing/Forwarding

between eNB, PDN GW and SGSN
of distribution and packet data
Lawful Interception support
anchoring function within EPC.
It relays the packet data within EPC via
the S5/S8 interface to or from the PDN
gateway.
A serving gateway is controlled by one
or more MMEs via S11 interface.
Packet Data Network (PDN) Gateway
PDN Gateway Functions

Mobility anchor for mobility between
3GPP access systems and non-3GPP
The PDN gateway provides the access systems. This is sometimes
referred to as the SAE Anchor function
connection between EPC and a Policy Enforcement (PCEF)
number of external data networks. Per User based Packet Filtering (i.e.
Thus it is comparable to GGSN in deep packet inspection)
2G/3G networks. Charging & Lawful Interception support
A major functionality provided by a IP Address Allocation for UE
PDN gateway is the QoS coordination Packet Routing/Forwarding between

between the external PDN and EPC. Serving GW and external Data Network
Therefore the PDN gateway can be Packet screening (firewall functionality)
connected via S7 to a PCRF (Policy

and Charging Rule Function).
Policy and Charging Rule Function (PCRF)
The PCRF major functionality is the Quality of PCRF: Policy & Charging
Service (QoS) coordination between the external Rule Function
PDN and EPC.
Therefore the PCRF is connected via Rx+
interface to the external Data network (PDN)
QoS policy negotiation with PDN
This function can be used to check and modify the
QoS associated with a EPS bearer and/or to
request the setup of a EPS bearer from the PDN.
This QoS management resembles the policy and
charging control framework introduced for IMS with Charging Policy: determines how
packets should be accounted
UMTS release 6.
Home Subscriber Server (HSS)
The HSS is already introduced by UMTS

release 5. HSS Functions
With LTE/SAE the HSS stores additionally
Permanent and central subscriber
data per subscriber for LTE/SAE mobility and database
service handling.
Some changes in the database as well as in Stores mobility and service data for
every subscriber
the HSS protocol (DIAMETER) will be
necessary to enable HSS for LTE/SAE. Contains the Authentication Center
(AuC) functionality.
The HSS can be accessed by the MME via
S6a interface.
EPS Bearer Hierarchy
UE e-NB
S-GW P-GW
Application
Peer
End-to-end Service
EPS Bearer
E-RAB S5/S8 Bearer
Radio Bearer S1 Bearer
LTE-Uu S1 S5/S8 SGi
E-UTRAN EPC
LTE standardized QCI characteristics

IP-CAN Bearers
NB SGSN GGSN
PS-RAB GTP-Tunnel
IP-CAN Bearer (PDP Context)
S-GW P-GW
e-NB
LTE-Bearer GTPTunnel
IP-CAN Bearer (EPS Bearer)
Interconnect / Roaming
S-GW P-GW support required
SGSN
NB
PS-RAB GTP-Tunnel GTPTunnel
(EPS Bearer)
IP-CAN Bearer

Radio Bearer (RB)
Radio Bearer
L2 service provided for transfer of info on the Air Interface

Describes L2 processes per bit-stream (flow)
Different QoS requirements supported by different RBs
Example
Flow A requires low latency but can tolerate packet loss of 10-2
Flow B has less stringent latency requirements, but can only tolerate a packet loss of
10-6
Flow A and B must be supported by 2 separate Radio Bearers

LTE Radio Bearer categories
Signalling Radio Bearers (SRB)
SRB0 is for RRC messages
Using the CCCH logical channel
SRB1 is for RRC / NAS messages

Used prior to the establishment of SRB2
Using DCCH logical channel
NAS messages may be piggybacked inside RRC messages
All messages are Integrity Protected and Ciphered after security activation
SRB2 is for NAS messages

Using DCCH logical channel
May be contained in RRC messages, but with no RRC control content
All messages are Integrity Protected and Ciphered after security activation
Lower priority then SRB1
Data Radio Bearers (DRB)

Carry User Plane content on the Air Interface

Radio Bearers
SRB1(RRC / NAS messages
SRB0(RRC messages on on DCCH)
CCCH)Used for RRC
connection setup DRB1(User content with QoS A
on DTCH1)
Multiple SRBs/DRBs to support

SRB2 (NAS messages on DCCH) on-going user connection
DRB2(User content with QoS B on

DTCH2)
LTE Identifiers
NAS Identities
LTE Identifiers
NAS Identities
LTE Identifiers
NAS Identifies
LTE Identifiers
LTE Identifiers
LTE Identifiers
LTE Identifiers
NAS EMM and ESM Procedures
Page91
EPS Mobility Management Procedures (1/2)
GUTI reallocation;
authentication;
EMM common procedures security mode
control;
identification;
EMM information.
attach and combined

attach
detach or combined
detach
EMM specific procedures normal tracking area
updating and
combined tracking
area updating
periodic tracking
area updating
.
EPS Mobility Management Procedures (2/2)
service request
EMM connection paging procedure
management procedures transport of NAS
messages
UE states and states transitions
EMM REGISTERED ESM ACTIVE
UE context AND default bearers exist: PDN Connection(s) exists:
IMSI, GUTI, TA list, IP address
IP-address, APN, QoS Parameters
(One default bearer and
ECM CONNECTED
zero one or more Dedicated bearers)
NAS Signaling Connection
S5 IP-address & TEID
(Handover)
S11 IP-address & TEID
NAS Connection NAS Connection S1-U IP-address & TEID
Establishment Release
(Data transfer Possible
when ECM Connected)
ECM IDLE
No NAS Signaling Connection
(Tracking Area Update)
E Bearer Last EPS Bearer

Atach Detach
Establishment Released
EMM DEREGISTERED ESM INACTIVE

No UE context No PDN connection
EPS AKA between UE and MME
TERMINAL RAND, AUTN MME receives EPS AV
(AUTN, RAND, XRES,
AUTN K[ASME]) from HSS
RAND
MME checks that

RES = XRES
CK IK RES
SN-ID
KDF
MME uses K[ASME] to
K[ASME] RES calculate
additional keys
UE uses K[ASME] to
calculate additional keys
EPS AKA
UE (with IMSI) HSS
eNodeB MME
USIM (with K) AuC (with IMSI, K)
GUTI/IMSI
GUTI/IMSI, SN id
Generate Authentication
Vectors
XRES, AUTN,
RAND, K[ASME]
RAND, AUTN
AUTN Verification
SRES Generation
SRES
SRES = XRES?
GUTI = Globally Unique Temporary Identity

96
Adatpted from 3GPP TS 33.102
EAP- AKA/ EAP AKA (non-3GPP)
Access GW, WLAN AP
(Trusted 3GPP Access)
ePDG
Terminal 3GPP AAA Server HSS
(Untrusted non-3GPP Access)
(EAP Peer) (EAP Server)
Initiate
connection
EAP Request/
Identity
EAP Response/
3GPP AAA Server
Identify
(UE Identity) EAP Response/ contacts HSS for
Identify Authentication
(UE Identity) Vectors
EAP Request/ AKA-

EAP Request/ AKA- Challenge
Challenge
(RAND, AUTH, MAC)
(RAND, AUTH, MAC)
Peer runs AKA and verifies the
AUTN and MAC, and derives the
RES and the session key.
EAP Request/ AKA-

Challenge EAP Request/ AKA-
(RES, MAC) Challenge
(RES, MAC)
Server checks the RES
and
EAP Success MAC and finds them
correct.
Authenticator extracts session (The Diameter message also
key contains the session key) 97
EAP Success
and forwards the EAP-Success
Authentication and tunnel setup using IKEv2 and
EAP-AKA
Untrusted non-
3GPP
access network PLMN
IKEv2 ePDG
UE
3GPP
EAP-AKA AVs HSS
AAA Server
User plane traversing IPSec tunnel between UE
and ePDG
Untrusted non-
3GPP
access network PLMN
UE
IP-SEC PDN GW
ePDG
AVs Generation Brief Overview (1/2)
The authentication vectors (AVs)are necessary to perform AKA
They are requested by the MEE
Generated by the HSS/AuC
LTE Authentication Vector = (XRES || AUTN || RAND || K[ASME])
AK = Anonymity key
AUTN = (SQN XOR AK || AMF || MAC)
MAC = Message authenticate code in this instance
AMF = Authentication Management Field
CK = Cipher key
IK = Integrity key
KDF = Key derivation function
MAC = A message authentication function
SQN = Sequence Number
XRES = Expected response
SRES = Signed response
100
AVs Generation Brief Overview (2/2)
> K The master key. Permanent pre-shared key stored in hardware.

Located on USIM and HSS/AuC
> CK and IK Cipher key and Integrity key
> K[ASME] Local master. The serving network ID (SNid) is used to
derive this key in addition to CK and IK.
> K[eNB] Used to derive additional keys used in handoff
> K[NASent] & K[NASint]- Protection of NAS traffic
> K[RRCent] & K[RRCint] - Protection of RRC traffic
101
AVs Generation
SQN Generate SQN

AMF RAND Generate RAND
f1 f2 f3 f4 f5
MAC XRES CK IK AK
SQN XOR AK KDF SN id
Note: SQN and RAND generation is not

standardized.
K
ASME
102
datpted from 3GPP TS 33.401
USIM Verification
RAND AUTN = (SQN XOR AK || AMF || MAC)

f5
AK
SQN
f1 f2 f3 f4
XMAC RES CK IK
XMAC = MAC?
103
datpted from 3GPP TS 33.401
Cryptography in LTE
Large change to cryptographic key structure

Introduced a new set of intermediate keys
Unique keys for each connection/bearer - large complicated
hierarchy
Similar to UMTS, we have 2 sets of algorithms for confidentiality and
integrity
EEA1/EIA1 - based on SNOW 3G
EEA2/EIA2 - based on AES (USA)
EEA3/EIA3 - based on ZUC (China)
CP and UP may use different algorithms
104
Key Hierarchy in LTE
105
Adatpted from 3GPP TS 33.401
LTE Non-Access Stratum
Security-related signaling between UE and the backhaul

Algorithm selection occurs between the UE and the MME
MME contains a list of confidentiality and integrity algorithms in a priority
order
NAS negotiation precedes AKA
Negotiation begins when an MME sends an integrity protected Security Mode
Command to UE
Contains evolved key set identifier (eKSI), list of security capabilities and
algorithms, IMSI request, and additional cryptographic information
The UE responds with an integrity protected encrypted message called the
NAS Security Mode Complete containing its IMEI and a MAC of the message
106
LTE Access Stratum
Signaling between UE and eNB

Algorithm selection occurs between these components
eNB contains a list of confidentiality and integrity algorithms in a
priority order
AS and RRC communication occur on the Packet Data
Convergence Protocol (PDCP)
AS protection is optional
107
Security
> Security functions include:

Guards against unauthorised EPS service usage (authentication of
the UE by the network and service request validation).
Provision of user identity confidentiality (temporary identification
and ciphering).
Provision of user data and signaling confidentiality (ciphering).
Provision of origin authentication of signaling data (integrity
protection).
Authentication of the network by the UE.
CALL FLOWS
109
Tracking Area Update (TAU)
MME SGW HSS

UE eNodeB
1. TAU Request
2. Security Functions 2. Security Functions
3. TAU Accept
4. TAU Complete
110
Tracking area update (1/2)
UE eNodeB New MME Old MME Old SGSN HSS

OR
RRC: Connection Setup

Complete NAS: TAU
Request Old-GUTI
S1AP: Uplink NAS

Transport TAI; ECGI
NAS: TAU
Request Old-
GUTI Dia: Update Location
Request
MMEId, IMSI
Dia: Cancel Location Request

IMSI; Cancellation
Type: MME_UPDATE_PROCEDURE
Dia: Cancel Location

Answer
Tracking area update (2/2)
UE eNodeB New MME Old MME Old SGSN HSS
OR
Dia/SS7: Cancel Location

Request
IMSI;
Cancellation Type:
SGSN_UPDATE_PROCEDU
RE
Dia/SS7: Cancel Location

Answer
S1AP: Downlink NAS Transport Dia: Update Location

NAS: TAU Accept Answer Subscription Data
New-GUTI; TA- UE
List; T3412
RRC: Downlink Information Transfer
NAS: TAU Accept
New-GUTI;
TA-List; T3412
RRC: Uplink Information

Transfer NAS: TAU Complete
S1AP: Uplink NAS Transport
NAS: TAU Complete
Periodic tracking area update (1/2)
UE eNodeB MME SGW PGW HSS
T3412
Expiry
RRC: Connection Setup

Complete NAS: TAU
Request
Old-GUTI S1AP: Initial UE
Message TAI; ECGI
NAS:
TAU Request
Old-GUTI
Optional: Authentication and NAS Security Activation
S1AP: Downlink NAS Transport

NAS: TAU Accept
New-
GUTI; TA-List; T3412
RRC: Downlink Information
Transfer NAS: TAU Accept
New-GUTI; TA-List; T3412

Periodic tracking area update (2/2)
UE eNodeB MME SGW PGW HSS
RRC: Uplink Information

Transfer NAS: TAU Complete

NAS: TAU Complete
S1AP: UE Context Release

Command
S1AP: UE Context Release

Complete
RRC: Connection
Release
INITIAL ATTACH 1/3
UE eNodeB MME HSS DNS SGW PGW PCRF
NAS: Attach Request:

IMSI; TAI; PDN type
S1AP: Initial UE Message

NAS: Attach Request:
IMSI; TAI; PDN type
Authentication and Dia: Authentication-Information-Request

NAS Security Activation IMSI; Visited-
PLMN-Id

NAS: Authentication Request NAS: Authentication Request Dia: Authentication-Information-Request Answer
RAND, AUTN Authentication Information (EPS-Vectors)
RAND, AUTN
NAS: Authentication Response

RES
NAS: Authentication Request
RES

NAS: Security Mode Command
NAS: Security Mode Command
NAS: Security Mode Complete

NAS: Security Mode Complete
INITIAL ATTACH 2/3
Dia: Update Location

MME Id; IMSI
Dia: Update Location Answer

APN; QoS; Charging Characteristics
DNS Query for GW Selection
GTPCv2: Create Session Request

MME F-TEID (S11); PGW IP-addr (S5-C); PDN
type; IMSI; bearer QoS; EBI
GTPCv2: Create Session Request
SGW F-TEID (S5-
C); SGW F-TEID (S5-U); PDN type;
IMSI; bearer QoS; EBI Dia: Control Credit Request
Initial_Request; Called-
Station-Id (APN); Subscription-ID
(IMSI); Default-EPS-Bearer-QoS
(QCI&ARP) ; QoS Information (APN-
AMBR)
Dia: Control Credit Answer

Initial_Request; Default-
GTPCv2: Create Session EPS-Bearer-QoS (QCI&ARP) ;
Response Cause QoS Information (APN-AMBR);
(req acc); PGW F-TEID Event-Trigger
(S5-C); PGW F-TEID (S5-
U); UE IP-add; bearer
GTPCv2: Create Session Response QoS; EBI
Cause (req acc); SGW F-TEID (S11); SGW F-TEID (S1-U); UE IP-
add; bearer QoS; PDN F-TEID (S5-C); PGW F-TEID (S5-U); EBI
INITIAL ATTACH 3/3
S1AP: Initial Context Setup Req.

Bearer QoS; E-
RABToBeSetup: QCI; SGW S1-U
IP+TEID;
NAS: Attach Accept
New GUTI; TA
List, T3412 APN; Bearer QoS; UE-
IP-address;
NAS: Attach Accept
New GUTI; TA List, T3412 APN; Bearer
QoS; UE-IP-address;
S1AP: Initial Context Setup Response

eNodeB S1-
U F-TEID
NAS: Attach Complete

NAS: Attach
Complete
GTPCv2: Modify Bearer Request
eNodeB F-TEID (S1-U); EBI
GTPCv2: Modify Bearer Response

Cause; EBI;
X2-based handover 1/3
No MME relocation, no S-GW relocation MME
Source eNodeB
2. S1 Path Switch
GT Request
ld P-U
U uo old
LTE
3. Update User
Plane
1. X2 Handover
and Data
Forwarding
GTP-U
SG
W PG
W
LT w
EU ne
un
ew P -U
GT
Target eNodeB
No MME relocation, no S-GW relocation
UE T -eNodeB S -eNodeB MME SGW
PDN Connection established (Steady state)
RRC Measurement Control
RRC Measurement Report
X2AP Handover Request
X2AP Handover Request Acknowledge
RRC Connection Reconfig Req Begin forwarding downlink

data from source to
destination eNodeB
X2AP SN Transfer Status
Non Contention RACH procedure

UE T -eNodeB S -eNodeB MME SGW
RRC Connection
Reconfig Comp
S1AP Path Switch Request
Modify Bearer Request
Modify Bearer Response
S1AP Path Switch Acknowledge
Uplink/Downlink Data Transfer
X2AP UE Context Release
Tracking Area Update Request
Tracking Area Update Response

S1-based handover 1/3
MME
Source eNodeB
1. S1 Handover
Preparation
GT
Old P-
U
E Uu Ol
LT d
3. Modify Bearer
2. S1 Handover
Resource
GTP-U
Allocation
SGW PGW
LT w
EU
uN Ne
U
ew TP-
G
Target eNodeB
UE S -eNodeB T -eNodeB MME SGW

S1AP Handover Reqd
S1AP Handover Req
S1AP Handover Req Ack
S1AP Handover Command

RRC Connection
Reconfig Req
S1AP eNodeB Transfer Status
GTP Forward User Data

UE S -eNodeB T -eNodeB MME SGW
S1AP MME Transfer Status
Non-contention based RACH procedure
RRC Connection Reconfig Comp
S1AP Handover Notify
GTP Modify Bearer Request
GTP Modify Bearer Response
S1AP UE Context Release Command
S1AP UE Context Release Complete

MME relocation, no S-GW relocation
UE S -eNodeB T -eNodeB S -MME T- MME SGW
S1AP Handover Reqd GTP Fwd Reloc Req
S1AP Handover Req
GTP Fwd Reloc Resp
S1AP Handover Command

RRC Connection
Reconfig Req
S1AP eNodeB Transfer Status
S1AP MME Transfer Status


GTP Modify Bearer Req
GTP Modify Bearer Rsp

GTP Fwd Reloc Comp
GTP Fwd Reloc Comp Ack


MME relocation, S-GW relocation
UE S -eNodeB T- eNodeB S - MME T - MME S-SGW T-SGW
RRC Meas Proc

S1AP Handover Reqd
GTP Fwd Reloc Req

GTP Create Session Request
GTP Create Session Response
S1AP Handover Req
Create Indirect Data Forwarding Tunnel Req
Create Indirect Data Forwarding Tunnel Resp
GTP Fwd Reloc Resp

Create Indirect Data Forwarding Tunnel Req
Create Indirect Data Forwarding Tunnel Resp
S1AP Handover Cmd
RRC Connection Reconfig
S1AP eNodeB status transfer
S1AP MME status transfer
GTP FW data Dir FW data
GTP FW data GTP FW data
GTP FW data
Ind FW data
GTP Modify Bearer Rsp
GTP Fwd Reloc Comp

GTP Delete Session Req
GTP Delete Session Rsp

Inter-RAT LTE -to- UMTS Handover 1/2
Preparation Phase
UE S -eNodeB T- RNC S - MME T - SGSN S-SGW T-SGW
RRC Meas Proc

S1AP Handover Reqd
GTP Fwd Reloc Req

RANAP Relocation Request
RANAP Relocation Request Ack
GTP Create Ind Data Fwd Tunn Req

Preparation Phase
UE S -eNodeB T- RNC S - MME T - SGSN S-SGW T-SGW
GTP Create Ind Data Fwd Tunn Resp
GTP Fwd Reloc Resp

Execution Phase
UE S -eNodeB T- RNC S - MME T - SGSN S-SGW T-SGW PGW
S1AP Handover Cmd
Mobility from EUTRA Cmd
UMTS Access Proc
HO to UTRAN Comp
GTP FW Down Link Data

Ind FW data
GTP FW Data
GTP FW data
Dir FW data
Execution Phase
UE S -eNodeB T- RNC S - MME T - SGSN S-SGW T-SGW PGW
RANAP Reloc Comp
GTP FW Reloc Comp
GTP FW Reloc Comp Ack
GTP Modify Bearer Resp
User Data Packets Uplink/ Downlink

Execution Phase
UE S -eNodeB T- RNC S - MME T - SGSN S-SGW T-SGW T-SGW PGW
GTP Delete Session Resp
S1AP UE Ctxt Rel Cmd
S1AP UE Ctxt Rel Comp

Inter-RAT UMTS -to- LTE Handover 1/2
Preparation Phase
UE S -RNC T- eNodeB S - SGSN T - MME S-SGW T-SGW PGW
RRC Meas Proc
RANAP Relocation Reqd
GTP Fwd Reloc Req
S1AP Handover Req

Preparation Phase
GTP Fwd Reloc Resp

Execution Phase
RANAP Relocation Cmd
RRC Hanover from UTRAN Cmd
Non-contention RACH Proc
GTP FW Down Link Data
Ind FW data
GTP FW Data
GTP FW Data Dir FW data

Execution Phase
GTP Fwd Reloc Comp
GTP Modify Bearer Resp
RANAP Iu Rel Cmd

Execution Phase
RANAP Iu Rel Comp
GTP Delete Session Resp

CSFB to UTRAN or GERAN using RRC connection release with
redirection, mobile terminated call (1/2)
UE eNodeB BSS/RNS MME MSC SGW HLR/HSS PGW SGSN
EPS/IMSI Attach Procedure
CS Service Notification
SGS Paging Request
Extended Service Request (with CSFB Response) SGS Service Request
UE Context Modification Request (CSFB Indicator)
UE Context Modification Response
Optional Measurement
Reports
RRC Connection Release with Redirection to

GERAN/UTRAN
UE Context Release Request
S1 Release Procedure
CSFB to UTRAN or GERAN using RRC connection release with redirection,
mobile
terminated call (2/2)
UE eNodeB BSS/RNS MME MSC SGW PGW SGSN
UE Changes to GERAN/UTRAN
If needed: Location Area Update or Combined Location Area Update/ Routing Area Updatec
If needed (CSFB to GERAN without support of Dual Transfer Mode): Suspension or Deactivation of Packet Switched
Services
Paging Response Paging Response
Establish CS Call
Mobile Originating SMS
SMS
UE MME MSC HLR/HSS SC
IWSMSC
EPS/IMSI Attach Procedure
UE Triggered Service Req
Uplink NAS Transport
Uplink Unidata
Forward Short Message
Message Transfer
Delivery Report
Delivery Report
Downlink Unidata
Downlink NAS Transport

Mobile Terminating SMS (1/2)
SMS
UE eNodeB MME MSC HLR/HSS SC
GMSC
EPS/IMSI Attach Procedure Message Transfer
SRI-SM
Forward Short Message
Paging
Paging
Paging
NAS Service Req

Service Req
Downlink Unidata
Downlink NAS Transport
Mobile Terminating SMS (2/2)
SMS
UE eNodeB MME MSC HLR/HSS SC
GMSC
Uplink NAS Transport
Uplink Unidata
Delivery Report
Delivery Report
Call Flow for SRVCC from E-UTRAN to GERAN/UTRAN (1/3)
Target Target Target IMS

UE eNodeB MME SGW/PGW MSC MSC SGSN BSS SCC AS
Measurement control and Reports
Handover Req
Bearer Splitting
PS to CS Req
Prep HO Req
HO Req
HO Ack
Prep HO Resp
Establish Circuit

Initiation of Session Transfer
Session Transfer,
PS to CS Resp
Update Remote
End , Release IMS
access leg
HO Command
HO from E-UTRAN
Command
UE Tuning and Handover Detection with the Target Network
Suspend
Suspend Req/ Ack Suspend


Updatce Bearer Req
Update Bearer Resp
Handover Complete
Handover Complete
PS to CS Complete
PS to CS Complete Ack
Dedicated Bearer Activation Procedure
Network Initiated (1/3)
UE eNodeB MME SGW PGW PCRF
For GTP based S5/S8
PCRF Initiated IP-CAN

Session, Begin
Create Dedicated Bearer
Request
For PMIP based S5/S8)
Gateway Control and QoS policy Rules

Provision Procedure, Begin

Request
E-RAB Setup Request/

NAS Activate Dedicated
Bearer Context Request
RRC Connection
Reconfig
RRC Connection
Reconfig Comp
E-RAB Setup Response
NAS Direct Transfer

NAS Activate Dedicated
Bearer Context
Response

Response
For GTP based S5/S8

Response
Session, End

Provision Procedure, End
User Initiated (1/1)
Request Bearer Resource

Modification

Modification
For GTP based S5/S8

Modification
Session, Begin

Provision Procedure, Begin
Dedicated Bearer Activation, Deactivation or Modification Procedure

Thank you!

EPC Presentation Final

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

EPC Presentation Final

Caricato da

Copyright:

Formati disponibili

EPC Session

Architecture , Interface and Protocols

LTE Bearers and QoS

2 | Videocon Mobile Services | 2010

Tablet and Smartphone

Laptop and Cellphone

Anything that can be connected

Full Mobility 350km/h Seamless Coverage

High Data Rate

6 | Videocon Mobile Services | 2010

7 | Videocon Mobile Services | 2010 Page7

8 | Videocon Mobile Services | 2010

3GPP R5 3GPP R6 3GPP R71 3GPP R8

With 2x2 MIMO and 64QAM likely for R8

9 | Videocon Mobile Services | 2010

10 | Videocon Mobile Services | 2010

13 | Videocon Mobile Services | 2010

Peak data rate

16 | Videocon Mobile Services | 2010

17 | Videocon Mobile Services | 2010

18 | Videocon Mobile Services | 2010

Time Division Frequency Division Code Division Frequency Division

User 1 User 2 User 3 User ..

20 | Videocon Mobile Services | 2010

Transmits hundreds or even thousands of separately modulated radio signals

Total transmission bandwidth

The peak ( centre

21 | Videocon Mobile Services | 2010

Orthogonality between subcarriers

The orthogonality between subcarriers is due to the specific frequency

Subcarriers in the same radio path are orthogonal to each other

23 | Videocon Mobile Services | 2010

Symbols are distorted in the time domain

24 | Videocon Mobile Services | 2010

total symbol time T(s)

25 | Videocon Mobile Services | 2010

f: f = 1/Tu. Though large Tu is preferred, it also means small subcarrier spacing in

Due to large number of subcarriers, the

The higher the peaks, the greater the

Having a UE with such a PA that works

Not best suited for use with mobile

27 | Videocon Mobile Services | 2010

Total channel bandwidth

28 | Videocon Mobile Services | 2010

Total channel bandwidth

29 | Videocon Mobile Services | 2010

0 Total channel bandwidth

Figure valid for time interval mTu t (m 1)Tu

30 | Videocon Mobile Services | 2010

Total channel bandwidth

31 | Videocon Mobile Services | 2010

1 PRB = 2 Slots = 2 * 0.5 ms

1 PRB (Physical Resource Block) = 12 Subcarriers = 180 kHz

1 PRB = 2 Slots = 2 * 0.5 ms

1 PRB (Physical Resource Block) = 12 Subcarriers = 180 kHz

Frequency 60 kHz Frequency

35 | Videocon Mobile Services | 2010

36 | Videocon Mobile Services | 2010 Page36

37 | Videocon Mobile Services | 2010 Page37

Physical Resource Block or Resource Block ( PRB or RB):

Subcarrier 1 0 1 2 3 4 5 6 0 1 2 3 4 5 6 Capacity allocation is based

38 | Videocon Mobile Services | 2010

# Total Subcarriers 100 x 12 = 1200

# OFDM symbols/ Time Slot 7