Mobile Broadband Evolution

Asia Technology Forum December 4-5, 2008

Vojislav Vucetic SP Marketing, Industry and Technology Marketing Group

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

Legacy Today Emerging (Voice Centric) (Voice and Data) (Data Centric)

OFDM voice and data

UMTS/EVDO IP E2E 3G Data Infrastructure ivity, efficiency, revenue) Open handset

TDMA Radio IP Insertion 2G Data (Core, Edge, RAN)

TDM Infrastructure Business performance (productBusiness performance 1990’s 2000’s 2010’s Mobile access evolution and IP infrastructure impact November_2008 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 4 The Drivers: A Mobile Internet “Perfect Storm”

Handsets Broadband Powerful New Devices High Speed Radio Access with Compelling UIs

100100 FoldFold IncreaseIncrease inin Billing Plans DataData TrafficTraffic Applications Aggressive Flat Rate All-You- byby 2013/142013/14 Lots of Compelling Apps Can-Eat Billing Plans Are Moving over from the Wired World

Worldwide Mobile Data Traffic (in PBytes per Month)

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

160% CAGR over next 4 years

The Mobile Internet Must Deliver Orders of Magnitude More Traffic for an Orders of Magnitude Lower Cost Per Bit

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

Mobile Internet gateways that can scale to 50 Gbps and more

Cost effective solutions to scale the RAN & improve indoor coverage

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

HLR PSTN

BTS BSC GMSC

BTS MSC/VLR BSC

CN to provide BTS CS Voice

Radio Access Network BTS (RAN)

HLR GMSC PSTN

Node B RNC 3G Router MSC/VLR CS Voice Network Node B RNC PS Data Network

PDN Node B IP GGSN Radio SGSN Access Network Node B (RAN)

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

HLR GMSC MSC/VLR BTS PSTN

Voice Part 3G BTS BSC/PCF Data Router Part

IP PDN BTS BSC/PCF PDSN HA

BTS

Technology D/L D/L U/L U/L Actual Theoretical Actual Theoretical UMTS WCDMA Rel’99 2.048Mbps 768 UMTS WCDMA Rel’99 (practical 384Kbps 350Kbps 384Kbps 350Kbps terminal) HSDPA Initial Devices (2006) 1.8Mbps > 1Mbps 384Kbps 350Kbps HSDPA Current Devices 3.6Mbps > 2Mbps 384Kbps 350Kbps HSDPA Emerging Devices 7.2Mbps > 3Mbps 384Kbps 350 Kbps HSDPA 14.4Mbps 384Kbps HSPA Initial Implementation 7.2Mbps >4Mbps 1.46Mbps 1Mbps HSPA Future Implementation 7.2Mbps 5.76Mbps HSPA 14.4Mbps 5.76Mbps HSPA+ (2x2 MIMO, DL 16 QAM, 28 Mbps 11.5Mbps UL 16 QAM) HSPA+ (2x2 MIMO, DL 64 QAM, 42Mbps 11.5Mbps UL 16 QAM) LTE (2x2 MIMO) 173Mbps 58Mbps LTE (4x4 MIMO) 326Mbps 86MBPS

Revenue Profitability Network cost (LTE)

Time Voice Data dominated dominated

Price per MByte has to be reduced to remain profitable

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 decade Long Term Evolution is a Revolution in the air interface from WCDMA to OFDMA/MIMO Evolved 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)

November_2008 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 20 What is LTE as defined in 3GPP Release 8 LTE 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

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 November_2008 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 22 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 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.912 The 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

3GPP 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 technologies The main objectives of the SAE work are to address the following: Impact on overall architecture resulting from RAN's LTE work Impact 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

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!)

2G/3G LTE CDMA/GSM/UMTS Control User Control User Plane Plane Plane Plane

HA / Serving/PDN GGSN Gateway

PDSN / MME SGSN

BSC / RNC

BTS / eNodeB NodeB

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

Beamforming Increases 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 resource Even 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 UL LTE 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

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

S1-c Base Station to MME interface Multi-homed to multiple MME pools SCTP/IP based S11 MME to SAE GW GTP-c Version 2

SAE GW

X2 inter base station SAE GW to PDN GW interface GTP or PMIP based macro mobility SCTP/IP Signalling GTP tunnelling S1-u Base Station to SAE GW following handover GTP-u base micro mobility

UTRAN SGSN GTPc Context Transfer

GTPu Macro Mobility MME SAE GW

PDN GW SAE GW PDN GW ENB S101 S103

PMIPv6 or MIPv4 FA Mode 3GPP2 S101: UDP application for pre- HRPD GW registration PDSN Sx-u: forward DL data to minimize

Rel-99 Rel-5 Rel-6 Rel-7 Rel-8 Rel-9 Rel-8 WCDMA HSDPA HSUPA MIMO 2x2 64 QAMOFDMA LTE

DL: 384 kps DL: 1.8 – 14.4 Mbps DL: 1.8 – 14.4 Mbps DL: 28 Mbps DL: 42 Mbps DL: 100 Mbps UL: 384 kbps UL: 384 kbps UL: 5.7 Mpbs UL: 11 Mpbs UL: 11 Mpbs UL: 50 Mpbs

2007 2008 2009 2010 2011+??

Aspect Mobile WiMaX 3GPP-LTE Core Network GRE based micro mobility and PMIP GTP based micro mobility and based macro mobility GTP/PMIP based macro mobility Access Technology OFDMA (DL) OFDMA (DL) OFDMA (UL) SC-FDMA (UL) FFT Size 128-1024 128-2048 Frequency Bands, 2.3, 2.5, 3.4, 5.8 Existing IMT 2000 bands GHz (0.7 through to 2.6) Channel Bandwidths, 5, 7, 8.75, 10 1.25, 2.5, 5, 10, 20 MHz Duplexing Method TDD but FDD in the works Primarily FDD, but also TDD

