GMPLS: IP-Centric Control
Protocols for Optical Networks
Yaohui Jin
State Key Lab of Advanced Optical Comm. System & Network
Network & Information Center
http://front.sjtu.edu.cn/~jinyh
Outline
 Part 1: Introduction
• Network trends
• Distributed control plane components
• Standardization
 Part 2: ITU-T ASON framework
 Part 3: IETF GMPLS architecture
• Evolution of standard
• GMPLS mechanisms
 Part 4: ASON/GMPLS is coming to us!
• IETF GMPLS implementation survey
• OIF Interoperability demonstration
• ASON/GMPLS in China
 Part 5: Conclusion
Part 1: Introduction
Network Trends
 Current world
Management
Plane
Centralized
SNMP
ATM
CORBA/
TMN
Data/Transport
Plane
SDH
IP
Service Layer
Give me more bandwidth!
Traffic interfaces
Transport Layer
Optical Give me more flexibility!
Network Trends
 Why we need ASON?
Management
Plane
ATM
IP
Service Layer
Data/Transport
Plane
Provide automatically
switching Traffic interfaces
for optical/transport networks by reusing
ubiquitous IP protocols with extensions.
 Discovery
 Routing
 Signaling
…
SDH
Distributed
Control Plane
Transport Layer
Optical
Benefits of ASON
Save on OPEX
In many of today's networks, highly specialized technicians often have to
spend days calculating and implementing connectivity changes. ASON
performs capacity assessment, path computation and provisioning rapidly.
Provide differential service levels
Based on data and optical protection levels that range from best effort to
fully protected with high availability.
Create new services
Set up and tear down connections in minutes for concert webcasts, high
speed data backup, employee training sessions and so on, generating new
service revenues by as much as 10 percent.
Postpone CAPEX investment
Cross-layer traffic engineering, dynamic routing and meshed restoration in
the optical network improves network throughput by as much as 30 percent,
allowing you to put off investments in additional capacity.
Distributed Control Plane Components
1. Discovery
– Protocol running between the
adjacent nodes.
– Am I connected to right neighbor?
– Who is my neighbor?
– What’s the type of service between
neighbor and me?
Distributed Control Plane Components
1. Discovery
2. Routing
– Link state information flooding
– Identical topology database in every
node
Distributed Control Plane Components
1. Discovery
2. Routing
3. Path Calculation
Z
A
– At source node
– Constraint based routing algorithm
– Output: an explicit route from A to Z
Distributed Control Plane Components
Z
A
1. Discovery
2. Routing
3. Path Calculation
4. Signaling
– Hop by hop
– Along the expected route
Distributed Control Plane Components
Z
A
1. Discovery
2. Routing
3. Path Calculation
4. Signaling
Except step 3, the others are protocol
procedures. To internetwork equipments
from different vendors, the protocols
have to be standardized
Standardization
Management Plane
TMN
ASON/ASTN
Control Plane
Transport Plane
Requirement
Architecture
Interfaces
…
SDH
OTN
SNMP
GMPLS
Architecture,
Protocols (IP-based)
SONET/SDH Ext.
G.709 Ext.
Recovery
…
SDH
OTN
…
ATM
Ethernet
…
UNI 1.0
ENNI 1.0
…
Part 2: ITU-T ASON framework
ITU-T Status
High Level
Requirements
G.807
ASTN
Architecture
G.8080
ASON
Detailed
Requirements
Protocols
G.7713
DCM
G.7712
DCN
G.7714
Disc.
G.7715
Routing
G.7713.1
G.7713.2
G.7713.3
G.7714.1
G.7715.1
O-PNNI
RSVP-TE
CR-LDP
Disc.
Routing
G.7716
Ctrl. Pl.
G.7717
CAC
ASON Architecture
NMI-A
ASON control plane
User
signaling
CC
I-NNI
CC
NMS
CC
CC
E-NNI
UNIcontrol
NMI-T
CCI
Clients
e.g. IP,
ATM, TDM UNI
Data
NE
NE
PI
NE
IrDI
Transport Plane
NE: Network Element
PI: Physical Interface
IrDI: Intra Domain Interface
NMS: Network Management System
NMI: Network Management Interface
CC: Connection Controller
CCI: Connection Controller Interface
UNI: User Network Interface
I-NNI: Internal Network-Network Interface
E-NNI: External Network-Network Interface
3 Types of Connections
NMI-A
ASON control plane
User
signaling
CC
I-NNI
CC
NMS
CC
CC
E-NNI
UNIcontrol
NMI-T
CCI
Clients
e.g. IP,
ATM, TDM UNI
Data
NE
NE
PI
NE
IrDI
Transport Plane
Permanent: set up from the management system with network
management protocols
Soft Permanent: set up from the management system which uses network
generated signaling and routing protocols to establish connections
Switched: set up by the customer on demand by means of signaling and
routing protocols
Part 3: IETF GMPLS architecture
IETF: Evolution of Standard
IETF
46-48
(1999)
IETF
48-49
(2000)
IETF
50-51
(2001)
• Step 1. MPLS: Multi-Protocol Label Switching
• Step 2. MPLS-TE: Traffic Engineering
• Step 3. MPlS: Multi-Protocol Lambda Switching
– MPLS control applied on optical channels (wavelengths
/lambda’s) and first “optical” IGP TE extensions
– New Protocol introduction for Link Management (LMP)
• Step 4. GMPLS: Generalized MPLS
– MPLS control applied on layer2 (ATM/FR/Ethernet), TDM
circuits (SDH/Sonet) and Optical channel (wave/fibre)
– IGP TE extensions including OSPF & IS-IS
• Step 5. GMPLS: More Extensions
IETF
52-55+
(2002)
–
–
–
–
LMP extended to “passive devices” via LMP-WDM
GMPLS covers G.707 SDH, G.709 OTN…
Graceful/hitless restart mechanisms (signalling & routing)
GMPLS-based Recovery
What is MPLS?





