Looking Beyond the Network Layer · IP Video economics clarifying, accelerating spend ... Gn HSS...

© 2007 Cisco Systems, Inc. All rights reserved. Cisco Confidential 1

Looking Beyond the Network Layer

Asia Technology Forum December 4-5, 2008

Vojislav VuceticSP Marketing, Industry and Technology Marketing Group


Agenda

Service Providers Business ObjectivesIndustry and Standards DirectionsService Providers Examples

Verizon Wireless A-IMSAT&T CARTS

Wireline and Wireless Capabilities ComparisonWireline-Wireless Converged ArchitectureSummary


IPIP

IntelligenceFlexibilityAdaptability

Meeting Service Provider Challenges To Make the Experience Provider Transition

DifferentiationLoyaltyRevenue

ServicesServices

EfficienciesEfficienciesOpExCapExProfits

ControlControlServiceNetworkBusiness

© 2007 Cisco Systems, Inc. All rights reserved. Cisco Confidential 4Source: CIBC, Cisco IBSG

Business Trends Impacting Service Providers

Wireline carriers challenged by wireless substitution and VoIP - looking at femtocell as broadband voice alternativeWireline broadband subscribers outpacing cable broadband subscribersIP Video economics clarifying, accelerating spend

Cable CAPEX peaking, subscriber growth slowingCable Labs Advertising RFP - search for new business modelsRespond to satellite HD competition via 1GHz upgrades and SDV

Sub growth slowing in developed markets / growing in emerging marketsWiMax threat driving HSPDA accelerationEnd-to-end IP architecture gaining support (e.g. A-IMS)

OTT voice/video disintermediates SPs in value chainP2P traffic growth degrading SP customer experiencePartnerships with SPs create coopetition model

Cable MSOsCable MSOs

Over-the-Top CarriersOver-the-Top Carriers

Wireline CarriersWireline Carriers

Wireless CarriersWireless CarriersIntegrated Communications

Provider

Integrated Communications

Provider

Experience Provider

Experience Provider


Winning Ingredients for Experience Providers Long-Term Growth and Profitability Require Innovation

Build Intelligent,Scalable IP NGN

Develop New Business Models and Partners

Improve the Customer Experience

Focus on New Services and Markets


Services in a SP Multiservice network

Consumer Business LegacyservicesWholesale

InternetVoice / Video / data

VoicePSTN / Multimedia

VideoOver the Top

Managed Service

Mobility

PSTNMigrate

Mobile RAN backhaulIP transition

TDMMigrate and evolve to

Ethernet

ATMMigrate and evolve to

Ethernet

F/REvolve to Ethernet

TDM/ATM Ethernet

L2 VPNsPt2Pt

Pt2MPtMPt2MPt

L3 VPNsConnectionless

Value-add ServicesBased on L3 visibility

TDM/ATM Ethernet

L2 VPNsPt2Pt

Pt2MPtMPt2MPt

L3 VPNsL2TP

Connectionless


NGN Standards and Industry Directions


ITU-T Y.2001 Definition of NGN

Next Generation Network (NGN):a packet-based network able to provide telecommunication services and able to make use of multiple broadband, QoS-enabled transport technologies and in which service-related functions are independent from underlying transport-related technologies.

It enables unfettered access for users to networks and to competing service providers and/or services of their choice. It supports generalized mobility which will allow consistent and ubiquitous provision of services to users.


ITU-T NGN Architecture

Service ControlFunctions

Transport stratum

Service stratum

ControlMediaManagement

Service UserProfiles

Transport User Profiles

ANI

Transport Control Functions

Resource and Admission

Control Functions

Network Attachment

Control Functions

NNIUNI

Application Support Functions & Service Support Functions

Applications

Transport Functions

End-UserFunctions

OtherNetworks

Service ControlFunctions

Transport stratum

Service stratum

ControlMediaManagement



Transport User Profiles

ANI

Transport Control Functions


Control Functions


Control Functions

Network Attachment

Control Functions

Network Attachment

Control Functions

NNIUNI

Application Support Functions & Service Support Functions

Applications

Transport Functions

End-UserFunctions

OtherNetworks

NGN Architecture Overview (ITU-T Y.2012)


TISPAN Sub-systems

Functional Architecture:Based on well defined sub-systems, functional blocks and defined interfaces

Functional blocks do not equate to devices; one or more functions can reside in a single device and one functional block to be spread over multiple devices.

Applications

Subsystems

RACSResource Admission Control Subsystem

UserEquipment Access Network TISPAN NGN Core

NASSNetwork Attachment

Sub-System

Application Functions (Servers – like Presence Servers, Conferencing Servers, Supplementary Voice services – but also Data Applications like Portals etc.)

Two types of application functions:AF-1 applications: don’t use Service Sub-systemsAF-2 applications: use Service control sub-systems

Application Functions (Servers – like Presence Servers, Conferencing Servers, Supplementary Voice services – but also Data Applications like Portals etc.)

