1 What is MPLS

2 MPLS Service Models

3 What is MPLS-TP

4 MPLS-TP Framework

5 MPLS-TP OAM Model

6 EPT Network Architecture

7 Service Overview

1 What is MPLS

2 MPLS Service Models

3 What is MPLS-TP

4 MPLS-TP Framework

5 MPLS-TP OAM Model

6 EPT Network Architecture

7 Service Overview
An VPWS service provides a point to point connection
between two nodes.

 From the customer’s perspective it looks as if a

leased link exists between the two locations.
 The Service provider can apply billing, ATM/FR/Eth/TDM

ingress/egress shaping and policing

 No MAC learning required
 One common Infrastructure for different access PE B
technologies (ATM, FR , Ethernet)
ATM/FR/Eth/TDM

ATM/FR/Eth/TDM

PE A PE C
IP / MPLS
Network

PW service

PE D ATM/FR/Eth/TDM
 From the customer’s perspective PE B
it looks as if all sites are B
Red VPLS
Service
connected to a single switched B

Green VPLS
VLAN like LAN Service

PE A PE C
 Service provider can reuse the
B
MPLS infrastructure to B
B
offer multiple services B

IP / MPLS
Network
 The Service provider can apply
billing, egress shaping and ingress
B
B
policing PE D
1 What is MPLS

2 MPLS Service Models

3 What is MPLS-TP

4 MPLS-TP Framework

5 MPLS-TP OAM Model

6 EPT Network Architecture

7 Service Overview
MPLS-TP is a subset of IP/MPLS, stripped out most of IP/MPLS complexities, with
additional functionality based on transport requirements

MPLS

IP/MPLS MPLS-TP

 ECMP
 MPLS forwarding Additional
 PHP
 MPLS/PWE3 architecture functionality based
 IP dependencies
 G-MPLS/T-LDP control plane on Transport
(forwarding)
 etc.. requirements.
 etc..
1 What is MPLS

2 MPLS Service Models

3 What is MPLS-TP

4 MPLS-TP Framework

5 MPLS-TP OAM Model

6 EPT Network Architecture

7 Service Overview
1 2
Transport LSP Service LSP / PWE
 NNI to NNI Label Path Establishment.  UNI-N to UNI-N Label Establishment.
 PWE as a Network Layer

PW adapts L2 client signals Strict path LSP, bidirectional and

to MPLS-TP LSPs. co-routed.
P
PE PE

 Transport LSP

Transport LSP 
P P
 Management System (OS)

P
PE PWE3s (IPLS, VPLS,
P P VPWS, VPMS)
PE MPLS (-TP) LSPs
PE

P P



 T-PE
T-PE S-PE S-PE MPLS-TP Client
Client MPLS-TP MPLS-TE
Network
Network

Core Access/Aggregation
Access/Aggregation

Works same as Multi-segment PW over MPLS-TP LSPs

Use of MS-PW is accentuated –

OAM

Protection
1 What is MPLS

2 MPLS Service Models

3 What is MPLS-TP

4 MPLS-TP Framework

5 MPLS-TP OAM Model

6 EPT Network Architecture

7 Service Overview
MPLS-TP uses In-band OAM similar to transport model.

RFC5586 Generic Associated Channel(G-ACh) generalizes PW ACh to

enable OAM on MPLS LSPs & Sections.

Link LSP PW
One common OAM solution for LSPs and PWs

All OAM functionality is in-band

LSP
Associated Channel
MPLS-TP OAM Compatible with MPLS OAM OAM Packets
Customer Traffic
MPLS-TP OAM
- MPLS Ping co-routed bi-directional LSPs


MPLS Echo Request

PE1 PE2

MPLS Echo Reply

MPLS Ping
MPLS echo request is sent in-band with LSP.
MPLS echo request packet has the following encapsulation
MPLS echo reply is in-band with LSPs

