Next Generation IP Transport

Cisco Confidential © 2012 Cisco and/or its affiliates. All rights reserved. 1

Evolution of Next Generation IP Transport

Wei Yin Tay Consulting Systems Engineer, Cisco Systems APJC

Dec 2012

© 2012 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 2

At the end of the session, the participants should be able to: •  Understand the technical details of the Unified MPLS for Large

Scare IP Transport system design

•  Explain the scale and operational advantages of the Unified MPLS approach over an IGP/LDP design

•  Understand the key enabling technologies for Unified MPLS, MPLS DoD, RFC3701, BGP PIC, LFA FRR etc.


•  Next Generation Internet Drivers

•  Unified MPLS Transport

•  Unified MPLS Functional Considerations Resiliency OAM and PM

•  Summary and Key Takeaways

•  FMC Backup

Next Generation Internet Drivers


Source: Cisco Visual Networking Index (VNI) Global IP Traffic Forecast, 2010–2015

More Devices

More Internet Users

Faster Broadband Speeds

More Rich Media Content

Key Growth Factors

Nearly 15B Connections 4-Fold Speed Increase

3 Billion Internet Users 1M Video Minutes per Second


§  MPLS does already satisfy number of NGN convergence requirements Full breadth of services enabling per domain convergence Compatible with heterogeneous network domains and their properties Proven by widespread adoption in Core, Edge and Aggregation

§  Latest MPLS developments address Transport Applications and scaling into the Access MPLS-TP for Static Provisioning, Transport Path performance monitoring and diagnostics* Scaling to 100,000s MPLS devices without any compromise in performance and operations** Low-end (access) devices support at scale***

§  MPLS – Proven Standards Based Convergence Technology * MPLS-TP – MPLS Transport Profile and MPLS-TP OAM ** MPLS Enhancements for extra large scale – BGP-4 + label (RFC3107) or multiple static MPLS-TP and dynamic IP/MPLS areas *** Achieved with MPLS-TP or MPLS LDP

MPLS

Core Edge Aggregation Access

IP/MPLS Cross-Domain Convergence

MPLS as Network Convergence TechnologyOptimizing Service Delivery


Core Domain MPLS/IP IGP Area

Aggregation Node

Aggregation Node

Aggregation Node

Aggregation Domain MPLS/IP

IGP Area/Process

Aggregation Node

Aggregation Node

Aggregation Node


IGP Area/Process

RAN MPLS/IP

IGP Area/Process

RAN MPLS/IP

IGP Area/Process

Core

Core

Core

Core

Node Access Domain Aggregation Domain Network Wide

Cell Site Gateways 20 2,400 60,000

Pre-Aggregation Nodes 2 240 6,000

Aggregation Nodes NA 12 300

Core ABRs NA 2 50

Mobile transport Gateways NA NA 20

~ 67,000 IGP Routes!

~45 IGP

Routes

~45 IGP

Routes

~ 2,500 IGP Routes!

~ 2,500 IGP Routes!

LDP LSP ! LDP LSP ! LDP LSP !

~45 IGP

Routes

Unified MPLS Transport


Problem Statement

•  Modern Network Requirements: Increase bandwidth demand (Video) Increase application complexity (Cloud and virtualization) Increase need for convergence (Mobility)

•  Traditional MPLS Challenges with differing Access technologies Complexity of achieving 50 millisecond convergence with TE-FRR Need for sophisticated routing protocols & interaction with Layer 2 Protocols Splitting large networks in to domains while still delivering services end-to-end Common end-to-end convergence and resiliency mechanisms End-to-end Provisioning and troubleshooting across multiple domains

How to simplify MPLS operations in increasingly larger networks with more complex application requirements

Unified MPLS addresses these challenges with elegant simplicity


Classical MPLS network with few additions

§  Common MPLS technology from Core, Aggregation, Pre-agg and potentially in the access

§  RFC 3107 label allocation to introduce hierarchy for scale

§  BGP Filtering Mechanisms to help the network learn what is needed, where is needed and when is needed in a secure manner

