Unified RAN Backhaul Architecture

8/2/2019 Unified RAN Backhaul Architecture

1/57

2009 Cisco Systems, Inc. All rights reserved. Cisco Confidential 1

Unified RAN BackhaulArchitecture

Karrthik VenuConsulting Systems EngineerCisco Systems


2/57

2006 Cisco Systems, Inc. All rights reserved. Cisco ConfidentialPresentation_ID 2

Agenda for the Session

Market and Technology

Trends and Evolution

Unified RAN Backhaul Architecture

Four Step Migration

Requirements

Building Blocks

Unified RAN Backhaul Industry

Standards and Certification

Products and Services

Summary and Wrap up


3/57


Voice ARPU down, although cell phones to be supported are growing fast(2.5 B Phones in 2006, going to 5 B in 2012), looking for data revenuegrowth

Cost-per-bit of traditional circuit based backhaul is too high to supportrequired expansion

Gigabit Ethernet costs less than an STM1 while providing far morebandwidth

Operators would like to cap investment in legacy technologies (TDM, ATM)in favour of an architecture with a future for Enterprise and Residential alongwith Future Mobile Services

RAN bandwidth requirements grow by an order-of-magnitude to support 3Gand 4G data services

HSPA, IPTV, Video Streaming, Gaming, etc.

IP Vendors entering Mobile Space with acquisitions & partnerships

Radio Vendors looking to go all IP/Ethernet route in some cases (cf. NSNNode B plans)

Market Trend


4/57


APAC Mobile Traffic Growth and Trends

Implication:APAC constitutes Majority of the

Global Cell sites


5/57


Implication:Mobile Backhaul consists of a

mixture of Connection Types. Air

connectivity dominates in Asia

Implication:Mobile Backhaul will need

to support a mixture of

Connection Protocols


6/57


Wireless Broadband EvolutionDriving backhaul capacity

Rel-99

WCDMA

Rel-5

HSDPA

Rel-6

HSUPA

Rel-7

MIMO 2x2

Rel-9

OFDMA

DL: 384 kbps

UL: 384 kbpsDL: 1.8 14.4Mbps

UL: 384 kbps

2007 2008 2009 2010 2011+

DL: 1.8 14.4 Mbps

UL: 5.7 Mpbs

DL: 28 Mbps

UL: 11 Mpbs

Rel-8

64 QAM

DL: 42 Mbps

UL: 11 Mpbs

DL: 100 Mbps

UL: 50 Mpbs

Rel-8

LTE

~10Mbps throughputper 1+1+1 site (5MHz)

~80 Mbps per

1+1+1 site

(10MHz)

HSDPA:16 QAM DL14.4 Mbps

HSDPA:Always on

scalingHSUPA:5.7 Mbps

HSDPA:64 QAM or

MIMO

HSUPA:16QAM

Always on

scaling

HSDPA:64 QAM and

MIMO

OFDMA

BW Growth 100% yr/yrAll-you-can-eat data plansBillions of devices/subs/flows

Broadband apps going mobileFixed-mobile convergence Integrated wireline/wireless PE

Scale Trends


7/57 2006 Cisco Systems, Inc. All rights reserved. Cisco ConfidentialPresentation_ID 7

3GPP Mobile Network ArchitectureIncrease Throughput and Reduce Latency

BSC

BTS

GMSC

MGW

PSTN Internet

CS

Domain

GMSC

RNC

GGSN

MGW SGSN

PSTN Internet

Node B

CS

Domain

PS

Domain

GMSC

RNC

GGSN

MGW

cSGSN

PSTN Internet

Node B

CS

Domain

PS

Domain

eNodeB

PSTN Internet

PS

Domain

Data VoIP

SAE-GW

MME

DirectTunnel

DirectTunnel

Pre Rel 99 2G GSM GPRS/EDGE

Circuit Switched Voice/Data

T1 Access / CHOC Core

Integrated CTL/Data Plane

Rel 99 3G UMTS

Packet Switched Data

ATM-IMA acc./CHOC Core

