Seamless Mpls Alu

BACKHAUL EVOLUTION Bruno De Troch June 2014

COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

OVERALL AGENDA

1. SReXperts EMEA 2014 Presentation 2. Seamless MPLS Details 3. Comparison with MPLS-TP

2 COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

SReXperts 2014 Presentation Bruno De Troch June 2014

COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

AGENDA

1. The importance of backhaul 2. The traditional backhaul model 3. Drivers for changes in backhaul 4. Capacity evolution 5. Connectivity evolution 6. The service oriented backhaul model 7. Conclusions

4 COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

AGENDA

1. The importance of backhaul 2. The traditional backhaul model 3. Drivers for changes in backhaul 4. Capacity evolution 5. Connectivity evolution 6. The service oriented backhaul model 7. Conclusions

5 COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

DELIVERING SERVICES WITH QUALITY IN A COMPETITIVE WORLD • Demand is surging - Many more smart devices, sometimes with shared data plans - More time is spent online - Growing media rich consumption - Increasing QoE expectations

• New services should be enabled quickly and across the full customer base

• High competitive pressure

• Operational cost and complexity should be reduced

6 COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

THE IMPORTANCE OF BACKHAUL AS SEEN BY MANY SERVICE PROVIDERS

“The facts are we have the nation's largest 4G network covering nearly 250 million people with LTE and HSPA+ with enhanced backhaul," “It's important to note thatexperience.” having enhanced backhaul in place is necessary to deliver a 4G

* From a FierceWireless interview with 2 Tier 1 MNOs

7 COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

AGENDA

1. The importance of backhaul

2. The traditional backhaul model 3. Drivers for changes 4. Capacity evolution 5. Connectivity evolution 6. The service oriented backhaul model 7. Conclusions

8 COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

THE TRADITIONAL BACKHAUL MODEL LAYERS AT WORK • Pipe Model - Point-to-Point - From Access Node (AN) to a “smarter” Service Node (SN) Smart(er)

- Lower Layer (below IP Layer) technology

Node Access Node

Backhaul

Non-IP

• Many examples (Mobile and Non-Mobile)

IP

- BS – BSC (TDM Circuit, ATM PVC, Ethernet E-Line) - DSLAM – BNG (Wire, ATM PVC, Ethernet E-Line) - CPE – PE (Wire, TDM Circuit, FR/ATM PVC, Ethernet E-Line)

• One hop @IP might result in one or more hops at lower layer(s) 9 COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

THE TRADITIONAL BACKHAUL MODEL WHY DID WE DO THIS? • Cost

• Perceived Complexity of higher layers

• Operational reasons - IP address management - Responsibility and ownership spread across teams - …

10 COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

THE TRADITIONAL BACKHAUL MODEL CHALLENGES • “Non-Intelligent” (mostly at lower layer) decision at pipe entry - Defer decision to the more centralized service node/location (SN) - Also if packet is dropped or needs special handling

Access

Smart(er)

IN

OUT

Node

Node

• Non-granular service locations

Backhaul

- Either before IN or after OUT of pipe - No mid-way escape possible

• Any-to-any costly or not-optimal - From IN to many pipes – scaling problem on access node - Hub-and-spoke of pipes – scaling problem on hub node, E2E latency problem Smart(er) Access

IN

OUT

Node

Smart(er)

Node Access

IN

OUT

Node

Backhaul

Backhaul

11 COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

Node

THE TRADITIONAL BACKHAUL MODEL QUESTIONING THE MODEL • Would it make sense to have IP decisions earlier in the chain? - Why would we do it? - What would we gain? L3

• Would it cost much more (to operate)? < L3

< L3

< L3

< L3

IP/MPLS

• What is the ideal midway point? L3

• Blindly cross-connecting below the IP layer assumes you can trust the packet gets closer to the destination L3

- Is this always true?

< L3

< L3

< L3

< L3

- What about path/service redundancy? - At what layer is it best handled? - How does different layers interact? - Is fine-tuning of protocols/timers needed?

< L3

< L3 L3

12 COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

IP/MPLS

AGENDA

1. The importance of backhaul 2. The traditional backhaul model

3. Drivers for changes 4. Capacity evolution 5. Connectivity evolution 6. The service oriented backhaul model 7. Conclusions

13 COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

DRIVERS FOR CHANGES IN BACKHAUL • Capacity Increases - More subscribers/devices/applications generate more and bigger flows

