iConnect™ MPLS/GMPLS for NG

Converged Optical and Carrier
Ethernet Networks
9 October 2007
1

Turin Networks Confidential – Do Not Distribute

MPLS/GMPLS andConverged Network

2

Turin Networks Confidential – Do Not Distribute

MPLS Objectives for Ethernet and TDM Services over a
SONET/SDH Transport Network
Enable scalability for Ethernet Services over SONET/SDH
infrastructure
Provide fast reroute for Ethernet Service protectionMore efficient bandwidth usage over SONET/SDH network
Enable TDM service to be carried in conjunction with thepacket network
Simplify Service Operations versus provisioning a router
Provide “Point and Click, End to End” provisioning
Allow Carriers to build on SONET/SDH resiliency and provide
Carrier Ethernet Service SLAs with QoS

3Turin Networks Confidential – Do Not DistributeGMPLS Background
Used by SONET/SDH MSPP to automate
provisioning
Each network element running GMPLS supports:
OSPF-TE routing
RSVP-TE signaling
Label distribution through RSVP

GMPLS is a superset of MPLS
In IP MPLS, data and management packets mixed in same bit stream.
TDM GMPLS establishes bidirectional LSPs

MPLS and GMPLS are peers

4Turin Networks Confidential – Do Not Distribute

Bridging the MPLS and GMPLS domain
Ethernet cards in MSPPs can be adapted toexchange the necessary routing information toallow MPLS and GMPLS domains to communicate
These Ethernet cards will be responsible for:Establishing an OSPF neighbor relationshipExchanging IP routing information
Receiving and sending RSVP requests
Switching MPLS labels

The adapted Ethernet cards are simply a clientinterface into the existing GMPLS control plane

5

Turin Networks Confidential – Do Not DistributeConverged Services Infrastructure
What problem are you trying to solve?
All Services over a Common Network Infrastructure
All services over an Ethernet Transport Network

Network needs to support Ethernet services andTDM services
Different ways to implement – each having pros and cons

Different approaches to take depending
upon which problem you want to solve

6

Turin Networks Confidential – Do Not DistributeConverged Transport Technology Choices
IEEE 802.1ad (Provider Bridges / QinQ)IEEE 802.1ah (Provider Backbone Bridges)
Provider Backbone Transport (PBT)

Ethernet over SONET/SDH
Ethernet over MPLS (Pseudo wires)

7

Turin Networks Confidential – Do Not DistributeConverged Transport Technology Choices- Ethernet Transport
IEEE 802.1ad (Provider Bridges / QinQ)
Most commonly implemented Ethernet service delivery technology
S-VLAN ID (S-VID) used to identify 4095 services
Uses customer’s MAC address for forwarding
RSTP or MSTP for protection/restoration

IEEE 802.1ah (Provider Backbone Bridges)
I-SID used to identify 16M services
B-VLAN ID (B-VID) used to identify backbone tunnel
RSTP or MSTP for protection/restoration

Provider Backbone Transport (PBT)
Backbone tunnels (working and protected) identified via globally unique 60 bit BVID+Destination MAC address
Can use GMPLS to pre-provision protected tunnel

Disables Ethernet control plane (BPDUs)
Can use GMPLS (g-LSPs) as control plane for simplified tunnel provisioning
RSVP-TE for CAC for deterministic QoS and BW management

8

Turin Networks Confidential – Do Not DistributeConverged Transport Technology Choices- SONET/SDH Transport
Uses 802.1ad (S-VID) or 802.1ah (I-SID) for service
identification
Uses VCAT and LCAS for bandwidth on demand
Dynamic resizing of SONET/SDH VC containers

Can use RSTP/MSTP or SONET/SDH APS for protection
Can use GMPLS to pre-provision or calculate protected path/tunnel

Uses GMPLS (g-LSPs) as control plane for simplified end-toend path/tunnel provisioning
RSVP-TE for CAC for Ethernet packet services for deterministic QoS and BWmanagement
Simultaneously supports TDM services

MSPPs today support Switched Ethernet and EPL Services over SONET/SDH
GMPLS provides the common control plane for Ethernet and TDM services

9

