lte sae overview workshop final

Slide titleIn CAPITALS

50 pt

Slide subtitle 32 pt

SAE Overview Workshop

Top right corner for field-mark, customer or partner logotypes. See Best practice for example.

Slide title 40 pt


Text 24 pt

Bullets level 2-520 pt

© Ericsson AB 2009 SAE Overview 2009-03-052

General Agenda

Part 1. Presenter: Eduardo Alonso (80’)

– Introduction– Architecture– Product Realisation

PART 2. Presenter: Johan Ljungqvist (15’)

– Services

PART 3. Presenters: Eduardo Alonso/Johan Ljungqvist (10’)

– Additional information


50 pt


PART 1: SAE architecture

SAE/EPC introduction CentraMarch 2009

[email protected] architect for PDN GSDC Madrid


Slide title 40 pt


Text 24 pt



Agenda

Introduction Architecture

– Basic EPS Architecture– LTE– EPC– Interfaces towards 3GPP access– Non-3GPP access networks– Interfaces towards non-3GPP access– HSS– PCRF– Voice Call Continuity– Mobility and session management in SAE

Product Realisation– Ericsson Products


Slide title 40 pt


Text 24 pt



Core Network

What is SAE/LTE

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

EPCeUTRAN

User mgmt

added


Slide title 40 pt


Text 24 pt



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

3GPP terms vs industrial terms


Slide title 40 pt


Text 24 pt



Why SAE/LTE? Broadband growth

Source: OVUM, Strategy Analytics & Internal Ericsson

0

300

600

900

1200

1500

1800

2100

2005 2006 2007 2008 2009 2010 2012

Su

bs

cri

pti

on

s (

Mil

lio

ns

) Mobile Broadband

Fixed Broadband

2011

Mobile broadband growth: Broadband becomes personal


Slide title 40 pt


Text 24 pt



Source: Ericsson

Need an “all IP” system with more efficiency, more capacity and higher speeds

Why SAE/LTE? Strong growth in data trafficWCDMA & HSPA world average

Packet data

Voice

Jan07

Feb07

Mar07

Apr07

May07

June07

July07

Aug07

Sep07

Oct07

Nov07

Dec07

Relative Network Load

2

4

3

1

5


Slide title 40 pt


Text 24 pt



Why SAE/LTE?Competing technologies threat

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.


Slide title 40 pt


Text 24 pt



SAE/LTE – Performance Targets 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 !


Slide title 40 pt


Text 24 pt



Enriched services

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

PC/Laptop symbol

Video ConferencingM-commerce

Music

Gaming

Doctor/mechanic

TV watching

Messaging


Slide title 40 pt


Text 24 pt



Agenda





Slide title 40 pt


Text 24 pt



Internet, Operator Service etc.

EPC EPC - Evolved Packet Core

eUTRAN eUTRAN - Evolved UTRAN

EPS – Evolved Packet System

EPS (SAE/LTE) Architecture


Slide title 40 pt


Text 24 pt



Packet core evolutionAdaptation for increasing capacity needs

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/eHSPAGSM

SGSN

Charging

GGSN


Slide title 40 pt


Text 24 pt



Packet core evolutionImprove quality and reduce costs – Just started

Fair mobile broadband usage

Bandwidth management

Policy implementation

Deep packet inspection

End-to-end Quality of Servicecontrol

Service-aware charging

PCRF

IP networks

HLR

GSM

ChargingSASN

GGSN

Note: SASN could be standalone or integrated in GGSN

SGSN

WCDMA/eHSPA


Slide title 40 pt


Text 24 pt



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

Packet core evolutionEvolved Packet Core – Next step

Note: SASN could be standalone or integrated in PGW

SAPC

IP networks

GSM

ChargingSASN

MME

WCDMA/eHSPA

SGSN

PGW

UM


Slide title 40 pt


Text 24 pt



Agenda





Slide title 40 pt


Text 24 pt



What is LTE?

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


Slide title 40 pt


Text 24 pt



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

time

frequency

time

frequency

User 1User 2User 3

Transmission Schemes


Slide title 40 pt


Text 24 pt



Key LTE radio access features

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 MHz1.4 MHz

TX TX


Slide title 40 pt


Text 24 pt



Peak Data RatesLTE Standard Capabilities

LTE 4x4,20+20 MHz

0

50

100

150

200

250