• Coverage and Convergence Requirements - Any Device on Any Access from Anywhere to Anywhere

• Service Requirements - New services impose new requirements (latency limits, synchronization, …)

• Operational Challenges - Efficiency, simplicity and cost gains through automation

• Standardization - All IP

14 COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

EXAMPLE: MOBILE BACKHAUL EVOLUTION FIRST AND SECOND PHASE • Phase 1 (2G/3G): Capacity Increases – Point-to-Point connectivity model (no changes) - TDM/FR/ATM migrated to Ethernet for higher throughput - Still Point-to-Point between eNBs and RNCs

• Phase 2 (2G/3G/LTE):

Capacity Increases – Metro Fabric connectivity model - Ethernet/IP with higher throughput - Consistent Any-to-Any between eNBs and RNC/EPC/SeGW

15 COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

EXAMPLE: MOBILE BACKHAUL EVOLUTION THE THIRD PHASE • Phase 3 (Converged Backhaul): Capacity Increases – Global Fabric connectivity model - Ethernet/IP with even higher throughput - Metro Fabric to Global Fabric - many possible termination points (eNBs, MSAN, OLT, WiFI AP, RNC, EPC, WiFi GW, BNG, CDN, MBMS GW, DPI, IPTV GW, DC GW, …) - could be distributed or centralized - could be physical of virtual

16 COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

AGENDA

1. The importance of backhaul 2. The traditional backhaul model 3. Drivers for changes

4. Capacity evolution 5. Connectivity evolution 6. The service oriented backhaul model 7. Conclusions

17 COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

CAPACITY EVOLUTION - THROUGHPUT (MOBILE) DATA TRAFFIC INCREASING DRAMATICALLY 30 Gbps

10 Gbps 5 Gbps

*Traffic Evolution over 5 years (taken from a European mobile operator, measured at peering point) 18 COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

THROUGHPUT IS NOT THE ONLY CAPACITY PARAMETER THE IMPACT OF BACKHAUL DELAY ON PERFORMANCE

LTE TCP Window/Packet Drop/Delay on Mobile Throughput • Delay is

the main

factor affecting LTE throughput.

• TCP throughput = TCP_Window_Size/Round_Trip_Time (latency).

• Dropped packets can have a huge impact on overall throughput. • Large TCP window improves RF channel rate, but packet drop impact is more severe for large window. 19 COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

AGENDA

1. The importance of backhaul 2. The traditional backhaul model 3. Drivers for changes 4. Capacity evolution

5. Connectivity evolution 6. The service oriented backhaul model 7. Conclusions

20 COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

CONNECTIVITY EVOLUTION REQUIREMENTS • Convergence - Any access (Multiple Media, Speeds, …) - Any topology

• Any to Any Connectivity

• Large Scale

• Cost

21 COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

EXAMPLE: LTE CHANGES THE ARCHITECTURE TRADITIONAL 2G, 3G

BACKHAUL (TDM, ATM, Ethernet)

MTSO BSC/RNC

Hub & Spoke

REGIONAL/NATIONAL BACKBONE (IP/MPLS)

DATA CENTER GGSN

MACROCELL SGSN

MTSO BACKHAUL (IP/MPLS,CARRIER ETHERNET) Any-to-Any (X2, S1 flex)

BSC/RNC SeGW

Packet Sync

REGIONAL/NATIONAL BACKBONE (IP/MPLS)

IPSec

LTE, LTE+

SMALL CELL SGWs

CENTRALIZED BBU 22 COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

DATA CENTER PGWs

TODAY: SERVICE BORDERS ARE STILL NETWORK BORDERS RNC SGSN MTSO

IP-VPN

IP/MPLS

GGSN

Mobile Core

CSG

3G to

Hub Mobile backhauling network

Mobile core network

LTE

RNC S1 SGSN MTSO

X2 secured

Se-GW IP-VPN X2 unsecured

GGSN

IP/MPLS Mobile Core

CSG

S-GW

P-GW

Hub Mobile backhauling network

Mobile core network 23

COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

MME

CONVERGED BACKHAUL REQUIRES EVEN MORE FLEXIBLE ARCHITECTURE MTSO BSC/RNC SeGW

BACKHAUL (IP/MPLS,CARRIER ETHERNET) Any-to-Any (X2, S1 flex)

Packet Sync

REGIONAL/NATIONAL BACKBONE (IP/MPLS)

DATA CENTER PGWs

IPSec

LTE, LTE+