Turin Networks Confidential – Do Not DistributeService Types and Requirements
A look at the services and converged
infrastructure performance requirements

10

Turin Networks Confidential – Do Not DistributeConverged Services Transport
WSPISP
TSP

DS1s/E1sand
PDHoE(PWE/CESoP)

Wireless
BackhaulBusiness, Government,
Education

11VSPConverged
Services Transport
Network

E-Line (EPL,EVPL), E-LAN,TDM Voice andPrivate Lines

Turin Networks Confidential – Do Not Distribute

Ethernet P2P andP2MP Ethernet Virtual
Connections (EVCs)
Residential
Triple-Play

Triple Play Service Transport Options
DSL, PON, HFC
Power line

802.1ah/PBT B-VLAN,MPLS LSP or
GMPLS g-LSP
802.1Q

ISP

VSP

AccessMultiplexer(CMTS, PON,
DSLAM or PowerLine Head End)PBB/PBT,MPLS orSONET/SDH

Telephony Service
Internet Access Service
VoD/MoD ServiceVSP

802.1ad(QinQ)P2MP EVCs

P2P EVCs(VoD/MoD)

TSP

IPTV Service

802.1Q VLAN ID can identify subscriber or service
If typical customer subscribes to 3 to 5 services
802.1Q VLAN ID would support ~800 subscribers per Access Mux

12(IPTV)

Turin Networks Confidential – Do Not DistributeServices to support over Converged Transport
Network – Business, Govt. and Education Services
Ethernet Private Line and Ethernet Internet Access“Pipe service” most commonly implemented over SONET/SDH

Ethernet VPNs
E-Line (EVPL) and E-LAN (VPLS, TLS)
Can implement over Ethernet, MPLS and SONET/SDH

Legacy services over Ethernet
PBX PRI Trunks
T1/E1 Private Lines
Require PDHoE to implement over Ethernet or MPLS
Transported unaltered over SONET/SDH

13

Turin Networks Confidential – Do Not DistributeMultiservice Transport Network Service
Management Requirements
Fault Isolation
Need to determine if the fault is in the Ethernet Service Layer orTransport Layer
Need to be able to troubleshoot:Ethernet Service, end to end (Service Continuity Check)End-to-end path and local interconnections

QoS Performance Monitoring (PM)Need to measure/report at service level and transport level:
Delay, Delay Variation and Loss
Goodput and Throughput

Required for Service Level Objectives specified in SLA

14Turin Networks Confidential – Do Not DistributeMany

EoS/EoSDH(VCAT/LCAS/GMPLS)

PB(QinQ)

EoMPLS(PWE)

Some

Deployments

Converged Services Transport Technology“Magic Quadrant”

Palit
note

PBB
PBT(GMPLS)
Early Stages

MatureTechnology Maturity

15

Turin Networks Confidential – Do Not Distribute

iConnect™ Network

16

Turin Networks Confidential – Do Not DistributeTurin Optimized Service Delivery Architecture
Ethernet

Connection Oriented MPLS Ethernet

MPLSSONETAccess

MetroTE-300

ResidentialServiceEdge

E2E MPLS aware
Ethernet /SONET/OTN

Ethernet

Core10GbE

TE-206
OC-48
TE-25

Wireless

TE-b

TE-aInternet

PWE3
Enet

DWDM

Video

GFP
DS3/E3nxT1

10GbE

Traverse

TPE-1200
PPP
GbE
nxT1

Business

IP/MPLS

Traverse

EoPDH

Traverse

Voice

iConnect™

Seamless delivery of Ethernet End-to-End Services
Guaranteed Ethernet SLA Service delivery quality
Access over any media, coexistence of SONET and Optical Ethernet.
17Turin Networks Confidential – Do Not DistributeMobility Network Evolution Target
Any to Any Service with Ethernet Transport
Ethernet
Transport
AccessAny Service
can be transportedusing Ethernet

EdgeCoreEdge

Ethernet

MPLS

Ethernet

IPTDM

MPLS
Only in Core

Ethernet

AccessIPMPLSIP
Ethernet

Ethernet

Pseudowire

TDM
Pseudowire

IPIP