300

350

Pea

k D

ata

Rat

es [

Mbp

s]

Downlink

Uplink

LTE 2x2,5+5 MHz

LTE 2x2,20+20 MHz


Slide title 40 pt


Text 24 pt



Agenda





Slide title 40 pt


Text 24 pt



EPS High Level ArchitectureOptimized for performance and cost efficiency

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 accessMME

SAE GW

eNodeBS

-G

W P-

GW


Slide title 40 pt


Text 24 pt



EPC architecture 3GPP operatorDetailed view, non-roaming case, 3GPP accesses

• 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

MMESGSN

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


Slide title 40 pt


Text 24 pt



SAE Roaming supportExtending today’s successful model

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

Otheraccesses

S8

PDN GW

SAE GW

Home PLMN

Visited PLMN

Note: HSS and AAA excluded for simplicity

LTE

Serv GW

SAE GW

hPCRF

S7PDN GW

Serv GW

SAE GW vPCRF

S9

SGi

IP networks

SGi

IP networks

PDN GW

SAE GWS7

2G/3GOtheraccesses

• 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


Slide title 40 pt


Text 24 pt



Roaming ScenariosHome Routed Traffic

HSS

HLR

MMESGSN

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

S8HPLMN

VPLMN


Slide title 40 pt


Text 24 pt



Roaming ScenariosLocal Breakout

HSS

HLR

MMESGSN

V-PCRF

2G 3G

Gb Iu-C

S3

S4

S1-C S1-U

S12

S11

S10

SGi

Gx

IP networks

S6aGr

LTE

PDN GW

Serv GW

S5

HPLMN

VPLMN

H-PCRF

S9


Slide title 40 pt


Text 24 pt



S7SGi

Rx+

SIP

IMS domain S-CSCFI-CSCF

IP networksP-CSCF

PCRF

SAE GW

SAE impact on IMS

The Packet core evolution is transparent to IMS services.


Slide title 40 pt


Text 24 pt



Agenda





Slide title 40 pt


Text 24 pt



MME/GW

S1S1 S1

X2 X2

eNode BeNode B eNode B

EvolvedPacketCore

EvolvedUTRAN

eUTRAN (LTE) interfacesLogical view


Slide title 40 pt


Text 24 pt



eNodeB Interfaces 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

S1S1 S1

X2 X2



Slide title 40 pt


Text 24 pt



eNodeB Interfaces 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

S1S1 S1

X2 X2



Slide title 40 pt


Text 24 pt



The EPC (SAE) Interfaces

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

MMESGSN

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


Slide title 40 pt


Text 24 pt




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

MMESGSN

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


Slide title 40 pt


Text 24 pt




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

MMESGSN

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


Slide title 40 pt


Text 24 pt




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

MMESGSN

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


Slide title 40 pt


Text 24 pt




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

MMESGSN

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


Slide title 40 pt


Text 24 pt




S10 Interface

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

• Protocol: GTP-C

HSS

HLR

MMESGSN

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


Slide title 40 pt


Text 24 pt




S11 Interface

• Reference point between MME and Serving GW.

• Protocol: GTP-C

HSS

HLR

MMESGSN

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


Slide title 40 pt


Text 24 pt




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

MMESGSN

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


Slide title 40 pt


Text 24 pt




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

MMESGSN

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


Slide title 40 pt


Text 24 pt



Agenda


– Basic EPS Architecture– LTE– EPC– 3GPP Interfaces– Non-3GPP access networks– Non-3GPP interfaces– PCRF– Voice Call Continuity– HSS– Mobility and session management in SAE

Product Realisation– Ericsson Products and Roadmap

Summary


Slide title 40 pt


Text 24 pt



SAE architecture with non 3GPP networks


Slide title 40 pt


Text 24 pt



SAE architecture with non-3GPPaccess networks

• 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

ePDGPDN GW

SAE GW

Serv GW

S5”Legacy” 3GPPaccess networks

”Legacy” 3GPP2access networks

LTE


Slide title 40 pt


Text 24 pt



Agenda





Slide title 40 pt


Text 24 pt



Non-3GPP interfaces to HSS

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 interfaceSTa / SWa = legacy AAA interface to 3GPP AAASWm = AAA to ePDG


Slide title 40 pt


Text 24 pt



Non-3GPP access GW interfaces

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


Slide title 40 pt