SMALL CELL SGWs

CENTRALIZED BBU

BACKHAUL (IP/MPLS,CARRIER ETHERNET) Any-to-Any (X2, S1 flex, MSAN-BNG)

REGIONAL/NATIONAL BACKBONE (IP/MPLS)

Packet Sync

IPSec

MOBILE, FIXED

SMALL CELL SGWs

CENTRALIZED BBU

24 COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

DATA CENTER PGWs

AGENDA

1. The importance of backhaul 2. The traditional backhaul model 3. Drivers for changes 4. Capacity evolution 5. Connectivity evolution

6. The service oriented backhaul model 7. Conclusions

25 COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

THE SERVICE ORIENTED BACKHAUL MODEL TOWARDS A CONVERGED ACCESS AND AGGREGATION • Make the backhaul flexible enough for true service flexibility - Any access - Any topology - Any service characteristics - Any service termination point location - Network Function Virtualization

• Decouple transport and services - Topological freedom of infrastructure - Multiple service overlays

26 COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

THE GLOBAL ANY TO ANY FABRIC

BACKHAUL (IP/MPLS,CARRIER ETHERNET) Any-to-Any (X2, S1 flex, MSAN-BNG)

MTSO BSC/RNC

Packet Sync

REGIONAL/NATIONAL BACKBONE (IP/MPLS)

IPSec

MOBILE, FIXED

SMALL CELL SGWs

CENTRALIZED BBU

GLOBAL ANY-TO-ANY FABRIC

27 COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

DATA CENTER PGWs

THE GLOBAL FABRIC POSSIBLE IMPLEMENTATION • Use IP/MPLS as unifying layer - Bring it closer to the access - Access Node connects Wire/Lambda to IP/MPLS Domain

• Only 2 Touch Points for Service Enablement - Access Node to Access Node - Access Node to Service Node - Service Node to Service Node L3

• No intermediate domain borders < L3

IP/MPLS IP/MPLS IP/MPLS L3

28 COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

THE GLOBAL ANY TO ANY FABRIC CHALLENGES • Scale - Higher number of devices - More access nodes - More service nodes

- Accommodate lower capabilities of most devices - Control plane - Data plane

• End to end Resiliency - Transport - Services

• Manageability

29 COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

THE GLOBAL ANY TO ANY FABRIC GOALS ARE IN-LINE WITH SEAMLESS MPLS CONCEPT • Scalability - Allow the network to scale to 100s of metro regions with 1000+ nodes each, recognizing that some nodes (e.g. access) have more limited capabilities

• Fast Restoration - Support fast service restoration after failures (using local or E2E repair techniques). Transport restoration can speed up service restoration but service restoration is the ultimate goal.

• End-to-End Provisioning - Remove service-specific configuration between MPLS domains - Create end-to-end services by decoupling service and transport layer

30 COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

WHAT DID WE GAIN? SERVICE FLEXIBILITY BY DECOUPLING TRANSPORT AND SERVICES • Transport: - MPLS Transport possible between ANY possible endpoints - Optimize Transport Paths irrespective of Application

• Services: - Overlay irrespective of transport - Per-service Characteristics

31 COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

To avoid waste of badndwith and extra-delays, MME / SGW / PGW shall be selected in same ePC site as SeGW ! dependency between transport and service

EXAMPLE OF SERVICE FLEXIBILITY CENTRALIZED SEGW E-LINE (Ethernet, MPLS, …) RAN / e-RAN / Access

VPLS / H-VPLS

7750-SR

IP-VPN

SeGW

Core

Backhaul/Aggregation

PCRF

VRF VRF

IP-VPN

VRF

PGW

Fiber or leased lines

ETH

VRF

ETH

IP-VPN

7750-SR

VRF

SGW

VRF

SeGW

IP VPN

ePC site 1

ETH

PON

E-UTRAN VPN

ETH

MME

7750-SR SeGW

ETH IP VPN

PCRF VRF

ETH

IP-VPN ETH

VRF VRF

PGW

RNC site

uWave

VRF

ETH

IP-VPN

VRF VRF

ETH

SGW

SeGW

ETH

ePC site 2 eNB SeGW selection per ePC site: • Same for all if Active-Standby ePC

VRF

• Per TAU/RAU if Active-Active (Load sharing)

IP se c

32 COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

N R P V e t a iv r P

VRF Signalling VRF User Plane VRF OAM

MME

S1-MME S1-U / X2 / S5 OAM

