Introduction to LTE/EPC (EPS) Network with Comparison with GPRS Core Network

Mustafa Golam

2/4/2014 Mustafa Golam, CTO, BDTele(BigData In Telecom) 1


Air Interface capacity Modulation scheme (FM, QPSK, 16QAM, 64QAM)

Multiple Access Technology

Air Interface Bandwidth (Frequency in kHz, MHz,)

Node Capacity Number of simultaneously users

Power support

Transport Network/Transmission TDM/ATM/ETHERNET

Throughput


1G FDMA (NMT, ect) Analog, CS only

2G TDMA (GSM, ect) Voice, SMS, CS data transfer

2.5G TDMA (GPRS) CS,PS data~ 50kbps

2.75G TDMA (EGPRS+EDGE) CS, PS data ~150-384 kbps

3-3.5G WCDMA (UMTS) CS, PS ~14.4-42 Mbps

3.9G OFDMA (LTA/SAE=>EPS) PS ~ 100 Mbps

4G IMT Advanced PS ~350 Mbps


Standard Year Multiple

Access

Modulation Bandwidth

NMT-450 1981 FDMA FM 25 kHz

NMT-900 1986 FDMA FM 12.5 kHz

ETACS 1985 FDMA FM 25 kHz

AMPS 1983 FDMA FM 30 kHz

JTACS 1988 FDMA FM 25 kHz

NTT 1979 FDMA FM 12.5 kHz

Standard Year Multiple

Access

Modulation Bandwidth

PCS (CDMAOne) 1993 CDMA QPSK/

BPSK

1.25 MHz

GSM 1990 TDMA GMSK 200 kHz



Need an “all IP” system with more efficiency, more capacity and higher speeds 2/4/2014 Mustafa Golam, CTO, BDTele(BigData In Telecom) 9


Source: OVUM, Strategy Analytics & Internal Ericsson

0

300

600

900

1200

1500

1800

2100

2005 2006 2007 2008 2009 2010 2012

Su

bsc

rip

tio

ns

(Mil

lio

ns)

Mobile Broadband

Fixed Broadband

2011

Mobile broadband growth: Broadband becomes personal 2/4/2014 Mustafa Golam, CTO, BDTele(BigData In Telecom) 11





LTE is the Global standard for Next Generation – FDD and TDD 2/4/2014 Mustafa Golam, CTO, BDTele(BigData In Telecom) 16

Freely downloadable from:

http://ftp.3gpp.org/specs/html-info/36-series.htm







0

5

10

15

20

25

30

35

40

45

50

HSPA R6 2004

HSPA R7 2007

HSPA R8 2008

LTE 2x2, 5+5 MHz

2008

Pea

k D

ata

Rat

es [

Mb

ps]

Downlink

Uplink

HSPA Evolution provides similar performance as LTE in 5MHz 2/4/2014 Mustafa Golam, CTO, BDTele(BigData In Telecom) 18

LTE 4x4, 20+20 MHz

2008

0

50

100

150

200

250

300

350

Pea

k D

ata

Rat

es [

Mb

ps]

Downlink

Uplink

LTE 2x2, 5+5 MHz

2008

LTE 2x2, 20+20 MHz

2008

> 5 MHz trunking gain gives improved LTE performance 2/4/2014 Mustafa Golam, CTO, BDTele(BigData In Telecom) 19

Base station located at x. L1 Throughput Max: 154 Mbps Mean: 78 Mbps Min: 16 Mbps UE Speed Max: 45 km/h Mean: 16 km/h Min: 0 km/h Sub-urban area with Line-of-sight: less than 40% of the samples Heights of surrounding buildings: 15-25 m


http://www.ericsson.com/ericsson/corpinfo/publications/review/2008_03/files/LTE.pdf

http://www.ericsson.com/ericsson/corpinfo/publications/review/2008_03/files/LTE.pdf

Cdma2000 EvDO Rev A 3.1Mbps DL, 1.8Mbps UL EvDO Rev B 4.9Mbps (64QAM)

Multicarrier 14.7Mbps in 5MHz with MIMO 29Mbps!

HSPA 14Mbps DL and 5.8Mbps UL Evolved HSPA

With MIMO 28Mbps DL With 64QAM 21Mbps DL Combined 42Mbps DL, 11Mbps UL (16QAM)

DL UL

LTE 1.4 9.2Mbps 2.2Mbps

LTE 3 25Mbps 7.1Mbps

LTE 5 42.2Mbps 12.2Mbps

LTE 10 85.4Mbps 27.3Mbps

LTE will provide high data rate user experience

Release99 (DCH Channels) 384 kbps Introduce HSDSCH (HSDPA channel)

Access technology CDMA Air interface bandwidth 5Mhz Modulation Schemes

QPSK/16QAM/64QAM First higher data rates

2005 (P4) QPSK, 5 codes, HSDSCH => 2Mbps 16QAM, 5 codes HSDSCH => 3.6Mbps Follow the race

P5 =>7.2 Mbps and 14.4 Mbps 10 codes or 15 codes with 16QAM

P7 => 21 Mbps using 64 QAM


14

21/28 42

84

Rel-7: 15 codes, 64QAM, MIMO+16QAM

Rel-8: Multi Carrier, 64QAM+MIMO

Rel-9 :Multi Carrier + MIMO

Rel-6: 16QAM, 14 Mbps DL Peak rates in Mbps

168 4 Carrier- Multi Carrier


Second carrier

First carrier

Physical layer (L1) peak rate: 42.2 Mbps

One receiver with 10 MHz bandwidth combines traffic from two carriers

Adjacent 5 MHz carriers

Benefits:

– Up to 42 Mbps peak rate

– Higher bit rates in whole cell

– Higher capacity

42 Mbps



What is Different in LTE?


LTE stands for Long Term Evolution which is introduced by 3GPP to define a new high-speed radio access method for mobile communications systems.

LTE offers a smooth evolutionary path from other cellular systems.

GSM EDGE WCDMA HSPA LTE


GSM LTE

EDGE LTE

WCDMA LTE

LTE Non 3GPP Technologies


High data rates Downlink > 100Mbps Uplink > 50Mbps Cell edge data rates 2-3 X HSPA Rel6 (2006)