Two types of application functions:AF-1 applications: don’t use Service Sub-systemsAF-2 applications: use Service control sub-systemsRegistration and initialisation of User Equipment

Access Session establishmentNetwork Level ID and authenticationTypically: DHCP-Server, RADIUS-Server, CPE-Config Server.

Registration and initialisation of User EquipmentAccess Session establishmentNetwork Level ID and authenticationTypically: DHCP-Server, RADIUS-Server, CPE-Config Server.

Resource Handling (QoS, Security/NAT) for Access Session (PPP/IP-session) and Application Session (SIP, …):

Resource Handling (QoS, Security/NAT) for Access Session (PPP/IP-session) and Application Session (SIP, …):

Multiple Subsystems defined – using the same transport infrastructure: Core IMS subsystem(the most prominent one)PSTN/ISDN emulation subsystem(PES)

Possible future additions:Streaming SubsystemContent broadcast subsystem

Multiple Subsystems defined – using the same transport infrastructure:Core IMS subsystem(the most prominent one)PSTN/ISDN emulation subsystem(PES)

Possible future additions:Streaming SubsystemContent broadcast subsystem

Transport Functions:Access Switches, DSLAMs,BRAS, …

Transport Functions:Access Switches, DSLAMs,BRAS, …

End Devices (Phone, PC, …) as well as Access Gateway/CPE

End Devices (Phone, PC, …) as well as Access Gateway/CPE


Reference Architecture of the IP Multimedia Core Network Subsystem (TS23.228)

P-CSCF

S-CSCFMGCF HSS

Cx

IP Multimedia Networks

IM-MGW

CS Network

Mn

Mb

Mg

Mm

MRFP

Mb

Mr

Mb

Legacy MobileSignaling Networks

I-CSCF

Mw

Mw

Gm

MjMi

BGCF

Mk

Mk

C, D,Gc, Gr

UE

Mb

Mb

Mb

MRFC

SLF

Dx

Mp

CS

CS

IMS Subsystem

Cx

Mm

AS

ISC Sh

Ut

BGCF Mg Dh


Basic Configuration of a 3GPP Access PLMN supporting CS and PS services (using GPRS and EPS) and interfaces – TS23.002

BSS

BSC

RNS

RNC

CN

Node B Node B

IuCS IuPS

Iur

Iub

USIM

ME

MS

Cu

Uu

MSC server SGSN

Gs

GGSN GMSC server

GnHSS

(HLR, AuC)

Gr/S6d

GcC

D

E

EIR

F Gf

GiPSTN

IuCSIuPS

VLR B

Gp

VLR G

BTS BTS

Um

RNC

Abis

SIM

SIM-ME i/f or

MSC server

B

PSTN

cell

CS-MGW CS-MGW

CS-MGW

Nb

Mc Mc

Nb

PSTN PSTN

Nc

Mc

A Gb

Rx

Nc

PCRF Gx

eNB eNB

E-UTRAN-Uu

PDN-GW

MME

S-GW

E-UTRAN

X2

S4

S8 S5

SGiS9

S1-U

S1-MME

S6a

S13

Gx

Gxc

S11

S12S3

3GPP Release 8


Service Providers NGN Directions

Verizon Wireless A-IMS Evolution and AT&T CARTS


ServicesData

Manager

Charging

SecurityManager

BREWSDP

OpenDevice Initiative

VideoAS

SIPAS

SIPAPP3rd Party

AS/SDP

Service Broker

ApplicationManager

Wireline LTE EV-DO

MME RNCRNC

BTSeNB

Wireline IP Layer IMS Non-IMS

SIP/IMS Services Non-SIP/Non-IMS ServicesFollowA-IMS/3GPP Rel 8Functional Grouping

IMS Session Control

Bearer/IP Transport

WSGW SGW HSGW

ENUMServer

SIPAPP

SDP

AppEnablers

(e.g., Presence)

MediaServer

PDN Gateway

Wireless

PCRF

SDP

WEBAPP

Non-SIPAPPNon-SIP

APPNon-SIPAPP

SpecificNon-SIP

APPSpecificNon-SIP

APP

Note: This slide courtesyof Verizon (4/19/08)

Verizon Target Converged Architecture


What AT&T Expect From the Network of the Future

Source: Siroos Afshar, AT&T, NXTcomm, June 18, 2007


Main GoalProvide a single, common, and shared infrastructure that facilitates the development of real-time services (e.g., voice, video, multi-media)Enables highest quality and availability, the shortest possible TTM, and the lowest cost of operations and maintenance

Architecture PrinciplesTransport via a single, global, IP/MPLS-based networkUniform service support within AT&T network.Flexible and cost-optimized. Enable fast and easy creation of new servicesSupport easy deployment of externally developed services.Build in the infrastructure security, high-availability, and low cost of operation

AT&T CARTS


AT&T CARTS – Common Architecture for Real-Time Services

CARTS is based on 3GPP/IMS Source: Hank Kafka, VP-Network Architecture,3G Americas Executive Briefing, November 14, 2007


Wireline-Wireless Convergence


3GPP Access