§  Loop Free Alternates FRR for 50 msec convergence with no configuration required

§  BGP Prefix Independence Convergence to make the 3107 hierarchy converge quickly

§  Contiguous and consistent Transport and Service OAM and Performance Monitoring based on RFC-6374

§  Support Virtualized L2/L3 Services Edge using MPLS VPN, VPWS, VPLS


Core Domain MPLS/IP IGP Area

Aggregation Node

Aggregation Node

Aggregation Node


IGP Area/Process

Aggregation Node

Aggregation Node

Aggregation Node


IGP Area/Process

RAN MPLS/IP

IGP Area/Process

RAN MPLS/IP

IGP Area/Process

Core

Core

Core

Core

Node Access Domain Aggregation Domain Network Wide

Cell Site Gateways 20 2,400 60,000

Pre-Aggregation Nodes 2 240 6,000

Aggregation Nodes NA 12 300

Core ABRs NA 2 50

Mobile transport Gateways NA NA 20

~ 67,000 IGP Routes!

~45 IGP

Routes

~45 IGP

Routes

~ 2,500 IGP Routes!

~ 2,500 IGP Routes!


~254 IGP Routes ~ 6,020 BGP Routes

~45 IGP

Routes



~45 IGP

Routes

LDP LSP ! LDP LSP ! LDP LSP ! LDP LSP ! LDP LSP !

iBGP Hierarchical LSP!

Reduction in BGP routes towards Access


•  The network is organized in distinct IGP/LDP domains Domains defined via multi-area IGP, different autonomous systems or different IGP processes. No redistribution between domains Intra-domain communication based on IGP/LDP LSPs.

•  The network is integrated with a hierarchical MPLS control and data plane based on RFC-3107: BGP IPv4 unicast +label (AFI/SAFI=1/4)

Inter-domain communication based on labeled BGP LSPs initiated/terminated by the Unified MPLS PEs. LSPs are switched by Unified MPLS ABRs or ASBRs interconnecting the domains, configured as labeled iBGP RRs with Next Hop Self


MPLS MPLS MPLS

•  In general transport platforms, a service has to be configured on every network element via operational points. The management system has to know the topology.

•  Goal is to minimize the number of operational points

•  With the introduction of MPLS within the aggregation, some static configuration is avoided.

•  Only with the integration of all MPLS islands, the minimum number of operational points is possible.

MPLS Access AGG AGG

LER LSR LER

AGG AGG Access

Operational Points


•  Disconnect & Isolate IGP domains No more end-to-end IGP view

•  Leverage BGP for infrastructure (i.e. PE) routes Also for infrastructure (i.e. PE) labels

Backbone Aggregation

.

Access Region 2

.

PE31

R

PE21

Access .

Region1

.

Aggregation

PE11 PE21

ISIS Level 2 Or

OSPF Area 0

ISIS Level 1 Or

OSPF Area X

ISIS Level 1 Or

OSPF Area Y

Isolated IGP & LDP Isolated IGP & LDP Isolated IGP & LDP BGP for Infrastructure

BGP for Services


172.1.1.0/24

1.  BGP advertises labeled routes. •  When advertising routes R2/R7 set Next Hop to self, just like R3/R8, R5/R10

and possibly (R4/R9) 2.  Access nodes only need 2 routes and only a few 100 LSPs

•  When R4/R9 do NHS, no route export necessary between IGP hierarchies

L5

L2 L3 L1

L6 L7

L1

L2

L3

L4 L5

L6

L7

L8

An

Note: Label distribution over diagonal links not shown

R2 R3 R4 R5

R7 R8 R9 R10

A1

In Label Out Label

Next Hop Outgoing IF

Any DoD R5 S0 Any DoD R10 S1

Destination Best next hop 0.0.0.0/0 R5 0.0.0.0/0 R10

Route Table size for Access Nodes: 2

Ak 172.2.1.0/24