Turns an ATM switch into a router
Turns an IP router into an ATM switch
Put IP routing protocols on devices that are not IP routers
Different way to forward packets through a router
Label is local unique,
while IP address
is global unique
Routing
Routing
LSD
Protocol Messages
labels
FIB
LIB
LSR A
LSD
Protocol Messages
labels
FIB
Labeled
Packets
LIB
LSR B
LSD
FIB
Labeled
Packets
LIB
LSR C
LSD: Link State Database, FIB: Forwarding Information Table
LIB: Label Information Table, LSR: Label Switching Router
Traffic Engineering with MPLS




Constraint Based Routing extensions to IS-IS or OSPF
Explicitly routed MPLS path
Controlled from ingress using RSVP-TE or CR-LDP
Label Switched Path (LSP) tunnels are uni-directional pt-pt
connections
 Packets no longer need to flow over the shortest path
Egress
LSR
Ingress
LSR
User defined LSP
constraints
Constraint-based routing
Extended IGP
Routing Table
Traffic Engineering
Database (TED)
Constrained Shortest
Path First (CSPF)
Reduces the level of manual configuration
Input to CSPF
Explicit Route
• Path performance constraints
• Resource availability
• Topology information
Output
• Explicit route for MPLS signaling
RSVP Signaling
User
Constraints
MPLS Can Be Re-Used in Optical
Generalized Label Space 
Wavelength Identifier Space, Label
processing at control plane only
Label Space  FEC, Label processing
at both control and transport planes
MPLS Controller
IF in Label in IF out Label out
9
3
3
2
6
4
4
8
7
Common
Control Plane
7
9
9
GMPLS Controller
IF in Label in IF out Label out
2
6
8
mapping
1
1
1
2
6
4
5
4
7
5
4
9
mapping
l1, l2
l1, l2
1
l1
Packet
Switching
Matrix
2
2
2
Optical
3x3
Channel
Matrix
3x3
l1, l2
l1, l2
2
l2
3
3
3
l1, l2
l1, l2
DeMux
Label Read
Label Write
Label Switched Router
Optical Cross-Connect
Mux
3
GMPLS Mechanisms






