Mobile Broadband Evolution - cisco.com 2G/2.5G/3G Mobile ... CATT, ZTE, Texas Instruments, Orange, IP Wireless, Marvell, Intel, T-Mobile, ... No RNC. node – RNC function integrated

© 2006 Cisco Systems, Inc. All rights reserved. Cisco ConfidentialDecember_2008 1

Mobile Broadband EvolutionAsia Technology Forum December 4-5, 2008

Vojislav VuceticSP Marketing, Industry and Technology Marketing Group

© 2006 Cisco Systems, Inc. All rights reserved. Cisco ConfidentialNovember_2008 2

Agenda

Introduction

2G/2.5G/3G Mobile Wireless – Network Architectures

3G/4G Radio Access Directions

3GPP LTE and EPS Network – Overview

3GPP/3GPP2 Standards Update

Technical Comparison of LTE and WiMaX

Femtocell - Overview

Wireless/Wireline Convergence in the EPC

WiMaX Update


Introduction


TDM Infrastructure

IP Insertion(Core, Edge, RAN)

IP E2E InfrastructureOpen handset

Mobile access evolution and IP infrastructure impact

Bus

ines

s pe

rfor

man

ce (p

rodu

ctiv

ity, e

ffici

ency

, rev

enue

)Mobile market in disruption…

Today(Voice and Data)

Emerging(Data Centric)

Legacy(Voice Centric)

TDMA Radio2G Data

UMTS/EVDO3G Data

OFDM voice and data

1990’s 2000’s 2010’s

http://images.google.com/imgres?imgurl=http://www.geekalerts.com/u/brick-mobile.jpg&imgrefurl=http://www.geekalerts.com/80s-brick-style-mobile-phone-in-mini-version/&h=368&w=470&sz=15&hl=en&start=23&tbnid=ZGLyre-e5lGeAM:&tbnh=101&tbnw=129&prev=/images%3Fq%3Dold%2Bmobile%2Bphone%26start%3D21%26ndsp%3D21%26hl%3Den%26rls%3DIRFA,IRFA:2006-34,IRFA:en%26sa%3DN

http://images.google.com/imgres?imgurl=http://www.google-phone.com/wp-content/uploads/2007/08/google-gphone-interface-search-earth.jpg&imgrefurl=http://www.google-phone.com/tags/att&h=397&w=478&sz=150&hl=en&start=43&tbnid=iD_HTyjXw5ulPM:&tbnh=107&tbnw=129&prev=/images%3Fq%3D4G%2Bphone%26start%3D42%26gbv%3D2%26ndsp%3D21%26svnum%3D10%26hl%3Den%26sa%3DN


BroadbandHigh Speed Radio Access

Billing PlansAggressive Flat Rate All-You-

Can-Eat Billing Plans

HandsetsPowerful New Deviceswith Compelling UIs

ApplicationsLots of Compelling AppsAre Moving over from the

Wired World

The Drivers: A Mobile Internet “Perfect Storm”

100 Fold Increase in Data Traffic by 2013/14

100 Fold Increase in Data Traffic by 2013/14


How Big … How Fast

Worldwide Mobile Data Traffic (in PBytes per Month)

2008 2009 2010 2011 2012North America 5.0 11.9 38.9 97.9 225.0Asia-Pacific 10.3 28.0 74.2 155.4 313.4Eastern Europe 0.1 0.3 0.8 1.9 5.6Western Europe 4.2 20.5 50.6 132.0 292.0South America & Caribbean 0.1 0.9 2.9 8.0 20.8Middle East & Africa 0.2 1.6 7.2 23.7 55.0Total (PB/Month) 19.9 63.3 174.6 419.0 911.8

Source: In-Stat, 8/08

160% CAGR over next 4 years


Mobile Internet gateways that can Mobile Internet gateways that can scalescaleto 50 Gbps and moreto 50 Gbps and more

Cost effective solutions to Cost effective solutions to scale scale the RAN & the RAN & improve indoor coverageimprove indoor coverage

AllAll--IP system architectures that can IP system architectures that can simplify simplify networks & lower the cost per bit networks & lower the cost per bit

Scaling the Mobile InternetThe Mobile Internet Must Deliver Orders of Magnitude More

Traffic for an Orders of Magnitude Lower Cost Per Bit

Ethernet backhaul solutions that can Ethernet backhaul solutions that can scalescaleto the 100s of Gbps to the 100s of Gbps


2G/2.5G/3G Mobile Wireless Network Architectures


GSM Wireless Voice Network (Circuit Switched)

PSTN

MSC/VLR

BTS

GMSC

BTS

BTS

BTS

HLR

BSC

BSC

Radio AccessNetwork

(RAN)

CN to provide CS Voice


GSM/UMTS Wireless Network (CS and PS)

3GRouter

IP PDN

PSTN

CS VoiceNetwork

PS DataNetwork

SGSN GGSN

MSC/VLR

Node B

GMSC

Node B

Node B

Node B

HLR

RNC

RNC

Radio AccessNetwork

(RAN)


UMTS (Universal Mobile Telecommunications System)

UTRA (UMTS Terrestrial Radio Access)The most common form of UMTS (3G) uses W-CDMA as the underlying air interface

http://en.wikipedia.org/wiki/W-CDMA


Wireless WAN in the CDMA Environment

PDSN HA

BSC/PCF

MSC/VLRBTS

BTS

BTS

BTS

3GRouter

IP PDN

PSTN

VoicePart

DataPart

GMSCHLR

BSC/PCF


3G/4G Radio Access Directions


Evolution of TDMA, CDMA, and OFDM Systems


WiMaX vs. HSPA, WiMaX 2.0 vs. LTE? (source: WiMaX Forum)


Throughput Performance of Different Wireless Technologies (Blue Indicates Theoretical Peak Rates)

Technology D/L Theoretical

D/L Actual

U/L Theoretical

U/L Actual

UMTS WCDMA Rel’99 2.048Mbps 768UMTS WCDMA Rel’99 (practical terminal)

384Kbps 350Kbps 384Kbps 350Kbps

HSDPA Initial Devices (2006) 1.8Mbps > 1Mbps 384Kbps 350KbpsHSDPA Current Devices 3.6Mbps > 2Mbps 384Kbps 350KbpsHSDPA Emerging Devices 7.2Mbps > 3Mbps 384Kbps 350 KbpsHSDPA 14.4Mbps 384KbpsHSPA Initial Implementation 7.2Mbps >4Mbps 1.46Mbps 1MbpsHSPA Future Implementation 7.2Mbps 5.76MbpsHSPA 14.4Mbps 5.76MbpsHSPA+ (2x2 MIMO, DL 16 QAM, UL 16 QAM)

28 Mbps 11.5Mbps

HSPA+ (2x2 MIMO, DL 64 QAM, UL 16 QAM)

42Mbps 11.5Mbps

LTE (2x2 MIMO) 173Mbps 58MbpsLTE (4x4 MIMO) 326Mbps 86MBPS


Latency of Different Technologies


3GPP LTE and EPS Network – Overview


Traffic increase requires low cost/bit technologies

Source: Light Reading

Voice dominated

Data dominated

Traffic volume

Revenue

Time

Network cost (LTE)

Price per MByte has to be reduced to remain profitable

Network cost (existing technologies)

Profitability


LTE and EPS

A new radio (Long Term Evolution) and core (System Architecture Evolution-SAE) all-IP network ensuring 3GPP systems remains competitive [against WiMaX and 3GPP2 UMB(*)] over the next decadeLong Term Evolution is a Revolution in the air interface from WCDMA to OFDMA/MIMOEvolved Packet System is the new core network supporting the new LTE radio, plus legacy, plus non-3GPP networks (EVDO, WiMaX, WiFi)NOTE: 3GPP2 UMB will probably never be deployed (Development stopped by QCOM in November, 2008)


What is LTE as defined in 3GPP Release 8LTE is NOT 4G (yet)

4G will be a set of requirements defined by ITU-R for IMT Advanced systems – 1Gbps to low mobility, 100 Mbps to highly mobile users (IMT-Advanced is work in progress)

4x4 LTE estimated to provide 300 Mbps

4x4 LTE


3GPP Release 8 Evolution Objectives

Radio Side (LTE – Long Term Evolution)– Improvements in spectral efficiency, user throughput, latency

– Simplification of the radio network

– Efficient support of packet based services: MBMS, IMS, etc.

Network Side (SAE – System Architecture Evolution)

– Improvement in latency, capacity, throughput, idle to active transitions

– Simplification of the core network

– Optimization for IP traffic and services

– Simplified support and handover to non-3GPP access technologies


3GPP Standardization Activities

One of the biggest standardizations efforts so far

More than 20,000 contributions submitted to 3GPP Release 8 in 2007

Companies that had significant contributions to 3GPP Release 8

Ericsson, Nokia, Samsung, Motorola, Qualcomm, NTT DoCoMo, NSN, ALU, Nortel, LG Electronics, Huawei, NEC, Siemens, Panasonic, Vodafone, CATT, ZTE, Texas Instruments, Orange, IP Wireless, Marvell, Intel, T-Mobile, China Mobile, KDDI, Telecom Italia, AT&T, Starent, Cisco, Verizon Wireless, Nextwave, Philips, Sharp, Fujitsu, …


3GPP LTE Background3GPP work on the Evolution of the 3G Mobile System started with the RAN Evolution Work Shop in late 2004, with the objective

"to develop a framework for the evolution of the 3GPP radio-access technology towards a high-data- rate, low-latency and packet-optimized radio-access technology"

The Next Generation Mobile Networks (NGNM) initiative, led by seven network operators*, provided additional objectives and recommendations for the initiative.3GPP TR 25.913 captures the resulting detailed requirements, e.g.

100 Mb/s downlink and 50 Mb/s uplink peak data rates, Low control plane latency (<50 ms from idle to active)Low user plane latency (<5 ms for small IP packet)

A feasibility study and resulting framework for the Evolved UTRA and Evolved UTRAN Long Term Evolution (LTE) was conducted in TR 25.912The resulting E-UTRA and E-UTRAN is specified in the 3GPP 36.xxx series, e.g.:

TS 36.401: Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Architecture description (Release 8)TS 36.300: Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)

*NGMN members: China Mobile Communications Corporation, KPN Mobile NV, NTT DoCoMo Inc., Orange SA, Sprint Nextel Corporation, T-Mobile International AG & Co KG and, Vodafone Group PLC.


3GPP SAE3GPP SA WG2 started its own Study for the System Architecture Evolution (SAE) in December 2004, with the objective

"to develop a framework for an evolution or migration of the 3GPP system to a higher-data-rate, lower-latency, packet-optimized system, that supports multiple Radio Access Technologies (RATs).”

It was initiated when it became clear that the future was IP with everything (the "all-IP" network, AIPN – see TS 22.978), and that access to the 3GPP network would ultimately be not only via UTRAN or GERAN but by WiFi, WiMAX, or even wired technologiesThe main objectives of the SAE work are to address the following:

Impact on overall architecture resulting from RAN's LTE workImpact on overall architecture resulting from SA1's “all-IP” (AIPN) work

For example support for a variety of access networks and end-to-end Quality of Service (QoS)

Overall architectural aspects resulting from the need to support mobility between heterogeneous access networks


High-Level LTE and EPS Architecture


LTE (Long Term Evolution) Architecture

Flattened network architecture with fewer nodes (only base stations and gateways) – known as Evolved Packet System - EPS

No RNC node – RNC function integrated in to an ‘evolved Node-B’ (BTS), known as e-NodeB

Architecture provides separation of Control and Data Planes

Supports IP Packet Switched traffic only – It is an All IP Network

All services delivered using IP Packet connections, including voice and video (and of course data!)


Functional Migration from 2G/3G to SAE2G/3G LTE

CDMA/GSM/UMTS

Source: IEEE Communications Magazine, Jan/Feb, 2009

HA / GGSN

PDSN / SGSN

BSC / RNC

BTS / NodeB

Control Plane

eNodeB

MME

User Plane

Control Plane

User Plane

Serving/PDN Gateway

HA / GGSN

PDSN / SGSN

BSC / RNC

BTS / NodeB

Control Plane

eNodeB

MME

User Plane

Control Plane

User Plane

Serving/PDN Gateway


Advanced Antenna Techniques used by LTE

LTE is enhanced with MIMO (Multiple Input, Multiple Output), Spatial-Division Multiple Access (SDMA) and Beam Forming


BeamformingIncreases user data rates by focusing the

transmit power in the direction of the user, effectively increasing the signal strength at the UE (mobile)

Beamforming most beneficial for users in weaker signal strength areas, typically the edge of cell coverage



DL MIMO (Down Link Multiple-In Multiple-Out)

Supports up to 4x4 MIMO in the DL, using four transmit antennas at Node-B to transmit orthogonal (parallel) data streams to the four receive antennas at the mobile User Equipment (UE).

Increases user data rates without additional transmit power or bandwidth.




SDMA (Spatial Division Multiple Access)Enables multiple users to send/receive data

using the same time-frequency OFDM resourceEven though transmissions are simultaneous the

spatial separation ensures that the data streams to (and from) the users do not interfere with each other

Increases cell capacity in both the DL and ULLTE does not support simultaneous MIMO

and SDMA operation to a user; hence a trade off between a higher data rates, and a higher system capacity


EPS Nodes and Functions

Evolved Node-B (eNB)This is an evolved Node B (BTS), hosted at a cell site

RNC (Radio Network Controller) function is integrated in to the eNB

RNC integration means fewer hops in the media path, thus lowering the latency



Mobility Management Entity (MME)Signaling-only entity – no IP data packets go through the MME

Main function is to manage the UEs mobility

UE authentication and authorization

Idle mode UE tracking and reachability

Separate signaling element allows operators to grow data traffic and signaling capacity independently



Serving Gateway (S-GW) and PDN Gateway (P-GW)

This two gateways may be implemented as a single network element

S-GW acts as a local mobility anchor for UEs(mobiles) being served

P-GW interfaces with external PDNs

P-GW provides IP functions such as address allocation, packet classification and routing,policy enforcement, and mobility anchoring for non-3GPP networks


LTE/System Architecture Evolution

X2 inter base station interface

SCTP/IP SignallingGTP tunnelling

following handover

S1-c Base Station to MME interfaceMulti-homed to multiple MME poolsSCTP/IP based

S11 MME to SAE GWGTP-c Version 2

S1-u Base Station to SAE GWGTP-u base micro mobility

SAE GW to PDN GWGTP or PMIP based macro mobility

SAE GW

SAE GW


Non-LTE (non-3GPP) radio support

PDN GWSAE GW

MME

ENB

SGSNUTRAN GTPc Context Transfer

GTPu Macro Mobility

3GPP2

PDSN

PMIPv6 or MIPv4 FA Mode

S101 S103

S101: UDP application for pre- registration

Sx-u: forward DL data to minimize loss on handover

PDN GW

SAE GW

HRPD GW


Radio Evolution Driving Backhaul Capacity

Rel-99

WCDMA

Rel-5

HSDPA

Rel-6

HSUPA

Rel-7

MIMO 2x2

Rel-9

OFDMA

DL: 384 kpsUL: 384 kbps

DL: 1.8 – 14.4 MbpsUL: 384 kbps

2007 2008 2009 2010 2011+??

DL: 1.8 – 14.4 MbpsUL: 5.7 Mpbs

DL: 28 MbpsUL: 11 Mpbs

Rel-8

64 QAM



Rel-8

LTE


Technical Alignment Between WiMaX and LTEAspect Mobile WiMaX 3GPP-LTECore Network GRE based micro mobility and PMIP

based macro mobilityGTP based micro mobility and GTP/PMIP based macro mobility

Access Technology OFDMA (DL)

OFDMA (UL)

OFDMA (DL)

SC-FDMA (UL)

FFT Size 128-1024 128-2048

Frequency Bands, GHz

2.3, 2.5, 3.4, 5.8 Existing IMT 2000 bands

(0.7 through to 2.6)

Channel Bandwidths, MHz

5, 7, 8.75, 10 1.25, 2.5, 5, 10, 20

Duplexing Method TDD but FDD in the works Primarily FDD, but also TDD

MIMO Mode Diversity/Spatial Multiplexing/Collaborative SM

Diversity/Spatial Multiplexing/Collaborative SM

Modulation 64 QAM/16QAM/QPSK 64 QAM/16QAM/QPSK

Frame Length 5ms 1ms

Typical MAC overhead

~25% ~15-20%

Vehicular support Up to 120 kmph Up to 250 kmph


3GPP Release 8 - Architecture Overview


Evolved Packet System

The System Architecture Evolution (SAE) defines the Evolved 3GPP Packet Switched domain (aka Evolved Packet System - EPS)

S1 -U

S1 -MME

E -UTRAN

2G/3G SGSN S4

S3MME

S11

S10

3GPP Access

ServingGa teway

SGi

PCRF

Gx

HSS

S2b

SWn

Operator 's IP Services

(e.g. IMS, PSS etc.)

SWm

SWx

UntrustedNon -3GPP IP

Access SWa

HPLMN

Non -3GPP Networks

S6b

Rx+

PDNGateway

ePDG 3GPP AAA Server

Gxb

S2a

Gxa

TrustedNon -3GPP IP

Access STa

S 7c

S5

S6a

UE

SWu

The EPS provides IP connectivity for 3GPP and non-3GPP Access Networks

UTRAN, E-UTRAN, Trusted and Untrusted Non-3GPP Access


Evolved Packet System

Up until Release 8, 3GPP IP mobility was based on GTPHowever, other networks (notably CDMA) had IP mobility based on Mobile IP For Release 8 some vendors and operators preferred to use GTP, others preferred to use Mobile IPConsequently, both options were allowed and specified by 3GPP:

TS 23.401 defines a GTP-based EPS supporting 3GPP IP Access networks onlyTS 23.402 defines a (Proxy) Mobile IP-based EPS supporting 3GPP and non-3GPP IP Access networks

For roaming between GTP-based and Mobile IP-based EPSes, the baseline interworking is GTP


3GPP Access

Non-Roaming EPS Reference Architecture

E-UTRANPDN

GatewayServing GatewayeNodeB

PCRF

Operator’s IP Services

HSS

Gxc(Gx+)

S11(GTP-C)

S1-U(GTP-U)

S2b(PMIPv6,

GRE)

MME

S5 (PMIPv6, GRE)

S6a(DIAMETER)

S1-MME(S1-AP)

GERAN

S4 (GTP-C, GTP-U)UTRAN

SGSN

Trusted Non-3GPP IP Access

Untrusted Non-3GPP IP Access

S3(GTP-C)

S12 (GTP-U)

S10(GTP-C)

S5 (GTP-C, GTP-U)

Gx(Gx+)

Gxb(Gx+)

SWx (DIAMETER)

STa (RADIUS, DIAMETER)

ePDG

3GPPAAA

SWn (TBD)

S2c (DSMIPv6)

S2c

S6b(DIAMETER)

SWm(DIAMETER)

SGi

SWa (TBD)

Gxa(Gx+)

Rx+

S2c

UE

UE

UE

SWu (IKEv2, MOBIKE, IPSec)

S2a(PMIPv6, GREMIPv4 FACoA)

Evolved Packet Core

Non-3GPPIP Access Trusted Untrusted

3GPP IP Access

LTE

2G/3G


3GPP Access

Non-Roaming EPS Reference Architecture

E-UTRANPDN

GatewayServing GatewayeNodeB

PCRF


HSS

Gxc(Gx+)

S11(GTP-C)

S1-U(GTP-U)

S2b(PMIPv6,

GRE)

MME

S5 (PMIPv6, GRE)

S6a(DIAMETER)

S1-MME(S1-AP)

GERAN


SGSN



S3(GTP-C)

S12 (GTP-U)

S10(GTP-C)

S5 (GTP-C, GTP-U)