Low Delay/latency User Plane RTT < 10ms RAN RTT (fewer nodes, shorter TTI) Channel set up < 100ms from IDLE to Active (fewer nodes, shorter

messages, quicker node response

High spectral efficiency Initially 3X HSPA release6

Spectrum flexibility Operation in wide range of spectrum (New, existing) 1.4, 3, 5, 10, 15 or 20 Mhz (flexibility) FDD or TDD mode form start

All over IP (end to end)


Cost affective and simple (CAPEX/OPEX) Less signaling Auto configuration E-NodeB Self optimization Fewer Nodes (low latency, reduced RTT) Easy migration from GSM/WCDMA Less signaling One domain, IP domain (No separate CS

domain) Flattening architecture (common Packet Core) Possibility of Reuse/share equipment Focus on services from PS domain





Packet Data Gateway (P-GW)

Serving Gateway (S-GW)

Mobility Management Entity (MME)

e-UTRAN (eNodeB)





S-GW and P-GW functions: Implemented on common node

Called SAE-Gateway

Realized with Red-back Smart-Edge 1200 router in Ericsson Solution


Charging, Packet filtering (QoS), PCEF (QoS)

IP PoP

EPS Bearer Handling

Not seen by terminal

Mobility anchoring


Packet filtering (QoS)

Termination of U-plane packets for paging reasons

Switching of U-plane for support of UE mobility


MME functions are added in the Serving GPRS Support Node (SGSN-MME 2009B release).

Handles security Authentication, Authorization and Accounting (AAA)

Idle state mobility handling

EPS Bearer control/management (QoS)

UE attach/detach handling (registration ect)

IRAT handover


All ready existing MBPN solution can be utilized

Zain well positioned for this convergence (Using Juniper routers switches in MPBN)

MPLS nodes in the 2G/3G access (LTE can share)

Different aggregation levels are to expect

L2 equipment or L3 equipment or combination of it can be used



Terminates all user plane functions seen by the terminal (including security)

Radio Resource Management Radio Bearer Control

Radio Admission Control

Connection Mobility Control

UL/DL scheduling

IP header compression and encryption of user data streams

Measurement and measurement reporting


LTE RADIO Interface


Flexible bandwidth <5 MHz bandwidths up to 20 MHz

• Uplink: SC-FDMA with dynamic bandwidth

– Higher power efficiency, reduced interference

• Downlink: Adaptive OFDMA

– Adaptation in time and frequency domain

• Multi-Antennas, both RBS and terminal

– MIMO, beamforming, TX and RX diversity

• Both FDD and TDD supported

• Adaptive complex modulation

– DL = QPSK,16QAM, 64QAM

– UL= QPSK, 16QAM


From 1.4 up to 20 MHz spectrum allocations

Compare WCDMA 5MHz

Support both FDD and TDD modes

Supports use of MIMO multiple antenna configurations

OFDM in DL

SC-FDMA in UL


Frequency

…

The available Bandwidth is divided into 15 KHz Sub-carriers. After data is mapped to these carriers, they are multiplexed and Transmitted to the users.

One sub-carrier gives a low speed, but a number multiplexed together will give a higher speed. Users are assigned sub-carriers in groups of twelve

15kHz




LTE radio access Downlink: OFDMA Uplink: SC-FDMA

Advanced antenna solutions Diversity Multi-layer transmission (MIMO) Beam-forming

Spectrum flexibility Flexible bandwidth New and existing bands Duplex flexibility: FDD and TDD

SC-FDMA

OFDMA

20 MHz 1.4 MHz

TX TX



Downlink: Multi-layered OFDM Channel-dependent scheduling and link adaptation in time and frequency

domain

Uplink: Single Carrier-FDMA Higher uplink system throughput

Improved coverage and cell-edge performance

Lower terminal cost and improved battery life

Downlink Uplink

frequency frequency

User 1 User 2 User 3



12 subcarriers * 15KHz = 180 KHz





Orthogonal: all subcarriers zero at sampling point (an integer number of cycles for one symbol for all subcarriers)

Subcarrier spacing is 15 kHz (7.5 kHz for MBMS)

Implemented in practice using the Discrete Fourier Transform (DFT)

FDM OFDM


Resistance to the damaging effects of multipath delay spread Robust against ISI

Scalable system bandwidth

Adopts easy to frequency and phase distortions in the received signal Reference signals are used for

the correction (coherent detection)

Ability to easily manipulate phase and frequency makes it suitable for MIMO or beamforming

Easy to implement

data1

data2

data3

data4

User #1 scheduled

User #2 scheduled

Time-frequency fading, user #1

Time-frequency fading, user #2


The consequence of multi-path propagation is the time dispersion Time-adjacent symbols start to

overlap and generate inter-symbol-interference (ISI)

Symbol is prolonged by adding a guard time between the symbols Adding an “empty” guard time

destroys the orthogonality and introduces inter-carrier interference (ICI)

To maintain the orthogonality the prefix is made cyclic

Prefix time must be longer than the longest excess delay


Normal CP is 5.21/4.69 μs Provides for a time delay caused by

multi-path of up to 1.4 km Adequate for most coverage scenarios

Extended CP of 16.67 μs Covering an excess delay of up to 5 km Use of extended CP provides 6 symbols

per slot

It is possible on the downlink to combine the extended CP with half inter-carrier distance (7.5 kHz) to increase the robustness against long delays

Multi-path channel measurements on 900 MHz and 1.7 GHz showed that for urban areas the delay spread (DS) in 90 % of the cases were below 0.7 μs

For different rural environments, the DS values could be between 5 and 20 μs in 90 % of the cases These kinds of environments are more

challenging


High PAPR Sensitive to Doppler and

frequency errors



20 MHz, PB3, 2x2 MIMO

Network design that maximizes both coverage and SINR is required

› Highest order modulation is chosen based on radio channel conditions (SINR)

› Different order modulations allow for sending more bits per symbol

› System can flex to the actual fading conditions


Maximum symbol rate = 14 * NRB * 12 Maximum bit rate = Maximum symbol rate * bits/symbol * coding rate * MIMO gain

Maximum channel rate (Mbps) for SISO

› 14 OFDM symbols per 2 slots (1ms sub frame) per subcarrier

› 12 subcarriers per resource block

Channel banwidth (Mhz) 1.4 3 5 10 15 20

Transmission bandwith configuration NRB 6 15 25 50 75 100

QPSK 1/2 1.008 2.52 4.2 8.4 12.6 16.8

QPSK 1 2.016 5.04 8.4 16.8 25.2 33.6

16 QAM 1/2 2.016 5.04 8.4 16.8 25.2 33.6

16 QAM 1 4.032 10.08 16.8 33.6 50.4 67.2

64 QAM 1/2 3.024 7.56 12.6 25.2 37.8 50.4

64 QAM 1 6.048 15.12 25.2 50.4 75.6 100.82/4/2014 Mustafa Golam, CTO, BDTele(BigData In Telecom) 66

Throughput vs. Relative Distance to Cell Border

0

20000

40000

60000

80000

100000

120000

140000

160000

0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100%

Relative Distance to Cell Border

Th

rou

gh

pu

t [k

bp

s]

5 MHz

10 MHz

15 MHz

20 MHz

RLC, HARQ, TCP, Application overheads etc.

Interference and cell loadings are key factors

Good cell plan is very important

“average” user experience region


Single-carrier FDMA

Single-carrier

Improved power amplifier efficiency

Reduced terminal power consumption and cost and improved coverage

FDMA

Intra-cell orthogonality in time and frequency domain

Improved uplink coverage and capacity

High degree of commonality with LTE downlink access

Can be seen as pre-coded OFDMA

Same basic transmission parameters (frame length, subcarrier spacing, …)

OFDMA SC-FDMA

frequency frequency

User 1 User 2 User 3


Single-carrier transmission in uplink enables low PAPR that gives more than

4 dB better link budget and reduced power consumption compared to OFDM

OR

Improved coverage ( > 60% improvement )

Higher data rates ( > 2.5 times improvement )

R Mbps

2.5xR Mbps

Reduced power consumption Longer battery life



Multiplexing “Capacity multiplication”

Example

Transmit several signals in different directions

Diversity “Reduce fading”

Example

Transmit the signal in all directions

Directivity Antenna/Beamforming gain

Example

Transmit the signal in the best direction

Channel knowledge (average/instant)

› Different techniques make different assumptions on channel knowledge at RX and TX

› Many techniques can realize several benefits

› Realized benefit depends on channel and interference properties


› Better data rate coverage

–Directivity and diversity improves link budget

› Potential for higher data rates

–Spatial domain provides extra dimension

–Spatial multiplexing in certain scenarios at high SINR

Higher Spectral efficiency! 2/4/2014 Mustafa Golam, CTO, BDTele(BigData In Telecom) 72

Channel capacity: C log2(1+SNR) Low SNR regime: log2(1+SNR) SNR

Increase SNR => Transmit Diversity

High SNR regime: log2(1+SNR) log2(SNR)

Increasing SNR does not give higher rate => Increase number of transmitted layers (symbol streams) =

MIMO

Capacity (bps)

SNR NSNR


Space-time Code (STC): Redundant data sent over time and space domains (antennas)

Capacity (max data rate):

c b a

Space

Time

Code

c b a

c’ b’ a’

MOD

MOD

Space

Time

Decoder

c b a

Data is not redundant – less diversity but less repetition Transmit rmax parallel symbol streams rmax = min(NR, NT)

Provides multiplexing gain to increase data rate

Capacity: C = BW * rmax * log2(1+(CINR/rmax))

f e d c b a

e c a

f d b

MOD

MOD

Space

Time

Decoder

f e d c b a

NR NT

1

1.1

1.2

1.3

1.4

1.5

1.6

1.7

1.8

1.9

1 3 5 7 9 11 13 15 17 19 21 23 25 27 29 31 33 35 37

MIM

O G

ain

C/(I+N)

MIMO Gain vs. C/(I+N)

LTE provides spectrum flexibility for operation in differently sized spectrum

10 MHz 15 MHz 20 MHz 3 MHz 5 MHz 1.4 MHz

› LTE supports paired and unpaired spectrum on the same HW platform

fDL

fUL

FDD

fDL/UL

TDD

Highest data rates for given bandwidth and peak power

Unpaired spectrum

Maximum commonality between FDD and TDD 2/4/2014 Mustafa Golam, CTO, BDTele(BigData In Telecom) 76

FDD

Band ”Identifier” Frequencies (MHz)

1 IMT Core Band 1920-1980/2110-2170

2 PCS 1900 1850-1910/1930-1990

3 GSM 1800 1710-1785/1805-1880

4 AWS (US &

other)

1710-1755/2110-2155

5 850 824-849/869-894

6 850 (Japan) 830-840/875-885

7 IMT Extension 2500-2570/2620-2690

8 GSM 900 880-915/925-960

9 1700 (Japan) 1750-1785/1845-1880

10 3G Americas 1710-1770/2110-2170

11 UMTS1500 1428-1453/1476-1501

12,

13,

14

US 700 698-716/728-746

776-788/746-758

788-798/758-768

TDD

Band ”Identifier” Frequencies (MHz)

33,34 TDD 2000 1900-1920

2010-2025

35,36 TDD 1900 1850-1910

1930-1990

37 PCS

Center Gap

(1915)1910-1930

38 IMT Extension

Center Gap

2570-2620

39 China TDD 1880-1920

40 China TDD 2300-2400


700MHz Band 13 (Upper C) 10MHz FDD Band 12 ( Lower 700)

C+B 5 & 10 MHz A+B 5 & 10MHz

New players Cdma2000 tier3 players

AWS A or B or F 10MHz C or D or E 5MHz

1900MHz, 850MHz 1.4MHz, 3MHz spectrum constraint 5,10MHz available spectrum

A B C

52

D E A B C

58 595453 5655 57

698

MHz 704 740734728722710

806

MHz

C

Lower 700 MHz

60 61 62 63 64 65 66 67

752 782 788758

68 69

A

716 746 764

D C A DPublic

Safety

770 776 794 800

Public

Safety

Upper 700 MHz

B B

LTE provides solution for many spectrum scenarios 2/4/2014 Mustafa Golam, CTO, BDTele(BigData In Telecom) 78

SC-FDMA Low peak to average power ratio

Cheaper power amplifier in the UE



Mobility management for idle UEs

UE Authentication

EPS bearer management

Configuration and control security

Paging initiation for idle UEs


Broadcast of system information

Establish, release and maintain calls

Mobility Inter-cell handover

IRAT

selection and reselection


Header compression and decompression of IP data flows

Transfer of data

Integrity protection of control plane data

Maintenance of sequence numbers for Radio bearers


Unacknowledged Mode (UM)

Acknowledged Mode (AM)

RLC transparent mode

Segmentation & Concatenation of RLC SDUs


HARQ

Priority handling (scheduling)

Transport format selection

DRX control (Discontinuous reception) prolong the mobile's battery life

The mobile station listens only to the paging channels within its DRX group

network will only page the mobile in that group of paging channels

Intended to maintain continuous transmission



Intra-LTE mobility

Inter-LTE mobility

ECM_CONNECTED mode mobility Inter RAT HO (to 3G/2G)

Inter MME (pool) HO (to 3G/2G)

Intra LTE HO (within one MME pool) intra/inter eNB

ECM_IDLE mode mobility Cell reselection with TA update


No LA

No RA

TA controlled by MME

TA list exists in the MME



Collocation with separate antenna system

Collocation with dual diplexer and shared mast feeder

Collocation with shared antenna


Add another antenna system for LTE

Simplest way to collocate LTE with existing technology

Make sure antenna separation either vertically or horizontally When vertically work with tilting

When horizontally work azimuth


Shared feeder and separate antennas

One diplex to combine Rx/Tx signal

One diplex to split signal to different ASC/TMA

Check the antenna dB isolation (minimum 30 dB isolation) to avoid inter-modulation



New antenna supporting both old technology and LTE frequencies

At least 30 dB isolation antenna between LTE and other technology


S4

SGSN

MME

HSS

SGW

eNodeB GSM WCDMA CDMA

IMS/IP Networks

Non 3GPP

technologies

S6

d

S1-UP

S3

S1-MME

S11

S6a

S4

PDN-GW

S8

S5

S2a



LTE RAN OSS

Transport

EPC

Aligned functionality

Testing in operator

environment

terminals

2/4/2014 Mustafa Golam, CTO, BDTele(BigData In

Telecom) 97

• Long Term Evolution is the 3GPP workgroup focused on developing the Evolved - UTRAN to bring it to next generation standards.

• System Architecture Evolution is the corresponding workgroup to develop the Evolved Packet Core.

E-UTRAN EPC

EPS


Telecom) 98