Text 24 pt



Fully Converged Deployment


Slide title 40 pt


Text 24 pt



Agenda





Slide title 40 pt


Text 24 pt



HSS in SAE/EPC & IMS network

HSS

HLR

AAA

ePDG

PDN GW

Serv GWMMESGSN

PCRF

LTE2G 3G Non-3GPPNon-trusted

Non-3GPPTrustedEg cdma

SWx

Gb Iu-C

S3

S4

S1-C S1-U

S12

S10

S11

S5/S8

SGi

S6b

Gx

GxcGxb

Gxa

STa

S2b

S2a

S2c

SWaSWn

SWm

IP networks

S9

S6a

Gr

S101/102

S103


Slide title 40 pt


Text 24 pt



HSS – 3GPP Procedures 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 interfaceSTa / SWa = legacy AAA interface to 3GPP AAASWm = AAA to ePDG


Slide title 40 pt


Text 24 pt



IPnetworks

• 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

HSSHSS HLR/AuCHLR/AuC

EMAEMA

HSS-SHSS-S HLR-SHLR-S

CUDBCUDBEMAEMA

I-HSSI-HSS

CUDBCUDBEMAEMA

IPnetworks

IMS

FixedBroadband

IMSIMS

PacketCable

LTE

IPnetworks

User Management EvolutionSmooth evolution towards all-IP and UDC

Smooth and step-wise evolution with business needs

CDMA2000

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

FixedBroadband

CDMA2000

2G/2.5G/3G

WLAN WLAN


Slide title 40 pt


Text 24 pt



Subscription Profiles

Front-End Server

FE server

Monolithic

Node

OA

M

PROTOCOLS

LOGIC

DB

OA

M

PROTOCOLS

LOGICSignalling &

application logic

DBFE data profiles

Classic Server

PROVISIONINGLOGIC

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

Evolution with new architectureCUDB

Separation of subscription and traffic scalability for improved OPEX & CAPEX

SW Upgrade

Data migration


Slide title 40 pt


Text 24 pt



Agenda





Slide title 40 pt


Text 24 pt



PCRF

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.


Slide title 40 pt


Text 24 pt



PCRF enhancements in SAES9 interface for roamers


Slide title 40 pt


Text 24 pt



PCRF enhancements SAENew reference points: Gxa, Gxc


Slide title 40 pt


Text 24 pt



Agenda





Slide title 40 pt


Text 24 pt



Voice Call Continuity

1. VoIP based on MMTel over LTE

2. CS Fallback in EPS


Slide title 40 pt


Text 24 pt



1. VoIP based on MMTEL over LTE 3GPP TS 23.237 Multimedia Subsystem (IMS) Service Continuity

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.


Slide title 40 pt


Text 24 pt



2. CS fallback in EPS architecture

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.


Slide title 40 pt


Text 24 pt



Agenda





Slide title 40 pt


Text 24 pt



EPS Mobility Management States

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


Slide title 40 pt


Text 24 pt



EPS Connection Management States

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)


Slide title 40 pt


Text 24 pt



LTE states: another approach, UE perspective


Slide title 40 pt


Text 24 pt



Mobility management Initial UE connect

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.


Slide title 40 pt


Text 24 pt



Mobility managementPDN-GW selection - user data based

MME

UE

1. APNrequest.

4. Inform UE on PDN-GW.

5. Establish user plane connection (bearer)

eNodeB

Associated MME/ S-GWsHSS

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


Slide title 40 pt


Text 24 pt



Session managementS-GW selection – location based

MME

S-GW

S-GW

UE

SA1

1. APNrequest.

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

3. Establish user plane connection (bearer)

eNodeB

UE

SA2S-GWeNodeB

Configured MME/S-GWs

Connects UE to “best” S-GW based on residing Service Area (SA)


Slide title 40 pt


Text 24 pt



Mobility Management Intra-LTE Handovers

MME

MME

S-GW

eNBSA SA

MME

eNB

eNB

S-GW

eNBeNB

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


Slide title 40 pt


Text 24 pt



Unchanged or relocated

Mobility Management Intra-LTE Handover (X2)

S1-MMES1-U

S5/S8

S6a

S-GW

eNBeNB

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

S11S11

Data forwarding

PDN-GW


Slide title 40 pt


Text 24 pt



Unchanged or relocated