Gx(Gx+)

Gxb(Gx+)

SWx (DIAMETER)


ePDG

3GPPAAA

SWn (TBD)

S2c (DSMIPv6)

S2c

S6b(DIAMETER)

SWm(DIAMETER)

SGi

SWa (TBD)

Gxa(Gx+)

Rx+

S2c

UE

UE

UE



• Common anchor point for all IP Access Networks (3GPP and non-3GPP)• Assigns/owns IP-address for UE (v4/v6)• Processes all IP packets to/from UE• Can be in home and/or visited network

• Anchor point for 3GPP IP Access Networks only (2G/3G/LTE)• Processes all IP packets to/from UE• Controlled by MME• Uses network-based mobility towards PDNGW (GTP or PMIPv6)• Always in same network as eNodeB

• Handles all signaling traffic (no user plane traffic) • Interacts with HSS for user authentication, profile download, etc.• Interacts with eNodeB and Serving GW to control tunnels, paging, etc.• Interacts with SGSN for 2G/3G

• Performs radio resource management, incl. handovers• Interacts with MME for all signaling plane processing• Exchanges user plane traffic with Serving GW• Wireless or fixed access network

• Close integration with the EPC• Supports mobility, policy and AAA interfaces to the EPC

• EPC point of attachment for untrusted IP access networks (“Internet”) •IPSec to UE for EPC connectivity• Network-based mobility towards PDNGW (PMIPv6)


3GPP Access

Roaming Architecture: 3GPP Access, Home Routed Traffic, GTP-Based

PDN Gateway

Serving Gateway

hPCRF


HSS

S6a(DIAMETER)

Gx(Gx+)

Rx+

Note: Protocol choice analysis in TR 29.803

SGi

VPLMN (GTP)

HPLMN (GTP)

S8a(GTP-C, GTP-U)


3GPP Access

Roaming Architecture: 3GPP Access, Home Routed Traffic, PMIP-Based

PDN Gateway

Serving Gateway

hPCRF


HSS

S6a(DIAMETER)

Gx(Gx+)

Rx+


SGi

vPCRFVPLMN (PMIP)

HPLMN (PMIP)

S9(DIAMETER)

Gxc(Gx+)

S8b(PMIPv6, GRE)


3GPP Access

Roaming Architecture: Non-3GPP Access, Home Routed Traffic, PMIP-Based

PDN Gateway

Serving Gateway

hPCRF


HSS

S2b(PMIPv6,

GRE)

S6a(DIAMETER)



Gx(Gx+)

Gxa(Gx+)

SWx (DIAMETER)

Rx+

SWm(DIAMETER)



3GPPAAA

SGi

SWa(TBD)

vPCRF

3GPPAAA Proxy


ePDG

SWn(TBD)

VPLMN (PMIP)

HPLMN (PMIP)

Gxb(Gx+)

S9(DIAMETER)

SWd (RADIUS, DIAMETER)

Gxc(Gx+)

S8b(PMIPv6, GRE)

SWu

S6b(DIAMETER)


Roaming Architecture: 3GPP Access, Local Breakout, GTP-Based

3GPP Access

PDN Gateway

Serving Gateway

hPCRF


HSS

S6a(DIAMETER)

Rx+


vPCRFVPLMN (GTP)

HPLMN (GTP)

S9(DIAMETER)


Gx(Gx+)

S5SGi

Rx+


Roaming Architecture: 3GPP Access, Local Breakout, PMIP-Based

3GPP Access

PDN Gateway

Serving Gateway

hPCRF


HSS

S6a(DIAMETER)

Rx+


vPCRFVPLMN (PMIP)

HPLMN (GTP or PMIP)

S9(DIAMETER)



Gxc(Gx+)

Gx(Gx+)

S5SGi

Rx+


3GPP Access

Roaming Architecture: Non-3GPP Access, Local Breakout

PDN Gateway

Serving Gateway

hPCRF


HSS

S2b

S6a(DIAMETER)


Gxa(Gx+)

SWx (DIAMETER)

Rx+

SWm(DIAMETER)



3GPPAAA

SWa(TBD)

vPCRF

3GPPAAA Proxy


ePDG

VPLMN (GTP or PMIP)

HPLMN (GTP or PMIP)

Gxb

S9(DIAMETER)



Gxc(Gx+)

Gx(Gx+)

S5SGi

Rx+

SWn(TBD)

SWu


S6b


3GPP Access

Roaming Architecture: All Access, Home Routed and Local Breakout

PDN Gateway

Serving Gateway

hPCRF


HSS

S2b

S6a(DIAMETER)


Gxa(Gx+)

SWx (DIAMETER)

Rx+

SWm(DIAMETER)



3GPPAAA

SGi

SWa(TBD)

vPCRF

3GPPAAA Proxy


ePDG

VPLMN (GTP or PMIP)

HPLMN (GTP or PMIP)

Gxb

S9(DIAMETER)



PDN Gateway

S8a/b

Gx(Gx+)

S5 SGi

Gx(Gx+)

Rx+Gxc

(Gx+)

SWn(TBD)

SWu


S6b(DIAMETER)

S6b


Notes on Roaming and Local Breakout

Home Routed traffic and Local Breakout supported at the same time for a given UE

However, for a given application, only one of them can be used at a given point in time

GTP/PMIP interworking onus for 3GPP Access is on the PMIP-based network

If visited network is PMIP-based, and home network is GTP-based, then the Serving Gateway in the visited (PMIP) network must offer S8a (GTP) interface to the home network.If visited network is GTP-based, and home network is PMIP-based, then the PDN Gateway in the home (PMIP) network must offer S8a (GTP) interface to the visited network.Differences in PCC infrastructure (Gxc interface to Serving Gateway) expected to be handled by PMIP-based network as well

This applies to the existence of the interface as well as any resulting differences in policy flows (S9)


GTP and MIP


High level Comparison between GTP and Mobile IP

GTP (Proxy) Mobile IPKey management and confidentiality

None (done at the access) Optionally, IPSec can be used (e.g. GRX)

IPSec with automated (IKE) or manual key exchange

Inter-Technology handoff No MIP could be deployed as an extra layer

Yes

Context Transfer (policy, QoS, charging, etc)

Yes No (needs new extensions)

QoS management Yes No (needs new extensions)

Access Agnostic No Yes

IETF Compliant No Yes

Air-interface capacity impact

Optimized Depends on MIP model

Client impact No client required Yes with CMIP Can be alleviated with PMIP



Policy and Charging Enforcement Function (PCEF)

E-UTRANServing GatewayeNodeB Operator’s

IP Services

HSS

Gxc(Gx+)

S11(GTP-C)

S1-U(GTP-U)

S2b(PMIPv6,

GRE)

MME

S5 (PMIPv6, GRE)

S6a(DIAMETER)

S1-MME(S1-AP)

GERAN


SGSN



S3(GTP-C)

S12 (GTP-U)

S10(GTP-C)

S5 (GTP-C, GTP-U)

Gx(Gx+)

Gxb(Gx+)

SWx (DIAMETER)


ePDG

3GPPAAA

SWn(TBD)

S6b(DIAMETER)

SWm(DIAMETER)

SGi

SWa(TBD)

Gxa(Gx+)

Rx+

UE

UE

Note: Refer to TS 23.203, 23.401, and 23.402 for further details

PCRF

PDN Gateway

UE



GTP/PMIP in EPSGTP use in EPS split in -C and -U plane

GTP-C for S3, S4, S5, S8, S10, S11 and S101GTP-U for S1-U, X2, S4, S5, S8, S12 (version FFS)

PMIPv6 used in EPS on S2, S5, S8New GTP control plane being specified (TS 29.274). New feature includes:

New QoS mechanism and UE Context (separation of control and user plane entities)New IEs (bearer, function)Idle mode signaling reductionInter 3GPP mobilityEnd marker packet

GTP user plane version still in discussion but it will likely be an enhanced GTPv1 version with backward compatible extensionsEPS PMIPv6 being specified (TS 29.275). Enhancements are required to align PMIP and GTP capabilities as required for EPS, some of them are addressed in the current internet-draft

Path Management (e.g. heartbeat, restoration)Dual Stack capabilities


LTE/EPS Interworking with WiMaX


LTE/EPS Interworking Possible integrated PDN GW and CSN

E-UTRANPDN

Gateway/CSN

Serving GatewayeNodeB

PCRF


HSS

Gxc(Gx+)

S11(GTP-C)

S1-U(GTP-U)

MME

S5 (PMIPv6, GRE)

S6a(DIAMETER)

S1-MME(S1-AP) S10

(GTP-C)

S5 (GTP-C, GTP-U)

Gx(Gx+)

SWx (DIAMETER)

3GPPAAAS6b

(DIAMETER)

SGi

R3-PCC(Gx+)

Rx+

UE

UE

WiMAX

ASNGw

BTS

WiMAX

UE

(RADIUS)R3

(PMIP, GRE)


3GPP/3GPP2 Standards Update


3GPP Structure and Leadership - Current TSG Structure

TSG – Technical Specification Group

TSG GERANGSM EDGE Radio Access Network

TSG RANRadio Access Network

TSG SAService & System Aspects

TSG CTCore Network & Terminals

GERAN WG1Radio Aspects

RAN WG1Radio Layer 1 spec

SA WG1Services

CT WG1MM/CC/SM (lu)

GERAN WG2Protocol Aspects

RAN WG2Radio Layer 2 spec

Radio Layer 3 RR spec

SA WG2Architecture

GERAN WG3Terminal Testing

RAN WG3Lub spec, lur spec, lu spec, UTRAN O&M requirements

SA WG3Security

CT WG3Interworking with external networks

RAN WG4Radio Performance Protocols aspects

SA WG4Codec

CT WG 4MAP/GTP/BCH/SS

RAN WG5Mobile Terminal

SA WG5Telecom Management

CT WG5Smart Card Application Aspects


3GPP/3GPP2 Standards Activities - Summary

3GPP Current Status (as of September 18th, 2008) after SA Plenary Meeting