http://www.sonyericsson.com/spg.jsp?cc=gb&lc=en&ver=4000&template=pp1_loader&php=php1_10238&zone=pp&lm=pp1&pid=10238



Telecom) 99

CS Domain

PS Domain

IMS Domain

GERAN

UTRAN

External Networks

(CS)

External Networks

(PS)

E-UTRAN

Enhanced Packet Core

LTE/SAE workgroups (3GPP)

Core Network


Telecom) 100

RNC

NodeB NodeB

SGSN

GGSN MSC-S

MGW

Core Network, CS and PS domains

UTRAN


RNC

NodeB NodeB

SGSN

GGSN MSC-S

MGW

Only the PS domain is defined

RNC functions moved to E-Node B


E-NodeB E-NodeB

MME S-GW

P-GW

X2

IRAT Handover

Interface with SGSN

Idle mode mobility management

Interface with external networks

Charging

IP PoP

Terminates UP packets

Switching of UP for mobility reasons

Typically arranged in pools

All RRM including:

Bearer Control

Admission Control

Connected mode Mobility mgmt

UL/DL scheduling

S1


Indoor eNodeB

Minimal Footprint –400x600 mm (16x24 in)

Reduced Height –1435 mm (57 in)

Central Redundant Fans

12 Radio Units

6 sectors with 2x2 MIMO or 3 sectors dual band and 2x2 MIMO


Telecom) 104



The LTE/SAE transport study is a cross DU/PA team activity within the LTE/SAE Network Level System project (BNET) that

delivers an educational overview of the current and future e-2-e LTE transport network deployment scenarios in the different areas Access, Aggregation/Metro and Backbone: Typical deployment scenarios based on Vendor view Customer view of main customers Different alternative/options, dependent on

technology geographical and subscriber aspects (rural, urban, …) legal / business aspects (cost of leased lines) legacy aspects (e.g. a lot of fiber connected sites already in place)

identifies issues, conclusions and additional requirements on the transport solutions and products.


eNBBTS

eNBNode

B

ADMADMADMADM

1*E1/T1

2*E1/T1

ATM/

IMA/

n*E1/T1

ADMADM

SDH/SONET network

BSC

... 63*E1/T1

STM-1/OC-3c

RNCRNC

ATM

STM-1/OC-3c

μWμW

eNBBTS

eNBNode

B

ADMADM

1*E1/T1

2*E1/T1

ATM/

IMA/

n*E1/T1

μWμW

TextSite

Router

TextRouter

IP/MPLS

Packet

Switched

Network

IP/MPLS

Packet

Switched

Network

TextMSC -S

TextM-

MGw

Switching Core Other Core

sitesAggregationCell Site

Cell Site

Backbone already realized as packet based transport

Mobile Backhaul often still TDM and ATM access and SDH/SONET based Metro

Switching Core

Access Aggregation Core Metro

LRAN HRAN


RNC

RBS

RBS

RBS

RBS

RBS

RBS

RAN domain

BSC

RBS

3.6 Mbps

14 Mbps

28 Mbps

42 Mbps

80-160 Mbps

eNB

eNB eNB

eNB

SAE Gw

Evolution from narrowband voice to bandwidth demanding data centric transport…

Cost per bit needs to decrease rapidly


Operators therefore have different possibilities to tackle this problem:

Find a faster and cheaper way to get transport to cell sites using fiber.

Deploy self-built access to the cell-site (most likely microwave).

Look into converged architectures, e.g. using xDSL or GPON access where possible.

Agree on lower leased line tariffs based on long write off time for fiber and

longer agreement periods

It is not possible to build profitable mass-market mobile data backhaul infrastructure based on leased lines and/or bundles of E1s/T1s.


Switch Site

Aggregation Hub 2

Aggregation Hub 1

Cell Site

1) Microwave access

2) Fiber access & transport

3) xDSL access

4) GPON access

5) P-t-P fiber access

Mobile Backhaul dedicated Mobile Backhaul using BBA infrastructure (incl FMC)

Aggr . 1

cell site

Eth ( Cu )

Eth ( Cu )

Cu

Aggr . 2

xDSL xDSL

Cu

Cu

Other

Core Sites

Switch

ONT

Passive

Splitter

Eth OLT Switch

Switch

Switch resilient optical

connection

Switch

Switching Core

resilient optical

connection (ring or mesh)

Text Site

Router

GGSN SAE

Gw GGSN SAE

Gw

3 PP Service Network

Text Router Text BB

Router

μW

μW μW

DSLAM

RAN evolves towards native IP/Ethernet

eNB

eNB

eNB

eNB

MSPP

Router Router

Support for multiple technologies like PB/PBB, MPLS-TP. Routing function needed for IP/MPLS based transport.

MSPP MSPP

Rout. & Switch. & BRAS

MSPP

MSPP

L2/L3 demarcation variable

Demarcation might be even on cell site

PoP towards ‘Internet’ and/or ‘other operator’ Different geographical reach for different solutions !!

Switch


Aggr.

cell site

Eth ( Cu )

Other

Core Sites

Switching/ Core

Text Site

Router

GGSN SAE

Gw

μW μW eNB

eNB

IP/MPLS backbone

IP/MPLS backbone

SE 400

Fiber distribution point

Tier 2 HUB Fiber node

1 GE 1 GE

1 GE

cell Site

5 x

1 x

Partly in line with /// P-t-P Fiber and Microwave vision scenario but downsized/simplified

No Metro/HRAN, reuse of IP/MPLS backbone for trial phase

3PP Service Network

Switch

Extreme Summit

Optical

Optical

OMS 870

Optical Switch

Extreme Summit

Optical

OMS 870

MINI-LINK MINI-LINK

PoP towards ‘Internet’ and/or ‘other operator’

Switch

Extreme Summit


Aggr . 1

cell site

Eth Cu )

Eth ( Cu )

Aggr . 2

Other

Core Sites

Switch

Switch

Switch resilient optical

connection

Switching Core