EXAMPLE OF SERVICE FLEXIBILITY DISTRIBUTED SEGW E-LINE (Ethernet, MPLS, …)

Independence of ePC node selection from SeGW architecture

VPLS / H-VPLS

RAN / e-RAN / Access

IP-VPN Core

Backhaul/Aggregation

7750-SR 7750-SR PCRF VRF VRF VRF

Fiber or leased lines

ETH

PGW

VRF

ETH

7750-SR

SeGW

VRF VRF

VRF

User Plane VPN

VRF VRF

ETH

PON

Signalling VPN ETH

ETH

VRF

ETH

VRF

OAM VPN

SGW

SeGW

ePC site 1

MME

7750-SR PCRF

VRF VRF VRF

ETH

SeGW

VRF

RNC site

uWave

Optimized X2 delay

ETH

PGW

VRF VRF VRF

SGW

ETH ETH

ePC site 2 VP LS

VRF backhaul

IP se c

N R P V e t a v i r P

VRF Signalling

S1-MME

VRF User Plane VRF OAM

S1-U / S5 X2 33

OAM

COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

Larger SeGW deployment

MME

SERVICE OVERLAY MECHANISMS HOW ARE SERVICES INSTANTIATED? • SDN Techniques - Assume any-to-any connectivity through global fabric - Similar to datacenter flat L2 network

• Any service can be instantiated anywhere - Flexible movement of services - NFV Ready

• In combination with End-to-End Network Management System

34 COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

SERVICES OVERLAY THROUGH A WAN SDN CONTROLLER ReST

Abstract Service API and Model (ReST, NETCONF)

Virtual Service Directory (VSD) XMPP

Virtual Service Controller (VSC)

NETCONF, CLI, PCEP, SNMP, OF

OF

dVRS

Virtual Service Controller (VSC)

WAN SDN Controller (WSC)

3rd Party PE

7x50

1830

1830

White Box

SD VPN nCPE

7x50

WAN Data Center

Data Center

35 COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

OF

FUNCTIONAL COMPONENTS OF A WAN SDN CONTROLLER Policy server ( VSD)

OSS/Portal

ReST, Netconf/YANG, XMPP Service Manager

OFPeering/ Controller OF Controller OF

BGP

Service DB

Resource Resource Manager Manager

ReST

PCEP

RR

BGP-LS

PCEP

Netconf/YANG

ReST

IP PCE

PCEP

PCEP

SAM

PCEP

CLI, SNMP, OF

White box

36 COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

Optics PCE

TED+LSP

OF

TED + LSP

OSPF-TE

ACCESS TO THE GLOBAL FABRIC WHERE IS THE IDEAL ENTRY POINT TO THE IP/MPLS GLOBAL NETWORK? L3

< L3

Single Connection Dedicated to one customer Fixed Cost Optimized

IP/MPLS L3

Any to Any Multiple (Redundant) Paths Statistical Multiplexing Flexibility

37 COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

EXTENDING THE GLOBAL FABRIC NON IP/MPLS MULTIPLEXED ACCESS • Heterogeneous solution is still sometimes necessary - Ethernet, L2oGRE - Why: specific requirements, legacy, cost, politics - Example: CPRI

• Then a common management system is even more necessary

38 COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

EXAMPLE: COMMON PUBLIC RADIO INTERFACE (CPRI) Radio Equipment

Radio Equipment Controller

!"#$%&'() CPRI (e.g. over fiber) RF Only

Centralized Base Band Unit (BBU)

Summary • Interface standard for encapsulating antenna samples sent between a radio and a baseband unit (BBU) • Separation of functions brings efficiency and scale , aligned with a cloud model

Characteristics • Not packet based; signals are interleaved in a low latency TDM-like fashion • Assumes near zero jitter, near zero bit error rate • Defines multiple constant bit rate containers in multiples of 614Mbit/s up to 9.6Gbit/s • Allows larger containers to be made up of smaller containers • Containers can be mixed between different sectors and between different technologies • Includes alarms and timing/synchronization

39 COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

AGENDA

1. The importance of backhaul 2. The traditional backhaul model 3. Drivers for changes 4. Capacity evolution 5. Connectivity evolution 6. The service oriented backhaul model

7. Conclusions

40 COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

CONCLUSIONS • Backhaul architectures need to evolve to cope with new service requirements

• Service Flexibility is the key driver

• IP/MPLS is the right technology to enables the required global any to any fabric

