hiT 7300

GMPLS Introduction
Objectives

Upon completion of this eLearning, you will be able to:

• Describe GMPLS
• Recognize the difference between ASON and GMPLS
• Describe features, added benefits, and advantages of ASON/GMPLS
• Identify the architectural components of ASON networks
• Describe control plan protocols and functions
• Describe different protection types of a call

© 2018 Coriant. All rights reserved 00232 R7 2

 ASON/ GMPLS Overview

© 2018 Coriant. All rights reserved 00232 R7 3

Meaning of ASON/GMPLS

• ASON (Automatically Switched Optical Network)

– Architecture for transport networks enabling distributed connection control
– Requirement and architecture documents have been approved by ITU-T

• WSON (Wavelength Switched Optical Network)

– ASON networks based on WDM switching technology (photonic layer)
– Framework and specific ASON extension under definition by IETF

• GMPLS (Generalized Multi-Protocol Label Switching)

– Defines a suite of protocols to implement ASON/WSON functionality
– Extends MPLS signaling and routing protocols for use in circuit switched transport networks like SDH, OTN, DWDM
– GMPLS protocol standards are defined at the IETF
– Interoperability requirements at GMPLS domain borders (UNI, E-NNI, I-NNI) are defined by OIF

© 2018 Coriant. All rights reserved 00232 R7. 4

ASON / GMPLS Value Proposition for Transport Networks

Automated Network Operation

• Automated topology/resource discovery Reduce OPEX
• Automated end-to-end service provisioning
• Multi-layer/domain networking
VeryHigh
Very High Network
Network Reliability
Reliability
• Multiple failure network recovery Reduce CAPEX
• Bandwidth efficiency by sharing of
restoration capacity
FlexibleService
Flexible service Provisioning
provisioning

• Bandwidth on demand
• Class of services at transport layer
Improve revenues
• Traffic engineering

• Coriant’s optical and electrical switching platforms provide GMPLS control plane for photonic (wavelength) and electrical
(OTN) layers

© 2018 Coriant. All rights reserved 00232 R7. 5

 Architectural Components of ASON Networks
Network Management Plane (MP)
TNMS ASON - configuration management
manager - fault and performance monitoring
- accounting and security management
- manual service creation
ASON/GMPLS Control Plane (CP)
- network topology discovery
- automated e2e service creation
- traffic engineering
- automated service protection/restoration
hiT 7300
Data Transport Plane (DP)
- e2e data transport and aggregation
- multi-layer (lightpath, TDM, packet)
connectivity
© 2018 Coriant. All rights reserved 00232 R7.
The MP performs management
functions for the data transport
plane, the control plane and the
network as a whole.
The CP performs the service call and
connection control functions. Using
GMPLS protocols, the CP can set up
and tear down network connections,
and restore network connections in
failure cases.
The DP provides end-to-end transfer
of client user data information. The
transport plane is usually layered as
defined in ITU-T Rec. G.805.
6
GMPLS Control Plane
GMPLS Control Plane Protocols

• LMP: Link management protocol

– Manage and maintain the health of control and data planes between two neighboring nodes;
• OSPF-TE: Open shortest path first-Traffic Engineering
– Routing protocols for the auto-discovery of network topology, advertise resourse avaliability (e.g
bandwidth or protection type);
• CSPF: Constraint Shortest Path First
– Based on OSPF route information, calculated the path for tunnel;
• RSVP-TE: Resource reservation protocol for traffic engineering
– Based on CSPF’s result, send message to create the tunnel hop-by-hop.

© 2018 Coriant. All rights reserved 00232 R7 8

GMPLS Control Plane Functions
Inventory and Resource Management
1. Neighbor Discovery 2. Global Topology Discovery

Management Plane

Control Plane

Transport Plane

Protocols:
Dynamic Provisioning Network Resilience (without UNI) 1: LMP
2: OSPF-TE
3. Signaling for Connection Provisioning 5. Distributed Recovery 3: RSVP-TE
4: CSPF
4. Routing (Path Calculation) 6. Fault Localization 5: all
6: LMP

© 2018 Coriant. All rights reserved 00232 R7 9

GMPLS Control Plane Functions in hiT 7300 DWDM Networks

ASON (WSON) topology discovery for DWDM

• Automated discovery of ASON DWDM network topology
• Discovery of available wavelength capacity on OMS TE links

OCh service provisioning

• Automated end-to-end service provisioning of OCh channels by GMPLS control plane
• Optical path computation by central PCE (offline) or embedded PCE in NE
 Including path validation on linear and nonlinear optical impairments