Mobility Management Intra-LTE Packet Handover (S1)

S1-MME

S1-U

S5/S8

S6a

S-GW

eNBeNB

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)

S11S11

MME MMES10

Packet forwarding

PDN-GW


Slide title 40 pt


Text 24 pt



LTE-2G/3G mobilityCase #1: Independent networks

Gb/Iu S1-MME S1-U

S11

SGi

S6aGr

GGSN

LTEGSM/WCDMA

HLR

PacketGW

SGSN MME

HSSGi

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


Slide title 40 pt


Text 24 pt



HLR

Gb/Iu

Gn(S3)

Gn(S4)

S1-MME S1-U

S11

SGi

S6aGr

PacketGW

GGSN

SGSN MME

LTEGSM/WCDMA

HSSGi

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

LTE-2G/3G mobilityCase #2: Packet mobility, no RAN support


Slide title 40 pt


Text 24 pt



HLR

Gb/Iu S1-MME S1-U

S11

SGi

S6aGr

PacketGW

SGSN MME

LTEGSM/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 informationb) 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)

LTE-2G/3G mobilityCase #3: Packet mobility, RAN support

HLR/HSS integration


Slide title 40 pt


Text 24 pt



LTE-2G/3G mobilityCase #4: Packet HO

HLR

Gb/Iu S1-MME S1-U

S11

SGi

S6aGr

PacketGW

SGSN MME

LTEGSM/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

GnS4

GnS3

HLR/HSS integration


Slide title 40 pt


Text 24 pt



SummaryLegacy network impact

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


Slide title 40 pt


Text 24 pt



Ericsson RecommendationGeneric

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


Slide title 40 pt


Text 24 pt



Agenda





Slide title 40 pt


Text 24 pt



Ericsson products and Roadmap

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


Slide title 40 pt


Text 24 pt



SGSN-MME 2009B Key values

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


Slide title 40 pt


Text 24 pt



MME MkVIIBxxv4

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


Slide title 40 pt


Text 24 pt



Mobile Gateway & Converged Gateway

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.


Slide title 40 pt


Text 24 pt



Mobile Packet Gateway (MPG)

For 3GPP/LTE network access

An evolution from the market-leading Ericsson GGSN

Ericsson Packet Gateways

Converged Packed Gateway (CPG)

For broadband LTE networksand non-3GPP convergence

A new product based on a proven platform (SmartEdge)


Slide title 40 pt


Text 24 pt



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

Converged Packet GW


Slide title 40 pt


Text 24 pt



Mobile Packet GatewayKey features

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)


Slide title 40 pt


Text 24 pt



Ericsson value propositions

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 onMobile and Converged Gw

– Both Gateways will evolve to address future needs


Slide title 40 pt


Text 24 pt



HSS

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.


Slide title 40 pt


Text 24 pt



HSS 5.0 Modules and Interfaces

-5Zx

XCAP Authentication Support,

MME

System Performance managementFault managementConfiguration managementSystem SW management

Sh

HSS Provisioning

ProvisioningSystem

Server

AS

SIP Application Server

HLR

MAP

XCAP Server

SIH

SAE

S6aESM

SAE Subscription module

Cx

SSO

retrieval from the HLR at any time

Authentication vectors retrieval

OSS-RC

MAP

SDASubscription Data Access module

Subscription DataAccess

PAM

Packet Access module

GGSN/AAA

SWa, S6b, STa, SWm, Wa

WSMWLAN Subscription

module

SWx

PDN GW

TSP 6 /NSP 6.0 platform

D’/Gi

CUDBLDAP SLF

3GPP AAASWx

LDAPSOAP

Provisioning notifications

ePDG

AAA

Access Gateway

XCAPAggregationProxy

AVG Authentication Vector

Generator module

ISMIMS Subscription

module

CSCF


Slide title 40 pt


Text 24 pt



LTE RAN L10 A

Ericsson solution based on:

– RBS 6000 platform First mainstream products in 2009/2010


50 pt


Part 2: SAE services


[email protected] Manager Packet Core BUGS PA CSI


Slide title 40 pt


Text 24 pt



Content

SAE Business & Service overview SAE challenges & opportunities SAE service sales support Summary & conclusion


Slide title 40 pt


Text 24 pt



SAE/LTE market activities

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


Slide title 40 pt


Text 24 pt



SAE solution viewContent and interdependencies

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