Non-Roaming Release 8 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)


Wireless/Wireline Convergence

The EPC is not limited to supporting 3GPP IP Access NetworksOther wireless access networks are supported (e.g. CDMA (in Release 8) and WiMaX in future)Wireline access networks can be supported as well

Some features provided by the EPC are applicable to a wireline access network

MobilityPolicy Authentication & AuthorizationAccountingLawful InterceptSecure Access Application Control (e.g. IMS)

Additional Wireline Features to be considered for a converged EPCResidential Network Address Translation (NAT)Location Information


EPC Features and Wireline RequirementsMobility

Not all devices need mobility or handover support (nomadic vs. mobile)Mobility features incur additional overall processing and transport costInvoke mobility features only for devices that need it

PolicyBoth wireless and wireline access networks support policy and charging infrastructure Existing standards (3GPP PCC and ETSI TISPAN) are reasonably similarOngoing work to harmonize capabilities and interfaces (Rx and Gq’)Re under definition in TISPAN (Diameter-based)

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 TS23.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 accounting (eventually DIAMETER)On-line charging is based on DIAMETER Credit-Control (DCCA)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 relevant content (and other information) to law enforcement agency

EPC Features and Wireline Requirements


EPC Features and Wireline RequirementsSecure Access

Wireline 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 servicesSolves some residential NAT traversal issues when using network-based mobilityCan 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 networksMay consider skipping ePDG for such trusted IP access networks


Additional Wireline RequirementsResidential 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 Possible 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 parallelarchitecture and interfaces (see e.g. ETSI TISPAN CLF function)


One Approach to Converged Architecture


Consolidated Wireless and Wireline in 3GPP EPS Architecture

Two different strategies for supporting wireline access networks in the EPS:

Treat the wireline access as an untrusted Non-3GPP IP AccessTreat the wireline access as a trusted Non-3GPP IP Access


S2a(PMIPv6, GREMIPv4 FACoA)

3GPP Access


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

PDN Gateway

Serving Gateway

PCRF


HSS

S2b(PMIPv6,

GRE)

S5 (PMIPv6, GRE)

S6a(DIAMETER)

S5 (GTP-C, GTP-U)

SWx (DIAMETER)

ePDG

3GPPAAA

SWn(TBD)

S6b(DIAMETER)

SWm(DIAMETER)

SGi

SWa(TBD)

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 GWPCRF can install policies on ePDG for use in the EPC only (Gxb not specified in Release 8 though)

Untrusted Non-3GPPIP Access

Gxc(Gx+)

Gx(Gx+)

Gxb(Gx+)

Gxa(Gx+)

Rx+


3GPP Access

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

PDN Gateway

Serving Gateway

PCRF


HSS

S2b(PMIPv6,

GRE)

S5 (PMIPv6, GRE)

S6a(DIAMETER)

Untrusted Non-3GPP IP Access

S5 (GTP-C, GTP-U)

SWx (DIAMETER)

STa (RADIUS, DIAMETER)

Note: Refer to TS 23.402 for further details

ePDG

3GPPAAA

SWn(TBD)

S6b(DIAMETER)

SGiUE

UE


BNG

AN

RG


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 GatewayAuthentication and policy interfaces in wireline access may not match Gxa and STa

SGiS2a(PMIPv6, GREMIPv4 FACoA)

Gxc(Gx+)

Gx(Gx+)

Gxb(Gx+)

SWm(DIAMETER)

SWa(TBD)

Gxa(Gx+)

Rx+

AN Access Node (DSLAM)BNG Broadband Network Gateway

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

with routing)

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

We have been collaborating with a large US-based service provider on this Several other carriers and vendors are interested in this topicThe initial works already started in 3GPP SA1 and BBF

The following slides provide a very high-level overview of such a possible merged architecture


{Gxa, Rq, Ia, location, access}

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

I-BGF


IP Access)

CNGCF e2e3

a3,a4

e1

Note: Multiple (service specific) eBNG are

likely to exist in a single deployment

{PDN Gateway,

C-BGF}

{Gx, Ia}

Wx*

{Rx+, Gq’, location, access}

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

location-proxy} {Gxd, Ia}

PDN


3GPP and non-3GPP Accesses

GPRSAccess

HSPAAccess

LTEAccess

CDMA2000

Access

WiMaXAccess

NGN (TISPAN)Access

WiFiAccess

CableAccess

GPRS PacketCore

Evolved Packet Core (EPC)

Common IMS

BBFAccess

3GPP and BBF need to work together to support the BBF access into the EPC core


Summary

Network Architecture are aligning towards an all IP architecture

Common application execution environment already defined (i.e. IMS and non-IMS)

New opportunity for the service provider to think their network architecture

Share a common IP Core and control layerDedicated access components

The evolution to converged architecture is the activity for standards organizations and forums

Looking Beyond the Network Layer · IP Video economics clarifying, accelerating spend ... Gn HSS...

Documents

Transcript of Looking Beyond the Network Layer · IP Video economics clarifying, accelerating spend ... Gn HSS...