resilient optical

connection (ring or mesh)

Text Site

Router

GGSN SAE

Gw GGSN SAE

Gw

3 PP Service Network

Text Router Text BB

Router

μW

μW μW

eNB

eNB

eNB

MSPP STN

MSPP MSPP

Rout. & Switch. & BRAS

MSPP

PoP towards ‘Internet’ and/or ‘other operator’

OMS 1410 R1 OMS 1410 R1

OMS 1410 -or-

SM 480

SE400/800/1200

SE400/800/1200

SE400/800/1200

MINI-LINK TN 4.1 6pD MINI-LINK

TN 4.1 2pB

MINI-LINK TN4.1 2pB

SIU 01 ?

EDA 1200 products ECN430/ EMN120

BTS

STN

We need a gap filler since NG-SIU development is late. Currently under discussion, e.g. ‘T750’

6-38 GHz 6-38 GHz

OMS 1410 -or-

SM 480


SGi

S12

S3

S1-MME

PCRF

Gx

S6a

HSS

Operator's IP Services

(e.g. IMS, PSS etc.)

Rx

S10

UE

SGSN

LTE-Uu

E-UTRAN

MME

S11

S5 Serving Gateway

PDN Gateway

S1-U

S4

UTRAN

GERAN


Security Domains and VPN Structure

Today – 3GDT sets GGSN and RNCs into one security Domain

SAE GW needs to connect to eNodeB, which has a different physical access security

IP connectivity to external networks In 2G/3G, DNS and Gn traffic connect only through Gp firewall and Security Domain


Mobile-PBN

IMS Module

External

Networks

PRAN

Gi, SGi

SGi

S6a, S9

S1-U, S1-MME

S1-MME

IuPS-C

IuPS-U, S12

Gb,

IuPS-U,

S101

IuPS-U

Gi

S7, Gx, Rx, S9

S6a

Gn, Gp

DNS.Gn, Gp, S3,

S4, S10, S11

IuPS-C, BSSAP,

S6a, S6a, DNS

S11, S4, S5, S8, S2a

S1-U

Gx

GGSN

SGSN/MME

RNC

PCRF

HSS

eNodeB

DNS, Gp, S8

S12

SAE-GW

Mobile Backhaul or Mobile-PBN

transport services, depending on

SAE GW and MME sites

PRAN

Gi, SGi InternetISP

S6a, S9,

DNS, Gp, S8GRX/IPX

Gi, SGi

Gi Firewall

DNS, Gp, S8, S9

Gx, Rx, S9,

S6a, DNS

DNS, Gx, Rx,

S9, S6a

Internet

Access

IP Inter-

connect

(Gp)

DNS, S6a

IP Interconnet (Gp) Firewall

DNS

Proxy

(eDNS)

eDNS (APN

resolution)

DNS

iDNS (APN

resolution)

DNS

IMS Firewall

DNS

eDNS

(DIAMETER

resolution)

IMS

DMZ

DNS

Serv. &

Control

Sig

iDNS

(DIAMETER

resolution)

CDMA 2000 (not in Mobile-PBN scope)

S2a

S101

RNCPDSN

Media

(Core)

BSSAP

GbR2C

(RAN)

BSC

Signal.

(SS7)

201-08-001-012/4/2014 Mustafa Golam, CTO, BDTele(BigData In Telecom) 117

The new main nodes that implement the Evolved Packet Core are the MME and the SAE GW. Depending on the typical placement of these nodes, certain sites in the network will include SAE GW, MME, or both.

Based on the dimensioning done, there will be no SAE GW nodes in mobile access sites in the mid term. We will find SAE GWs in all core sites, including Mobile-PBN Primary and Secondary sites.


The MME mode of the SGSN will support considerably more subscribers than for 2G/3G access in an LTE only mode, the target is 3 M SAU, corresponding to 5000 connected eNodeB. The number of required MME nodes in the network will be lower than the amount of SAE GW nodes.

In conclusion, there will be two basic EPC site types for the core network, one including only SAE GW, and one including SAE GW and MME.

In addition to these site types, there will be dedicated central sites hosting the HSS and SAPC nodes.


Node selection will involve enhanced DNS features compared to APN resolution in 2G/3G PS networks

MME Selection by an eNodeB Mechanism under discussion

MME Selection at Inter eNodeB handover (with MME relocation)

NAPTR DNS query by the source MME Answer as SRV or A/AAAA record