LFIB size for Access Nodes: O(# active LSPs * # Paths) ≈ 200

BGP+label BGP+label BGP+label


172.1.1.0/24

1.  Distribute the service label from R2 to R5 •  In this case, prefix 172.1.1.0/24 has the label “50”

2.  Use that label together with the BGP Next Hop to forward the packet •  R5 will advertise 50 to A1 when a label for 172.1.1.0/24 is requested. R3 and R2

set BGP Next Hop to self.

LR7

LR3 LR4 LR2

LR8 LR9

LR2

LR3

LR4

LR5 LR

7

LR8

LR9

LR10

An

R2 R3 R4 R5

R7 R8 R9 R10

A1

In Label Out Label

50 LR3/50

Destination Best next hop 172.1.1.0/24 R3(or R4) 172.2.1.0/24 R3(or R4)

Ak 172.2.1.0/24

Destination Best next hop 172.1.1.0/24 An 172.1.2.0/24 Ak

Destination Best next hop 172.1.1.0/24 R2 172.1.2.0/24 R2

In Label Out Label LR4 LR3

In Label Out Label LR3 LR2

In Label Out Label LR2 50

Note: PHP operation not shown in these tables. R5 in this case would not push two labels but just one. Just like R4, R3 and R2 would actually only see the service label 50 on ingress. For clarity this explicit form was chosen.

50 LR2

50

LR3

50

LR4

50

50

BGP+label BGP+label BGP+label


•  Core and Aggregation Networks form one IGP and LDP domain. •  With small aggregation platforms the scale recommendation is less than 1000 IGP/LDP nodes.

•  All Mobile (and Wireline) services are enabled by the Aggregation Nodes. The Mobile Access is based on TDM and Packet Microwave links aggregated in Aggregation Nodes enabling TDM/ATM/Ethernet VPWS and MPLS VPN transport

Distribution Node

Core and Aggregation IP/MPLS Domain

Core Node

Aggregation Node

Core Node

Core Node

Core Node

IGP/LDP domain!

Aggregation Node

Aggregation Node

Aggregation Node

Aggregation Node Pre-Aggregation

Node

IP/Ethernet

Fiber and Microwave 3G/LTE

TDM and Packet Microwave, 2G/3G/LTE

Mobile Transport GW

Mobile Transport GW

CSG

CSG


Core and Aggregation IP/MPLS domain

IGP Area

Aggregation Node

Aggregation Node

Aggregation Node

Aggregation Node

Pre-Aggregation Node

RAN IP/MPLS Domain



•  The Core and Aggregation form a relatively small IGP/LDP domain (1000 nodes) •  The RAN is MPLS enabled. Each RAN network forms a different IGP/LDP domain •  The Core/Aggregation and RAN Access Networks are integrated with labelled BGP LSP •  The Access Network Nodes learn only the MPC labelled BGP prefixes and selectively and optionally the neighbouring RAN networks labelled BGP prefixes.

RAN IP/MPLS Domain


Mobile Transport GW

Core Node

Core Node

Core Node

Core Node

Mobile Transport GW

CSG

CSG

CSG

CSG

CSG

CSG


Core Network IP/MPLS Domain

IP/Ethernet

Fiber and Microwave 3G/LTE


Aggregation Network IP/MPLS Domain

Aggregation Node

Aggregation Node


Core Node


iBGP (eBGP across ASes) Hierarchical LSP!

•  The Core and Aggregation Networks enable Unified MPLS Transport •  The Core and Aggregation Networks are organized as independent IGP/LDP domains •  Core and Aggregation Networks may be in different Autonomous Systems, in which case the inter-domain LSP is enabled by labeled eBGP in between ASes •  The network domains are interconnected with hierarchical LSPs based on RFC 3107, BGP IPv4+labels. Intra domain connectivity is based on LDP LSPs •  The Aggregation Node enable Mobile and Wireline Services. The Mobile RAN Access is based on TDM and Packet Microwave.

TDM and Packet Microwave, 2G/3G/LTE

Aggregation Node

Aggregation Node

Aggregation Node

Core Node

Core Node

Core Node

Mobile Transport GW

Mobile Transport GW

CSG

CSG


RAN IP/MPLS domain

Core Node

Core Node

Core Node

Core Node


iBGP (eBGP across ASes) Hierarchical LSP!

•  The Core, Aggregation, Access Network enable Unified MPLS Transport •  The Core, Aggregation, Access are organized as independent IGP/LDP domains •  Core and Aggregation Networks may be in different Autonomous Systems, in which case the inter-domain LSP is enabled by labeled eBGP in between ASes •  The network domains are interconnected with hierarchical LSPs based on RFC 3107, BGP IPv4+labels. Intra domain connectivity is based on LDP LSPs •  The Access Network Nodes learn only the required labelled BGP FECs, with selective distribution of the MPC and RAN neighbouring labelled BGP communities

RAN IP/MPLS domain




Aggregation Node



Core Node

Aggregation Node

Aggregation Node

Aggregation Node

Core Node

Core Node

Core Node

Mobile Transport GW

Mobile Transport GW

CSG

CSG

CSG CSG

CSG

CSG


RAN MPLS/IP

IGP Area/Process

RAN MPLS/IP

IGP Area/Process

MPC iBGP community"into RAN IGP"

RAN IGP CSN Loopbacks "into iBGP"

Core

Core

Core

Core

LDP LSP !LDP LSP ! LDP LSP ! LDP LSP !

LDP LSP !

i/eBGP Hierarchical LSP!

• The Core and Aggregation are organized as distinct IGP/LDP domains that enable inter domain hierarchical LSPs based on RFC 3107, BGP IPv4+labels and intra domain LSPs based on LDP •  Core and Aggregation Networks may be in different Autonomous Systems, in which case the inter-domain LSP is enabled by labeled eBGP in between ASes •  The inter domain Core/Aggregation LSPs are extended in the Access Networks by distributing the RAN IGP in the AggregationIPV4 unicast + label iBGP and the Mobile Transport Gateways labeled iBGP prefixes into RAN IGP.

Core Node

Core Node

Core Node

Core Node



Aggregation Node



Core Node

Aggregation Node

Aggregation Node

Aggregation Node

Core Node

Core Node

Core Node

Mobile Transport GW

Mobile Transport GW


MPC iBGP community"into RAN IGP"

RAN IGP CSN Loopbacks "into iBGP"

CSG

CSG

CSG CSG

CSG

CSG


D1

PE11

PE12

IP/MPLS control plane

1.1.1.1

Default Static Route

0/0

0/0

•  Access node remains extremely simple no IGP, no BGP, static default routes only to PE


•  Service provisioning only on access node

•  Configuration of xconnect triggers LDP request for label to use for remote destination

D1

PE11

PE12

1.1.1.1

Service Provisioning

Port P xconnect 1.1.1.1

Service Provisioning

LDP DoD Request (1.1.1.1)

LDP DoD Request (1.1.1.1)



D1

PE11

PE12

1.1.1.1

LDP DoD Reply (L=21)

LDP DoD Reply (L=31)


•  PE replies with label value to use for remote location based off full network knowledge


D1

PE11

PE12

1.1.1.1


•  End to end service is now created for both primary and backup path


•  Access node is extremely simple no IGP, no BGP

•  Access node may have an LSP towards any other node

•  Access node only knows the labels it needs

•  Simple and Scaleable

•  Leverage existing technology (simplicity)


•  Extend MPLS to the Access without the need for much intelligence or memory on these boxes

2 route entries, MPLS DoD and an LFIB the size of the established LSPs are sufficient

•  End-to-End reachability information kept at nodes that scale well (ABRs)

•  Minimize the size of the IGP Clear separation of routing domains, improved convergence in the access & aggregation domains. With NHS on all ABRs, no core routes are leaked into access & aggregation, and no access & aggregation routes into the core.

Unified MPLS Resiliency


•  Unified MPLS Transport: •  Core, Aggregation, Pre-Aggregation baseline using BGP PIC Core/Edge

•  Can benefit from LFA FRR in Core and Aggregation if topology is LFA

•  LDP IP/MPLS Access uses remote LFA FRR •  Labeled BGP Access uses labeled BGP control plane protection

•  MPLS VPN Service •  eNB UNI: Static Routes •  MPC UNI: PE-CE dynamic routing with BFD keep-alive •  Transport: BGP VPNv4/v6 convergence, BGP VPN PIC, VRRP on MTG

•  VPWS Service: •  UNI: mLACP for Ethernet, MR-APS for TDM/ATM •  Transport: PW redundancy, two-way PW redundancy

•  Synchronization Distribution: •  ESMC for SyncE, SSM for ring distribution. •  1588 BC with active/standby PTP streams from multiple 1588 OC masters


CSG

CSG

CSG CSG

CSG

CSG

CN-RR

RR

iBGP IPv4+label

Core Network IS-IS L2

Access Network

OPSF 0 / IS-IS L2

Aggregation Network IS-IS L1

Aggregation Network IS-IS L1

Access Network

OPSF 0 / IS-IS L2

MTG

iBGP IPv4+label

iBGP IPv4+label

iBGP IPv4+label

iBGP IPv4+label

PAN Inline RR

next-hop-self

PAN Inline RR

next-hop-self

CN-ABR Inline RR

next-hop-self

CN-ABR Inline RR

next-hop-self



BGP PIC Edge <100 msec

BGP PIC Core <100 msec

LFA FRR, Remote-LFA FRR < 50msec

Mobile Packet Core SGW/PGW

MME


Failure Scenario IGP Availability Function BGP Availability Function CSG Uplink LFA FRR Transient CSG link/node LFA FRR PAN link/node BGP PIC Core Transient AGG link/node BGP PIC Core Agg/Core ASBR link/node

BGP PIC Edge

Core link/node LFA FRR BGP PIC Core MTG link/node BGP PIC Edge


•  What is LFA FRR? Well known (RFC 5286) basic fast re-route mechanism to provide local protection for unicast traffic in pure IP and MPLS/LDP networks

Path computation done only at “source” node

Backup is Loop Free Alternate (C is an LFA, E is not)

•  No directly connected Loop Free Alternates (LFA) in some topologies

•  Ring topologies for example: Consider C1-C2 link failure

If C2 sends a A1-destined packet to C3, C3 will send it back to C2

•  However, a non-directly connected loop free alternate node (C5) exits

33

A

C

E

B

D

F

2 2 10

2

1

8 4

C1

C3

C5

A2 A1

C2 C4


http://tools.ietf.org/html/draft-shand-remote-lfa•  Remote LFA uses automated IGP/LDP behavior to extend

basic LFA FRR to arbitrary topologies

•  A node dynamically computes its remote loop free alternate node(s)

Done during SFP calculations using algorithm (see draft)

•  Automatically establishes a directed LDP session to it The directed LDP session is used to exchange labels for the FEC in question

•  On failure, the node uses label stacking to tunnel traffic to the Remote LFA node, which in turn forwards it to the destination

•  Note: The whole label exchange and tunneling mechanism is dynamic and does not involve any manual provisioning

34

A1

C1

C2

C3

C4

A2

Backbone

Access Region

C5 Directed LDP session


•  C2’s LIB C1’s label for FEC A1 = 20

C3’s label for FEC C5 = 99

C5’s label for FEC A1 = 21

•  On failure, C2 sends A1-destined traffic onto an LSP destined to C5

Swap per-prefix label 20 with 21 that is expected by C5 for that prefix, and push label 99

•  When C5 receives the traffic, the top label 21 is the one that it expects for that prefix and hence it forwards it onto the destination using the shortest-path avoiding the link C1-C2.

35

A1

C1

C2

C3

E1

C4

A2

Backbone

Access Region

C5 Directed LDP session

21

20

99

21 99

21 X

21


•  MPLS-TE FRR 1-hop Link 14 primary TE tunnels to operate

14 backup TE tunnels to operate

No node protection

•  MPLS-TE FRR Full-Mesh 42 primary TE tunnels to operate

14 backup TE tunnels to operate for Link protection

28 backup TE tunnels to operate for Link & Node protection

•  Remote LFA Fully automated IGP/LDP behavior

tLDP session dynamically set up to Remote LFA Node Even ring involves 1 directed LDP sessions per node

Odd ring involves 2 directed LDP sessions per node

No tunnels to operate

36

AG1-1

CSS-1

CSS-2

CSS-3

CSS-4

AG1-2

CSS-5

*For the count, account that TE tunnels are unidirectional

Odd Ring

AG1-1

CSS-1

CSS-2 CSS-3

AG1-2

CSS-4

Even Ring

tLDP session for link CSS 2-3

tLDP session for link CSS 1-2

tLDP session for links

CSS 1-2 and 2-3


http://tools.ietf.org/html/draft-shand-remote-lfa•  Simple operation with minimal configuration

•  No need to run an additional protocol (like RSVP-TE) in a IGP/LDP network just for FRR capability

Automated computation of node and directed LDP session setup

Minimal signalling overhead

•  Simpler capacity planning than TE-FRR TE-FRR protected traffic hairpins through NH or NNH before being forwarded to the destination

Need to account for the doubling of traffic on links due to hairpinning during capacity planning

Remote-LFA traffic is forwarded on per-destination shortest-paths from PQ node

37

A1

C1

C2

C3

E1

C4

A2

Backbone

Access Region

C5

TE-FRR Backup tunnel NH protection

Remote-LFA tunnel to PQ node

If you need Traffic Engineering then TE is the way to go. But, if all you need is fast convergence, consider simpler options!


•  BGP Fast Reroute (BGP FRR)—enables BGP to use alternate paths within sub-seconds after a failure of the primary or active paths

•  PIC or FRR dependent routing protocols (e.g. BGP) install backup paths

•  Without backup paths

Convergence is driven from the routing protocols updating the RIB and FIB one prefix at a time - Convergence times directly proportional to the number of affected prefixes

•  With backup paths

Paths in RIB/FIB available for immediate use

Predictable and constant convergence time independent of number of prefixes


P

•  Upon failure in the core, without Core PIC, convergence function of number of affected prefixes

•  With PIC, convergence predictable and remains constant independent of the number of prefixes

Core

1

10

100

1000

10000

100000

125

000

5000

0

7500

0

1000

00

1250

00

1500

00

1750

00

2000

00

2250

00

2500

00

2750

00

3000

00

3250

00

3500

00

Prefix

LoC

(ms)

PICno PIC

1

10

100

1000

10000

100000

1000000

0

5000

0

1000

00

1500

00

2000

00

2500

00

3000

00

3500

00

4000

00

4500

00

5000

00

Prefix

msec

250k PIC250k no PIC500k PIC500k no PIC

§  Upon failure at the edge, without edge PIC, convergence function of number of affected prefixes

§  With PIC, convergence predictable and remains constant irrespective of the number of prefixes

PIC Core PIC Edge

Unified MPLS Functional Aspects OAM and PM


•  OAM benchmarks Set by TDM and existing WAN technologies

•  Operational efficiency Reduce OPEX, avoid truck-rolls Downtime cost

•  Management complexity Large Span Networks Multiple constituent networks belong to disparate organizations/companies

•  Performance management Provides monitoring capabilities to ensure SLA compliance Enables proactive troubleshooting of network issues


RNC/BSC/SAE CSG Mobile Transport GW Aggregation

MPLS VRF OAM

IPSLA Probe

NodeB

IPSLA Probe

IPSLA PM

IP OAM over inter domain LSP – RFC 6371,6374 & 6375

MPLS VCCV PW OAM

IPSLA Probe

IPSLA Probe IPSLA PM

VRF VRF

LTE, 3G IP UMTS, Transport

3G ATM UMTS, 2G TDM, Transport

End-to-end LSP With unified MPLS RFC6427, 6428 & 6435

CC / RDI (BFD) Fault OAM (LDI / AIS / LKR) On-demand CV and tracing (LSP Ping / Trace) Performance management (DM, LM)

Tran

spor

t OA

M

Serv

ice

OA

M


Fixed Mobile Convergence


Converged CE + Unified RAN

Unified RAN

Carrier Ethernet

Telcos (+ MSOs)

Typical Services: •  Security •  Business Ethernet • Triple Play •  Wholesale Ethernet • Internet Access

Mobile Operators

Typical Services: •  Mobile Internet •  Wholesale RAN Backhaul

Value

Expand into CE services Leveraging Unified RAN

Expand into RAN services Leveraging Carrier Ethernet

Intelligent Converged

Network

Typical Services: • Security •  Business Ethernet •  Mobile Internet •  Triple Play •  Internet Access •  RAN Backhaul

Converged Scenarios: Fixed/Mobile Infrastructure Wholesale Ethernet / RAN Backhaul Mobile Operator with Business Services

© 2012 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 45 45

§  Types of network ‒  Mobile backhaul only ‒  Converged with other services

§  Types of mobile traffic ‒  2G/3G ‒  4G only ‒  2G/3G/4G ‒  Small cell

§  Packet Core placements options ‒  Centralized ‒  Distributed

•  Network architecture options MPLS access & aggregation L2 access & aggregation L2 access, MPLS aggregation L3 access & aggregation MPLS access & aggregation

•  Network timing options GPS Sync. Ethernet PTP: 1588v2008 Hybrid


Mobile Backhaul Bandwidth - Radio Behavior

Spectral Efficiencybps/Hz

Bandwidth, Hz

64QAM

16QAM

QPSK

cell average

Busy TimeMore averaging

UE1

UE2

UE3

: : :

Many UEs

Quiet TimeMore variation

UE1

64QAMCell average

UE1

bps/Hz

QPSKCell average

UE1

bps/Hz

Hz Hz

a) Many UEs / cell b) One UE with a good link c) One UE, weak link