• OCh service creation and SLA provisioning using TNMS (ASON manager)

OCh service restoration

• Pre-planned (shared) OCh restoration
 single failure recovery by pre-planned restoration path
• Dynamic OCh restoration by Dynamic Source Rerouting (DSR)
 Multiple failure service recovery by dynamic path rerouting
• 1+1 OCh/ODU protection combined with OCh restoration
 Multiple failure fast service recovery (50ms)

© 2018 Coriant. All rights reserved 00232 R7 10

 GMPLS Data Transport Plane for
hiT 7300

© 2018 Coriant. All rights reserved 00232 R7 11

ASON Components/Layers Overview

• ASON Components and Layers

– Physical Interface: Actual physical port.
– Component Link: Logical link between two I-NNI ports (representing the physical fiber connection).
– TE-Link: Association of traffic engineering parameters (metric and SRLG) to the Component Link.
– LSP (Label Switched Path): E2E GMPLS tunnel (ODUk).
– CALL: E2E ASON service built upon one (unprotected) or more (protected) LSPs. Calls are managed by
(and stored in) the ingress node (A-node).

Call

Configuration
encapsulation

LSP LSP CALL

sequence
sequence
Frame

…
Physical Component
TE-Link Interface Link
TE-Link
LSP CALL
Component Link
Physical Interface

(Compliant with ITU ASON standard naming)

© 2018 Coriant. All rights reserved 00232 R7 12

Traffic Engineering (TE) Link

• Traffic Engineering (TE) Links are connections between the NEs inside GMPLS domain
which
– represent the data links in the control plane and
– model the physical OMS which are identified by unnumbered addresses and
– are always considered bidirectional.
– are used for path calculation and GMPLS signaling.
TE Link Management

• The control plane automatically build unbundled TE-Links, and then no manual
configuration by the operator will be required.
• After triggering the Auto TE Link detection by LCT, the Control Plane will automatically
create a TE-Link for each Component Link existent in the NE.
• Then, ASON Manager is only required to
– retrieve, update and display the TE Links automatically created by the NEs.

• If one Component Link is disabled and if the respective TE-Link have an inactive Call
associated, the TE-Link will be in deactivate state.
After the call be deleted it’s possible to delete TE-Link too.
Label Switch Path (LSP)

• Path through the network formed of cross-connected labels on a series of data plane
links.
• The route used by the LSP can be selected in two different ways depending on the
requirements of the Call, the same route can be specified hop by hop by the user.
• Depending on the call type, routes are preplanned in Coriant TransNet or calculated by
the control plane.

© 2018 Coriant. All rights reserved 00232 R7 15

hiT7300 GMPLS Call Characteristics

• In the case of the hiT 7300 only services on the OCh layer are supported.
• Elementary signal/rate: 2.5G, 10G, 40G, 100G and 200G.
• Termination: the GMPLS Calls are terminated on the transponder, filter or amplifier cards
• Direction: bidirectional.
• Connection type: Soft Permanent Connection (SPC).
• The GMPLS controller configures the necessary cross connections and wavelength
assignment

hiT 7300 hiT 7300

A call is a relationship between two endpoints (with working and
protecting paths) within ASON domains. A call has one or more
underlying Label Switched Paths (LSPs)

Call
© 2018 Coriant. All rights reserved 00232 R7 16
Connection Types / Calls supported by GMPLS

The following types of Calls are supported:

• Transponder Calls (connection starting at transponder):
this is the normal connection type. It is possible to use different wavelengths on the
working and restoration paths.
• Alien/friendly Calls (in case of an alien wavelength or friendly wavelength):
GMPLS services (unprotected or shared mesh restored) can only start at filter ports;
working and restoration path must use the same wavelength.
• Mixed transponder/alien Calls:
GMPLS services can start/end at a filter port and end/start at a transponder; working
and restoration path must use the same wavelength.

The Term “Call” corresponds in this context to the OCh Connection. One Call is one
OCh Connection with one or more LSPs.

© 2018 Coriant. All rights reserved 00232 R7 17

GMPLS Calls Overview

• Calls are the relations between two

endpoints (with working and protection
paths) within ASON domains.

• The following protection classes are

supported:
– Unprotected
» The unprotected scheme provides no resilience ability and
consists of one path.
– Pre-planned shared-mesh restoration
» A wavelength can be shared by two or more restoration
LSPs
– 1+1 protection combined with shared-mesh
restoration
» It is realized as two independent OCh shared-mesh
restoration Calls with OChP configured (manually) on both
ingress and egress nodes.
– Dynamic Source Rerouting (DSR)
» DSR automatically reroutes the protected traffic as long as
network resources are available.
available supported types of Calls in the hiT 7300 NEs