PDN GW (///->SAE GW) Selection NAPTR query for APN name sent by MME

Serving GW Selection (///->SAE GW) NAPTR query for tracking area sent by MME


Same Principles as developed in Mobile-PBN

MME SAE GW

Legend

1000 Base T

CN

nodes

Router PIU 1port1

port0

Router PIU 2port1

port0

Router PIU 3port1

port0

Router PIU 4port1

port0

201-08-005-01

10 GE

10 GE

Interface 1

10 GE

Interface 2

SR 1

SR 1

SW 1

SW 2


Same Principles as developed in Mobile-PBN

Design Options: Use combined router/switches and direct SGi connection

The SAPC and HSS nodes will be connected as in earlier Mobile-PBN releases

MME SAE GW

Legend

1000 Base T

CN

nodes

Router PIU 1port1

port0

Router PIU 2port1

port0

Router PIU 3port1

port0

Router PIU 4port1

port0

201-08-006-00

10 GE optical

10 GE

Interface 1

10 GE

Interface 2

SR 1

SR 2

End user

Services and

Internet Access


Logical Connectivity shown here for two networks only.

SR_1 SAE GW

(10) GE

SW_1

(10) GE

(10) GE

LAGLAG

LAG

(10) GE

(10) GE

(10) GE

LAG

Internet APN

context

CN VRF

CN_GN_GSN_1

IAC VRF

GI_IAC_1

SR_2 SW_2

LAG

LAG

IAC VRF

CN_GSN_2

GI_IAC_2

CN VRF

Core

Context


Bandwidth Traffic volume between Core sites might reach up to 20

Gbps

Capacity upgrade required

Site distribution According to dimensioning, it is expected that SAE GW

will be distributed to Core Sites only, without further spread-out towards access, at least not in the mid term


Traffic Type R6.1 BB/SI TIPI (R6.1

clients)

Network Control Network

Control CS6

NTP

Telephony Realtime EF

Signaling (SS7), Gb,

high prio charging

Signaling CS5 DNS

Radius

O&M Interactive

O&M Background

Guaranteed

Bandwidth

CS2

CS1

Streaming (Iu, Gn, Gi)

Gi SN, Gi L2TP AF31

Interactive (Iu, Gn, Gi) AF21

Charging low prio CS1

Background (Iu,Gn,Gi) AF11

Internet Background Best Effort BE

Alignment with TIPI-2 study

It assumed that PRAN will follow, too.

Client nodes expected to be in line with default DSCP values defined in TIPI-2 study

Client network classes will be mapped to a limited number of backbone classes defining queuing and scheduling behavior

Mobile-PBN Reference Network of 11.5 Mio Subscribers

Two scenarios: 10% or 50% penetration

Traffic per subscriber: 463 kbit/sec (aggressive Traffic Model)

For scenario 1 (Western Europe, 10% penetration)

total number of 1,150,000 LTE subscribers with an aggregated throughput of 363 Gb/s

For scenario 2 (US, 50% penetration)

total number of 5.75 Million subscribers and an aggregated throughput of 1.8 Tb/s

SAE GW capacity of 256,000 subscribers and 100+ Gb/s throughput, and a total number of SAU in the MME of 3 Million

Scenario 1 : 5 SAE GW, 1 MME

Scenario 2 : 23 SAE GW, 2 MME 2/4/2014 Mustafa Golam, CTO, BDTele(BigData In Telecom) 126

Aspects to be considered:

Operational benefit of centralizing core nodes to a few central sites

Closeness of SAE GW to the Internet peering points and the possibility to get rid of high traffic volumes early by pushing out SAE GW nodes further out towards the access.


EPC in Details


Up to 300 Mbit/s DL & 75 Mbit/s UL

Possible to use LTE in many different frequency bands, both FDD and TDD schemes

Coexist with other systems like GSM, WCDMA and even none 3GPP such as CDMA2000

100% IP based core


System Architecture Evolution (SAE) is the core network architecture of 3GPP's future LTE wireless communication standard.

SAE is the evolution of the GPRS Core Network, with simplified architecture, all IP networks, and support for different access technologies.

The main component of the SAE architecture is the Evolved Packet Core (EPC), also known as SAE Core. The EPC will serve as equivalent of GPRS networks.


Major Vendors have implement LTE network across the

Continant.

Huawei implemented the first commercial LTE network in Norway

ZTE implemented the LTE network in HK

LTE implementation is on going rapidly across the globe..



MMEHSS S-GW P-GW

EPC

MPG/

CPG

WCDMA / GPRS

EPC


Functionality Compare

MME Attach and detach of UE

Authentication procedure with assistance of the HSS

Choosing SGW and PGW for the UE

Manage PDN connections and EPS bearers

Mobility Procedures

UE tracking

Paging

SGSN – Attach and detach of MS

– Authentication procedure with assistance of the HLR

– establishment of the connection for MS via the GGSN

– Session management

– Mobility management

– Subscriber data management


Hardware Based on WPP platform, upgrade

from SGSN, called SGSN-MME in new products.

Only control plane

Only IP (v4 and v6)

Protocol stacks: S1AP, NAS, DIAMETER,GTPV1 and GTPV2

MME in pool supported


Functionality in S-GW & P-GW

S-GW Packet routing and forwarding Local mobility anchor for the user plane during inter-

eNodeB handovers Charging

P-GW Provides IP connectivity towards external PDNs Policy and admission control Packet filtering per user Service based online and offline charging


Hardware New product in E///

Based on SmartEdge 1200 platform

Redback SmartEdge OS 6.1.3

Fully meshed slot to slot

Protocol stacks: DIAMETER, GTPv1 and GTPv2


Hardware Based on Juniper M120 platform,

upgrade from GGSN

Functionality enabled through GGSN software upgrade.

Multi access support for GSM, WCDMA and LTE networks.

Mobility provided between all 3GPP access networks.


The HSS contains the database holding subscription information for UE subscribing to the EPS network.

HSS can also be used in various systems, such as IMS Communication System, EPS and any type of wireless access.

Functionality in EPS

Subscription Management , Subscription Profile Configuration , Authentication Support

Operator Determined Barring, User Profile Management and Service Authorization

Mobility management, Roaming restrictions


Hardware Based on TSP platform, a new

platform

Multi access support for EPS, WLAN and wireless access networks.

Dicos, Linux OS

VIP concepts for traffic and transport

Protocol stacks: Diameter, MAP, SigTRAN,


Functionality

Subscriber, device, and access-aware handling

policy control decisions

Flow-based charging


Hardware Based on TSP platform

Used both in WCDMA and EPS systems

Dicos, Linux OS

VIP concepts for traffic and transport

Protocol stacks: Diameter, SigTRAN



› The EPS architecture is made up of a EPC (Packet Core Network) and a eUTRAN Radio Access Network

› The CN provides access to external packet IP networks and perform a number of CN related functions (e.g. QoS, security, mobility and terminal context management) for idle and active terminals

› The RAN performs all radio interface related functions for terminals in active mode



GGSN

Gi

Packet Data Networks (Internet)

Node B

RNC

BTS

BSC

Iu up/S12

Iub

Gb

UTRAN GERAN

Control Interface

User Data Interface

SGSN

Gn

Iu/Gn-UP (Rel-7 One Tunnel)

LTE

eNode B

S1-C S1-U

› 3GPP Rel-7 specifies the feature called “3G Direct Tunnel” where the user plane goes direct between RNC and GGSN

› 3GPP Rel-8 specifies a SAE GW and a MME. SW upgrade of the GGSN gives SAE GW functionality and MME functionality in the SGSN

› LTE capable eNode Bs are introduced

SGSN/MME

GGSN/SAE GW


Core Network

New System for packet data transmission over broadband radio access.

Evolution from 3GPP 2G and 3G.

Standarization ongoing in 3GPP release 8.

Non-3GPP

CS networks

”IP networks”

3G

2G

Circuit Core

IMS domain

EPC eUTRAN

User mgmt

added


3GPP terms:

EPS = Evolved Packet system. 3GPP Global name for the whole system, including eUtran, EPC and user equipment.

eUTRAN = Evolved UTRAN. Access part of the system.

EPC = Evolved Packet Core. Core part of the system

Industrial terms:

LTE = Long term evolution. Group all new e-nodeBs providing broadband radio access to end users.

SAE = System Architecture Evolution. Core part evolved to meet requirements of the LTE.

SAE/LTE = Evolved Packet System


Ensuring that 3GPP is attractive in comparison with competing technologies (WiFi, WiMax, Flarion, …) As ”simple” as competing technologies (fewer nodes)

A flat optimized 2-node architecture for user plane (OPEX and CAPEX)

Reduce cost per bit

Secure investments made by our customers

Higher speeds than any of the competitors

Interfaces towards all 3GPP and non-3GPP access technologies for interconnection with SAE.


High data rates – Downlink: >100 Mbps – Uplink: >50 Mbps – Cell-edge data rates 2-3 x HSPA Rel. 6 (@ 2006)

Low delay/latency – User plane RTT: Less than 10 ms ( RAN RTT ) – Channel set-up: Less than 100 ms ( idle-to-active )

High spectral efficiency – Targeting 3 X HSPA Rel. 6 (@ 2006 )

Spectrum flexibility – Operation in a wide-range of spectrum allocations – Wide range of Bandwidth (from 1.4 MHz to 20 MHz) – Support for FDD and TDD Modes

Cost-effective migration from current/future 3G systems

Focus on services from the packet-switched domain ! 2/4/2014 Mustafa Golam, CTO, BDTele(BigData In Telecom) 151


More people at the same time, doing it faster and with even better quality

PC/Laptop symbol

Video Conferencing M-commerce

Music

Gaming

Doctor/mechanic

TV watching

Messaging


Internet,

Operator Service etc.

EPC EPC - Evolved Packet Core

eUTRAN eUTRAN - Evolved UTRAN

EPS – Evolved Packet System


3G Direct Tunnel: capacity

improvement, bypassing the SGSN node,

reduces CAPEX.

All-ip transport: Reduces costs and

improves escalability.

SGSN pool: network resilience and

reduces signalling.

HSPA: Higher throughput in the radio

access improves user perception.

IP networks

HLR

WCDMA

/eHSPA GSM

SGSN

Charging

GGSN


Fair mobile broadband usage

Bandwidth management

Policy implementation

Deep packet inspection

End-to-end Quality of Service control

Service-aware charging

PCRF

IP networks

HLR

GSM

Charging

SASN

GGSN

Note: SASN could be standalone or integrated in GGSN

SGSN

WCDMA

/eHSPA


LTE

NON-3GPP

WLAN

EPC achievable by

straightforward software upgrades

– GGSN upgrade to Mobile Packet

Gateway (in a later phase)

– SGSN upgrade to triple-access

Multi-access (access agnostic)

Flat architecture: 2 nodes for user traffic (based on 3GDT idea)

IP transport infrastructure allowing

pooling for SAE GWs, and MME,

sharing the eNodeBs

Note: SASN could be standalone or integrated in PGW

SAPC

IP networks

GSM

Charging

SASN

MME

WCDMA

/eHSPA

SGSN

PGW

UM


LTE = Long Term Evolution (of 3GPP family) Evolution path for GSM/EDGE, WCDMA/HSPA,

HSPA+

LTE is being specified in 3GPP Release 8

Now also known as eUTRAN

Designed primarily for mobile broadband packet data

simple architecture

Flexible design to allow deployment in new and re-farmed spectrum

Takes radio performance to the next level

LTE is the next step in radio for mobile broadband 2/4/2014 Mustafa Golam, CTO, BDTele(BigData In Telecom) 157

Downlink: Multi-layered OFDMA Channel-dependent scheduling

and link adaptation in time and frequency domain

Uplink: Single Carrier-FDMA Higher uplink system

throughput

Improved coverage and cell-edge performance

Lower terminal cost and improved battery life

Downlink Uplink

frequency frequency

User 1

User 2

User 3


MME = ”Mobility Management Entity”

eNodeB = the LTE base station

Signaling User traffic

IP networks

2G/3G

LTE

Optimized UP

path for LTE

Interconnection of

other access

technologies using

Mobile IP

Policy Control and Charging –

enhancements of 3GPP R7

Full reuse of user

Management HSS and IMS

enhacements 3GPP R7

User traffic and signaling

separation in core network

Other

access MME

SAE GW

eNodeB S

-GW

P-G

W


• Common GW for all accesses

• Core network pooling for LTE

access

• Policy control also supporting LTE

• Diameter for LTE user management

• Smooth interworking 2G/3G – LTE

• 3G Direct Tunnel for HSPA

SAE GW

HSS

HLR

MME SGSN

PCRF

2G 3G

Gb Iu-C

S3

S4

S1-C S1-U

S12

S11

S10

SGi

Gx

IP networks

S6a

Gr

LTE

PDN GW

Serv GW

S5


2G/3G

SGi

IP networks

• Basic case: home tunnelling

• Smooth upgrade to support LTE and

other accesses

• Support for 3 operator model

• GTP and MIP options for roaming

Other accesses

S8

PDN GW

SAE GW

Home PLMN

Visited PLMN

Note: HSS and AAA excluded for simplicity

LTE

Serv GW

SAE GW

hPCRF

S7

PDN

GW Serv GW

SAE GW vPCRF

S9

SGi

IP networks

SGi

IP networks

PDN GW

SAE GW S7

2G/3G Other accesses

• Advanced case: both home tunnelling and local

breakout possible

• Roaming controlled by home network policies

• PCRF-to-PCRF roaming interface

• GTP and MIP options for roaming

S8

LTE


HSS

HLR

MME SGSN

PCRF

2G 3G

Gb Iu-C

S3

S4

S1-C S1-U

S12

S11

S10

SGi

Gx

IP networks

S6a

Gr

LTE

PDN GW

Serv GW

S8 HPLMN

VPLMN


HSS

HLR

MME SGSN

V-PCRF

2G 3G

Gb Iu-C

S3

S4

S1-C S1-U

S12

S11

S10

SGi

Gx

IP networks

S6a Gr

LTE

PDN GW

Serv GW

S5

HPLMN

VPLMN

H-PCRF

S9


S7 SGi

Rx+

SIP

IMS domain S-CSCF I-CSCF

IP networks

P-CSCF

PCRF

SAE GW

The Packet core evolution is transparent to IMS services.


S1 Interface S1 UP, eNodeB<->P/S-GW S1 CP, eNodeB<- >MME

X2 Interface eNodeB<- > eNodeB

S11 Interface MME<->P/S-GW

S3 Interface SGSN<->MME

S4 Interface SGSN<->P/S-GW


MME/GW

S1 S1 S1

X2 X2

eNode B eNode B eNode B

Evolved

Packet

Core

Evolved

UTRAN


S1 Interface The interface between eNodeB and SAE

(MME and S-GW) In the user plane, based on GTP User Data

Tunnelling (GTP-U) (similar to today’s Iu and Gn interface)

In the control plane, more similar to Radio Access Network Application Part (RANAP), with some simplifications and changes

Split into S1-CP (control) and S1-UP (user plane). Signalling transport on S1-CP will be based

on SCTP Payload transport on S1-UP will be based on

GTP-U

S1 is a many-to-many interface.

MME/GW

S1 S1 S1

X2 X2

eNode B eNode B eNode B 2/4/2014 Mustafa Golam, CTO, BDTele(BigData In Telecom) 167

X2 Interface

The interface between eNodeB Mainly used to support active mode UE

mobility May also be used for multi-cell Radio

Resource Management (RRM) functions

X2-CP interface will consist of a signalling protocol called X2-AP on top of SCTP

The X2-UP interface is based on GTP-U The X2-UP interface will be used to

support loss-less mobility (packet forwarding).

The X2 interface is a many-to-many interface.

MME/GW

S1 S1 S1

X2 X2

eNode B eNode B eNode B 2/4/2014 Mustafa Golam, CTO, BDTele(BigData In Telecom) 168

S3 Interface

•enables user and bearer information exchange for inter 3GPP access network mobility in idle and/or active state.

•Based on Gn reference point as defined between SGSNs.

•Protocol: GTP-C

HSS

HLR

MME SGSN

PCRF

2G 3G

Gb Iu-C

S3

S4

S1-C S1-U

S12

S11

S10

SGi

Gx

IP networks

S6a

Gr

LTE

PDN GW

Serv GW

S5

SAE GW


S4 Interface

• Provides related control and mobility support between GPRS Core and the 3GPP Anchor function of Serving GW

• Is based on Gn reference point as defined between SGSN and GGSN.

• In addition, if Direct Tunnel is not established, it provides the user plane tunnelling.

• Protocol: GTP-C / -U

HSS

HLR

MME SGSN

PCRF

2G 3G

Gb Iu-C

S3

S4

S1-C S1-U

S12

S11

S10

SGi

Gx

IP networks

S6a

Gr

LTE

PDN GW

Serv GW

S5

SAE GW


S5 Interface

• Provides user plane tunnelling and tunnel management between Serving GW and PDN GW.

• Used for Serving GW relocation due to UE mobility and if the Serving GW needs to connect to a non-collocated PDN GW for the required PDN connectivity.

• Protocol: GTP (or PMIPv6)

HSS

HLR

MME SGSN

PCRF

2G 3G

Gb Iu-C

S3

S4

S1-C S1-U

S12

S11

S10

SGi

Gx

IP networks

S6a

Gr

LTE

PDN GW

Serv GW

S5

SAE GW


S6a Interface

• Enables transfer of subscription and authentication data for authenticating/authorizing user access to the evolved system (AAA interface) between MME and HSS.

• Protocol: Diameter.

HSS

HLR

MME SGSN

PCRF

2G 3G

Gb Iu-C

S3

S4

S1-C S1-U

S12

S11

S10

SGi

Gx

IP networks

S6a

Gr

LTE

PDN GW

Serv GW

S5

SAE GW


Gx Interface

• provides transfer of (QoS) policy and charging rules from PCRF to Policy and Charging Enforcement Function (PCEF) in the PDN GW.

• Protocol: DIAMETER

HSS

HLR

MME SGSN

PCRF

2G 3G

Gb Iu-C

S3

S4

S1-C S1-U

S12

S11

S10

SGi

Gx

IP networks

S6a

Gr

LTE

PDN GW

Serv GW

S5

SAE GW


S10 Interface

• Reference point between MMEs for MME relocation and MME to MME information transfer.

• Protocol: GTP-C

HSS

HLR

MME SGSN

PCRF

2G 3G

Gb Iu-C

S3

S4

S1-C S1-U

S12

S11

S10

SGi

Gx

IP networks

S6a

Gr

LTE

PDN GW

Serv GW

S5

SAE GW


S11 Interface

• Reference point between MME and Serving GW.

• Protocol: GTP-C

HSS

HLR

MME SGSN

PCRF

2G 3G

Gb Iu-C

S3

S4

S1-C S1-U

S12

S11

S10

SGi

Gx

IP networks

S6a

Gr

LTE

PDN GW

Serv GW

S5

SAE GW


S12 Interface

• Reference point between UTRAN and Serving GW for user plane tunnelling when Direct Tunnel is established.

• Protocol: based on the Iu-u/Gn-u reference point using the GTP-U protocol as defined between SGSN and UTRAN

HSS

HLR

MME SGSN

PCRF

2G 3G

Gb Iu-C

S3

S4

S1-C S1-U

S12

S11

S10

SGi

Gx

IP networks

S6a

Gr

LTE

PDN GW

Serv GW

S5

SAE GW


SGi Interface

• Reference point between the PDN GW and the packet data network.

• Packet data network may be an operator external public or private packet data network or an intra operator packet data network, e.g. for provision of IMS services.

• This reference point corresponds to Gi and Wi functionalities and supports any 3GPP and non-3GPP access systems

HSS

HLR

MME SGSN

PCRF

2G 3G

Gb Iu-C

S3

S4

S1-C S1-U

S12

S11

S10

SGi

Gx

IP networks

S6a

Gr

LTE

PDN GW

Serv GW

S5

SAE GW



• 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 AAA mechanisms

• Security support for non-trusted accesses

HSS AAA

PCRF

Non-trusted Trusted

IP networks

ePDG PDN GW

SAE GW

Serv GW

S5 ”Legacy” 3GPP

access networks

”Legacy” 3GPP2

access networks

LTE


Non 3GPP access control to SAE supported via the following interfaces:

STa, SWa, SWm, SWx, S6b towards 3GPP AAA: User Authentication

Subscriber profile management

PDN-GW selection support

Roaming restriction

Network access control

SWx = 3GPP AAA interface

STa / SWa = legacy AAA interface to

3GPP AAA

SWm = AAA to ePDG


S2a Interface

• Reference point for the control plane and user-plane between PDN-GW and Trusted non-3GPP networks.

•Protocol : PMIPv6, GRE

S2b Interface

• Reference point between PDN-GW and the ePDG. Used to provide SAE Core Network access and session mobility for un-trusted access networks such as fixed and WLAN deployments

•Protocol : PMIPv6

S2c Interface

• Reference point between PDN-GW and the UE. Used to provide client-based session mobility.

•Protocol : DSMIPv6

SWn Interface This reference point is used for forced forwarding of UE-initiated tunnelled packets towards the ePDG •Protocol : Locally agreed, e.g. routing based



HSS

HLR

AAA

ePDG

PDN GW

Serv GW MME SGSN

PCRF

LTE 2G 3G Non-3GPP

Non-trusted

Non-3GPP

Trusted

Eg cdma

SWx

Gb Iu-C

S3

S4

S1-C S1-U

S12

S10

S11

S5/S8

SGi

S6b

Gx

Gxc Gxb

Gxa

STa

S2b

S2a

S2c

SWa SWn

SWm

IP networks

S9

S6a

Gr

S101/102

S103


EPC Supported via S6a Interface (DIAMETER) to MME: Attach / Detach Authentication Location Update Purge Reset

EPC <-> 2G/3G mobility supported via intruduction of HSS layered architecture (HLR FE, HSS FE and CUDB)

Non 3GPP mobility supported via STa, SWa, SWm, SWx, S6b: User Authentication Subscriber profile management PDN-GW selection support Roaming restriction Network access control

SWx = 3GPP AAA interface

STa / SWa = legacy AAA interface to

3GPP AAA

SWm = AAA to ePDG


IP

networks

• Simplification with all accesses through I-HSS

• I-HSS incl. support for System Architecture Evolution (SAE)

2010-2011

LTE

• Data Centralization • Cost reduction by User Data

Consolidation (UDC)

2009

• Emerging markets: subscriber growth

• Mature markets: new features

2007-2008

HSS HLR/AuC

EMA

HSS-S HLR-S

CUDB

EMA

I-HSS

CUDB

EMA

IP

networks

IMS Fixed

Broadband

IMS IMS

Packet

Cable

LTE

IP

networks

Smooth and step-wise evolution with business needs

CDMA2000

2G/2.5G/3G 2G/2.5G/3G

Fixed

Broadband

CDMA2000

2G/2.5G/3G

WLAN WLAN


Front-End Server

FE server

Monolithic

Node

OA

M

PROTOCOLS

LOGIC

DB

OA

M

PROTOCOLS

LOGIC Signalling &

application logic

DB FE data profiles

Classic Server

PROVISIONING LOGIC

Modified network architecture from monolithic towards layered (Simple Upgrade)

Subscriber data is moved from subscription nodes to the Centralized User Database, CUDB (data migration service)

Simplified management with direct Provisioning towards CUDB (one subscription profile)

Improved network scalability when Front-End Server converted to data- and stateless machine

OA

M

CUDB

Separation of subscription and traffic scalability for improved OPEX & CAPEX

SW Upgrade


Node belonging to the SACC solution

Main task: control of authorized services per user and QoS control per bearer (PDP context).

SAPC allows SACC subscriber differentiation and flexibility by means of policy evaluation.




1. VoIP based on MMTel over LTE

2. CS Fallback in EPS


One of the possible solutions for voice continuity in the SAE network is the usage of MMTEL IMS application, this is Voice over IP.

Handover of voice calls from LTE to 2G/3G CS possible : Initiated by HO signaling between the MME and the Inter Working Function (IWF) part of the MSC Server.


Key feature to enable co-existence of CS voice on

2G/3G with LTE.

Feature allows a mobile using LTE to temporarily switch to 2G/3G CS when initiating or receiving a voice call.

After the call is terminated, the mobile switches back to LTE again.

The exact solution for this is still under discussion in 3GPP.


EMM-DEREGISTERED:

•EMM Context in MME

holds no valid location

or routing info for UE

• Context data can still

be stored in UE.

EMM-REGISTERED:

• UE can receive

services requiring

registration in EPS

•UE location known to

MME to Tracking Area

granularity

•UE has at least 1 active

PDN context

•UE sets up EPS

security context

EMM - DEREGISTERED EMM - REGISTERED

Attach accept, TAU accept

Detach, Attach Reject, TAU reject, EUTRAN interface switched off due to Non-3GPP handover, All bearers deactivated,

EMM - DEREGISTERED EMM - REGISTERED

Attach accept, TAU accept

Detach, Attach Reject, TAU reject All bearers deactivated

EMM state model in UE

EMM state model in MME 2/4/2014 Mustafa Golam, CTO, BDTele(BigData In Telecom) 193

ECM-IDLE ECM-CONNECTED

RRC connection established

RRC connection released

ECM-IDLE ECM-CONNECTED

S1 connection established

S1 connection released

ECM state model in UE

ECM state model in MME

ECM-IDLE:

•RRC connection not

established.

•UE location known at

Tracking area level.

•UE performs Tracking

Area Updates.

•MME does paging to

locate the UE.

•Performs service

request procedure to

send data uplink

ECM-CONNECTED:

•RRC connection UE-

eNodeB

•UE location known to

MME to cell level.

•Tracking Area Updates

at change of MME

(mobility or load

balancing)



MME

PDN-GW

PDN-GW

UE

1. Attach initiate/ establish

4. Inform UE on PDN-GW.

5. Establish user plane connection (default bearer)

eNodeB

Associated MME/S-GWs

HSS

2. User data request.

3. User data: GW ID, Default APN.

PDN-GW

Note: As opposed to 3GPP 2G/3G: Default user APN is configured in the HSS, not in the UE. Default context bearer is always established on attach. Mobile gets an IP on attach.


MME

UE

1. APN request.

4. Inform UE on PDN-GW.

5. Establish user plane connection (bearer)

eNodeB

Associated MME/ S-GWs HSS

2. User data request.

3. User data: GW ID, APN, roaming info and IP addr. (for non-3GPP handover).

PDN-GW

PDN-GW

PDN-GW


MME

S-GW

S-GW

UE

SA1

1. APN request.

2. Inform eNodeB on S-GW, based on UE TA within SA1

3. Establish user plane connection (bearer)

eNodeB

UE

SA2 S-GW eNodeB

Configured MME/S-GWs

Connects UE to “best” S-GW based on residing Service Area (SA) 2/4/2014 Mustafa Golam, CTO, BDTele(BigData In Telecom) 198

MME

MME

S-GW

eNB

SA SA

MME

eNB

eNB

S-GW

eNB

eNB

TA group

Two main modes for mobility for Intra LTE

X2 Mobility

With or without S-GW relocation

S1 Mobility

With or without packet forwarding

Direct or indirect packet forwarding

With MME relocation

With S-GW relocation

Combined relocation


Unchanged or relocated

S1-MME S1-U

S5/S8

S6a

S-GW

eNB eNB

HSS

S5/S8 Initiated by UE cell change

Optimized mobility

Different modes

Unchanged MME

unchanged or relocated SAE-GW

X2 transfers traffic during handover, meanwhile relocation from target to source eNB and potentially relocation of S-GW

S-GW

MME

S1-U

X2

S11 S11

Data forwarding

PDN-GW


Unchanged or relocated

S1-MME

S1-U

S5/S8

S6a

S-GW

eNB eNB

HSS

S5/S8 Initiated by UE cell change

Triggered when no X2 for handover exists

May relocate the MME; this procedure may also relocate both the MME and the Serving GW

Packet forwarding during handover and any relocation procedures

Additional RAN – EPC signaling compared to X2 mobility

S-GW

S1-U

(X2)

S11 S11

MME MME S10

Packet forwarding

PDN-GW


Gb/Iu S1-MME S1-U

S11

SGi

S6a Gr

GGSN

LTE GSM/ WCDMA

HLR

Packet GW

SGSN MME

HSS Gi

Gn

No specific network support, complete overlay

The terminal has support for both LTE and 2G/3G

At power on, the terminal attaches to either LTE or 2G/3G packet depending on coverage and preferences

Common subscription data need to be accessible from both HLR and HSS Not 100% overlap between data sets The HLR/HSS integration is targeting only consistent

user data in case #1 (not for mobility)

At loss of coverage, the terminal need to attach to the other network through some logic. No network support for controlling the terminal behaviour Idle mode behaviour is terimnal implementation

dependent In Connected mode, access NW change is triggered by

loss of connection

GGSN is used as anchor when 2G/3G is used, PGW is used as anchor when LTE used This means no preservation of IP addresses when

changing access -> applications may need to be restarted

(Note that the term ”PGW” here is used for the combination of Serving GW and PDN-GW)

Common subscription data


HLR

Gb/Iu

Gn (S3)

Gn (S4)

S1-MME S1-U

S11

SGi

S6a Gr

Packet GW

GGSN

SGSN MME

LTE GSM/ WCDMA

HSS Gi

Gn

A connection between SAE GW+MME and SGSN is established Gn used for a rel-7 SGSN Gn or S3+S4 may be used for a rel-8 SGSN

GGSN may be kept in the network but is not used for LTE-capable terminals

At power on, the terminal attaches to either LTE or 2G/3G packet depending on coverage and preferences

PGW is always used as anchor (for 2G/3G/LTE) This allows for preservation of IP addresses when changing

access

The LTE network is not communicating GSM/WCDMA neighboring cell information

The GSM/WCDMA network is not communicating LTE neighboring cell information

The terminal behaviour at loss of coverage is as for case #1

Mobility supported: LTE->2G/3G using RAU 2G/3G->LTE using TAU

HLR/HSS integration required to support mobility

HLR/HSS integration


HLR

Gb/Iu S1-MME S1-U

S11

SGi

S6a Gr

Packet GW

SGSN MME

LTE GSM/ WCDMA

HSS

Gn (S3)

Gn (S4)

GGSN

Gi

Gn

Same case as #2, but with additions: a) The LTE network is now communicating GSM/WCDMA

neighboring cell information b) The GSM/WCDMA network is now communicating LTE

neighboring cell information (requires update to rel-8) c) No support for traffic handover