Integrated CTL/Data Plane

Rel 4-7All IP Core introduced (R4)

Separation of Data/Ctl planes (R7)

Ethernet Transport (R5)

Radio Ctl pushed toward NodeB

Direct Tunnel/Flat IP introduced

Rel 8+ LTE /SAE Specified

CS Domain collapsed -> VoIP

Ctl plane fully decoupled

Direct NodeB Connectivity



Architecture Requirements

From 2G/3G To LTE

888



Current RAN Architecture

RNC

SDHATM

Switch

2G BTS

3G Node B

BSC

ChSTM1

STM1c

2G BTS

3G Node B

2G BTS

3G Node B

2G BTS

3G Node B

2G BTS

3G Node B



IP, Metro

1. Deploy Alternate (IP) backhaul forData Traffic

RNC

SDH

2G BTS

3G Node B

BSC

ATMSwitch

ChSTM1

STM1c

2G BTS

3G Node B

2G BTS

3G Node B

IP, Metro,

xDSL

Cisco

7600

Cisco 7600

MWR 2941

Voice & Clocking

Data



2. Deploy IP Node B

RNC

SDH2G BTS

3G Node B

BSC

STM1c

2G BTS

3G Node B

2G BTS

3G Node B

IP, Metro,

xDSL

Cisco

7600

Cisco 7600

IP Node B

Cisco 7600

IP, Metro,xDSL

Cisco 7600

ME3400E

IP Node B

MWR 2941

MWR 2941IP Node B

IP, Metro



IP, Metro

3. Migration into IP RANEnter the Pseudo wire

RNC

SDH2G BTS

3G Node B

BSC

STM1c

2G BTS

3G Node B

2G BTS

3G Node B

IP, Metro,

Cisco7600

IP Node B

Cisco 7600

IP, Metro,xDSL

Cisco 7600

ME3400E

IP Node B

MWR 2941IP Node B

MWR 2941

IP, Metro,

Cisco 7600

MWR 2941



Network OffloadGGSN/PGW

MPC/

EPC

Internet

Offload

Call

Localization

RAN-CDN

AIR

IP-RAN

Standard Services

Video

NB Wi-Fi

3G/

4G
http://images.google.com/imgres?imgurl=http://www.ep-momentum.eu/Portals/0/icons-logos/youtube-logo.png&imgrefurl=http://www.ep-momentum.eu/&usg=__OKgxdiKH0EF5ruBXZjqukEdiz_4=&h=424&w=640&sz=191&hl=en&start=3&um=1&tbnid=NLKLllaxCevhfM:&tbnh=91&tbnw=137&prev=/images?q=youtube&hl=en&rlz=1T4GGIH_enUS253US253&sa=N&um=1


14/57 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicPresentation_ID 14

Typical installed Backhaul Architecture

4xE1

4xE1

16xE

1

4xE1

4xE1

32xE1

4xE1

4xE1

2xSTM-1

STM-4/16

STM-16/64

BSC

RNC

BSC

Cell sites and Access Aggregation and controller sites

HSPA < 7.2 Mbps:

3-4 xE1 for 3G1 xE1 for 2G Leased Linesmight still be an

affordable solution

Aggregation in TDM / SDHno statistical gain

Fiber rings

based on SDH ideal

for real-time traffic

ATM

aggregation

PDH MWR

typically with up

to 32xE1



Evolution towards Packet backhaul

BSC

RNC

BSC

Cell sites and Access Aggregation and controller sites

3G Packet or Hybrid IuB

LTE

1xE1 for 2G Packet Leased

Lines

Statistical Aggregation

Packet rings

Packet MWRadaptive

Modulation



A closer look to Microwave domain

AccessMW ring

AggregationMW ring

Aggregationfiber ring

Controllersite

AccessMW tree

Legacy MW

Packet MW

fiber

ACCESS

AGGREGATION

Packet MW access

High spectral efficiencyAdaptive modulation

Packet MW access ring

High spectral efficiencyRing protection

Support of PWE for