Link Management Protocol (LMP)
Routing Extensions
Signaling extensions
Link bundling
Forwarding adjacency
LSP hierarchy
New protocol
Reuse IP MPLS
Scalability
Part 4: ASON/GMPLS is coming!
IETF GMPLS implementation survey
Company
Signaling
Protocol
Type
SDH/SONET
Extensions
Software
Genealogy
Switching
Capability
Label
Type
Status
Availability
Accelight
Equip.
R
Yes
External
PTL
MGS
Beta
Agilent
Tester
R
Yes
Internal
PTLF
MGWS
Product
On sale
Alcatel
Equip
R
Yes
External
TLF
GWS
Beta
On sale
Calient
Equip.
R
Ext + TE
LF
G
Beta
On sale
Ciena
Code
R
Yes
External
T
S
Alpha
Internal
Data Connection
Code
R
Yes
Ext + GMPLS
PTL F
MGWS
Product
On sale
Equipe
Equip.
R
Yes
Internal
PT
GS
Alpha
internal
First Wave
Code
R+L
Internal
LF
GW
Alpha
Internal
HCL Techno.
Code
R
Yes
ISI+TE,GMPLS
T
GS
Develop
-
Intel
Equip.
R
Yes
Internal
PT
MGS
Develop
-
Japan Telecom
Code
R
Juniper
Equip.
R
Lumentis
Equip.
R
Marconi
Equip.
R
Movaz
Equip.
R
NEC
Equip
NetPlane
Code
NTT
Equip.
R
Nortel
Code
Polaris
Equip
R
Yes
External
T
S
Develop
Internal
Tellium
Equip.
R
Yes
External
TLF
GS
Alpha
Internal
Tropic
Equip.
R
External
PLF
MGW
Develop
Wipro
Code
R+L
Internal
PT
MGS
L
G
P: 10, T: 14, L: 14,
F: 9
M: 10, G:21, W: 9, P: 4, A: 4, B: 3, D:
S: 17
7
Anonymous 2
24
Internal
G
Develop
Internal
Internal
P
MGS
Beta
Field trial
Ext+GMPLS
L
G
Develop
Internal
Yes
Internal
TLF
GWS
Yes
LabN+GMPLS
L
GS
Product
On sale
R
Yes
External
T
S
Product
On sale
R
Yes
Internal
PTLF
MGWS
Product
On sale
MGW
Develop
Yes
External
L
Equip: 14
Code: 8
-
-
Yes
PL
-
Yes
R
External
R:23
L:3
17
P=PSC, T=TDM, L=LSC, F=FSC
M=MPLS label, G=generalized label, W=waveband label, S=SDH/SONET label
Internal: 9
External: 14
-
-
MGWS
On sale
Internal
-
-
Internal
-
Develop
On sale
Internal
Source: IETF CCAMP working Group
On sale: 8
OIF Interoperability demonstrations
 UNI 1.0 demo at SuperComm 2001
• User Network Interface (UNI) 1.0 signaling
specification
• Proofed UNI interworking with over 25 vendors on
control plane and data plane
 ENNI 1.0 demo at OFC 2003
• Inter domain signaling
• Inter domain OSPF/ISIS based routing
• UNI and SPC initiated connection setup and removal
across multi domains over control plane
• Participated by over 12 vendors
ASON/GMPLS in China
 Some government funds
• National High Technology Research and Development
Program ( “863” PROGRAM), launched in March 1986.
• National Natural Science Foundation of China (NSFC)
• Some local government programs, such as Shanghai Optical
Science and Technology Program (SOST)
 “863” focuses on practical issues that are more related