Stage 1 completed June 2008Stage 2 completed June 2008 (with the exceptions that will be completed by December 2008Stage 3 freezing target December 2008, but will be probably moved to March 2009 (?)OAM/Charging freezing target: Stage 3 freezing + 3 months = March 2009 + 3 months?Testing freezing target: TBDSummary of all Release 8 Features – Target publication remains December 2008

3GPP2 target date for X.P0057 is December 2008


3GPP Release 8 E-UTRAN Standards TimelineLayer 1 specifications are very stableRemaining specs went under change control 12/07, even though many/most were not readyExpect a wave of CRs in 2009 to fix defects

Jul Oct Oct Oct OctJan Jan JanApr Apr AprJul Jul Jul

2006 2007 2008 2009

Stage 2 Change Control

Stage 2 Freeze


Stage 3 Freeze

Stage 2 DevelopmentStage 3 Development

Oct Oct OctJan Jan JanApr Apr AprJul Jul Jul

2007 2008 2009


Stage 2 Freeze


Stage 3 Freeze

Stage 2 Development

Stage 3 Development

3GPP Release 8 EPC Standards TimelineStage 2 work winding down, a few key issues remain open

Stage 3 work just beginning. (3GPP likely to “declare”completion by EOY 08)

Expect a wave of CRs in 2009 to fix defects and to last 12-16 months

Jan

Jan

Stage 3 might end in 03/09


Key EPC Network Elements


Key Attributes of LTE and the EPS LTE supports high bandwidth

– Support for high throughput in the core is important– Example: 1/3 Million users at 120 kbps equals 40 Gbps

LTE does not have a “circuit” or “voice” mode– Cellular networks will eventually move to VoIP– Support for large number of small packets will be important– High availability and reliability will be critical (ESSENTIAL)

Move to “always-on” model– LTE can be fixed-line competitor– With “all-IP” and “always-on”, more users will be active at a given point in time– Expect increased machine-to-machine communication with varying call models– High session count must be supported

Conclusion– Network must support high session count, high throughput, and high packet-per-

second (pps) count– Network must be highly available and reliable


Key Attributes of the EPCThe EPC supports both 3GPP and non-3GPP access networks

– Allows us to build a single unified core network that can support a variety of different access networks, e.g. UTRAN, HRPD, LTE, IEEE 802.11,etc.

– Allows for an evolutionary approach to the EPS

– Access network technologies can evolve without impacting the core

Non-3GPP access networks not limited to wireless networks– EPS supports fixed networks as well

– Enables better support for femto-cell and facilitates fixed-mobile convergence

– We have been working with various customers on a converged wireless and wireline EPS architecture based on a combined EPS (TS 23.402) and ETSI TISPAN model

EPC is service independent– Provides a general IP network infrastructure with support for a variety of applications

• SIP and non-SIP, user and machine, managed and non-managed,

– Subscriber databases, policy, charging, and IP mobility must all be generic

– Security and control of non-managed services must be addressed as well


Key Attributes of the EPCEPC allows for both home routed traffic and local breakout

– Home routed traffic incurs additional overhead, delay and cost, but also allows for home provider specific processing of traffic

– Local breakout is more efficient and allows for “hot potato” routing

EPC provides mobility services for all types of access networks– Allows for roaming and handover between different types of access networks

• Optimized solution being developed for LTE-HRPD handover; WiMAX handover will be done as well (3GPP Release 9)

– Facilitates access network independence and fixed-mobile convergence– Multiple protocol choices for mobility services though

• Network-based (GTP, PMIPv6) and client-based (DSMIPv6, MIPv4)

Conclusion– Network must allow for a variety of access network technologies, both wireless and

fixed– Network must be designed to support fixed-mobile convergence– Network should be application agnostic and allow for varying call models– Network should be prepared to support different mobility protocols


EPC Platforms DirectionsMobile networks & the Internet are converging

Ramp in packet traffic will have implications on infrastructure

EPC platforms address the LTE/EPC requirements by providing:– Several orders of magnitude more bandwidth, packet processing capability

and high session count– A variety of form factors and scalability points to support different deployment

models and scales

– Support for multiple airlink and access technologies (macro all the way to femto, 2G/3G/LTE, non-3GPP and wireline network integration)

– Carrier-class design for high reliability and availability

– DPI capabilities for P2P, billing, advertising, etc.

– Increased scalability while reducing complexity through platform and management integration

IP expertise is a critical success factor going forward


LTE/EPC and CDMA Carrier


E-UTRAN – eHRPD Connectivity and Interworking Architecture – X.P0057


LTE/EPC and Traditional 3G Service Provider


Two Types of LTE/3G Interworking

Pre-Release 8 3G NetworkPDN GW handles handover to/from Pre-Release 8 SGSNs

Release 8 3G NetworkMME and SGW handle handover to/from Release 8 SGSNs


Non-roaming Architecture: LTE/3G (Pre- Release 8) Interworking

SGi

Gn

Gn

S1-MMEPCRF

S7

S6aHSS

S10

UE

GERAN

UTRAN

Pre Rel-8 SGSN

E-UTRAN

MME

S11

S5ServingGW

PDNGW

Rx+

Gr

S1uOperator's IP Services(e.g. IMS, PSS etc.)

OnlineCharging

CGF(offline)

Gy (DCCA)

Gz (GTP’)

Lawful Intercept


Non-roaming Architecture: LTE/3G (Release 8) Interworking

SGi

S4

S3

S1-MMEPCRF

S7

S6aHSS

S10

UE

GERAN

UTRAN

Rel-8 SGSN

E-UTRAN

MME

S11

S5ServingGW

PDNGW

Rx+

Gr

S1uOperator's IP Services(e.g. IMS, PSS etc.)

OnlineCharging

CGF(offline)

Gy (DCCA)

Gz (GTP’)

Lawful Intercept


Options for LTE/3G Inter-working

Upgrade all the SGSNs in the legacy 3G network to Release 8 prior to LTE interworking

Only S-GW deals with handover with legacy SGSNs

– Simplified handover architecture

P-GW need not support legacy Gn/Gp interface


Technical Comparison of LTE and WiMAX


Executive Summary

WiMAX has following benefits over LTEMature standards and large ecosystem of chip, device, network providers. Expect commercial LTE rollout in 2010

WiMAX systems will be cheaper and simpler

WiMAX has following drawbacks over LTELTE interworks with existing 3GPP, 3GPP2 systems very well. Enables gradual roll-out

LTE has higher spectral efficiency compared to WiMxX 1.0

Expect WiMAX 1.5 and 802.16m to catch up

Large pools of FDD spectrum make LTE attractive

Determining factors for WiMAXTDD; Fixed/Portable Usage; Greenfield Operator; Emerging Market

Determining factors for LTEFDD; Mobile Usage; Cellular Operator; Developed Markets


Comparison -- System Level Similarity /Differences Advantages/Disadvantages

W&L are IP based architectures.

W&L are “flat” architectures with most radio functionality at the base site

WiMAX relies heavily on IETF based protocols where appropriate while LTE relies on combination of IETF and legacy 3GPP protocols

WiMAX benefits from reuse of equipment and protocols (deployed in enterprise and carrier IP networks) in cost and expertise savings. Two examples: AAA, and HA

(only) LTE provides separation of control (MME) and bearer (S-GW)

Allows for independent scaling of bearer and control. Allows combining S-GW and PDN-GW.

(only) WiMAX enables creation of distinct Access and Connectivity Provider

Enables business models where different connectivity providers share same radio access network

W&L support IPv4, IPv6

WiMAX supports Ethernet Convergence

Ethernet convergence is useful for many deployments such as Enterprise connectivity

LTE provides extensive support for interworking with 3GPP, 3GPP2 providers

WiMAX will provide loosely coupled interworking with 3GPP2 starting Rel. 1.5

Enables smooth transition from 3GPP2 and 3GPP systems to LTE

W&L: WiMAX & LTE


Comparison -- Security/ Mobility/ QoS

Similarity /Differences Advantages/DisadvantagesW&L provide mutual authentication, and encryption of over-the-air traffic and maintain key hierarchies

LTE Security is based on USIM

WiMAX device security is based on certificates

LTE is consistent with cellular technology

WiMAX is consistent with security mechanisms in Enterprise and Cable industry

W&L support roaming (simple IP) and mobility (continuity of IP address)

W&L provide mobility between BS (within GW), across GWs in radio network.

LTE has network mobility based on GTP and PMIP while WiMAX has based on PMIP

PMIP is IETF based mobility protocol while GTP was defined and used in 3GPP. WiMAX can reuse off-the-shelf AAA, and HA

W&L provide service flows based on traffic flow classification

W&L provide QoS for constant and variable bit rate services

LTE enables client-based setup of service flows

This feature is expected in future WiMAX release


Comparison-Likely Operator Profile

Prefer WiMAX Prefer LTE

Spectrum Availability

TDD spectrum in 2.5, and 3.5 FDD spectrum in multiple frequency bands. (While LTE supports TDD, unlikely to be big focus)

Primary Service Type

Broadband wireless service for residential usage

Broadband wireless service for mobile and portable devices

Legacy or Greenfield operators

Primarily Greenfield operators (Sprint Clearwire being the significant exception)

Legacy 3GPP and 3GPP operators to migrate to LTE based on broadband demands and device availability

TTM Considerations

Current Availability of inter operable devices and equipment favors WiMaX

Earliest large scale commercial deployment in 2010.


LTE Deployments and Interworking


Trials Timeline (Best Guess)

Operators Dates

Verizon, Vodafone, China Mobile Pre-Commercial Trial through mid 2009

Verizon to go commercial early 2010

NTT DoCoMo Ongoing Trials

Commercial early 2010

T-Mobile Demonstration is MWC (1Q, 2008)

No announcements on commercialization

LTSI (LTE-SAE Trial Initiative). Major Operators (Vodafone, China Mobile, FTO, Telefonica, Telcom Italia)

Proof of Concept completed

Interoperability Tests planned through end of 2009

Customer Trials in 2010


End to End System Architecture

Functional Mapping

PDN-GW maps to HA

HSS maps to AAA

(S-GW and MME combined) map to ASN-GW

eNodeB maps to BS

UE maps to SS (subscriber station)

LTE

SS

BS

ASN-GW

HAAAA

R6

R3

R8

R4

WiMAX

S10

UE

eNodeB

S-GWMME

PDN-GW

HSS

S1-MME

S5

S11

X2

S1-u

S6


Interworking with other Wireless Networks

S-GWMME

PDN-GW

LTE E-UTRAGPRS/UMTS

SGSN

cdma200/HRPD

PDSN

WLAN

ePDGS3

S4S2a S2b

WiMaX LTELoosely coupled interworking with cdma200 in Release 1.5

Well defined interfaces (as shown above) for GPRS/UMTS, cdma2000, and WiFI


Interworking with 3GPP2

WiMAX LTECoupling Type

Loosely Coupled system sharing HA, HAAA and Billing

Tightly Coupled system sharing PDN-GW (HA), HAAA and Billing

Mobility Supports handover between cdma2000 and WiMAX using Mobile IP

Supports handover between cdma2000 and LTE using Mobile IP

Access Network Coupling

No coupling at access network layer

Tunnel between MME and RAN for exchanging control messages (pre-registration)

Tunnel between S-GW and PDSN for exchanging data packets.

Physical Layer Coupling

No coupling at physical layer eNB provides information about 3GPP2 BTS’ (frequency, etc).

eNB specifies measurements

eNB determines when to handover to 3GPP2


Mobility


Network Mobility

SS

BS

ASN-GW

HAAAA

R6

WiMaX

MIP

UE

eNodeB

S-GWMME

PDN-GW

HSS

GTP

GTP

GTP

UE

eNodeB

S-GWMME

PDN-GW

HSS

GTP

PMIPv6

PMIPv6

GTPGTP

LTE


Network MobilityWiMaX LTE

GTP (23.401) PMIPv6 (23.402)Method Type Mobile IP v4 (CMIP, PMIP) GPRS Tunneling Protocol (GTP v2) PMIPv6

Main Elements ASN-GW (FA) in the ASN and Home Agent in the CSN

MME, Serving Gateway, and PDN- GW. MME and Serving Gateway in the visited network, PDN-GW in visited or home network.

MME, Serving Gateway (acts as MAG), and PDN-GW (acts as LMA). MME and Serving Gateway in the visited network, PDN-GW in visited or home network

Mobility Scenarios

1) Intra ASN