27
© Ciena Confidential and Proprietary This roadmap is not a commitment and is intended for reference purposes only.
MPLS-TP OAM
- MPLS Traceroute co-routed bi-directional LSPs


MPLS echo request

PE1 PE2

MPLS echo reply

MPLS traceroute
MPLS traceroute request is sent in-band with LSP.
MPLS traceroute reply is in-band with LSPs
MPLS traceroute request / reply packet has the following encapsulation

28
© Ciena Confidential and Proprietary This roadmap is not a commitment and is intended for reference purposes only.
1 What is MPLS

2 MPLS Service Models

3 What is MPLS-TP

4 MPLS-TP Framework

5 MPLS-TP OAM Model

6 EPT Network Architecture

7 Service Overview
Bharti MPLS-TP Architecture
Access Aggregation Core

• TDM Aggregator Node

• Cater MSP 1+1 requirement
SDH

TDM using Ch.STM-1 smart SFP

aggregating over 6200 (Interop)

Agg Ring / Mesh

VRRP

MPLS Cloud
Dual Home Ring (10G)
MSC/RNC/EPC

MWA • PW stitching functionality meet by

node at the aggregation layer • Terminating node for all LSPs & PW
• 802.1Q hand off to VRRP nodes

• Cater Packet & TDM access requirement

• Cater MSP 1+1 requirement

• MS-PW Cater 50ms switchover requirement as well as scale and interoperability requirements

• MS-PW support in Ciena box will cater to mesh networks through Static/Dynamic stitching
Access to Core (Packet Services)

AG-1 Core-A

Secondary Static LSP-2

Primary Static LSP-1
Secondary Static LSP-2 SP
Primary Static LSP-1 PW-2A

AC-1

MWA Access Ring Cloud Symbolizes

Multiple Cascaded VRRP
Aggregation Rings

Standard LAG

Secondary Static LSP-2

PW-2B
Primary Static LSP-1 SP
Secondary Static LSP-2 Core-B
Primary Static LSP-1
AG-2
• Aggregator Node of Access
Ring will act as PW stitching • Reliable handoff to RNC/EPC
• 2 Static LSPs with PW facing towards
point • Redundant handoff to PE
NTE-A and similar setup from AG-2 site
node (Deterministic Path) routers using VRRP at the
• Fiber cut in each ring will provide 50ms NNI
traffic protection
1 What is MPLS

2 MPLS Service Models

3 What is MPLS-TP

4 MPLS-TP Framework

5 MPLS-TP OAM Model

6 EPT Network Architecture

7 Service Overview
Wireless Backhaul-3G Service

3G RNC
Node PW-100

B VRRP

PW-200

Node
Data VLAN: 100
B Voice VLAN : 200
OAM VLAN : 300
Active co-routed LSP for Voice, Data, OAM
Backup co-routed LSP for Voice, Data, OAM
Active PW Multi segment
Stitching Point Active co-routed LSP for Voice, Data, OAM
Backup PW
Backup co-routed LSP for Voice, Data, OAM

 One VPWS instance with 3 bundled VLANs for data, voice & OAM
 On active (PW-100) PW failure, VS enables protection switching and makes backup peer(PW-200) PW active

1:1 static co-routed bidir LSP protection for carrier class resiliency

 E2E Static Solution

Wireless Backhaul-LTE Service

EPC

eNod
eB

eNod
S1-u: 400
eB S1-c: 500
X2: 600

Active co-routed LSP for S1-U/C/X2

Multi segment Backup co-routed LSP for S1-U/C/X2
Stitching Point
Active co-routed LSP for S1-U/C
Backup co-routed LSP for S1-U/C

Active co-routed LSP for S1-U/C

Backup co-routed LSP for S1-U/C
 One VPWS instance for point-to-point data & control traffic i.e. for S1-u (VLAN 400 )and S1-c (VLAN 500)

 Fully meshed VPLS instance for X2 communication on each access node ring. This uses VLAN 600

 1:1 static co-routed bidir LSP protection for S1-u,S1-c and X2 traffic.