41 COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

Seamless MPLS Details

COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

SEAMLESS MPLS END-2-END MPLS ENABLING SCALE AND SIMPLICITY

MPLS Metro 1

MPLS Core

MPLS Metro 2

Service label (PW,VC label) Transport Layer

Inter-area/AS label (BGP label) Intra-area/AS label (LDP/RSVP)

WHY SEAMLESS MPLS ?

SEAMLESS, SCALABLE, RESILIENT

• Cloud services

• Existing MPLS features (LDP inter area LSP, inter area RSVP LDPoRSVP, PW switching) do not address end to scale, resiliency and manageability

• MPLS being deployed end-to-end form access to aggregation to the IP core layers of the network

• Seamless MPLS extends MPLS network to integrate access, aggregation and core into a single MPLS domain

• Makes deploying services faster and more flexible by removing network boundaries • Helps scale the end-to-end network to more than 100,000 MPLS devices • Supports end-to-end fault detection, fast protection and end-to-end operations, administration and maintenance (OAM) functions.

MOTIVATIONS AND DRIVERS • Fixed Mobile Convergence • Evolution to LTE

For additional Information: Seamless MPLS Techblog

• Based on existing protocols (like BGP and LDP) minimizing risk 43 COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

SEAMLESS MPLS THE PRINCIPLE • Seamless MPLS extends the core domain and integrates aggregation and access domains into a single MPLS domain, whilst taking into account the limited feature-set and scale of aggregation nodes (AGNs) and access nodes (ANs) • Uses ‘divide-and-conquer’ approach – large problem is divided into many smaller problems • Gateway between core and aggregation and core network is implemented by an Area Border Router (ABR) • Architecture can be used for residential, MBH, or business services (de-coupling transport from service layer) • Does not require any new protocols - just uses existing protocols such as BGP, LDP, RSVP and IGP (IS-IS/OSPF)

PE

PE

Access

Aggregation

Metro-region

ABR

P

ABR

Core

44 COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

PE

PE

Aggregation

Access

Metro-region

SEAMLESS MPLS KEEPING THE SCALABILITY, RESILIENCY AND END-POINT PROVISIONING 2

SERVICE PW

END-POINT PROVISIONING

Inter-metro MPLS transport tunnel Metro MPLS tunnel

Metro MPLS tunnel

P

ABR-11

BNG

ABR-21

PE-1

PE-2

Aggregation

Aggregation

3

RESILIENCY

ABR-12

PE-1 Access

Metro MPLS tunnel

ABR-22

IP/MPLS Metro 1

IP/MPLS core

~1000 MPLS nodes

PE-2 Access IP/MPLS Metro 2 ~1000 MPLS nodes

1

SCALABILITY

METRO 1 IGP/MPLS domain

Core connecting 100s of metro regions

CORE IGP/MPLS domain 45 COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

METRO 2 IGP/MPLS domain

SEAMLESS MPLS EXAMPLE OF ARCHITECTURE Filtering of BGP routes to allow only relevant loopbacks to be leaked in the access domain

LDP FRR LFA , RSVP protects against link or local ABR failures

Resiliency is based on EDGE PIC for labeled BGP route

RR NHSelf

NHSelf with label reprogramming in the local ABR to allow having end to end BGP label LSP

iBGP-3107

iBGP-3107

LDP /RSVP

LDP/RSVP

LDP/RSVP

RR NHSelf iBGP-3107

ISIS L2 OSPF area 0 Different instance

ISIS L2 OSPF area

Can also work with ASBR,

iBGP-3107

LDP/RSVP

LDP/RSVP

ISIS L2 OSPF area

ISIS L1 OSPF area

if no collapsed PEs exist between core and aggregation ABR - RR NHSelf

ABR

ABR

ABR/ PE CSG

End to end provisioning No service awareness in intermediate nodes All domains separated at MPLS level

•

RR NHSelf

RR NHSelf

iBGP-3107

ISIS L1 OSPF area

• •

IBGP 3107 is used for inter-metro MPLS connectivity

ABR / PE

Aggregation

Aggregation

CSG

P ABR

IP/MPLS core

NHSelf

ABR

NHSelf

eBGP-3107

IP/MPLS Metro 2

IP/MPLS Metro 1

46 COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

ASBR

ASBR

Comparison with MPLS-TP

COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

MPLS EVOLUTION • Over 10 years old! - Initially “fast switching” mechanism - Evolved to service delivery mechanism