MIMO Mode Diversity/Spatial Diversity/Spatial Multiplexing/Collaborative SM Multiplexing/Collaborative SM

Modulation 64 QAM/16QAM/QPSK 64 QAM/16QAM/QPSK Frame Length 5ms 1ms Typical MAC ~25% ~15-20% overhead Vehicular support Up to 120 kmph Up to 250 kmph November_2008 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 39 3GPP Release 8 - Architecture Overview

The System Architecture The EPS provides IP connectivity Evolution (SAE) defines the for 3GPP and non-3GPP Access Evolved 3GPP Packet Networks Switched domain (aka Evolved UTRAN, E-UTRAN, Trusted and Packet System - EPS) Untrusted Non-3GPP Access

HSS 3GPP Access S6a SWx 2G/3G SGSN S4 PCRF S 7c S3 Rx+ MME Gx S11 Operator 's IP S1 -MME SGi Services S10 Serving PDN (e.g. IMS, PSS E -UTRAN Ga teway Gateway etc.) S1 -U S5 S6b S2b Gxb SWm 3GPP AAA S2a ePDG Server SWn HPLMN

Non -3GPP Gxa Networks SWu Trusted Untrusted Non -3GPP IP Non -3GPP IP Access SWa Access STa

Up until Release 8, 3GPP IP mobility was based on GTP However, 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 IP Consequently, both options were allowed and specified by 3GPP: TS 23.401 defines a GTP-based EPS supporting 3GPP IP Access networks only TS 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

November_2008 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 42 Non-Roaming EPS Reference Architecture Evolved Packet Core 2G/3G 3GPP Access SWx (DIAMETER) HSS S12 (GTP-U) UTRAN S4 (GTP-C, GTP-U) S6a PCRF SGSN (DIAMETER) GERAN S3 Rx+ (GTP-C) MME S11 Gxc (GTP-C) (Gx+) LTE Gx Gxa Gxb S1-MME (Gx+) (Gx+) (Gx+) 3GPP (S1-AP) S10 S6b AAA (GTP-C) (DIAMETER) Serving S5 (PMIPv6, GRE) PDN Operator’s eNodeB E-UTRAN S1-U Gateway Gateway SGi IP Services (GTP-U) S5 (GTP-C, GTP-U) S2c SWm (DIAMETER) S2a S2b UE (PMIPv6, GRE SWa MIPv4 FACoA) (PMIPv6, GRE) (TBD) ePDG 3GPP SWn IP Access (TBD) Trusted Non-3GPP Non-3GPP Untrusted Trusted IP Access Non-3GPP Untrusted IP Access IP Access S2c (DSMIPv6)

STa (RADIUS, DIAMETER) SWu (IKEv2, S2c MOBIKE, IPSec) UE

November_2008 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 43 Non-Roaming EPS Reference Architecture • Handles all signaling traffic (no user plane traffic) • Common anchor point for all IP Access • Interacts3GPP with HSS Access for user authentication, profile download, etc. SWx (DIAMETER)Networks (3GPP and non-3GPP) HSS • Interacts with S12eNodeB (GTP-U) and Serving GW • Assigns/owns IP-address for UE (v4/v6) toUTRAN control tunnels, paging, etc. • Processes all IP packets to/from UE • Interacts with SGSNS4 (GTP-C, for 2G/3G GTP-U) S6a • Can be in home and/orPCRF visited network SGSN (DIAMETER) GERAN S3 Rx+ (GTP-C) MME S11 Gxc (GTP-C) (Gx+) Gx Gxa Gxb S1-MME (Gx+) (Gx+) (Gx+) 3GPP (S1-AP) S10 S6b AAA (GTP-C) (DIAMETER) Serving S5 (PMIPv6, GRE) PDN Operator’s eNodeB E-UTRAN S1-U Gateway Gateway SGi IP Services (GTP-U) S5 (GTP-C, GTP-U) S2c SWm (DIAMETER) S2a S2b UE (PMIPv6, GRE SWa MIPv4 FACoA) (PMIPv6, GRE) (TBD) • Performs radio resource ePDG management, incl. handovers SWn • Interacts with MME for all (TBD) signaling plane processing Trusted • Exchanges user plane Non-3GPP Untrusted IP Access Non-3GPP traffic with •ServingWireless GW or fixed access network IP Access • Close integration with the EPC S2c (DSMIPv6) • Supports mobility,• Anchor policy point and for 3GPP IP Access • EPC point of attachment AAA interfaces to the EPC STafor (RADIUS, untrusted IP access Networks only (2G/3G/LTE) DIAMETER) • Processes all IP packets to/from UE SWu (IKEv2, S2c networks (“Internet”) • Controlled by MME MOBIKE, IPSec) •IPSec to UE for EPC • Uses network-based mobility towardsUE connectivity PDNGW (GTP or PMIPv6) • Network-based mobility towards PDNGW (PMIPv6) • Always in same network as eNodeB UE

HPLMN (GTP) HSS

S6a hPCRF (DIAMETER)

Rx+

Gx (Gx+)

PDN Operator’s Gateway SGi IP Services

S8a (GTP-C, GTP-U) VPLMN (GTP)

3GPP Serving Access Gateway

HPLMN (PMIP) HSS

S6a hPCRF (DIAMETER)

Rx+ S9 (DIAMETER)

Gx (Gx+)

PDN Operator’s Gateway SGi IP Services

S8b VPLMN (PMIP) (PMIPv6, GRE) vPCRF

Gxc (Gx+)

3GPP Serving Access Gateway

HPLMN (PMIP) SWx (DIAMETER) HSS

S6a hPCRF (DIAMETER)

Rx+ S9 (DIAMETER)