If both a) and b) are supported, the network provides full idle mode control

PGW is always used as anchor (for 2G/3G/LTE) This allows for preservation of IP addresses when changing

access

Mobility supported: LTE->2G/3G using RAU 2G/3G->LTE using TAU

Interruption time during inter-system mobility reduced

a) LTE->2G/3G mobility (requires support in LTE network) b) 2G/3G->LTE mobility (requires support in GSM/WDCMA

network)

HLR/HSS integration


HLR

Gb/Iu S1-MME S1-U

S11

SGi

S6a Gr

Packet GW

SGSN MME

LTE GSM/ WCDMA

HSS Additional features in terminal, SGSN, MME and both RANs to support packet HO

Very short interruption times for inter-system handovers possible in both directions (<0.5 sec)

This mobility case is needed for handovers of realtime services including VoIP/MMTel

PGW is always used as anchor (for 2G/3G/LTE)

This allows for preservation of IP addresses when changing access

GGSN

Gi

Gn

Info exchange

Gn S4

Gn S3

HLR/HSS integration


Case #1: Independent networks Only common/double provisioning in HLR and HSS needed,

no rel-8 upgrades required

Case #2: Packet mobility, no RAN support Integration of HLR and HSS needed, no rel-8 upgrades

required

Case #3: Packet mobility, RAN support For the direction LTE->2G/3G, no rel-8 upgrades are required For the direction 2G/3G->LTE, a rel-8 capable 2G/3G RAN is