legacy TDM and ATM

PacketIuB / LTE

ATM IuB

Packet Microwave RingTraffic protection

Pre-aggregation

1+1 MW protection



LTE/SAE System Components

X2 inter base station interfaceSCTP/IP Signalling

GTP tunneling following handover

S1-c Base Station to MME interfaceMulti-homed to multiple MME pools

SCTP/IP based

S11 MME to SAE GWGTP-c Version 2

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

S5 SAE GW to PDN GWGTP or PMIP based macro mobility

SGW

SGW

MME GW

MME GW

PDN GW

E-UTRAN Control Plane with 2G/3G

interworking

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

eNodeB

Simplified and flattened RANwith IP to the edge

Radio resource management, incl. handovers Interacts with MME for all signaling planeprocessing Exchanges user plane traffic with Serving GW

Subscriber-aware Data Plane anchoring for allAccess Networks

Common anchor point for all IP AccessNetworks (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

Data Plane anchoring for 3GPP AccessNetworks with 2G/3G interworking

Anchor point for 3GPP IP Access Networksonly (2G/3G/LTE) Processes all IP packets to/from UE

Controlled by MME Uses network-based mobility towards PDNGW (GTP or PMIPv6)



LTE Network Requirements

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

SGW

SGW

MME GW

MME GW

PDN GW

No longer Pt-to-Pt relationship withmultipoint requirements

Network intelligence for advanced

services and traffic manipulation

X2 interface introduces directcommunication between eNodeBs

More Distributed architecture for GW

placement & local break-out

Different traffic types with differenttransport requirements



LTE/SAE Architectural Requirements

LTE/SAE factors Network Requirement

Direct X2 interface & handover between eNodeBs Distributed network intelligence

Distributed architecture, increased Bandwidth,

traffic offload/Insertion/Caching

Distributed Data-plane Gateway intelligence

IPSec requirement in the backhaulIPSec gateways (IKEv2) requirement in the

Aggregation

Authentication and Security framework Intuitive and secure networking

IPv6 framework fully defined IPv6 and IPv4 support mandatedMulticast requirements Multicast and Multicast VPN support

Synchronisation (Freq. & Phase) requirements Packet and Physical Layer options

Strict Latency requirement (LTE/SAE standard) Optimal platform and network design required

Intelligent H-QoS requirements Extensive UNI QoS capabilities required

Wholesale offering with Multi-Operator Core Network Intelligent network identification and forwarding

Simplified Fast Convergence optionsOptimised and simplified IP/MPLS fast

convergence

OAM mechanisms & Performance monitoring Troubleshooting and fault isolation/SLA metrics



CellSite

AccessLayer

MetroEthernetLayer

GERingor

Ptto

Pt

BSC RNC

Option1

Option3

Option2

10GEor

IPoDWDM

Accessnode E

NPE

CoreMetro

Option5

Option4

Backbone

Layer

SGW

NativeL2 L2VPN L3 MPLSVPN

L2VPN L2VPN L3 MPLSVPN

NativeL2 L3 MPLSVPN

L2VPN L3 MPLSVPN

IP L3 MPLSVPN

Unified RAN Deployment Scenarios

Option

6 L3 MPLS

VPN



Switched versus Routed Transport

In Switched Transport , One P2P connection is established foreach NodeB to reach RNC.

Each IP NodeB is assigned to a different IP subnet from RNC.

IP NodeB sends ARP end-to-end to reach RNC to learn RNCs MAC

IP RNC is become IP gateway of IP NodeB. For any traffic sent by one Node B destined to any subnet, thetraffic is required to be routed at the RNC.

The P2P connection provide full control of each IP NodeB/RNC communication, and perfect isolation amongIP NodeBs.

However, foreach new connection or connection to be modified, the network connection is required toestablish, not only the VLAN ID is to be re-assigned but also the IP address of radio equipment.

RAN modification/expansion causes both network and radio to change accordingly

In Routed Transport , all NodeB and RNC are working independently on different IP subnets.

If adding new RNC or a NodeB is re-attached to another RNC for more resource, there is no network re-

configuration such as VLAN tear-down and reconfigure to accomplish this service change. On NodeB side,also no need to reconfigure the VLAN number nor the IP gateway.

Using IP routing in the network, it will provide ARP resolution and routing functions. In return, the networkrequirements on radio equipment will be lessen.



Survey Question #1

How do you see various Unified RAN backhaularchitectures evolving ?

We see a clear need and trend of migration from TDM to IP for2/3/4 G and Next Generation Data Services

We prefer using existing TDM and ATM network with EoSDH for

Mobile DataWe need to understand the value of Unified Backhaul for Any Gservices from TCO / Service Architecture point of view

We want a seamless migration leveraging existing architectures



Unified Backhaul Synchronization

232323



Synchronization Requirement



Synchronization1: SyncE

Synchronous Ethernet (SyncE) offers End to End Transport ofFrequency Synchronization

Each device in the Aggregation and Access Network will need tosupport SyncE

SyncE is transmitted on the Physical Layer, hence is not subjectedto Switching Delay and Variations

SSU act as Slave Tier in SyncE Hierarchy

Fiber Interfaces to be used vs Copper

Synchronization of Phase (e.g. for E-MBMS) is still to beStandardized for SyncE

Agg RNC

Aggregation

Packet Network

SyncE (SSU)

Agg

SyncE

BTS

SyncE (PRC)


26/57

2009 Cisco Systems, Inc. All rights reserved. Cisco PublicPresentation_ID 26

Synchronization2: IEEE1588-2008

Centralized Grand Master Clock (PRC) at Aggregation

Deployment of Master/Boundary Clock at appropriate site e.g. > 10 hops. This enables:

mitigating the number of Hops. The Boundary clock helps correct the PDV on the local interface

scaling the endpoints since each Master/Boundary Clock is able to then act as a Master toendpoints downstream

Redundancy towards the upstream Grand Master Clock as its able to work with Active and standbyclocks

Packet Delay Variation (PDV) is key. Ensure Next Generation (IP) Microwave hasminimal PDV when Adaptive Modulation is enabled.

Options in Next Generation (IP) Microwave that can correct the PDV on the Interface

Master/Boundary Clock

Pre-Agg

Grand Master Clock

IEEE1588-2008

Agg

RNC

Aggregation

Packet Network


27/57


Advantages Disadvantages

GPS Reliable PRCRelatively cheapFrequency and phase

Antenna required

US Govt owned

PRC/BITS Reliable PRCGenerally Available

No PhaseNeed to maintain TDM in all Ethernetdeployment

1588-2008 Packet Based(Frequency and Phase)

Requires Master w/ PRCPerformance influenced by networkUndefined Profiles in SP environments

SyncE/ESMC Physical layer(Frequency)

No PhaseEvery node in chain needs to support

NTPv4 Packet Based(Frequency and Phase)

Not as robust as 1588-2008Open standardSome proprietary implementations

Ethernet Clocking Mechanism Comparisons


28/57


Unified RAN

QoS , Resiliency and Security

282828


29/57


Backhaul Sample traffic profile

QCI Class IPMarkings

Priority**

EgressBW

Scheduler Traffic Type MPLS EXP

1 COS1 EF High 30% Max Priority Voice (GBR) 5

3 CS5 High Gaming 5

Control EF High All SignalingSome OAM

5

2 COS2V AF41 High 40% BWR CBWFQ Conversational Video 4

4 AF31 High Multimedia Streaming 4

5 COS2 CS4 High 30% BWR CBWFQ IMS Signaling 3

6 AF32 Low GETS data,

Audio/video applications

3

AF33 Low 20% BWR CBWFQ OAM Medium 2

7 COS3 AF21 High Audio/Video Applications

VoIP (non GBR)

2

CS2 High For Future use 2

8 AF22 /

AF 23

Low 10% BWR CBWFQ Low Latency Data 1

9 COS4

(Default)

CS0 Low TCP, UDP, FTP,.. 1

AF11 Low OAM, Bulk reporting

,

0

Draft


30/57


Fixed and Variable delays

Packetization delay

Serialization delay

Processing delay

Propagation delay

Queuing delay

Fixed Delays

Variable Delay

Propagation delay is fixed only if the path for allTraffic between source and destination does not change

QoS addresses Queuing delay


31/57


Unified RAN QoS

ESNCSN EAN

Ingress QOS:

-Traffic classification

Egress QOS:

- Per-VLAN Shaping

- Per-VLAN Scheduling

Egress QOS:

- Per-VLAN Shaping

- Per-VLAN Scheduling

Egress QOS:

- Port-based Scheduling

- Port-based shaping- 6 Queues based on EXP

Ingress QOS:

- Set MPLS EXP

Egress QOS:- Port-based Scheduling

- Port-based shaping

- 6 Queues based on EXP


32/57


Unified RAN Security Area Layer 2 Features Purpose

MAC Address(CAM Table Overflow)

Port Security, per VLANMAC Limiting

Per VLAN MAC-Limiting

Broadcast/Multicast Storms

Storm ControlEffect Limited toBridge-Domain

Hijack ManagementUse Encrypted Access (SSH, Not Telnet), OOBManagement, Disable Password Recovery, EncryptedPasswords

Area MPLS Feature PurposeMPLS

Forwarding

no mpls ip propagate-ttl[forwarded | local]

Enables MPLS core privacy byhiding number of hops in MPLScore

MPLSControl Plane

VRF maximum route Configuration of mid- and maximumthreshold of number of VRF routes

MD5 LDP session authentication MD5-based authentication of LDPsessions

Global configuration or per LDPpeer


33/57


Unified RAN Resiliency

Ethernet Switching

EtherChannel, 802.3ad LACP (Sub-second, applicable to parallel links)

MST, PVSTP (


34/57


Unified RAN

Network Monitoring

343434


35/57


Backhaul Network:TDM versus PSN Variances

TDM

Circuit Switched DomainDedicated Bandwidth Packet Switched Domain

Statistically Multiplexed Bandwidth

IP/MPLS

Time Division MultiplexTools

Time Division MultiplexAssessment

Loop Circuit: UP/Down

BERT Errors

Latency

Packet SwitchedNetwork Tools

Packet SwitchedNetwork Assessment

Loop Circuit: UP/Down

BERT Errors

Ping Latency

Traceroute Loss

IP SLA & Net Flow Jitter

Protocol Debug IP Maximum Transmit Size

Packet Decode

L2 and L3 Convergence Time

L3 and L2 filters


36/57


Unified RAN Assurance

Enable IP SLA between the cell-site and Aggregation Nodes

Collect Latency, Jitter and Packet Loss

Performance Parameters Network Objectives

One-way Frame Delay 10 ms average, 15 ms max

One-way Frame Delay Variations < 4 ms

Frame Loss Rate 1 x 10-7

Network Availability 99.99% or higher


37/57


IP Host

How Does Cisco IOS IP SLAs Work?

1. Configure source

router2. If needed, configure

responder3. Schedule operations4. If needed, set

thresholds5. Measure Network6. Poll SNMP or CLI for

measurement results

ManagementApplication

SourceTarget

IP SLA ResponderMeasure

Measure PerformanceIP SLAs

Trigger Other OperationsBased on Thresholds/Timeouts


38/57


Unified RAN

Provisioning

383838


39/57


Typical Deployment ModelsDrawback analysis

1. Two-shipping

2. Staging effort (including unpacking/packing)

4. Need to poke hole in firewall if presented

Error prone and not scalable for IP RAN Access

3. Need to manually coordinate with the NOC

RemoteSite

Network

Stagingfacility

NOC

5. NOC to telnet and push configuration to branch devices

6. What if you sent the device to the wrong branch?


40/57


Deployment Model with CE (2)True Zero Touch Deployment

1. Device shipped from Cisco manufacturing to branch with no config.

3. Device is connected and initiates DHCP/TFTP requests for bootstrap

5. CE identifies the device and sends the full configuration to the device,

config agent loads the configuration, device operational.

4. Device loads bootstrap, initiates connection to CE

BranchOffice orCustomerPremises

NetworkSSL

ConfigurationEngine

Blah

Blah

Blah

Config

Blah

BlahBlah

bootstrap

DHCP/tftp

2. CE is notified to add the device and associated with a configuration template


41/57


Customer or Partner

Application

WebServices

XMLandSOAP

Web GUI or Web Services Interface

Beyond Initial DeploymentConfiguration and Image Services

Configuration Changes

Secure configuration updates to thousandsof devices in minutes

Secure distribution of service configuration(voice, VPN, and security)

Image Distribution

Cisco IOS Software images, Cisco Catalyst

software images, intrusion protection system(IPS) files, Cisco Security Manager files,Cisco IP Phone images, music-on-hold(MOH) files, interactive voice response(TCL IVR) files, and more

Image Activation: Any File, Anywhere

Cisco IOS Software and Cisco Catalystsoftware images can be activated andthe device reloaded and verified

Configuration commands can be applied

immediately prior to image activation

network


42/57


Unified RAN

Dimensioning


43/57


Backhaul Dimension Approach

Link Capacity is obtained by average of peak traffic of all connection overa long term statistical analysis

B is over provisioning factor varies based on DCH or HSDPA overhead

Link Capacity should meet delay requirement defined Application andRadio functions


44/57


Why Oversubscription

Not all users are connected all the time

Connected users are not using full bandwidth

During busy times, several users will share the cell and there willbe small variations in busy time mean

During Quiet time, a single user may have the whole cell to

themselves and this is when peak UE and cell throughput will beachieved

Dimension the Backhaul for Busy Time mean BW which is

considerably lower than peak BW Over Subscriber Top Down and Over Provision Down Top


45/57


Survey Question #2

How important is Clocking and QoS to your futureBackhaul Network ?

We prefer existing TDM for Clocking and QoS

We see a clear need for IP Clocking and QoS due to phase anddata service like VOIP , Video etc requirement

They are equally important and critical

Neither is important right now, were just trying to get thenetworks up and running


46/57


Transport StandardsEvolution with

MEF and Broadband

(MPLS) Forum


47/57


Metro Ethernet Forum 22

The New MEF 22 Specification

1. Provides generic specification for Carrier Ethernet backhaul

architectures for mobile networks (2G, 3G, 4G, LTE)2. User-Network Interface requirements

3. Service Requirements

Service definitions

Clock synchronization for application support

4. Includes guidance for migration strategy

Key Areas AddressedMigration from Legacy Networks

Scalability

Evolution with multiple Mobile Networks e.g. 2G, 3G and 4GCircuit Emulation Services


48/57


Broadband (MPLS) Forum - Backhaul

MPLS adds Carrier Grade Capabilities

Scalability

Resiliency

Manageability

Traffic Engineering & QoS

Multiservice

Traffic Isolation

Co-existence of Multiple Transport Options

Support of Multi-media traffic

Reliability Critical

Strategic Asset for new Revenue Generation


49/57


50/57


Largest,most

in

depth

test,

including:

DataCenter,IPCore,MobilePacketCore,

andIPRANBackhaul

Comprehensive

Testsimulatesrealisticmobileoperatorsnetwork

for2G,3GandLTE,1.5M ActiveSubscribers,4500+

EmulatedBaseStations

Realistic

LightReading EANTC

TestingnotfundedbyCiscoIndependent

2010 Cisco Systems, Inc. All rights reserved. Cisco Confidential

Byfarthelargestandmostindepthpublic,independent,third

partytestofmobileinfrastructurevendorperformanceever."

Carsten Rossenhvel

Managing Director, EAN

Hybrid Synchronization


51/57


ASR 9000

7609

CRS-3

CRS-3

ASR1000

ME3800ASR 9000

ASR9000

Nexus7000

ASR5000

SGSN

GGSN

Symmetricom

Master ClockRFC1588/SyncE

AX

S

TC

Emulated(e)NodeB

BTSNodeB

S

TC

ME3800

STC

Emulated(e)NodeB

MWR2941 ME3800

STC

7609

7609

ASR9000

ASR9000

ASR

9000

ASR

9000

ME3600

EmulatedBSCRNC

ANA

NAN

TimeWa

tch

HPCounter

2G/TDM

3G/ATM

Clock

GPS Antenna

Ethernet

Hybrid Synchronization

AX

Test Case:

ITU G.8261 Clock Synchronization (2, 6, and 24 Hours)

ANUE Impairment Generator Inserted between MWR and ME3800

Effective Hop Count 13

Benefits- High Quality of Experience

- Seamless Uninterrupted Roaming

Results:

Comparable to SONET/SDH accuracy (+/- 50 PPB / 50ns )

Meets LTE Multimedia Broadcast Media Services (+/- 0.05 ppm)

Frequency 9 ns

Phase 40 ns

Differentiation - 100X Competitive Solutions

SyncE or 1588 only solutions (+/- 1 s)

High Availability


52/57


ASR 9000

7609

CRS-3

CRS-3

ASR1000

ME3800ASR 9000

ASR9000

Nexus7000

ASR5000

SGSN

SGSN

MME

GGSNAX

S

TC

Emulated(e)NodeB

BTSNodeB

S

TC

ME3800

STC

Emulated(e)NodeB

MWR2941 ME3800

STC

7609

7609

ASR9000

ASR9000

ASR

9000

ASR

9000

ME3600

ANA

NAN

TimeWa

tch

HPCounter

2G/TDM

3G/ATM

ClockEthernet

REPMPLSFRR

X

XX

Symmetricom


EmulatedBSCRNC

GPS Antenna

AX

Test Case :

Link Resiliency Loss of Signal / Unidirectional Data

ANUE - Inserted in REP and MPLS Links

7600 Node Power Failure

Benefits

High Quality of ExperienceAlways ON Services

Out of Service Results:

REP Access 50 ms / 357 ms (Fast Hello)

MPLS Aggregation 28 ms / 120 ms (BFD)

Node Failure 170 ms

Lossless Recovery

Differentiation:

Robust Topology Agnostic Ethernet and MPLS Resiliency

2X Competitive Platforms Node/Ethernet/Unidirectional Data Loss

High Availability

Quality of Experience


53/57


ASR 9000

7609

CRS-3

CRS-3

ASR1000

ME3800ASR 9000

ASR9000

Nexus7000

ASR5000

SGSN

SGSN

MME

GGSNAX

S

TC

Emulated(e)NodeB

BTSNodeB

STC

ME3800

STC

Emulated(e)NodeB

MWR2941 ME3800

STC

7609

7609

ASR9000

ASR9000

ASR

9000

ASR

9000

ME3600

AN

TimeWa

tch

HPCounter

2G/TDM

3G/ATM

ClockEthernet

REPMPLSFRR

X

X

Quality of Experience

Symmetricom


EmulatedBSCRNC

GPS Antenna

AX

Test Case :

2G/3G/LTE Traffic Guarantees

Five Traffic Classes Per Mobile Profiles

REP and MPLS FRR Disabled

10G RAN Aggregation Link Failure (7600)

10G MPLS Link Failure (7600/9000)

BenefitsHigh Quality of Experience with Massive Scale

Optimized Service Aware Transport

Guaranteed Premium Service Level Agreements

Out of Service Results:

Lossless for High Priority (EF) Traffic (Voice, Control, Clock)

Lossless for Streaming Video (AF)

Only Best effort traffic affected by network congestion

Differentiation:

Industry leading QoS performance and scale

> 1 Million Mobile Flows Per Metro


54/57


DataCenter

IP Core

PacketCore

MobileBackhaul

CiscoAdaptiveIntelligentRouting

Ciscos Comprehensive IP Architecture

Centralized orDistributed

Monetization &New Models

Traffic and VideoOptimization

Offload at any

Network Point

Nexus 5000Nexus 7000 UCS

CRS

ASR 5000

ASR 90007600ASR1000 MWR 2941

ME 36/3800

Optimized for

Cloud Services

Ci S i f IP RAN
http://www.google.com/imgres?imgurl=http://www.geekiegadgets.com/wp-content/uploads/2010/04/flip_slide_HD-571x400.jpg&imgrefurl=http://www.geekiegadgets.com/2010/flip-slide-hd-shoot-it-slide-it-show-it-and-share-it/&usg=__3nmkaj09Ker4ZQ4Rkhmc8ZwMjGw=&h=400&w=571&sz=54&hl=en&start=3&um=1&itbs=1&tbnid=iQpvTP3EPe0nbM:&tbnh=94&tbnw=134&prev=/images?q=flip+slide+hd&um=1&hl=en&sa=N&rlz=1T4GGIH_enUS253US253&tbs=isch:1http://images.google.com/imgres?imgurl=http://webconferencing.org/wp-content/uploads/2009/06/cisco-webex_logo.gif&imgrefurl=http://webconferencing.org/&usg=__KtETb7HbL3_dpOzwS3bgO_hvQvA=&h=110&w=200&sz=7&hl=en&start=5&um=1&itbs=1&tbnid=JgW4xA10iMIadM:&tbnh=57&tbnw=104&prev=/images?q=webex+logo&um=1&hl=en&sa=X&tbs=isch:1http://images.google.com/imgres?imgurl=http://itunesm4ptomp3.files.wordpress.com/2009/07/504x_blackberry-tour.jpg&imgrefurl=http://itunesm4ptomp3.wordpress.com/2009/07/16/how-to-play-itunes-m4p-on-blackberry-tour-9630/&usg=__GGTzBUeqeEoeuoxjS3nyJpDKAY4=&h=839&w=504&sz=115&hl=en&start=13&um=1&itbs=1&tbnid=ankNE-oweUr1EM:&tbnh=144&tbnw=87&prev=/images?q=blackberry+tour&um=1&hl=en&sa=G&tbs=isch:1


55/57


IP-RAN RequirementsWorkshop- High-Level Business Needs

and Service Strategy

- Technology ConceptDevelopment

Readiness Assessment Detailed IP-RAN Business

Requirements IP-RAN Operational State Tools & Skills

MPLS Network Readiness

Assessment - QoS, Latency

Solution Definition- High-Level Design

- Resiliency Rqmts.

- Call Drop Rate, Set-

Up Time Rqmts.- Gap Analysis

Design- Low-Level Design

- Best Practices for

Clocking, IP-SLA,

QoS etc.

- Implementation Plan

- System Acceptance

Test Plan

- Operations Plan

Deployment-Cell-site and RNC

Integration

- Pilot

- Acceptance Testing- System

Implementation

- Traffic Migration

- NMS Implementation

- Operations Staff

Training

Operate- Solution Triage

- Break Fix Support

for HW/SW

OptimizeBase Operate Plus:- Solution

Infrastructure

Remote

Monitoring andManagement

- Operations Team

Mentoring

- Solution

Optimization

Program Management

DesignDiscover Deploy Operate

Prepare / Plan Design Implement Operate / Optimize

Cisco Services for IP-RANLifecycle Framework

Unified RAN Backhaul


56/57


Unified RAN BackhaulOverall Lessons Learned

Have a clear vision of where the RAN network architecture is going

Establish from the very beginning Technology, Services andNetwork roadmaps and manage platforms to support the keyfeatures to a specific timescale

Spend effort and time developing stringent deployment processes

and procedures to ensure quality and completeness of solutions

Stringent interoperability testing

Develop meaningful monitoring and Provisioning systems that

provide timely information for the capacity planning team to measuretraffic levels and forecast upgrades


57/57

Date post:	06-Apr-2018
Category:	Documents
Upload:	eslam-rashad
View:	218 times
Download:	0 times

Unified RAN Backhaul Architecture

Documents