Any ServiceAny Service• All Transport is over Ethernet• Native Ethernet Access node accepts all services• Takes advantage and benefits of MPLS with reduced cost
• Transported over Ethernet to Core Aggregator• Simplifies operational complexities• MPLS routing and protection in the core
• Allows legacy services currently deployed to be managed• Ethernet Protection Switching at the Edgeand transported on same transport network.

18Turin Networks Confidential – Do Not DistributeMobility Network Evolution
2007 with Turin Traverse
Ethernet
Transport
Over PDHAccess

GMPLS
Only in CoreEdge

Any Service
can be transported
using Ethernet
CoreEdge

Ethernet

TDM

Ethernet

TDM

GMPLS

IPIP

Ethernet
GFP

1gb or 10Gb
Ethernet
overSONET

Ethernet
MPLS
SONET

• Ethernet transported EoPDH at Access• Ethernet transported Ethernet over SONET at Edge
• TDM Transported TDM/SONET• GMPLS based path protection

19Access

Turin Networks Confidential – Do Not Distribute

TDM

IP
Ethernet
GFP

TDM

Mobility Network Evolution
2009 with Turin Traverse
Ethernet
Transport
Over PDHAccess

MPLS
Only in CoreEdge

Any Servicecan be transported
using Ethernet
CoreEdge

Ethernet

Ethernet

TDM

TDM

MPLS

IPIP

Ethernet
GFP

TDM

IP

1gb or 10Gb
Ethernet

MPLS
Ethernet

Ethernet
GFP•TDM Pseudo-wire aggregation on the Edge
• MPLS routing and protection in the core for all service

20Access

Turin Networks Confidential – Do Not Distribute

TDM

Mobility Network Evolution
End-to-End Ethernet using GMPLS (2008)
Primary LSPCore
ADM+ =MPLS

ADM with
GMPLS
Switching

Backup LSP

G-MPLS
Edge

LSP’S

OSPF-TE
RSVP-TE

A

Edge

LSP’S

B

GMPLS
• Delivers End-to-End Ethernet over TDM/Lambda• Support Path Restoration, more flexible use of BW.
• Support sub 50mS protection switching without dependency on SONET protection (EPL & EVPL)• Support Provider Backbone Bridge and PBB-TE
21

Turin Networks Confidential – Do Not DistributeMobility Network Evolution
End-to-End Ethernet - MPLS (beyond 2008)
Core Routers

MPLS

10GbE

B

OSPF-TEMPLS
A

LSP’S LER

XX

LSR

LSP’S

OSPF-TE
RSVP-TE
LDP

MPLS

MPLS
• Delivers Ethernet over MPLS
• Opens the Traverse Routing to external Routers.
• Provides E2E over the Core Routers• Traverse can be used as an LER (Edge Router for services)• Provides Fast Re-Route22

OSPF-TELSR

Turin Networks Confidential – Do Not Distribute

XXLSP’S

Conclusion
Turin solution builds on existing GMPLS based control plane
Several Technology Choices for converged services
infrastructure
Hitless addition/removal of optical BW using VCAT/LCAS
Selective upgrades to mesh network along spans that areheavily used
Allows TDM/Ethernet/MPLS/PBT switching to co-exist on thesame network element
MPLS encapsulation of Ethernet (EoMPLS) and pseudo-wires
Fast-reroute based protection of the RSVP tunnels
Enable an evolutionary change from TDM to packet switched
networks (pay as you grow)
Unified control plane model leverages the best of TDM/packet
worlds to provide optimal solutions
23

Turin Networks Confidential – Do Not Distribute

Summary – Why Turin?
Versatile, Next-Generation Product Offerings Rapid delivery of new packet-based services for the lowest cost Supports future product extensions through a continuous stream of
new service modules

Large and Diverse Customer Base
 Tier-1 such as Verizon, Alltel, NTT and Cable & Wireless as well as
numerous ILECs, CLECS, Utilities, Wireless carriers, and MSOs Drives broad feature set while fostering an emphasis on productresilience

Focus on Customers
 Large enough to be considered a industry leader, small enough tocare about our customers

24

Turin Networks Confidential – Do Not Distribute