Gx (Gx+) 3GPP S6b AAA (DIAMETER) PDN Operator’s Gateway SGi IP Services

S8b SWd (RADIUS, VPLMN (PMIP) (PMIPv6, GRE) S2b vPCRF DIAMETER) S2a (PMIPv6, (PMIPv6, GRE GRE) 3GPP MIPv4 FACoA) Gxc AAA Proxy (Gx+)

3GPP Serving Access Gateway Gxb (Gx+) SWm (DIAMETER)

SWa Gxa (TBD) (Gx+) ePDG SWn (TBD)

Trusted Untrusted Non-3GPP SWu IP Access Non-3GPP IP Access STa (RADIUS, DIAMETER) Note: Protocol choice analysis in TR 29.803 November_2008 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 60 Roaming Architecture: 3GPP Access, Local Breakout, GTP-Based

HPLMN (GTP) HSS

S6a hPCRF (DIAMETER)

Rx+ S9 (DIAMETER)

Operator’s IP Services

VPLMN (GTP) vPCRF

Rx+ Gx (Gx+) 3GPP Serving PDN SGi Operator’s Access Gateway S5 Gateway IP Services

HPLMN (GTP or PMIP) HSS

S6a hPCRF (DIAMETER)

Rx+ S9 (DIAMETER)

Operator’s IP Services

SWd (RADIUS, VPLMN (PMIP) vPCRF DIAMETER)

Rx+ Gxc Gx (Gx+) (Gx+) 3GPP Serving PDN SGi Operator’s Access Gateway S5 Gateway IP Services

HPLMN (GTP or PMIP) SWx (DIAMETER) HSS

S6a hPCRF (DIAMETER)

Rx+ S9 (DIAMETER)

3GPP AAA Operator’s IP Services

SWd (RADIUS, VPLMN (GTP or PMIP) vPCRF DIAMETER) 3GPP Rx+ AAA Proxy Gxc Gx (Gx+) (Gx+) S6b 3GPP Serving PDN SGi Operator’s Access Gateway S5 Gateway IP Services Gxb SWm (DIAMETER) S2a S2b (PMIPv6, GRE SWa MIPv4 FACoA) Gxa (TBD) (Gx+) ePDG SWn (TBD)

Trusted Untrusted Non-3GPP SWu IP Access Non-3GPP IP Access STa (RADIUS, DIAMETER) Note: Protocol choice analysis in TR 29.803 November_2008 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 63 Roaming Architecture: All Access, Home Routed and Local Breakout

HPLMN (GTP or PMIP) SWx (DIAMETER) HSS

S6a hPCRF (DIAMETER)

Rx+ S9 Gx (DIAMETER) (Gx+) 3GPP S6b AAA (DIAMETER) PDN Operator’s Gateway SGi IP Services

SWd (RADIUS, VPLMN (GTP or PMIP) S8a/b vPCRF DIAMETER) 3GPP Rx+ AAA Proxy Gxc Gx (Gx+) (Gx+) S6b 3GPP Serving S5 PDN SGi Operator’s Access Gateway Gateway IP Services Gxb SWm (DIAMETER) S2a S2b (PMIPv6, GRE SWa MIPv4 FACoA) Gxa (TBD) (Gx+) ePDG SWn (TBD)

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 (Proxy) Mobile IP Key management and None (done at the access) IPSec with automated (IKE) or confidentiality Optionally, IPSec can be used manual key exchange (e.g. GRX) Inter-Technology handoff No Yes MIP could be deployed as an extra layer Context Transfer (policy, Yes No (needs new extensions) QoS, charging, etc) QoS management Yes No (needs new extensions)

Access Agnostic No Yes

IETF Compliant No Yes

Air-interface capacity Optimized Depends on MIP model impact Client impact No client required Yes with CMIP Can be alleviated with PMIP

SWx (DIAMETER) HSS S12 (GTP-U) UTRAN S4 (GTP-C, GTP-U) S6a PCRF SGSN (DIAMETER) GERAN S3 Rx+ (GTP-C) MME S11 Gxc (GTP-C) (Gx+) Gx Gxa Gxb S1-MME (Gx+) (Gx+) (Gx+) 3GPP (S1-AP) S10 S6b AAA (GTP-C) (DIAMETER) Serving S5 (PMIPv6, GRE) PDN Operator’s eNodeB E-UTRAN S1-U Gateway Gateway SGi IP Services (GTP-U) S5 (GTP-C, GTP-U)

SWm (DIAMETER) S2a S2b UE (PMIPv6, GRE SWa MIPv4 FACoA) (PMIPv6, GRE) (TBD) ePDG

SWn (TBD)

Trusted Non-3GPP Untrusted IP Access Non-3GPP IP Access

STa (RADIUS, DIAMETER) SWu (IKEv2, MOBIKE, IPSec) UE

GTP use in EPS split in -C and -U plane GTP-C for S3, S4, S5, S8, S10, S11 and S101 GTP-U for S1-U, X2, S4, S5, S8, S12 (version FFS) PMIPv6 used in EPS on S2, S5, S8 New 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 reduction Inter 3GPP mobility End marker packet GTP user plane version still in discussion but it will likely be an enhanced GTPv1 version with backward compatible extensions EPS 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 November_2008 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 69 LTE/EPS Interworking with WiMaX

SWx (DIAMETER) HSS

S6a PCRF (DIAMETER)

Rx+

MME S11 Gxc (GTP-C) (Gx+) R3-PCC Gx (Gx+) S1-MME (Gx+) 3GPP (S1-AP) S10 S6b AAA (GTP-C) (DIAMETER) PDN Serving S5 (PMIPv6, GRE) Operator’s eNodeB Gateway/ E-UTRAN S1-U Gateway SGi IP Services (GTP-U) S5 (GTP-C, GTP-U) CSN