© 2018 Coriant. All rights reserved 00232 R7 18

Call Protection/Restoration Schemes Overview on hiT7300

 Unprotected
- If the working path fails, there is no protection. The
communication will be interrupted.
 DSR (Dynamic Source Rerouting)
- Multiple failure restoration.
- Upon failure, a new restoration path (E2E) is computed and
established by the ingress node. X
- The new LSP is established before the old LSP is torn
down.
 Pre-Planned Shared Restoration
- Restores a path affected by a failure end-to-end to a pre-
planned restoration path.
- Highly resources efficiency: the transport resources that are
not occupied can be shared among restoration paths that
don’t need the resources at the same time.
Working
Protecting
X Link failure

© 2018 Coriant. All rights reserved 00232 R7 19

Different Protection Types of a Call

20
Different Protection Types of a Call

 Unprotected call with GMPLS (1+1

path Protection)
 Pre-planned shared-mesh Unprotected Call with GMPLS (1+1 path Protection)

restoration
 1+1 protection combined with
shared-mesh restoration
 Dynamic Source Rerouting (DSR) OCh Shared Mesh Restoration - Preplanned

1+1 OCh Protection with OCh Pre-planned Shared Restoration

Dynamic Source Rerouting (DSR)

© 2018 Coriant. All rights reserved 00232 R7 21

Unprotected Call with GMPLS (1+1 path Protection)

• Working and protection paths are fixed provisioned with predefined routes and
wavelengths (wavelengths “lit” and constantly supervised)
• Fast protection (50ms) for optical channels or ODU path, optionally including
transponder/muxponder protection

protection OCh
optical protection card
(O02CSP)
(same wavelengths for
work./prot./restoration)
TXP CE

CE TXP

working OCh

CE: customer (client)

equipment
TXP: Transponder / Muxponder

© 2018 Coriant. All rights reserved 00232 R7 22

Pre-planned Shared Mesh Restoration Calls Overview

• OCh Pre-planned shared mesh restoration

• 1+1 OCh protection with OCh pre-planned shared restoration

© 2018 Coriant. All rights reserved 00232 R7 23

Pre-planned Shared Mesh Restoration on hiT 7300 OCh Layer

 Pre-planned restoration path is pre-provisioned by the control plane of

the network
 Pre-planned restoration path reserves network resources
 Pre-planned restoration path is only activated (lit) if required for
restoration of associated working path
 Optional bandwidth sharing: different pre-provisioned restoration paths
can (partially) share the same network resources (links & wavelengths)
 Optical performance pre-validated during planning process (offline)

© 2018 Coriant. All rights reserved 00232 R7 24

OCh Shared Mesh Restoration - Preplanned

working lightpath W1

CE TXP TXP CE

restoration lightpath R1
CE customer (client) equipment shared lightpath
segment (R1+R2)
TXP Transponder • optional regenerators (3R)
in each GMPLS lightpath
• 3Rs can be shared for different
restoration paths
restoration lightpath R2

CE TXP TXP CE
working lightpath W2

Optical Multiplex Section (OMS)

• Detection of OMS link failures and availability by control plane

• Resource reservation for pre-planned restoration paths with possibly wavelength sharing
• Working and restoration paths can optionally include regenerators (3Rs), which can be optionally be shared (pool)

© 2018 Coriant. All rights reserved 00232 R7 25

Partial Re-use of Working Path Resources for Restoration Path

W+R wavelengths W+R wavelengths

sharing on OMS link sharing on OMS link

failure

W
CE TXP TXP CE
W+R R W+R

W: Working path (LSP)

R: Restoration path (LSP)

• Real network topologies do not always allow fully disjoint end-to-end routes for working and restoration paths
• Service access points (transponders) can be located in deposited NE‘s which have only a single optical OMS link connection
(stub link) to the main DWDM (mesh) network
 sharing the same wavelength channel for working and restoration paths on common stub links saves any additional restoration
wavelength reservation on the OMS stub links

© 2018 Coriant. All rights reserved 00232 R7 26

Sharing of Regenerators for OCh Restoration

W
W
CE TXP REG TXP CE
R
R

W: Working path (LSP) shared

R: Restoration path (LSP) regenerator or
TXP: Transponder regenerator pool
REG: Regenerator

• Regenerators can be shared between working and corresponding pre-planned restoration GMPLS paths.
• Regenerators can be shared between different pre-planned restoration GMPLS paths.