2) Inter-ASN – ASN anchored

3) Inter-ASN with ASN relocation

1) No MME, S-GW relocation

2) No MME but S-GW relocation

3) MME and S-GW relocation

1) No MME, S-GW relocation

2) No MME but S-GW relocation

3) MME and S-GW relocation

Main Messages

Intra-ASN: Target ASN send Mobile IP re- registration with FA COA (target address)

GTP Messaging (Update Bearer Request) between Target S-GW and PDN-GW switches tunnel from source to target

PMIP Messaging (Proxy Binding Update) between Target S-GW and PDN-GW switches tunnel from source to target

Miscellaneous Better suited to support for legacy UTRAN (UMTS/3G)

Better suited for to handle mobility to HRPD. Verizon is primary driver


Security


Security

WiMaX LTE

Basis for Security

Device Certificate in MS/SS for device authentication

Shared Secret in UE and AuC for device authentication

Main Elements

Certificate in SS

BS and ASN-GW

AAA

USIM in UE

eNodeB and MME

HSS/AuC

Authenticatio n and Key Derivation

EAP (TLS, TTLS) between SS and AAA with ASN-GW as NAS

R6 Messages for key transfer between ASN-GW and BS

AKA (Authentication and Key Agreement) between UE and MME

DIAMETER Messaging between MME and HLR

S1 messages for key transfer between MME and BS

Miscellaneous Separate keys for Encryption and Signaling

Encryption (AES, 3DES)

Integrity (HMAC, CMAC)

Creation of temporary identity for user id confidentiality

Separate keys for Bearer and Signaling

Separate keys for Encryption and Message Integrity

EIA1 for Integrity and EIA2 for Encryption (SNOW 3G and AES)


Femtocell - Overview


Mobile Operator ChallengesImproving in-home Coverage

– Significant percentage of mobile traffic originated in the home

– Poor coverage leads to unhappy customers – churn

Reducing Operational Costs– Backhaul of cell tower traffic accounts for 20% of

mobile operator OPEX

– Site acquisition, leasing costs, power costs

– Capacity demand is expected to be 4x to 10x as migration to 3G and 4G proceeds

Increasing Revenue/Reducing Churn– High quality 3G signal in the home

– Enables new bundled service offerings (quad play)

– Enables “femtozone” and Connected Home services


What is a Femtocell?Tiny 3G home access point

– Provides 3G signal inside the home

– Standalone device or integrated into home gateway

– Works with all standard 3G handsets

Connects to the core network via the internet or managed IP network

– Becomes part of the wireless carrier’s network

– Uses home broadband connection for backhaul

Typical specification– Low power output (a few mW)

– Short range (similar to DECT)

– Self configurable


Femtocell Simplified Network Concept

BTS Wireless Core(MSC, SGSN)

Internet

Cellular Network

Standard 3G Handset

FemtocellAccess Point(<<100mW)

FemtoAccess

Controller

BroadbandConnection

(4 calls in 200kbps)

LicensedSpectrum

OperatorManagement &

Services

LicensedSpectrum

Residential GW


3G Femto and UMA/Dual-Mode Comparison

Characteristic UMA/Dual Mode FemtocellRequires broadband backhaul Yes Yes

Requires new handsets Yes No

Requires new radio CPE at home

No, though new CPE could optimize performance

Yes

Handset mobility Phone can be used in any public hotspot, e.g. Starbucks

Phone needs to be within femtocell range, and *might* be locked to a residence or location

Licensed Radio No Yes

Enables Quad Play Yes Yes

New Family/Zone plans Yes Yes

Integration into SIP/IMS Core UMA – Generally No Dual-Mode - Yes

Yes/Eventually

Battery Life Not as good Better

Bearer Voice Voice and Data

UMA/Dual Mode and Femtocell are complementary FMC applications


Architectural Approaches


Generic Femto Architecture (as defined by the Femto Forum)

Femto Access PointMobile

device

Home GW

Femto GW

Femto Management System

FAP-MS FGW-MS

FL

Fa

SeGW

Fixed Broadband Interconnect

Radio

i/f

Fm Fg

CS core

PS core

Subscriber Databases

Fb-cs

Fb-ps

Fr

HPLMN Core Network

IMS core

Fb-ims

HPLMN RAN


Fragmented Approach to Integration

UE(3G Terminal)

Femto AP RAN Controller Core Network(SGSN, MSC)

Embedded SIP Client (pre-IMS to CS core)

Embedded IMS Client (assumes deployed IMS)

IMS Centric

Radio CentricIub/IP

Split RNCEmbedded UMA Client

Devices shall not be impacted by any access

point architecture


Architecture Summary - Options

AP

AP

MSC

SGSN

bb

RAN (Tunneled Iu) RAN (Iu-h w/ modified RANAP) Corresponds to IP.Access current solution

AP

AP

Femto GW

MSC

SGSN

bbSec GW

Sec GW

Iu-cs

Iu-ps

Iu-cs

Iu-ps

Iuh over IPSecIu over IPSec

Iu Concen trator

SIP/IMS (Client in Femto Gw)

AP

AP

bbSec GW

Iu

Gm/Mw

Iu or Iuh over IPSec

MSC-S

CSCF

AP

AP

ePDGbbSec GW

Gi

Gm over IPSec MSC-S

CSCF

IWF-AS

HSS HSS

Femto GW

Diameter

SIP/IMS (Client in Femto AP)

Wm

Gm

SGSNIu-ps


PDNGateway

Long Term Vision of Femto Cell Gateway Integration (in SAE/LTE environment)

MobilityManagement

Entity

Serving SAEGateway

3GPP LTE IP Base Stations

PDNGateway

Internet

All-IP Femto Cells

FemtoGateway

Femto MobilityManagement

Entity

S1-c S1-u

Seamless Mobility

s10


Standardization Status


Main Organizations and Standards Bodies involved in Femto Definition

• Market representative organization pushing femto as the de facto solution for mobile coverage in the home for all access technologies (WCDMA, CDMA, WiMaX architecture)Organized in working groups covering service requirements (wg1), radio and interference management (wg2), network architecture (wg3) and legal issues (wg4)

• Mobile Service Providers organization defining deployment guidelines and interoperability proceduresPublished guidelines on Femto security and broadband network reqs

• 3G/GSM standardization BodyDefining standards for 3G W-CDMA and SAE/LTE Femtocell services and architecture

•DSL standardization bodyObjective is to reuse TR-069 framework for zero-touch provisioning of Femtocell Access Point

•Mobile Service Provider organization looking at beyond 3G services and architectureFully supporting FemtoForum work on Femtocell

www.femtoforum.org

www.gsmworld.com

www.3gpp.org

www.ngmn.org

www.broadband-forum.org

http://www.femtoforum.org/

http://www.gsmworld.com/

http://www.3gpp.org/

http://www.ngmn.org/

http://www.broadband-forum.org/


Wireless/Wireline Convergence in the EPC


Wireless/Wireline Convergence

The EPC is not limited to supporting 3GPP IP Access Networks or even wireless access networks

Wireline access networks can be supported as well

Features provided by the EPC that may be useful for a wireline access network

Mobility Policy Authentication & AuthorizationAccountingLawful InterceptSecure Access

Additional Wireline Features to consider for converged EPCResidential Network Address Translation (NAT)Location Information


EPC Features for Wireline

MobilityNot all devices need mobility or handover supportMobility features incur additional overall processing and transport costInvoke mobility features only for devices that need it

PolicyBoth wireless and wireline access networks support a policy and charging infrastructure Existing standards (e.g. 3GPP Policy and Charging Control - PCC, and ETSI TISPAN) are reasonably similar in overall concepts