required. This also requires a rel-8 SGSN

Case #4: Packet HO Requires rel-8 upgrades of SGSN as well as 2G/3G RAN

including support for Packet HOs HO performance optimization


Early Trials LTE only testing requires no integration with 2G/3G

network.

Further Trials Introduce packet mobility using Gn towards 3GPP R7

SGSN for IRAT trials without specific legacy support

Mobile Broadband deployments in 2010 Introduce packet mobility with PS session continuity in

the direction of LTE to 3G, can later be enhanced through 3G support

Voice over LTE deployments Packet handover with support for realtime mobility

HO performance optimization 2/4/2014 Mustafa Golam, CTO, BDTele(BigData In Telecom) 207

Ericsson is developing the following commercial products for release of SAE/LTE:

MME: SGSN-MME 2009B

SAE GW: Converged Packet Gw R1 and GGSN-MPG 2010A

HSS: HSS 5.0 and UDC R1 FP01

PCRF: SAPC 2009 B

eNodeB: LTE RAN L10 A


Fully commercial SGSN+MME in the same package

3GPP 2G, 3G + LTE/EPC functionality

Simple migration – reuse of service hardened SGSN hardware and software architecture

Continued focus on signaling and Mobile Broadband


IBxxv4

PEBv4

FSBv4

• Processor boards