(RADIUS) R3 (PMIP, GRE) UE

ASNGw

WiMAX

WiMAX BTS

December_2008 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 72 3GPP Structure and Leadership - Current TSG Structure TSG GERAN TSG RAN TSG SA TSG CT GSM EDGE Radio Access Radio Access Network Service & System Core Network & Terminals Network Aspects GERAN WG1 RAN WG1 SA WG1 CT WG1 Radio Aspects Radio Layer 1 spec Services MM/CC/SM (lu) GERAN WG2 RAN WG2 SA WG2 Protocol Aspects Radio Layer 2 spec Architecture Radio Layer 3 RR spec GERAN WG3 RAN WG3 SA WG3 CT WG3 Terminal Testing Lub spec, lur spec, lu spec, Security Interworking with external UTRAN O&M requirements networks RAN WG4 SA WG4 CT WG 4 Radio Performance Codec MAP/GTP/BCH/SS Protocols aspects RAN WG5 SA WG5 CT WG5 Mobile Terminal Telecom Management Smart Card Application Aspects

TSG – Technical Specification Group

3GPP Current Status (as of September 18th, 2008) after SA Plenary Meeting Stage 1 completed June 2008 Stage 2 completed June 2008 (with the exceptions that will be completed by December 2008 Stage 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: TBD Summary of all Release 8 Features – Target publication remains December 2008 3GPP2 target date for X.P0057 is December 2008

Stage 3 Change Stage 3 Freeze Layer 1 specifications are Control Stage 2 Change Stage 2 Freeze very stable Control Remaining specs went 2006 2007 2008 2009 under change control 12/07, even though many/most Jul Oct Jan Apr Jul Oct Jan Apr Jul Oct Jan Apr Jul Oct Jan were not ready Stage 2 Development Expect a wave of CRs in 2009 to fix defects Stage 3 Development

3GPP Release 8 EPC Standards Timeline Stage 2 work winding down, Stage 2 Change Stage 3 Change a few key issues remain Control Control open Stage 2 Freeze Stage 3 Freeze Stage 3 work just beginning. 2007 2008 2009 (3GPP likely to “declare”

Jan Apr Jul Oct Jan Apr Jul Oct Jan Apr Jul Oct Jan completion by EOY 08) Stage 2 Development Expect a wave of CRs in 2009 to fix defects and to last 12-16 months Stage 3 Development Stage 3 might end in 03/09

December_2008 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 76 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

The 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

EPC 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

November_2008 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 79 EPC Platforms Directions Mobile 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

Pre-Release 8 3G Network PDN GW handles handover to/from Pre-Release 8 SGSNs Release 8 3G Network MME and SGW handle handover to/from Release 8 SGSNs

GERAN Pre Rel-8 SGSN

UTRAN Gr Gn HSS S6a

S1-MME MME Gn PCRF S7 Rx+ S11 S10 Serving S5 PDN SGi UE Operator's IP Services EUTRAN- GW GW S1u (e.g. IMS, PSS etc.)

Gz (GTP’)

Gy (DCCA) CGF Online Lawful (offline) Charging Intercept

GERAN Rel-8 SGSN

UTRAN Gr S3 HSS S6a

S1-MME MME S4 PCRF S7 Rx+ S11 S10 Serving S5 PDN SGi UE Operator's IP Services EUTRAN- GW GW S1u (e.g. IMS, PSS etc.)

Gz (GTP’)

Gy (DCCA) CGF Online Lawful (offline) Charging Intercept

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

WiMAX has following benefits over LTE Mature 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 LTE LTE 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 WiMAX TDD; Fixed/Portable Usage; Greenfield Operator; Emerging Market Determining factors for LTE FDD; Mobile Usage; Cellular Operator; Developed Markets

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 WiMAX benefits from reuse of equipment and where appropriate while LTE relies on combination protocols (deployed in enterprise and carrier IP of IETF and legacy 3GPP protocols networks) in cost and expertise savings. Two examples: AAA, and HA (only) LTE provides separation of control (MME) and Allows for independent scaling of bearer and control. bearer (S-GW) Allows combining S-GW and PDN-GW. (only) WiMAX enables creation of distinct Access Enables business models where different and Connectivity Provider connectivity providers share same radio access network

W&L support IPv4, IPv6 Ethernet convergence is useful for many deployments such as Enterprise connectivity WiMAX supports Ethernet Convergence

LTE provides extensive support for interworking with Enables smooth transition from 3GPP2 and 3GPP 3GPP, 3GPP2 providers systems to LTE WiMAX will provide loosely coupled interworking with 3GPP2 starting Rel. 1.5

Similarity /Differences Advantages/Disadvantages

W&L provide mutual authentication, and encryption of over-the-air traffic and maintain key hierarchies LTE is consistent with cellular technology LTE Security is based on USIM WiMAX is consistent with security WiMAX device security is based on certificates 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. PMIP is IETF based mobility protocol while LTE has network mobility based on GTP and GTP was defined and used in 3GPP. WiMAX PMIP while WiMAX has based on PMIP 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 This feature is expected in future WiMAX LTE enables client-based setup of service release flows

Prefer WiMAX Prefer LTE

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

Primary Service Broadband wireless service for Broadband wireless service for mobile and Type residential usage portable devices

Legacy or Primarily Greenfield operators Legacy 3GPP and 3GPP operators to Greenfield (Sprint Clearwire being the migrate to LTE based on broadband operators significant exception) demands and device availability

TTM Current Availability of inter operable Earliest large scale commercial Considerations devices and equipment favors deployment in 2010. WiMaX

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 Proof of Concept completed Operators (Vodafone, China Mobile, FTO, Interoperability Tests planned through end of Telefonica, Telcom Italia) 2009 Customer Trials in 2010

PDN-GW Functional Mapping HA AAA HSS PDN-GW maps to HA S5 R3 S6 HSS maps to AAA S10 S11 MME S-GW (S-GW and MME combined) ASN-GW R4 map to ASN-GW S1-u R6 S1-MME eNodeB maps to BS eNodeB X2 BS R8 UE maps to SS (subscriber station) UE SS LTE WiMAX

PDN-GW

S2a S2b S4

S3 SGSN MME S-GW PDSN ePDG

cdma200/HRPD WLAN GPRS/UMTS LTE E-UTRA

WiMaX LTE Loosely coupled interworking Well defined interfaces (as shown with cdma200 in Release 1.5 above) for GPRS/UMTS, cdma2000, and WiFI

WiMAX LTE Coupling Loosely Coupled system sharing Tightly Coupled system sharing Type HA, HAAA and Billing PDN-GW (HA), HAAA and Billing Mobility Supports handover between Supports handover between cdma2000 and WiMAX using cdma2000 and LTE using Mobile IP Mobile IP

Access No coupling at access network Tunnel between MME and RAN for Network layer exchanging control messages (pre- registration) Coupling Tunnel between S-GW and PDSN for exchanging data packets. Physical No coupling at physical layer eNB provides information about Layer 3GPP2 BTS’ (frequency, etc). Coupling eNB specifies measurements eNB determines when to handover to 3GPP2

HA PDN-GW PDN-GW AAA HSS HSS

MIP GTP PMIPv6

GTP GTP ASN-GW MME S-GW MME S-GW

R6 GTP GTP

BS eNodeB eNodeB

SS UE UE GTP PMIPv6 WiMaX LTE

WiMaX 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 MME, Serving Gateway, and PDN- MME, Serving Gateway (acts as and Home Agent in the GW. MME and Serving Gateway in MAG), and PDN-GW (acts as CSN the visited network, PDN-GW in LMA). MME and Serving visited or home network. Gateway in the visited network, PDN-GW in visited or home network Mobility 1) Intra ASN 1) No MME, S-GW relocation 1) No MME, S-GW relocation Scenarios 2) Inter-ASN – ASN 2) No MME but S-GW relocation 2) No MME but S-GW relocation anchored 3) MME and S-GW relocation 3) MME and S-GW relocation 3) Inter-ASN with ASN relocation Main Intra-ASN: Target ASN GTP Messaging (Update Bearer PMIP Messaging (Proxy Binding send Mobile IP re- Request) between Target S-GW Update) between Target S-GW Messages registration with FA COA and PDN-GW switches tunnel from and PDN-GW switches tunnel (target address) source to target from source to target