• Considered complex due to overloading - Many functionalities - Many protocols - Dependability on IP

• Triggered competing solutions (eg PBB-TE) and MPLS adapted mechanisms (eg MPLS-TP) • Latest step is to extend the MPLS stretch and define interactions - Seamless MPLS - MPLS in the Access - Pseudowire Head-End Termination

THE PROMISES OF MPLS-TP • Focus on transport - Back to the roots: transport only - IP/MPLS considered too complex for transport - Need for better OAM toolkit

• Interest in the market is not because of added value, but rather because of simplicity

• MPLS-TP is relatively easy to implement for IP/MPLS based solutions

49 COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

MPLS-TP IN AN NUTSHELL • MPLS-TP is a subset of IP/MPLS - The data plane is exactly the same (labels!) - There is a special label that is used for “inband” communication (GAL -Generic Alert Label)

• MPLS-TP does not have a control plane - it is all down to manual configuration - of the different labels for tunnels, and PW

-- the use GMPLS asto MPLS-TP Plane The idea OAM isis to different – due the lackControl of IP infrastructure ( a control plane) the OAM functions and tools that are currently under definition must be able to operate in an IP-less environment; For OAM there are two offers on the table: (Y.1731) and BFD - It works with the GAL and some other infrastructure to be able to have multiple communications channels (ACH)

50 COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

MPLS-TP: MUST INTERWORK WITH NATIVE IP/MPLS Per RFC 5654 •

The MPLS-TP data plane MUST be a subset of the MPLS data plane as defined by the IETF.

•

The MPLS-TP design SHOULD as far as reasonably possible reuse existing MPLS standards.

•

Mechanisms and capabilities MUST be able to interoperate with existing IETF MPLS [RFC3031] and IETF PWE3 [RFC3985] control and data planes where appropriate.

•

Data-plane interoperability MUST NOT require a gateway function.

PRACTICAL (?) INTEGRATION OF MPLS-TP AND IP/MPLS

(*) Presented by TI at MPLS WC 2012 52 COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

MPLS-TP TO IP/MPLS PRACTICAL INTEGRATION CONCERNS • No E2E visibility for provisioning • No E2E OAM consistency • No E2E redundancy mechanisms • Slower convergence due to overlay (base on keep alive iso detection) • No native P2MP connectivity • No E2E consistent QoS • No flexible service deployment

53 COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

COMPARISON OF IP/MPLS AND MPLS-TP

Attribute Maturity Standardization Multi-vendorInteroperability Multi-vendor IP/MPLS MPLS-TP Interworking VPN Supported Services Support IP MulticastDelivery

IP/MPLS Proven,with many utilitydeployments 10+years Fullystandardized

MPLS-TP Infancy, little or no proven deployment experience for utilities Somestillinprogress

Proven,many

Limited

Proven, many

Unproven

L1, L2, L3 Full

L1, L2 only Transport only

Optimized

None

Protection

FRR oractive/standbypath

Traffic Engineering

Dynamic

Protectionswitching Static

Convergence

CommonNMS, training, and sparing for L1 to L3

Separate NMS, training, and sparing for L1/L2 and L3

OAM

Singleplatformf orL1toL3

SeparateplatformrequiredforL3

54 COPYRIGHT © 2013 ALCATEL-LUCENT . ALL RIGHTS RESERVED. . ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

Segment Routing

COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

MPLS OVERVIEW - HISTORY • Two main protocols: LDP or RSVP - LDP for scale and simplicity – extensions to LFA/LFA policies/RLFA - RSVP for TE and FRR for some time

• To scale MPLS we enabled - LDPoRSVP - Seamless MPLS: LBL-BGP with LDP/RSVP

• Traffic engineering: RSVP based • Services through: - BGP/IGP shortcuts, PW (T-LDP/BGP), VPLS (LDP/BGP), VPRN (BGP), MVPN (BGP/mLDP/P2MP RSVP)

• Issues: - TE solutions don’t scale when we want more granularity/dynamicity, RLFA too complex (dynamic T-LDP signaling)

LDP

RSVP

Overview

Multipoint to point

Point to point

Operation

Simple

LSP per destination/ TE-path

Dependencies

Relies on IGP

Relies on IGP TE

LBL allocation

Local significant per node (interface)

Local significant per node (interface)

Traffic Engineering No

Yes

Scaling

1 LBL per node (interface)

Nx(N-1)

Fast Reroute

LFA, LFA Policies, Remote LFA