Investigation of OTN Capabilities in the NREN Environment ... · Investigation of OTN Capabilities in the NREN ... OTN architecture for NRENs OTN testing – results ... Which OTN

connect • communicate • collaborate

Investigation of OTN Capabilities in the NREN Environment

(JRA1 Task 1, GN 3)

Anna Manolova Fagertun (DTU Fotonik)GN3 JRA1 T1&2 Workshop 2012, Copenhagen, 20-11-2012


Agenda

Background – the taskOTN introductionOTN architecture for NRENsOTN testing – resultsDiscussionSummary

2


JRA1 Task 1: OTN and GMPLS

The partners: NORDUnet, UNINETT and DTU FotonikThe vendors: ADVA, Ciena and Nokia Siemens NetworksTime-line: finalized in April 2012 (Deliverable DJ1.1.2)Goal:

To “learn” the technology – its advantages and limitationsTo investigate the maturity of existing platforms (not to compare!!)To evaluate the applicability of OTN within the NREN environment

The assumptions:Seamless integration of digital and optical layers (standardized)Common platform for mapping ANY type of client signal – fits with the diversity of NRENs and supported service typesMulti-granular switching and multi-level multiplexing for flexible high bit-rate flow handling Control-plane functionalities (GMPLS -compliant)

3


OTN introduction

G.709 (ITU-T) – “standardized method for transparent transport of services over optical wavelengths in DWDM systems”.

STANDARD – mapping, mux-ing, switching, OAM, multi-domain

4

Architecture, mapping, structures G.870, G.872

Management aspectsG.873.1/873.2, G.874,

G.808.1/808.2

Performance

G.8201, G.8251

Interfaces and equipment

G.806, G.709, G.798, G.798.1, G.959.1

Control PlaneG.8080,G.7712÷G.7716

Optical Transport Module

OTUk

OCC OCC OCC

Client

ODUk FECOH

OPUkOH

ClientOH

Dig

ital

dom

ain

Ass

ocia

ted

over

head

OOSOSC

OH

OH

OH

Non

-ass

ocia

ted

over

head

OCC


OTN benefits

Flexible “all-client-type” mapping (ODU0 and ODUFlex)Multi-level switching (any granularity)

TCM – Tandem Connection Monitoring

5

Service provider

Service providerCarrier

Client

Client

X

XX

X

X X

X

X

XX

A1 B1 C1 C2B2 A2

A1 - A2

B1 - B2

C1 - C2

TCM1 TCM1TCM2

TCM1TCM2TCM3

TCM1TCM2

TCM1

TCMi TCM OH field not in use TCMi TCM OH field in use

TCM2TCM3TCM4TCM5TCM6

TCM2TCM3TCM4TCM5TCM6

TCM3TCM4TCM5TCM6

TCM3TCM4TCM5TCM6

TCM4TCM5TCM6

HO ODUk ()

Client interface

Transport entity

Physical interface

HO ODUk ()

HO ODUk ()

ODUflexFlow (VLAN)

ODUflexFlow (VLAN)Phy

HO ODUk ()ODUflex

ODUj

Phy

Phy

Phy

ODUflexPhy


OTN benefits: cont.

ODUk protection standardized1+1 SNCPAPS-based schemes (1:1; 1:nshared protection, etc.)TCM-based SNCP(with sub-layer monitoring with SF/SD conditions per TCM level)

OCH/OMS SPRing protectionWork in progress – survivability at the analogue layer!!!!The challenge – APS channel implementation

– OOS – not standardized– IP packet format – use decoupled

CP

6

Control PlaneGMPLS-compatibleAutomatic topology discoveryAutomatic protection/restorationBandwidth on demandVertical integration across layers

CAPEX and OPEX savings!


NORDUnet

Domai 3

Xchange

OTN

Common Operation

Domain 2

GMPLS Enabled

Domain 4

* GMPLS enabled WSS based DWDM Node

GMPLS Enabled