Miscellaneous Better suited to support for legacy Better suited for to handle UTRAN (UMTS/3G) mobility to HRPD. Verizon is primary driver

WiMaX LTE

Basis for Device Certificate in MS/SS for device Shared Secret in UE and AuC for device authentication authentication Security Main Certificate in SS USIM in UE Elements BS and ASN-GW eNodeB and MME AAA HSS/AuC Authenticatio EAP (TLS, TTLS) between SS and AKA (Authentication and Key Agreement) n and Key AAA with ASN-GW as NAS between UE and MME Derivation R6 Messages for key transfer DIAMETER Messaging between MME between ASN-GW and BS and HLR S1 messages for key transfer between MME and BS Miscellaneous Separate keys for Encryption and Creation of temporary identity for user id Signaling confidentiality Encryption (AES, 3DES) Separate keys for Bearer and Signaling Integrity (HMAC, CMAC) Separate keys for Encryption and Message Integrity EIA1 for Integrity and EIA2 for Encryption (SNOW 3G and AES) November_2008 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 103 Femtocell - Overview

December_2008 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 104 Mobile Operator Challenges Improving 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

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

Operator Management & Services

Licensed BTS Wireless Core Spectrum (MSC, SGSN) Cellular Network

Standard 3G Handset Femto Access Controller Licensed Spectrum

Internet Femtocell Broadband Access Point Residential GW Connection (<<100mW) (4 calls in 200kbps)

Characteristic UMA/Dual Mode Femtocell Requires broadband backhaul Yes Yes Requires new handsets Yes No Requires new radio CPE at No, though new CPE could Yes home optimize performance Handset mobility Phone can be used in any public Phone needs to be within hotspot, e.g. Starbucks 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 Yes/Eventually Dual-Mode - Yes Battery Life Not as good Better Bearer Voice Voice and Data

UMA/Dual Mode and Femtocell are complementary FMC applications

Femto Management System

FAP-MS FGW-MS

Fm Fg HPLMN Core Network

Fr Femto GW Subscriber Databases

Fb-cs

Fa CS core Radio Fb-ps i/f Femto Fixed Broadband Interconnect PS core Access FL Home Mobile GW device Point Fb-ims SeGW IMS core

HPLMN RAN

IMS Centric Embedded SIP Client (pre-IMS to CS core) Devices shall not be Embedded IMS Client (assumes deployed IMS) impacted by any access Radio Centric point Iub/IP architecture Split RNC Embedded UMA Client

UE Femto AP RAN Controller Core Network (3G Terminal) (SGSN, MSC)

Iu over IPSec Iuh over IPSec

Iu-cs MSC Iu-cs MSC AP AP Iu Femto Sec Concen Sec bb bb GW GW trator GW AP AP Iu-ps SGSN Iu-ps SGSN

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

HSS HSS

Iu or Iuh over IPSec Diameter Gm over IPSec Wm MSC-S

Iu MSC-S IWF-AS AP AP Femto Gm/Mw Gm Sec Sec ePDG bb GW GW CSCF bb GW CSCF

AP AP Gi Iu-ps SGSN

SIP/IMS (Client in Femto Gw) SIP/IMS (Client in Femto AP)