Ongoing standards work to harmonize 3GPP PCC and ETSI TISPAN interfaces as well (Rx and Gq’)

Authentication and AuthorizationWireline access networks typically either do not perform access authentication, or they are moving away from doing soAuthorization is however still being done, e.g. installation of access network authorization profile from AAA upon network attach Conceptually similar to what is being done in 23.402 (except for authentication)



Accounting3GPP defines an overall charging infrastructure that supports both off-line and on-line charging

On-line charging mostly relevant to wireless thoughCharging rules can be installed by AAA or PCCOff-line charging in 3GPP networks often use GTP’ today, whereas other access networks typically use RADIUS based accounting (eventually moving to DIAMETER)On-line charging is based on DIAMETER Credit-Control (DCCA)In summary, overall architecture is similar between wireline and wireless, however deployed protocols and use of on-line accounting may differ

Lawful Intercept3GPP identifies the need for lawful intercept, but does not define the provider internal solution for this Similar solution applies for wireline and wireless networks

Mediation Device (MD) installs content intercept tap in intercept access point (IAP)IAP taps content and sends to MD, which forwards forwards relevant content (and other information) to law enforcement agency



Secure AccessWireline access networks may be either trusted or untrustedThe EPC defines the evolved Packet Data Gateway (ePDG) for secure EPC access over untrusted IP Access Networks

• Uses IKEv2 to establish an IPSec tunnel Provides a general solution for access to EPC mobility services over non- 3GPP access networks with some key benefits

• Can be invoked by only those elements that actually need mobility services• Solves some residential NAT traversal issues when using network-based mobility• Can be used to enable femto-cells over wireline networks (trusted and untrusted)

Downside to this solution is added tunnel overhead even for trusted IP access networks– May consider skipping ePDG for such trusted IP access networks


Additional Wireline Features for EPC

Residential Network Address Translation (NAT)Residential NAT is assigned IP address from access networkMobility enabled devices behind NAT will be assigned IP address by NAT

Breaks network-based mobility Solution: Operate in bridged mode or tunnel through NAT

Location InformationLocation information needed for emergency services

May also be used for authentication (e.g. NASS-bundled authentication as defined by ETSI TISPAN)

Location information handled outside the EPC today, however converged architecture may consider including it

Could be done as part of PCC infrastructure, or using a parallel architecture and interfaces (see e.g. ETSI TISPAN CLF function)


Some Benefits of Wireless/Wireline Convergence

Common infrastructure Policy: Common PCRF and a single policy profile that applies to both wireline and wireless.AAA: Common AAA and a single set of credentials that apply to both wireline and wirelessCharging: Common charging elements and ability to correlate bearer-level charging with application level charging irrespective of access used (example: VoIP)Subscriber data stores (HSS): Common data store facilitates applications spanning access technologies. Location-based services enabled as well

Facilitates common services across access networks and devicesExamples:

Single VoIP service (phone number) for both home and cellularSingle e-mail accountSingle user profile for content filtering, irrespective of access network used (e.g. iPhone or desktop)Single sign-on that works across access networks

Cross access network servicesFor example, dual-mode phone (WiFi)

Fully integrated model enables QoS, single-sign on, etc. on the wireline access networkePDG model would be “over-the-top” – still enables session continuity


Consolidated Wireless and Wireline EPS Architecture

There are basically two different strategies for supporting wireline access networks in the EPS:

1) Treat the wireline access as an untrusted Non-3GPP IP Access

2) Treat the wireline access as a trusted Non-3GPP IP Access



3GPP Access


Wireline Access using Untrusted Non- 3GPP IP Access:DSL Example

PDN Gateway

Serving Gateway

PCRF


HSS

Gxc(Gx+)

S2b(PMIPv6,

GRE)

S5 (PMIPv6, GRE)

S6a(DIAMETER)

S5 (GTP-C, GTP-U)

Gx(Gx+)

Gxb(Gx+)

SWx (DIAMETER)

ePDG

3GPPAAA

SWn(TBD)

S6b(DIAMETER)

SWm(DIAMETER)

SGi

SWa(TBD)

Gxa(Gx+)

Rx+

UE

UE


BNG

AN

RG

AN Access Node (DSLAM)BNG Broadband Network GatewayMAG Mobile Access GatewayPLMN Public Land Mobile NetworkRG Routing Gateway

Note: Refer to TS 23.402 for further details

UE

• Details of untrusted Non-3GPP IP Access not visible to the EPS - No integrated policy, QoS, charging, etc.

- Wireline access is “just a bit pipe”• UE creates IPSec tunnel to ePDG, and ePDG uses PMIP to PDN GW

• PCRF can install policies on ePDG for use in the EPC only (Gxb not specified in Release 8 though)

Untrusted Non-3GPPIP Access


3GPP Access

Wireline Access as Trusted Non-3GPP IP Access: DSL Example

PDN Gateway

Serving Gateway

PCRF


HSS

Gxc(Gx+)

S2b(PMIPv6,

GRE)

S5 (PMIPv6, GRE)

S6a(DIAMETER)


S5 (GTP-C, GTP-U)

Gx(Gx+)

Gxb(Gx+)

SWx (DIAMETER)


Note: Refer to TS 23.402 for further details

ePDG

3GPPAAA

SWn(TBD)

S6b(DIAMETER)

SWm(DIAMETER)

SGi

SWa(TBD)

Gxa(Gx+)

Rx+

UE

UE


BNG

AN

RG


AN Access Node (DSLAM)BNG Broadband Network Gateway

(next-gen BRAS per TR-101)MAG Mobile Access GatewayRG Routing Gateway (DSL modem with

routing)

• BNG will need to be enhanced with PMIPv6 functionality (MAG)

• Not all devices and services require IP mobility; allow for simple IP service to bypass PDN Gateway

• Authentication and policy interfaces in wireline access may not match Gxa and STa

SGiS2a

(PMIPv6, GREMIPv4 FACoA)

http://images.google.de/imgres?imgurl=http://www.joah.ch/layoutbilder/ProduktFotos/produkte_lg_hotel-tv_clip_image001.gif&imgrefurl=http://www.joah.ch/hotel-tv/produkte_lg_hotel-tv.php&h=364&w=350&sz=47&hl=de&start=15&um=1&tbnid=X3TLKA9fGL-CvM:&tbnh=121&tbnw=116&prev=/images%3Fq%3DTV%26svnum%3D10%26um%3D1%26hl%3Dde%26rls%3DGGLG,GGLG:2006-28,GGLG:en%26sa%3DN


Converged Architecture Based on Wireline Access as Trusted Non-3GPP IP Access

Cisco has been working on a combined wireless/wireline architecture based on the 3GPP Evolved Packet System and ETSI TISPAN

– Cisco has been collaborating with the major wireless SP

– Several other carriers are interested in this topic

The next slides provide a very high-level overview of such a “proposed” merged architecture


eBNG(Trusted non-3GPP

IP Access)


IP Access)

Converged Core Architecture: Simplified View

3GPP Access

Serving Gateway

HSS

3GPP AAAServer

AF

PDNTE

ARFCNG

AAA Server (UAAF+PDBF)

{Ta*,e5}

e1

S6c

S5

Gxc

S6a

SGi

TISPAN elements are shown in blue

Gm, etc. Mw, Mx

“Evolved BNG”

S2a (PMIP, MIPv4)

Note: Fast handover not yet considered

Di, Ds, Iz

PDNI-BGF


IP Access)

CNGCF e2e3

a3,a4

e1

Note: Multiple (service specific) eBNG are

likely to exist in a single deployment

{Gxa, Rq, Ia, location, access}

{PDN Gateway,

C-BGF}

{Gx, Ia}

Wx*

{Rx+, Gq’, location, access}

{S9, location, access, NAT}{PCRF, SPDF,

location-proxy} {Gxd, Ia}


Possible Deployment Scenarios


Deployment Models: Deployment Scenario 1

Pros

Centralization of OAM&P personnel and expertise

Minimal signaling delay between MME and SGW/PDNGW

Overall more efficient data plane processing by combined SGW/PGW

Cons

Core site failure will impact large number of users (signaling and data)Signaling and user-plane latency in large geographiesCore site bandwidth requirements and underlying transport network bandwidth requirements

Few core sites with• Centralized MME• Centralized combined SGW/PGW



ProsRegionalization of OAM&P personnel and expertiseOverall more efficient data plane processing by combined SGW/PGWCore site failure will generally not impact established sessions until handoverLimited user plane latencyBandwidth requirements are distributedTraffic can be off-loaded regionally for cost and capacity savings

ConsMME signaling latency in large geographiesCore site failure will impact MME signalingfor a large number of users

Cannot establish new sessions Cannot perform handover

Central core site with• Centralized MME• Combined SGW/PGW

Distributed core sites with combined SGW/PGWs (w. distributed Internet)



ProsCentralization and regionalization of OAM&P personnel and expertise

ConsCore site failure will impact large number of users (signaling and data)Signaling and user-plane latency in large geographiesCore site bandwidth requirements and underlying transport network bandwidth requirementsLess efficient overall data plane processing by separating SGW and PDNGW

Central core site with• Centralized MMEs• Centralized standalone PGWs

Distributed core sites with standalone SGWs


MME

MME

Deployment Models: Recommended Scenario

ProsRegionalization of OAM&P personnel and expertiseOverall more efficient data plane processing by combined SGW/PGWImpact of site failure is limited to the regionLimited signaling and user plane latencyBandwidth requirements are distributedTraffic can be off-loaded regionally for cost and capacity savings

ConsNone

Distributed core sites with• Regionalized MMEs• Regionalized combined SGWs/PGWs


Standalone or combined SGW/PGW

All traffic has to traverse both the SGW and the PGW– There are no benefits to keeping the SGW and PGW in separate locations– Still need open S5/S8 interfaces though in order to

Allow for home routed traffic in roaming scenarios (incl. regional roaming)Allow for handover to an area served by a different “SGW”