for control (AP) or

payload (DP).

• Flexible ”role” configuration

• Qty: Capacity

related

Boards for:

• Power distribution

• Internal Eth

communication.

Qty: 2 per magazine

Boards for:

• Software storage

• Node config.

Magnetic disk.

Qty: 2 per node

Magazine 2/4/2014 Mustafa Golam, CTO, BDTele(BigData In Telecom) 210

Ericsson will introduce the Converged Packet Gw R1 as the first product for SAE/LTE, optimized for very high throughput in future LTE intensive scenarios. It is referred to as the Converged Gateway.

Converged Gateway is a new development on a new platform, the SmartEdge 1200 from Redback.

The Ericsson GGSN-MPG 2010A will be introduced later, and will add the PDN and Serving Gateway functionality for SAE/LTE networks to the GGSN platform.

The Mobility Gateway fully reuses hardware and common functionality while adding the SAE specific functionality. Both current M20 and M120 platforms will be supported.


Mobile Packet

Gateway (MPG)

For 3GPP/LTE network access

An evolution from the market-

leading Ericsson GGSN

Converged Packed Gateway (CPG)

For broadband LTE networks

and non-3GPP convergence

A new product based on

a proven platform (SmartEdge)


Ericsson Converged Packet Gateway uses the SmartEdge 1200 platform

Introduces SAE Gateway functionality

– Market-leading Ericsson 3GPP software

– Fully 3GPP R8 compliant

– Serving and PDN Gateway functionality

– LTE support with mobility to GSM/WCDMA

– Mobility between LTE and CDMA (3GPP2) and fixed networks (MIP)

– Integrated Deep Packet Inspection functionality

Exploits key high performance MSER functionality – Routing, VPN, MPLS, VPLS

– Fully programmable ASIC-based broadband IP engine

– High availability architecture

– In-service software upgrade (ISSU) capability


Provides a smooth migration for Ericsson GGSN

customers to LTE/SAE using GGSN-MPG 2010 A.

It will be released in 2010.

Extensive feature-rich 3GPP mobile solution

Requires software upgrade to existing GGSN

Supports large subscriber numbers for substantial existing deployed base

(up to 6 million PDP sessions)


GGSN evolution to EPC Mobile Gw with full reuse of existing installed node

GGSN, (as well as SGSN, HSS and SAPC) can be upgraded by SW-only upgrade to support SAE/LTE

No additional hardware is needed

Converged Gw developed for distributed architecture

This solution perfectly addresses convergent operator with extensive throughput need per subscribers and low number of subscribers per node

Very flexible architecture and migration possible based on Mobile and Converged Gw

Both Gateways will evolve to address future needs


The first release to work with SAE will be

HSS 5.0: • First stage, monolithic

• supporting early implementations of SAE.

• No mobility IRAT requirements.

• It will be released in June 2009.

First solution implementing data layer structure

will be UDC R1 FP01: • It will handle SAE R1 with IRAT mobility requirements.

• It will include HLR FE, HSS FE, CUDB and PG as separated

nodes.

• HSS release will be 5.0.

• Released end 2009.


- 5 Zx

XCAP Authentication Support,

MME

System Performance management Fault management Configuration management System SW management

Sh

HSS Provisioning

Provisioning System

Server

AS

SIP Application Server

HLR

MAP

XCAP Server

SIH

SAE

S6a ESM SAE

Subscription module

Cx

SSO

retrieval from the HLR at any time

Authentication vectors retrieval

OSS-RC

MAP

SDA Subscription Data Access

module

Subscription Data Access

PAM

Packet Access module

GGSN/AAA

SWa, S6b, STa, SWm, Wa

WSM WLAN

Subscription module

SWx

PDN GW

TSP 6 /NSP 6.0

platform

D’/Gi

CUDB LDAP SLF

3GPP AAA SWx

LDAP SOAP

Provisioning notifications

ePDG

AAA

Access Gateway

XCAP Aggregation Proxy

AVG Authenticati

on Vector Generator

module

ISM IMS

Subscription module

CSCF


Ericsson solution based on:

RBS 6000 platform

First mainstream products in 2009/2010


Part 2: SAE services

SAE/EPC introduction


15+ RFIs and RFPs

1 customer trial on air

5 trials in the pipe

20+ additional trials being requested for 2009

First commercial launches planned end 2009

Broader deployment starting 2010


With SAE introduction, a phased end-2-end approach must be secured with regards to service scoping for:

Technical solution view

•EPC/SAE nodes •PBN connecting the SAE nodes with LTE •HSS/HLR for user management •SACC & Charging systems, including Policy & charging control •LTE Radio •Non-3GPP access integration

Project view •M-PBN introduction •3GDT introduction •SGSN Pool introduction •SACC implementation •SAE/EPC introduction •Multi Vendor Verification/Integration

Business view •2G/3G/CDMA interworking •Fixed/mobile convergence •VoIP •IMS introduction •Differentiated QoS 2/4/2014 Mustafa Golam, CTO, BDTele(BigData In Telecom) 221

Overlay network with 2G/3G handover/connectivity

WLAN / Wimax interworking & fixed/mobile convergence.

Customer provided IP backbone & KPI related acceptance testing.

Ongoing standardization & product development together with projects with high probability for Multi Vendor scenarios

Lack of resources & competence in new technology domains (TSP based HSS, Redback based CPG etc)


We can build on existing competence in the Packet Core & M-PBN domains

We have experience from deploying HSS with IMS

We have delivered SAPC with SASN for SACC

We have started early with service preparation for LTE & SAE compared to product development timeplan

We have learned (the hard way) from introducing e.g. MSS & SACC that careful planning is needed

Trial projects an excellent way of getting familiar with the new technology


Packet switched traffic will play a key role in future Mobile networks

Data volumes & customer ISP requirements will increase alot – also new types of traffic

Networks are getting more complex what comes to topology, interfaces & features used

Correct Service scoping in sales extremely important for project profitability & success

Need to start preparing for the great possibilities ahead!


Fewer Nodes

Simpler network architecture

Higher data bitrates over air

Higher data bitrates over TN

Reduced OPEX/CAPEX

LTE offers a smooth evolutionary path from other cellular systems


Delivering of IP Multimedia Services (IMS) leads to Introducing common service platform based on IMS

HSS together with some other nodes will replace HLR

SGSN/MME connected via well defined interface (S6) to the HSS

IMS services available for GSM/WCDMA/LTE

IMS services belongs to the service layer


EPS Evolved Packet System

EPC Evolved Packet Core

MME Mobility management Entity

SGW Serving Gateway

PDN-GW Packet Data Network Gateway

LTE Long Term Evolution

SAE System Architecture evolution

e-UTRAN Evolved UTRAN