PDN PDN Gateway Gateway

Mobility Femto Mobility Serving SAE Femto Management Management Gateway Entity Gateway Entity s10

S1-c S1-u Internet

3GPP LTE IP Base Stations All-IP Femto Cells

Seamless Mobility

November_2008 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 114 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), www.femtoforum.org radio and interference management (wg2), network architecture (wg3) and legal issues (wg4) • Mobile Service Providers organization defining deployment guidelines and interoperability procedures www.gsmworld.com Published guidelines on Femto security and broadband network reqs

• 3G/GSM standardization Body Defining standards for 3G W-CDMA and SAE/LTE Femtocell services and architecture www.3gpp.org

•DSL standardization body Objective is to reuse TR-069 framework for zero-touch provisioning of www.broadband-forum.org Femtocell Access Point

•Mobile Service Provider organization looking at beyond 3G services and architecture

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 & Authorization Accounting Lawful Intercept Secure Access Additional Wireline Features to consider for converged EPC Residential Network Address Translation (NAT) Location Information

Mobility Not all devices need mobility or handover support Mobility features incur additional overall processing and transport cost Invoke mobility features only for devices that need it Policy Both 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 Authorization Wireline access networks typically either do not perform access authentication, or they are moving away from doing so Authorization 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)

Accounting 3GPP defines an overall charging infrastructure that supports both off-line and on-line charging On-line charging mostly relevant to wireless though Charging rules can be installed by AAA or PCC Off-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 Intercept 3GPP 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 Access Wireline access networks may be either trusted or untrusted The 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

Residential Network Address Translation (NAT) Residential NAT is assigned IP address from access network Mobility 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 Information Location 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)

November_2008 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 121 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 wireless Charging: 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 devices Examples: Single VoIP service (phone number) for both home and cellular Single e-mail account Single 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 services For example, dual-mode phone (WiFi) Fully integrated model enables QoS, single-sign on, etc. on the wireline access network ePDG model would be “over-the-top” – still enables session continuity

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

November_2008 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 123 Wireline Access using Untrusted Non- 3GPP IP Access:DSL Example SWx (DIAMETER) AN Access Node (DSLAM) HSS BNG Broadband Network Gateway MAG Mobile Access Gateway S6a PCRF PLMN Public Land Mobile Network (DIAMETER) RG Routing Gateway Rx+

Gxc (Gx+) Gx Gxa Gxb (Gx+) (Gx+) (Gx+) 3GPP S6b AAA (DIAMETER) 3GPP Serving S5 (PMIPv6, GRE) PDN Operator’s Gateway Gateway SGi IP Services Access S5 (GTP-C, GTP-U) UE SWm (DIAMETER) S2a S2b • Details of untrusted Non-3GPP IP (PMIPv6, GRE SWa MIPv4 FACoA) (PMIPv6, GRE) (TBD) Access not visible to the EPS ePDG - No integrated policy, QoS, SWn charging, etc. (TBD) Trusted - Wireline access is “just a bit pipe” Non-3GPP BNG • UE creates IPSec tunnel to ePDG, IP Access Untrusted and ePDG uses PMIP to PDN GW AN Non-3GPP IP Access • PCRF can install policies on ePDG for use in the EPC only (Gxb not RG UE specified in Release 8 though) SWu (IKEv2, MOBIKE, IPSec)

SWx (DIAMETER) AN Access Node (DSLAM) HSS BNG Broadband Network Gateway (next-gen BRAS per TR-101) S6a PCRF MAG Mobile Access Gateway (DIAMETER) RG Routing Gateway (DSL modem with routing) Rx+

Gxc (Gx+) Gx Gxa Gxb (Gx+) (Gx+) (Gx+) 3GPP S6b AAA (DIAMETER) 3GPP Serving S5 (PMIPv6, GRE) PDN Operator’s Gateway Gateway SGi IP Services Access S5 (GTP-C, GTP-U) UE SWm • BNG will need to be (DIAMETER) S2a S2b (PMIPv6, GRE SGi SWa enhanced with PMIPv6 MIPv4 FACoA) (PMIPv6, GRE) (TBD) functionality (MAG) ePDG • Not all devices and SWn (TBD) services require IP BNG Untrusted mobility; allow for simple Non-3GPP Trusted IP Access IP service to bypass PDN Non-3GPP IP Access Gateway AN STa (RADIUS, • Authentication and policy DIAMETER) SWu (IKEv2, interfaces in wireline MOBIKE, IPSec) access may not match RG

Gxa and STa UE Note: Refer to TS 23.402 for further details

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

S6a HSS

Mw, Mx Gm, etc. AF Wx*

{Rx+, Gq’, location, access} {S9, location, access, NAT} Gxc {PCRF, SPDF, location-proxy} {Gx, Ia} {Gxd, Ia}

{PDN 3GPP Serving SGi TE S5 Gateway, I-BGF Access Gateway PDN PDN C-BGF} S6c

AAA Server {Ta*,e5} 3GPP AAA (UAAF+PDBF) Server

{Gxa, Rq, Ia, a3,a4 location, access} S2a (PMIP, MIPv4) Note: Multiple (service specific) eBNG are likely to exist in a single deployment e3 e2 eBNG CNGCF eBNGeBNG (Trusted(Trusted non-3GPP non-3GPP (TrustedIP non-3GPPAccess) e1 e1 IP Access) Di, Ds, Iz CNG ARF IP Access)

“Evolved BNG” Note: Fast handover not yet considered

Pros Cons

Centralization of OAM&P personnel Core site failure will impact large and expertise number of users (signaling and data) Signaling and user-plane latency in Minimal signaling delay between MME large geographies and SGW/PDNGW Core site bandwidth requirements and Overall more efficient data plane underlying transport network processing by combined SGW/PGW bandwidth requirements

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