An integrated SGW/PGW offers many benefits– Process half as many packets as standalone SGW and PGW. – Maintain 1/3 the number of tunnel endpoints as standalone SGW and PGW

(namely 1 instead of 2+1)– Encapsulate packets to user only once, whereas standalone SGW and

PGW have to encapsulate, decapsulate, and encapsulate again– Less overall IPSec processing (if used between SGW and PGW)– Fewer signaling messages to process– Fewer boxes to manage (OAM&P)


What about MME Integration ?

SGW/PGW scaling is dominated by IP packet logic and processingHigh bandwidthLarge number of packetsData plane feature processing (forwarding, encapsulation, decapsulation, QoS, charging, etc.)IP network platform (router) best suited for this.

MME scaling is dominated by signaling logic and processingCPU intensiveSignaling plane feature processing (authentication, paging, bearer control, user profile, etc.)General purpose processing platform best suited for this

MME and SGW/PGW scaling and development facing different constraintsLimited synergies by integrating MME with SGW and/or PGW:

Primarily a reduction in signaling latency and processing between the MME and SGWOf course, we still need open interfaces between MME and SGW (and PGW indirectly)

Also, current (3GPP) networks migrating towards separate data plane and user plane (SGSN user plane bypass using direct tunnelto GGSN)


IP Network Bandwidth Requirements

eNodeB

MME

SAE Gw

PDN Gw

MME

SAE Gw

x10sx100sx10000s

80Mbps

80Mbps

80Mbps

50:110:1

4Gbps

4Gbps

40Gbps


WiMaX Update


What is WiMaX? – The Business Case

WiMaX Forum – The Organization

WiMaX – The Architecture

WiMaX Development – Feature Specification

Agenda


What is WiMaX? The Business Case


What is WiMaX?

Worldwide Interoperability for Microwave Access is based on 802.16d/e (fixed/mobile)It competes directly against:

Twisted Pair (DSL) and Cable for Fixed Access, andGSM (3GPP) and CDMA (3GPP2) for Mobile Access

It also complements WiFi’s (802.11) predominantly indoor access and competes for outdoor access.It is IP-based all the way to the radio base station.It will operate in both unlicensed and licensed bands.It is an alternative last mile for mobile broadband access and hopefully less encumbered by IPR


WiMaX Value Summary

WiMAX value proposition is for operators to make money out of delivering services on the new Internet modelWiMAX is free from the legacy wire line-cellular because it’s roots are derived from the InternetWiMAX will match speeds of LTE (current proposal of 20 MHz now part of 1.5 Release.)WiMAX will have a cellular-based flavor of multicasting available via HSPA called Multimedia Broadcast Multicast Service or MBMSWiMAX embraces QoS controls and tools which allow operators to embrace multi-tier service pricing and level marketing. WiMAX is excellent where countries – locations have no existing infrastructure


Why is Mobile WiMAX attractive to operators ?

Intellectual Property Rights (IPR) problems with 3G (Qualcomm) Large ecosystem is developing including handset vendors Lots of mobile CAPEX up for grabsSpectrum is becoming available Will go all-IP e2e years ahead of 3GLeading the movement to “open” systemsIs being incorporated into WiFi muni-mesh opportunitiesWiMAX Forum driving the technology forward (approaching 400 members)Will adopt OFDMA and MIMO well ahead of the 3G campsEmerging Market is seeing lots of activity


WiMAX IPR Prevent “strangle-hold” seen in 3G/4G

Oct 2006


Broadband Wireless Market Adoption Reason for WiMAX as preferred technology is simple…

Higher throughput per subscriber, lower latency, built for IPEconomics/Business Case for 802.16 better than traditional 3G systemsModels after the successful “plug & play” scheme of Wi-FiFirst licensed-RF technology to enable “personal wireless broadband”.


WiMaX Forum The Organization


WiMAX Forum Charter

The charter of the WiMaX Forum is to promote WiMaX byDeveloping a certification program (CWG)

Promoting WiMAX in regulatory bodies (RWG)

Developing “profiles” for products and tests for certification (TWG) and

Filling in for missing standards in the network layer (NWG)


Mobile WiMAX Technology Evolution Vision

A fully backward compatible evolution on standards and productsProjections subject to change


IEEE 802.16 Previous Activity

IEEE 802.16: Air interface for fixed broadband wireless access, 10-66 GHz, April 2002Amendment 802.16a: Adds licensed and unlicensed 2-11 GHz for ETSI HiperMAN projectAmendment 802.16c: Added profiles (superceded by WiMAX)IEEE 802.16.2: Addresses “coexistence” fixed systemsIEEE 802.16d: Integrated previous and added non-line-of-sight capability (multipath), also called 802.16-2004IEEE 802.16e: Added mobilityIEEE 802.16f: Provides MIBIEEE 802.16g: Provides mobility managementIEEE 802.16m: Will provide next generation (4G) radio capabilities


IEEE 802.16 Recent Activity

Balloting P802.16Rev2/D5A compilation of all 802.16 approved standards with new features for FDD

Balloting P802.16j/D7 Relay NetworksEnables relay of radio signals to eliminate coverage gaps

Balloting P802.16h/D6 CoexistenceProvisions for operation in un-licensed bands

Completed 802.16m Performance Evaluation DocumentThe objective of this evaluation methodology is to define link-level and system- level simulation models and associated parameters that shall be used in the evaluation and comparison of technology proposals for IEEE 802.16m.

Working on 802.16m System Requirements Document (SRD)

The purpose of this standard is to provide performance improvements necessary to support future advanced services and applications, such as those described by the ITU in Report ITU-R M.2072. (IMT-Advanced)


IEEE Standard Evolution to 16m

16m Completion

expected by end of 2009 *Minimum Requirementsto be Exceeded by 16m


WiMAX Forum Eligible Voting Members listAlcatel-Lucent

Alvarion

AT&T

Bell Canada

Bridgewater Systems

Cisco Systems

Clearwire

Ericsson

Fujitsu

Huawei Technologies

Intel Corporation

KDDI

KT Corp.

Motorola

Navini

NEC

NextWave Telecom

Nokia

Nortel Networks

Posdata

Redline Communications

Samsung

Nokia Siemens Networks

SOMA Networks

Sprint

Starent Network

Telecom Italia

Telsima

ZTE Corporation


The WiMAX Forum Working Groups Structure


WiMAX forum’s nine working groupsApplications Working Group: Define applications over WiMAX™ that are necessary to meet core competitive offerings and that are uniquely enhanced by WiMAX technology.

Certification Working Group: Handles the operational aspects of the WiMAX Forum Certified program.

Evolutionary Technical Working Group: Maintains existing OFDM profiles, develops additional fixed OFDM profiles, and develops technical specifications for the evolution of the WiMAX Forum's OFDM based networks from fixed to nomadic to portable, to mobile.

Global Roaming Working Group: Assures the availability of global roaming service for WiMAX networks in a timely manner as demanded by the marketplace.

Marketing Working Group: Influences WiMAX technology adoption worldwide. Promotes WiMAX products, brands and standards, which form the basis for global interoperability of wireless broadband Internet anytime anywhere.

Network Working Group: Creates higher level networking specifications for fixed, nomadic, portable and mobile WiMAX systems, beyond what is defined in the scope of 802.16.

Regulatory Working Group: Influences worldwide regulatory agencies to promote WiMAX-friendly, globally harmonized spectrum allocations.

Service Provider Working Group: Gives service providers a platform for influencing BWA product and spectrum requirements to ensure that their individual market needs are fulfilled.

Technical Working Group: The main goal of the TWG is to develop technical product specifications and certification test suites for the air interface based on the OFDMA PHY, complementary to the IEEE 802.16 standards, primarily for the purpose of interoperability and certification of Mobile Stations, Subscriber Stations and Base Stations conforming to the IEEE 802.16 standards.


WiMaX The Architecture


WiMAX Architecture

Networks:

ASN: Access Serving Network

CSN: Connectivity Serving Network

MS

BSASN

BS

ASNGW

AAAproxy

HA

PF

R1 R3

BSASN

BS

ASNGW

CSN

R3

R4

R2 NAP vNSP

AAAPF

CSN

hNSP

R5

R6

R6

R6

R6

Operators:NAP: Network Access ProvidervNSP: Visited Network SPhNSP: Home Network SP

Network Elements:MS: Mobile Subscriber StationBS: Base StationASN GW: ASN Gateway (router)HA: Home AgentPF: Policy Function

InternetInternet


ASN-GWFA/PMIP

HA

BS BSBS

AAA

RadioMgmt

IP IP IP

Use WiMaX Forum standard interfaces

• R4 for Inter FA handoff (fast-handoff)

• R6 for micro mobility

• Rx for RRM interface

Radio Independent Functionality

• Fast Hand-off for Micro Mobility

R6Rx

R4 (optional) ASN-GWFA/PMIP

BS BS

IP IP

R6

R3

Macro & Micro Mobility: 802.16e Full Mobility Model

Internet


WiMAX IP-CS (PMIP)

R6 Control Plane handles Authentication, SF Assignment, etc

SF Session per user uniquely identified through GRE-Key

PMIP Client and FA embedded in ASN GW

HA is the Local Mobility Anchor (LMA)

EoMPLS

IP-CS

ASNGW

R6 GRE Mobile IP

HA

PMIP

PHY PHYPHY PHY PHY PHY

MAC MACLNK LNK LNK LNK

.16eCtrl .16eCtrlIP IP IP IP

ASNctrl ASNctrl CSNctrl CSNctrlControl (UDP 2231/R6)

GRE

LNKPHY LNKLNK

GREIP IP IPMAC

PHY

Micro Mobility

LNK

IP IP

IP

IPLNK

MACIP-CSIP-CS MIP MIPMacro Mobility

IP-CS Data Path (PMIP)


Profile Comparison

ASN Profile

Description Pro Con

Profile A Centralized platform

Separate BS and ASNGW

Split RRM: RRA at BS

and RRC at ASN-GW

Able to provide simplified pico-cell

Able to provide soft handover

Fewer backhauls for RRM messages