to the information industry and economy in China.
 NSFC encourages basic research and investigation on
breakthrough technologies.
Four R&D Phases in 863
Field trial
3TNet
In Yangtse R Delta
ASTN
ASTN equipments
In China
ASON
ASON testbed
ASON scalability
& GMPLS
In Tsinghua U &
Shanghai JiaoTong U
IP/OTN
“CAINONet”
Based on IP/OTN
1Q.1999-3Q.2001
3Q.2001-2002
2Q.2003-2004
2005
Preliminary ASON Testbeds (01-03)
 Goals: to make breakthrough in the ASON and
GMPLS key technologies.
 Two groups led by Universities:
• Group in Beijing: Tsinghua Univ., Beijing Univ. of
P&T, Peking Univ.;
• Group in Shanghai: Shanghai Jiao Tong Univ.,
Alcatel Shanghai BELL, Shanghai Optical
Networking Inc..
 Two different ASON testbeds
• in Beijing
• in Shanghai
ASON in SJTU
ASON Scalability Experiment (03-04)
 Goals:
• Partition of layers and domains
• Topology abstraction
• Information exchange between layers
• Fast convergence of network topology
• End-to-end restoration
 Scalability
•
•
•
•
Totally at least 200 emulated nodes
4 layers
10 domains in a single layer
50 nodes in a single domain
ASTN equipments and Trial (03-04)
 Equipments project’s goal: 12 ASTN nodes;
 Equipment R&D project participants:
• ZTE with BUPT, WRI(Fiberhome) with SJTU, Huawei Tech.
 ASTN trial working group:
• Carriers: Beijing R&D Center of China Telecom, Shanghai
Telecom;
• Research Institutes: Research Institute of Transmission Technol
(RITT), Shanghai Telecom Technol Research Institute;
• Equipment Vendors: ZTE, WRI(Fiberhome), Huawei, Datang
• Universities: SJTU, THU, BUPT, EUSTC, PKU
 Working Group Tasks:
•
•
•
•
•
To contribute documents, drafts and standards
To define trial topology and application models
To setup an interoperability lab with third-party test tools
To test and evaluate the developed ASTN equipments
To carry out ASTN network trials in labs and in field
OIF 2005 Interworking Demo
Lannion,
France
Waltham
, MAUSA
Middleto
wn, NJUSA
Beijing,
China
Berlin,
Germany
Torino, Italy
Musashin
o, Japan
What is 3TNet ?
 Enabling technologies:
• To make breakthrough the Tbps DWDM, Tbps
ASTN, Tbps IPv4/v6 Routers, and application
environment and supporting platforms.
 Network:
• To build a broadband information network in
Yangtse River Delta jointly with the regional carriers
and governments.
 Practical Application:
• To develop new types of services and value-added
services, support Internet DTV/HDTV and interactive
multimedia.
Part 5: Conclusion
 GMPLS re-uses MPLS-TE concepts for the definition of distributed
control plane protocols applicable to non-packet or “optical”
oriented networks. It is composed of 3 main components: LMP,
OSPF-TE/IS-IS, RSVP-TE/CR-LDP.
 Forward adjacency, LSP hierarchy and bundling create sufficient
scalability and flexibility for common network operations.
 Hitless restart and GMPLS-based recovery provide resiliency for
control plane and reliability for transport plane respectively.
 GMPLS vs. ASON. GMPLS suite today is a Subset of ASON in the
sense that it specifically addresses the I-NNI interface at control
plane level, GMPLS suite is a Superset of ASON as it considers
explicitly data and transport networks at control plane level. ASON
is a Network Architecture, while GMPLS is a Protocol Architecture.
Thanks for Your Attention!
GMPLS is not the future, … it is the present!
Live Show
http://202.120.32.205:8080/DMA/DCL_Flex-debug/DCL_GUI_FLEX.html