Pros Cons Regionalization of OAM&P personnel and MME signaling latency in large geographies expertise Core site failure will impact MME signaling Overall more efficient data plane processing for a large number of users by combined SGW/PGW Cannot establish new sessions Core site failure will generally not impact Cannot perform handover established sessions until handover Limited user plane latency Bandwidth requirements are distributed Traffic can be off-loaded regionally for cost and capacity savings

Central core site with • Centralized MMEs • Centralized standalone PGWs

Pros Cons Centralization and regionalization of Core site failure will impact large OAM&P personnel and expertise number of users (signaling and data) Signaling and user-plane latency in large geographies Core site bandwidth requirements and underlying transport network bandwidth requirements Less efficient overall data plane processing by separating SGW and PDNGW

November_2008 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 131 Deployment Models: Distributed core sites with • Regionalized MMEs • Regionalized combined Recommended Scenario SGWs/PGWs

MME

Pros Cons Regionalization of OAM&P personnel and None expertise Overall more efficient data plane processing by combined SGW/PGW Impact of site failure is limited to the region Limited signaling and user plane latency Bandwidth requirements are distributed Traffic can be off-loaded regionally for cost and capacity savings

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)

SGW/PGW scaling is dominated by IP packet logic and processing High bandwidth Large number of packets Data 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 processing CPU intensive Signaling 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 constraints Limited synergies by integrating MME with SGW and/or PGW: Primarily a reduction in signaling latency and processing between the MME and SGW Of 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 tunnel to GGSN)

MME

8 0 SAE Gw M b p 4Gbps s 40Gbps 80Mbps

s 4Gbps bp PDN Gw 80M SAE Gw eNodeB 10:1 50:1

MME

What is WiMaX? – The Business Case WiMaX Forum – The Organization WiMaX – The Architecture WiMaX Development – Feature Specification

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, and GSM (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 proposition is for operators to make money out of delivering services on the new Internet model WiMAX is free from the legacy wire line-cellular because it’s roots are derived from the Internet WiMAX 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 MBMS WiMAX 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

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

Oct 2006

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

The charter of the WiMaX Forum is to promote WiMaX by Developing 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)

A fully backward compatible evolution on standards and products Projections subject to change

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

Balloting P802.16Rev2/D5 A compilation of all 802.16 approved standards with new features for FDD Balloting P802.16j/D7 Relay Networks Enables relay of radio signals to eliminate coverage gaps Balloting P802.16h/D6 Coexistence Provisions for operation in un-licensed bands Completed 802.16m Performance Evaluation Document The 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)

16m Completion

expected by end of 2009 *Minimum Requirements to be Exceeded by 16m

Alcatel-Lucent Navini Alvarion NEC AT&T NextWave Telecom Bell Canada Nokia Bridgewater Systems Nortel Networks Cisco Systems Posdata Clearwire Redline Communications Ericsson Samsung Fujitsu Nokia Siemens Networks Huawei Technologies SOMA Networks Intel Corporation Sprint KDDI Starent Network KT Corp. Telecom Italia Motorola Telsima ZTE Corporation

Applications 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.

R2 NAP vNSP hNSP

ASN BS R6 ASN R1 GW MS BS R3 CSN CSN R6 AAA AAA proxy PF R5 PF R4 HA ASN BS R6 ASN R3 GW Network Elements: BS R6 MS: Mobile InternetInternet Subscriber Station BS: Base Station ASN GW: ASN Networks: Operators: Gateway (router) NAP: Network Access Provider HA: Home Agent ASN: Access Serving Network vNSP: Visited Network SP PF: Policy Function CSN: Connectivity Serving Network hNSP: Home Network SP

November_2008 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 154 Macro & Micro Mobility: 802.16e Full Mobility Model Use WiMaX Forum standard interfaces Internet • R4 for Inter FA handoff (fast-handoff) HA • R6 for micro mobility AAA • Rx for RRM interface R3 Radio Independent Functionality ASN-GW ASN-GW R4 (optional) Radio FA/PMIP FA/PMIP • Fast Hand-off for Mgmt Micro Mobility R6 R6 Rx

IP IP IP IP IP BS BS BS BS BS

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)

IP-CS

ASNGW HA

R6 GRE EoMPLSMobile IP

Control (UDP 2231/R6) PMIP .16eCtrl .16eCtrl ASNctrl ASNctrl CSNctrl CSNctrl MAC MAC IP IP IP IP PHY PHY LNK LNK LNK LNK PHY PHY PHY PHY IP-CS Data Path (PMIP) IP IP IP IP-CS IP-CS GRE Micro Mobility GRE MIP Macro Mobility MIP LNK MAC MAC IP IP IP IP PHY PHY LNK LNK LNK LNK

ASN Description Pro Con Profile Profile A Centralized platform Able to provide simplified pico-cell Difficult Interoperability between BS and Separate BS and ASNGW Able to provide soft handover ASNGW from different Split RRM: RRA at BS Fewer backhauls for RRM vendors messages and RRC at ASN-GW Heavy workload at ASN- GW Fewer vendors

Profile B Distributed platform Simple architecture Difficult to customize IP and wireless functions for Combined BS and ASNGW Suitable for small-scale operators deployment Expensive for large scale deployment Profile C Distributed platform Able to provide simplified pico-cell Extra backhauls for RRM messages Separate BS and ASNGW Open – multi -vendors can supply BS and ASNGW RRM at BS

November_2008 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 157 WiMAX Profiles Deprecated A BTS ASN ASN-GW Profile A: Central radio resource BTS management in ASN-GW approach [BSC] Profile B: Closed interfaces favor radio BTS network (BS) vendors PHY and partly MAC in BTS Profile C: Open interfaces with separation between radio and network functionality Handover-Control (RRM) in ASN-GW Routing and AAA/Paging in ASN-GW