Slide title 40 pt


Text 24 pt



Ericsson Core & IMS Portfolio

Mobile Packet Core & SAE

Softswitching& IMS

At the heart of Full Service Broadband

Subscriber Mgmt

Redback

LTE


Slide title 40 pt


Text 24 pt



Ericsson SAE and LTE Services A complete service offering

<Operator> introduction of SAE & LTE

BusinessStrategy

TechnologyStrategy

Procure-ment

Implement-ation

OperationTechnology

Design

Trial

Program/Project/Change Management

SolutionSelection

Multi-vendorVerification

Learning Services

Customer Support

Security Consulting

SolutionAnalysis

Network Design

Trial System

Project Management

SupportServices

NetworkRoll-OutLTE

Network PerformanceOptimization

SolutionIntegrationSAE & TMS

BusinessStrategy & Planning

NetworkStrategyConsulting

TechnologyConsulting

OperationalConsulting


Slide title 40 pt


Text 24 pt



Conclusions Customer specific solution scoping!

– Various implementation scenarios– Multi-vendor solution space– Solution and project scoping according to Project Sales process a MUST!

Competitive price!– Secure competetive price through barebone scoping– Feature implementation through add-on sales– Re-use of legacy infrastructure needed

LTE & SAE means an all IP network– Who delivers IP backbone?– Understand network requirements– Who does network design/review?

Secure end-to-end QoS– complete solution space need to be considered in order to secure a "end-to-end QoS

delivery of LTE Broadband connectivity"– complete solution space need to be considered in order to secure "timely & high

quality rollout"

Project sales approach a must!


Slide title 40 pt


Text 24 pt



Content



Slide title 40 pt


Text 24 pt



SAE challenges

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)


Slide title 40 pt


Text 24 pt



SAE opportunities

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


Slide title 40 pt


Text 24 pt



Content



Slide title 40 pt


Text 24 pt



BUGS scoping Support

Product Sales – High Volumes & standardized

Project Sales – Low Volumes & customized

NetworkDesign

Site Engineering

Installation ProductConfiguration Integration

Common Scope

Common Scope

Common Scope

Common Scope

Common Scope

Customer Project

WP

WP

WP

WP WP WP WP WP

WP

WP

WP

WP

WP

WP

WP

WP

WP

WP

WP

WP

WP

WP

WP

WP

WP

• WBS• SoW - WP• SICOP

• SD• SoW-SP• Normhour

NRO

Supporting doc.

Supporting doc.

SI


Slide title 40 pt


Text 24 pt



Understand what to deliver to make a good tender!

BUGS Scoping supportCSI Services Core needed something in between [NRO & SI] +

– Pre-scoped Sales objects so that the MU’s don’t have to start from the beginning each time.

– Major customer specific project adaptations needed at the MU– Examples and guidance how to scope an e2e view.

Core – Project Sales – Moderate Volumes

Customer Project

WP

WP WP WP WP

WP

WP WP

WP

WP

WP

WP

WP

WP

WP

WPWP

WP

WP

WP

WP

Service Package• Activity Overview• WBS• SoW – WP• Project Guideline• SICOP

WP

WP

WP

WP

Activity list – Specific Scenario

Supporting doc.


Slide title 40 pt


Text 24 pt



What is a Service Package ?

A Service Package

Provides an extensive service sales guidance regarding how to handle scope, cost and risks related to introduction of new technology and/or features

The Service Packages will both secure margins (by not underscoping=>underpricing) and will also most likely generate more sales (by not overscoping=>overpricing)

Is a predefined set of activities from the service portfolio ie from service areas NRO, CSI, Customer Support and Learning Services

Is found in the Ericsson Product Catalog


Slide title 40 pt


Text 24 pt



SAE service sales support

Service Package for SAE introduction available– Service Package description including activity overview & WBS– Scope of Work– Risk Inventory– Responsibility matrix– Cost (&price) guideline (found in ECP under ”NDI price guides”)– Project guideline including project template

Need to secure adequate Service scoping with regards to– Level of detail => make sure our understanding of an acticity is the same

as the customers– Requirements on customer => especially important in projects with split

responsibility– Total project scope => if something is left out, we usually end up doing

things FOC SAE introduction Service Package to be published in product catalog LTE & PRAN service packages also on the way


Slide title 40 pt


Text 24 pt



Content