Difficult Interoperability between BS and ASNGW from different vendors

Heavy workload at ASN- GW

Fewer vendors

Profile B Distributed platform

Combined BS and ASNGW

Simple architecture

Suitable for small-scale deployment

Difficult to customize IP and wireless functions for operators

Expensive for large scale deployment

Profile C Distributed platform

Separate BS and ASNGW

RRM at BS

Able to provide simplified pico-cell

Open – multi -vendors can supply BS and ASNGW

Extra backhauls for RRM messages


ASN

WiMAX Profiles

ASN GW

BSBSBS

ASN

BTSBTSBTS

ASNASN-GW

[BSC]

B

A

C

unspecifieddecomposition

Profile A: Central radio resource management in ASN-GW approach

Profile B: Closed interfaces favor radio network (BS) vendors

Profile C: Open interfaces with separation between radio and network functionality

PHY and partly MAC in BTS

Handover-Control (RRM) in ASN-GW

Routing and AAA/Paging in ASN-GW

Most ASN functions in BS

BS anchored by standard router

Inter-BS control over Ethernet

All radio-specific functions in BS

Handover-Control (RRM) in BS

Routing and AAA/Paging in ASN-GW

BSBSBS

Deprecated


Combined BS, ASN-Gateway, RRM in BS

ASN Profile B Current status: No new Development

P

P

PE

PE

P

PP P

ASPASP MPLS COREMPLS CORE NSP SERVICESNSP SERVICESCPECPE

ISPInternet

Residential

Residential

Business

Corporate

BRAS

PE

Voice

HomeAgent AAA

R1

R4

R2

R3

- HO- Data Path 1 & 2- Authenticator- Key Rec. &Dist.- Context- RRA + RRC- SF Auth & Mgt

- DHCP Proxy/Relay- MIP FA- Location Register- PMIP Client/Assist- AAA Client

R3

R4

BS+ASNG_FABS+ASNG_FA

BS+ASNGFA

BS+ASNGFA

R1


Separate ASNG, BS and RRM in BSASN Profile C Current Status: Active

P

P

PE

PE

P

PP P

ASPASP MPLS COREMPLS CORE NSP SERVICESNSP SERVICESCPECPE

ISPInternet

Residential

Residential

Business

Corporate

BRAS

PE

Voice

HomeAgent AAA

ASNG/FAASNG/FA

ASNG/FAASNG/FA

R1

R4

R6

R2

R3

- HO- Data Path 1 & 2- Authentication Relay- Paging Agent- Key Receiver- Context- RRA + RRC- SF Management

- HO- Data Path 1 & 2- Authenticator- Key Distributor- Context- SF Authorization

- DHCP Proxy/Relay- MIP FA- Location Register- PMIP Client- AAA Client- Paging Controller

BS ASN-GW

R3

R4

R6

BSBS

R1


WiMaX Development Feature Specification


Potential WiMAX Deployment Spectrum By Region: 2005 To 2008


WiMAX Forum CWG, RWG, TWG Activity

CWGWorking on the logistics of the certification programWave 2 certification CRSL 2.2 available for testing scheduled for August 2008The plug fest in May 2008 did include beamforming and MIMONWIOT plug fest planned for Nov. 2008

RWGWiMAX accepted into IMT-2000 family of productsAnalyzing world-wide radio parameters requirements (spectral mask) for MSResponding to inquiries from various countries

TWG achievements Developing “Profile 1.5” for FDD and TDD based WiMAXImproving and clarifying “Profile 1.0” and related tests for TDD-based WiMAXDeveloped new tests for “Radiated Performance” of antennasDeveloped coexistence mechanism of WiMAX with WiFi and BluetoothStarted technical work on using 700 MHz spectrum for WiMAX


WiMAX Forum Release 1.0 Activity

Release 1.0 CapabilitiesNetwork discovery and selection with roaming support

Radio Resource Management procedures inside ASN

Sleep/Idle mode and paging support

Pre-provisioned QoS framework

Authentication and Authorization based on EAP and RADIUS

IP & Ethernet support (Ethernet optional on BS and MS)

Three ASN profiles for splitting functions between BS and ASN-GW (optional to implement, Profile A deprecated)

Mobility management inside ASN and directly between ASNs

Mobility Management between ASN and CSN based on Mobile IP

Client MIP support as well as DHCP with Proxy MIP

Simple IP support added

No standardized functional decomposition inside CSN


WiMAX Authentication/security Key Exchange

EAP is method usedASN GW is the authenticator and is agnostic to the EAP Method. The transport of EAP is done between the ASN GW and the Base-Station as a control exchange. Base-station functions as EAP-Relay converting from PKMv2 to EAP messages over to ASN GW. ASNGW is EAP pass-through and any key generating EAP methods can be supported in the system The ASN GW, following EAP authentication of the subscriber, will also compute respective Access Keys (AKs) for each Base-Station.The ASN GW will also cache the PMK for the duration of the authentication, and will recomputeadditional AKs when the SS/MSS moves to another Base-station.Support for Un-authenticated user – 911 or Pre-paid for example


WiMAX Forum NWG Release 1.5 Activity

Note: Release 1 has undergone over 1200 Change Requests and a cover to cover sanity check was performed in September-November 2008 as backward compatibility and additional error handling was added in to create Version 1.3.Release 1.5 Specifications complete on:

Over The Air (OTA) Provisioning Bootstrap – Generic, OMA-DM, TR693GPP2-WiMAX Interworking – Loosely coupled with dual radio onlyNormative R8 Interface – Direct Base Station to Base Station interface Simple IP – Pre-provisioned connections from ASN to CSN (no MIP)IMS Support (IMS) – Capabilities needed to connect to the P-CSCFEmergency Services (E911) – Capabilities needed to connect to an E-CSCF Lawful Intercept (LI) – Generic Overview and North American LIPolicy Control (PCC) – Infrastructure needed to deliver policy rules and control QoSDynamic QoS – Activation/deactivation of pre-provisioned service flows with no PCCDiameter – Adding protocol elements to match RadiusEthernet Services – Ethernet CS over Service Flow paralleling IP CS over SFHandoff Data Integrity – Ensuring uninterrupted packet flow for mobilityRobust Header Compression (RoHC) – Reducing packet size of the air interface


WiMAX QoS & Scheduling Schemes Specifications & Applications…

Service Flows:Mechanism defined in Mobile WiMAX to

provide QoSUni-directional flow of packets

associated with certain defined QoS parameters for traffic

Connections:Unidirectional logical link between BS

and CPE Each connection is associated with a

service flow delivering the necessary QoS over the air interface

Packet Classifiers:Each service flow also has packet

classifiers associated with it to determine criteria used by the MAC layer to associate packets into service flows

Mobile WiMAX scheduling based on QoS service Flows associated with each packet

QoS Category Applications QoS Specifications

UGSUnsolicited Grant

Service

VoIP •

Maximum Sustained Rate

•

Maximum Latency•

Jitter TolerancertVR

Real-Time Variable Rate Service

Streaming Audio or Video

•

Minimum Reserved Rate

•


•

Maximum Latency•

Traffic PriorityErtVR

Extended Real-Time Variable Rate Service

Voice with Activity Detection (VoIP)

•


•


•

Maximum Latency•

Jitter Tolerance•

Traffic PrioritynrtVR

Non-Real-Time Variable Rate Service

FTPFile Transfer Protocol

•


•


•

Traffic PriorityBE

Best-Effort ServiceData, Web Browsing,

etc.•


•

Traffic Priority



Specifications undergoing V&V:Subscriber Identity Module (SIM) – MS-based authentication functionsLocation Based Services (LBS) – Network and GPS-based location determination of MS



Specifications under development:DSL Interworking – WiMAX access network as replacement for DSL infrastructureIWK 3GPP2 Single Radio – Optimized HO for single radio to/from HRPD networksIWK 3GPP EPS/EPC – Optimized HO for single radio to/from Release 8 core networks IWK 3GPP Pre-Release 8 – Single and dual radio HO to/from GPRS networksMCBCS-DSx – R1 Link-layer-controlled multicast/broadcast streaming servicesMulticast Broadcast Services (MCBCS-App) – R2 Application-controlled streaming servicesMobility Restriction – Additions to minimize HO for Fixed/Nomadic Spectrum regulationsPMIPv6 – R3 Mobility support based on PMIPv6Universal Services Interface (USI) – API for 3rd Party query of MS-related information

New requirements passed from SPWG for beyond Release 1.5:Device Reported Metrics (DRMD) – R2-based measurements on MS

Multimedia Session Continuity (MMSC) – Connection continuity over diverse accesses

Network Management (NMR) – FCAPS-style element management

IPv4-IPv6 Migration – Support for IPv6-based services over WiMAX


WiMAX Forum SPWG Release 2.0 Activity

Release 2.0 Completed RequirementsDRMD Phase 1 – Metrics available on current chip-setMultihop Relay BS (802.16j) – Defines relay use to extend outside radio coverageMulti-Media Session Continuity (MMSC) – SIP sessions across WiMAX, WiFi, LTEModernized Network Management (NMR) – Specifies FCAPS management controlsConnection Manager API – Defines connection manager to WiMAX Modules interactionIPv4-IPv6 Migration – Support for IPv6-based services over WiMAX

Release 2.0 Requirements Development:Device Reported Metrics (DRMD) Phase 2 – Metrics requiring modification of MS HW/SWFemto-Cell – Defines use of residential access points to extend radio coverage indoorsEmergency Telecommunications Service (ETS) – Support of government respondersRelease 2.0 Air Interface – Continuation of profile development

Release 2.0 Requirements On Hold (little activity):WiMAX Short Message Service/Multimedia Message Service/Instant Messaging Service

Defines service comparable to 3GPP and 3GPP2 services


Q & A


Documents

Mobile Broadband Evolution - cisco.com 2G/2.5G/3G Mobile ... CATT, ZTE, Texas Instruments, Orange, IP Wireless, Marvell, Intel, T-Mobile, ... No RNC. node – RNC function integrated