B BS ASN C BS ASN ASN BS BS GW unspecified BS decomposition BS Most ASN functions in BS All radio-specific functions in BS BS anchored by standard router Handover-Control (RRM) in BS Inter-BS control over Ethernet Routing and AAA/Paging in ASN-GW

CPECPE ASPASP MPLSMPLS CORECORE NSPNSP SERVICESSERVICES R2

Residential P P Voice BS+ASNG_FABS+ASNG_FA R3 ISP Residential PE R1 Internet

PE Corporate R4 PE P P Business BS+ASNGBS+ASNG BRAS FAFA Home Agent AAA

-HO - DHCP Proxy/Relay - Data Path 1 & 2 - MIP FA R1 - Authenticator - Location Register R3 - Key Rec. &Dist. - PMIP Client/Assist - Context - AAA Client - RRA + RRC -SF Auth & Mgt

CPECPE ASPASP MPLSMPLS CORECORE NSPNSP SERVICESSERVICES R2

Residential P P Voice

R6 R3 ASNG/FAASNG/FA ISP Residential PE R1 Internet

BSBS PE Corporate PE P P Business R4 ASNG/FAASNG/FA BRAS Home Agent AAA R4 -HO - Data Path 1 & 2 -HO - DHCP Proxy/Relay - Authentication - Data Path 1 & 2 - MIP FA R1 Relay R6 - Authenticator - Location Register R3 - Paging Agent - Key Distributor -PMIP Client - Key Receiver - Context - AAA Client - Context - SF Authorization - Paging Controller - RRA + RRC - SF Management BS ASN-GW

CWG Working on the logistics of the certification program Wave 2 certification CRSL 2.2 available for testing scheduled for August 2008 The plug fest in May 2008 did include beamforming and MIMO NWIOT plug fest planned for Nov. 2008 RWG WiMAX accepted into IMT-2000 family of products Analyzing world-wide radio parameters requirements (spectral mask) for MS Responding to inquiries from various countries TWG achievements Developing “Profile 1.5” for FDD and TDD based WiMAX Improving and clarifying “Profile 1.0” and related tests for TDD-based WiMAX Developed new tests for “Radiated Performance” of antennas Developed coexistence mechanism of WiMAX with WiFi and Bluetooth Started technical work on using 700 MHz spectrum for WiMAX

Release 1.0 Capabilities Network 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

November_2008No ©standardized 2006 Cisco Systems, Inc. All rights functional reserved. Cisco Confidential decomposition inside CSN 164 WiMAX Authentication/security Key Exchange EAP is method used ASN 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 recompute additional AKs when the SS/MSS moves to another Base-station. Support for Un-authenticated user – 911 or Pre-paid for example

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, TR69 3GPP2-WiMAX Interworking – Loosely coupled with dual radio only Normative 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-CSCF Emergency Services (E911) – Capabilities needed to connect to an E-CSCF Lawful Intercept (LI) – Generic Overview and North American LI Policy Control (PCC) – Infrastructure needed to deliver policy rules and control QoS Dynamic QoS – Activation/deactivation of pre-provisioned service flows with no PCC Diameter – Adding protocol elements to match Radius Ethernet Services – Ethernet CS over Service Flow paralleling IP CS over SF Handoff Data Integrity – Ensuring uninterrupted packet flow for mobility Robust Header Compression (RoHC) – Reducing packet size of the air interface

Service Flows: QoS Category Applications QoS Specifications Mechanism defined in Mobile WiMAX to UGS VoIP • Maximum provide QoS Unsolicited Grant Sustained Rate Service • Maximum Latency Uni-directional flow of packets • Jitter Tolerance associated with certain defined QoS rtVR Streaming Audio or • Minimum parameters for traffic Real-Time Variable Rate Video Reserved Rate Service • Maximum Connections: Sustained Rate • Maximum Latency Unidirectional logical link between BS • Traffic Priority and CPE ErtVR Voice with Activity • Minimum Each connection is associated with a Extended Real-Time Detection (VoIP) Reserved Rate service flow delivering the necessary Variable Rate Service • Maximum QoS over the air interface Sustained Rate • Maximum Latency Packet Classifiers: • Jitter Tolerance • Traffic Priority Each service flow also has packet nrtVR FTP • Minimum classifiers associated with it to Non-Real-Time Variable File Transfer Protocol Reserved Rate determine criteria used by the MAC Rate Service • Maximum layer to associate packets into service Sustained Rate flows • Traffic Priority BE Data, Web Browsing, • Maximum Mobile WiMAX scheduling based on Best-Effort Service etc. Sustained Rate • Traffic Priority QoS service Flows associated with each packet

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

Specifications under development: DSL Interworking – WiMAX access network as replacement for DSL infrastructure IWK 3GPP2 Single Radio – Optimized HO for single radio to/from HRPD networks IWK 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 networks MCBCS-DSx – R1 Link-layer-controlled multicast/broadcast streaming services Multicast Broadcast Services (MCBCS-App) – R2 Application-controlled streaming services Mobility Restriction – Additions to minimize HO for Fixed/Nomadic Spectrum regulations PMIPv6 – R3 Mobility support based on PMIPv6 Universal 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

Release 2.0 Completed Requirements DRMD Phase 1 – Metrics available on current chip-set Multihop Relay BS (802.16j) – Defines relay use to extend outside radio coverage Multi-Media Session Continuity (MMSC) – SIP sessions across WiMAX, WiFi, LTE Modernized Network Management (NMR) – Specifies FCAPS management controls Connection Manager API – Defines connection manager to WiMAX Modules interaction IPv4-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/SW Femto-Cell – Defines use of residential access points to extend radio coverage indoors Emergency Telecommunications Service (ETS) – Support of government responders Release 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