OTN

OTN

OTN

OTN

OTN

OTN architecture for NRENs

Standard E-NNI between domains – fast, seamless service establishment across borders

Extended OAM across borders (end-to-end service monitoring) – SLA verification

Multi-level TCM – fast failure localization

Advanced MUX and switching for traffic exchange at different levels

7


OTN tests

Client mapping and ODU switchingODU 0 and ODU FlexMulti-stage multiplexing, sub-flow switching

SurvivabilityProtection and RestorationGMPLS-assisted survivability

Cross-domain OAMTCMTCM Delay measurements

GMPLS control plane supportTopology discoveryAutomatic service establishment/tear downAutomated restoration

8


Test setups

ADVA CIENA

9

NSN


Test results

Client signal mappingHigh-speed signal mapping – 10GE and 40 GE (GFP, GMP, BMP)ODU 0 – demonstratedODU Flex – no vendor had it available (only a lab demo)

ODU switching and multi-stage ODUk MappingMUX path: ODU0-ODU1-ODU2-ODU3ODU 0 – switched in themiddle node

Conclusions:– Functionalities according to standardization– The most promising feature (ODU Flex) is in the roadmaps– Very attractive features for support of high-bandwidth, dynamic

cross-domain services. 10


Test results cont.

SurvivabilityMany standardized schemes available

– 1+1 SNC/I – SD/SF at OTU overhead

– 1+1 SNC/N – SD/SF at PM field of ODU overhead

– 1+1 SNC/S – SD/SF at TCM level –very attractive for multi-domain environments

Control-plane assisted restoration– Dynamic control of the path via its

cost – either administrative or based on delay measurements

Hybrid Restoration/Protection– Pre-computed protection path– At time of failure, switch to the

protection path and reactively compute a new protection path

11

ConclusionsStandardized ODUksurvivabilityControl-plane assisted survivabilityMesh-based recovery

Explicit control of backup path via costsAutomatic – saves OPEX

Combined schemes – great flexibility, novel service opportunities


Test results cont.

TCMClientProviderInter-provider link

ResultsVery clear indication where the failure isNo more “pointing fingers” – exact responsibility indicatorRequires cooperative pre-planning, design and setup (complex and non-standardized procedure)Different vendors had different “views” of applicability! Multi-vendor interoperability can be problematic

12


Test results cont.

GMPLS Via packet traces analysis

– Topology discovery – via the OSPF-TE protocol– Automated provisioning and tear-down of connections– Automated restoration

Standard implementations, with added proprietary features– May differentiate the vendors on the market– But provides for interoperability issues– Explicit GMPLS interoperability between different

implementations is a must– Could be a GREAT tool for integrated, cross-layer/cross-

domain control (operational intelligence)

13


Discussion

Is OTN a relevant technology for your network? Why? Internally for the NREN itselfWith respect to serving current and future clientsWith respect to multi-NREN service delivery

Which OTN functionalities are interesting for your organization, and which are irrelevant? Can you see any potential use for future services in you organization?Is OTN relevant for GEANT (as a backbone provider)? – interconnecting NRENs and facilitating guaranteed QoS across domains

14


Summary

Highly scalable, future-proof technology

Unprecedented client signal mapping

Advanced OAM&P functionalities (GMPLS-ready)

Excellent solution for multi-domain service provisioning

Major vendors already offer advanced OTN functionalities

15


JRA1 Task 1 Contributors

Contributors:

Lars L. Bjørn – NORDUnetKurosh Bozorgebrahimi – UNINETT Alberto Colmenero – NORDUnet (Task Leader)Rasmus Lund – NORDUnetAnna Manolova Fagertun – DTU Fotonik

Please check the white paper and the final deliverableat the GN3 site

16


Thank you for your attention

17

Documents

Investigation of OTN Capabilities in the NREN Environment ... · Investigation of OTN Capabilities in the NREN ... OTN architecture for NRENs OTN testing – results ... Which OTN