© 2018 Coriant. All rights reserved 00232 R7 27

1+1 OCh Protection with OCh Pre-planned Shared Restoration

protection OCh
optical protection card
(O02CSP)
(same wavelengths for 2nd failure
1st failure
work./prot./restoration)
TXP CE

CE TXP

working OCh

CE: customer (client) equipment

TXP: Transponder / Muxponder
shared restoration OCh for
working/protection OCh

• fast 1+1 OCh protection via optical channel protection card

• double failure resilience by restoration of failed OCh trails
• shared OCh restoration for both working and protection OCh path, sharing the same wavelength
© 2018 Coriant. All rights reserved 00232 R7 28
Dynamic Source Restoration (DSR) on hiT 7300 OCh layer

 Dynamic rerouting of optical channels by control plane in case of

failure(s) using any free wavelengths
 Wavelength (re-)assignment for rerouted channel (if necessary)
 Local rerouting around failed network segments (make-before-break
with resource re-use)
 Optical channel performance validation within NE

© 2018 Coriant. All rights reserved 00232 R7 29

GMPLS for Dynamic Source Rerouting (DSR) Overview

• DSR calls are supported for

– OCh connections between hiT 7300 transponder/muxponder line ports (without 3R)
» Optional: with 1+1 client side protection using O02CSP/O03CP
» Optional: with 1+1 line side protection using O02CSP
– OCh connections between hiT 7300 alien wavelength ports (without 3R)

 Call modifications
– Unprotected call (with explicit hop list) to DSR call (preserving same explicit hop list in case of no failures)
– DSR call to unprotected call with explicit hop list

 Switching types and parameters

– Non-revertive or revertive switching
» revertive calls: the initial path and resources of an LSP is reserved by the GMPLS CP
» non-revertive calls: the GMPLS CP reserves only the resources for the actual path
– Revertive switching by manual or automatic control
» automatic revertive switching: switch back to the initial path in case of failure recovery and expiry of wait-to-
restore timer
» manual revertive switching: the operator can trigger revertive switching via TNMS
– Wait-to-restore time (for automatic revertive switching)
– Maximum recoveries (1-10) by rerouting

© 2018 Coriant. All rights reserved 00232 R7 30

 Dynamic Source Rerouting (DSR) for Optical Channels

• Fully automated OCh restoration by GMPLS control plane, using any free wavelength capacity on OMS links
• Dynamic Source Rerouting (DSR) of OCh path between ingress and egress transponder ports, or alien wavelength
ports
 Optical path performance validation by control plane for transponder connections
 complete optical channel re-routing between ingress and egress NEs, supporting wavelength change for tunable transponders
 re-use (if possible) of existing wavelength connections on fault-free links

Mx:0.1
B
CE TXP

Mx:0.1
Mx= Performance metric A 2nd failure

1st failure
{0.1 or 0.22 or 0.3 or 0.4} Mx:0.1
Mx:0.1
1st selected Path: ∑Mx=0.2<0.9 F
2nd selected Path : ∑Mx=0.4<0.9 C Mx:0.2
3rd selected Path : ∑Mx=0.6<0.9 3rd failure TXP CE

4th selected path: ∑Mx=0.7<0.9

Mx:0.3
h
D
Mx:0.3 Mx:0.3

E
© 2018 Coriant. All rights reserved 00232 R7 31
1+1 OCh Protection with OCh Dynamic Source Restoration (DSR)

Restored OCh #2
after 2nd failure
E
D SRLG=8

2nd failure

optical protection card

(O02CSP)
(same wavelengths for Initial OCh #2 F
work./prot./restoration)
Restored OCh #1 1st failure
after 3rd failure TXP CE

CE TXP
Initial OCh #1
A C
CE: customer (client) equipment
TXP: Transponder / Muxponder
Restored OCh #1
after 1st failure

B
• Fast 1+1 OCh protection (50ms) via transponder cards and optical protection card
• Multiple failure resilience by GMPLS restoration of failed OCh trails
• 2-path diverse routing based on shared risk link group parameters (SRLGs)
© 2018 Coriant. All rights reserved 00232 R7 32
Summary

In this eLearning, the following content was covered:

• Describing GMPLS
– Recognizing the difference between ASON and GMPLS
– Describing features, added benefits, and advantages of ASON/GMPLS
– Identifing the architectural components of ASON Networks
– Describing control plan protocols and functions
– Describing different protection types of a call

© 2018 Coriant. All rights reserved 00232 R7 33

For more information on
Coriant Training Services:
training@coriant.com