Slide title 40 pt


Text 24 pt



Summary & conclusion

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!


50 pt


Part 3: Additional information


Prepared by Alberto VillaescusaPresenters: Eduardo Alonso and Johan Ljungqvist


Slide title 40 pt


Text 24 pt



GCC activities

GSDC Spain is Global Competence Center for Packet Core and EPC/SAE

SAE introduction Service Package

Activities ongoing/planned:– 3GDT Project Approach and Cost Calculation Guideline– CSI CPG Service Preparation– SAE Network Design Guidelines

GSDC Spain CA Core Network PCN Global Competence Center portal: https://ericoll.internal.ericsson.com/sites/GSDC_Spain_CA_Core_Network_PCN_Global_Competence_Center_portal/default.aspx


Slide title 40 pt


Text 24 pt



SAE resources & competence

Need to secure LTE & SAE Service Sales & Delivery competence

– people with good e2e & business understanding to support project scoping, service cost estimation etc (Solution Architects)

– Need to secure that we have people with well defined competence skills on elements. A project of this complexity/magnitude will always be a team effort

– SAE/EPC => build on existing SGSN/GGSN/Redback competence

– SAE brings great possibilities for skilled & experienced Packet Core personnel. Build on existing skills to handle what is new


Slide title 40 pt


Text 24 pt



SAE competence map (I)

SAE Competence survey Roles:

– Account Manager– Customer Solution Sales– Consultant– Solution Architect– Customer Project Manager– Service Engineer, CSI– Service Engineer, Customer Support– Others


Slide title 40 pt


Text 24 pt



Redback, smartedge routers => Redback training, Job rotation, self-studies (my learning) MME, CPG, HSS node competence => Trials, FOA, seminar, documentation,

– NW design and dimensioning including traffic models – Configuration & Integration– O&M– Troubleshooting

IP (MPBN) => IP certifications, Job rotation, selfstudy, lab excercises– Routing/Switching– Troubleshooting– QoS (at least when voice is included)– MPBN/PRAN reference model for PCN/SAE

LTE/SAE overview (including radio, OSS...) => selfstudy, overview presentation (GCC) SAE service portfolio and guidelines => BUGS documentation increase awareness 3GPP standards for SAE => selfstudy (e.g. 23.203 & 23.401/402) SACC => Job rotation, basic course exist, selfstudy, lab exercises (simulators)

– SAPC, SASN, PISC, Gx, Gy– Design, integration & testing

Integration & testing

EKB as general competence sharing activity Excellent self study material available in product catalogue

SAE competence map ctd.


Slide title 40 pt


Text 24 pt



Self study useful links

Evolved Packet Core Technical overview:http://gask2web.ericsson.se/pub/picov/get?DocNo=262/22109-FGB101256&Lang=EN&Format=*SOURCE*&HighestFree=Y This one has a really nice set of related 3GPP specs recommended for further studies

In the CPG area you find some good documents as well. Business guide is well written & comprehensive, also a good FAQ that eg answers questions on how our two SAE GW offerings compare:http://prodcat.ericsson.se/Default.asp?ArticleId=66F12A8B-ABAB-410C-80E2-2F154DA0AA28&ArticleType=ProductAreaHP&LNav=DocumentList&viewdoclist=1&N=5450

SGSN-MME 2009B info:http://prodcat.ericsson.se/Default.asp?ArticleId=1E0F281C-E966-4423-A9C7-8C829BD66C40&ArticleType=ProductHP&LNav=DocumentList&viewdoclist=1&N=3985

SAE/EPC link collection:https://knowledgebase.internal.ericsson.com/GSN%20SW%20Deployment%20and%20Support/SAE/Lists/Forum/Threaded.aspx?RootFolder=%2fGSN%20SW%20Deployment%20and%20Support%2fSAE%2fLists%2fForum%2fSAEEPC%20link%20collection&FolderCTID=0x01200200273260155D3337418CE0F93F438B812D&TopicsView=https%3A%2F%2Fknowledgebase%2Einternal%2Eericsson%2Ecom%2FGSN%2520SW%2520Deployment%2520and%2520Support%2FSAE%2Fdefault%2Easpx


Slide title 40 pt


Text 24 pt



SAE knowledge Base site SAE KB Subcommunity


Slide title 40 pt


Text 24 pt



lte sae overview workshop final

Documents