§ BW is designed on per cell/sector, including each radio type § Busy time – averaged across all users § Quiet Time – one/two users (Utilize Peak bandwidth)

§ For multi-technology radio- sum of BW for each technology § Last mile bandwidth- Planned with Peak § Aggregation/Core – Planned with Meantime Average § Manage over subscription


Cell Site

Access Layer

Aggregation Layer

GE Ring or Pt-to-Pt

BSC RNC

L3 MPLS VPN

L3 MPLS VPN

Option 1

Option 3

Option 2

10 GE or IPoDWDM

Access node

Aggregation

node Distribution

node

Core E-UTRAN

Ethernet uW

Option 5

E-LINE/E-LAN (L2VPN)

Option 4

Fibre

Backbone Layer

L3 MPLS VPN

L3 MPLS VPN

SGW

L2VPN

L2VPN E-LINE/E-LAN (L2VPN) L3 MPLS VPN

Mobile Backhaul Transport Architecture


X2 inter base station interface SCTP/IP Signalling GTP tunnelling following handover

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

S1-u Base Station to SAE GW GTP-u base micro mobility

SAE GW to PDN GW GTP or PMIP based macro mobility

SGW SGW

MME GW

MME GW

PDN GW

No longer Pt-to-Pt relationship with multipoint requirements

Network intelligence for advanced services and traffic manipulation

“X2” interface introduces direct communication between eNodeBs

Demarcation point between the radio and the Backhaul technology

Different traffic types with different transport requirements


Converged Transport


•  IPoDWDM acts on the entire router interface as in the case of Transponders

•  All IPoDWDM features leverage the OTN overhead and FEC which act on the entire router interface

OTN FEC Packet Packet

OTN FEC Packet Packet

DWDM controller

Data controller

Connection via External TXP

IPoDWDM

Summary


Unified MPLS simplifies the transport and service architecture •  Unified MPLS LSPs across network layers to any location in the network

•  Flexible placement of L2 and L3 transport to concurrently support 2G,3G, and 4G services, as well as wholesale and wireline services.

•  Service provisioning only required at the edge of the network

•  Divide-and-conquer strategy of small IGP domains and labeled BGP LSPs helps scale the network to hundred of thousands of LTE cell sites

•  Simplified carrier-class operations with end-to-end OAM, performance monitoring, and LFA FRR fast convergence protection

Thank you.

Next Generation IP Transport

Technology

Transcript of Next Generation IP Transport