Investigation of OTN Capabilities in the NREN Environment (JRA1 - - PowerPoint PPT Presentation

investigation of otn capabilities in the nren environment
SMART_READER_LITE
LIVE PREVIEW

Investigation of OTN Capabilities in the NREN Environment (JRA1 - - PowerPoint PPT Presentation

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 connect communicate collaborate Agenda Background the task


slide-1
SLIDE 1

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

slide-2
SLIDE 2

connect • communicate • collaborate

Agenda

Background – the task OTN introduction OTN architecture for NRENs OTN testing – results Discussion Summary

2

slide-3
SLIDE 3

connect • communicate • collaborate

JRA1 Task 1: OTN and GMPLS

The partners: NORDUnet, UNINETT and DTU Fotonik The vendors: ADVA, Ciena and Nokia Siemens Networks Time-line: finalized in April 2012 (Deliverable DJ1.1.2) Goal: To “learn” the technology – its advantages and limitations To 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 types Multi-granular switching and multi-level multiplexing for flexible high bit-rate flow handling Control-plane functionalities (GMPLS -compliant)

3

slide-4
SLIDE 4

connect • communicate • collaborate

OTN introduction

G.709 (ITU-T) – “standardized method for transparent transport of services

  • ver optical wavelengths in DWDM systems”.

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

4 Architecture, mapping, structures G.870, G.872 Management aspects G.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 Plane G.8080,G.7712÷G.7716

Optical Transport Module OTUk OCC OCC OCC Client ODUk FEC OH OPUk OH Client OH Digital domain Associated

  • verhead

OOS OSC OH OH OH Non-associated

  • verhead

OCC

slide-5
SLIDE 5

connect • communicate • collaborate

OTN benefits

Flexible “all-client-type” mapping (ODU0 and ODUFlex) Multi-level switching (any granularity) TCM – Tandem Connection Monitoring

5

Service provider Service provider Carrier Client Client X X X X X X X X X X

A1 B1 C1 C2 B2 A2 A1 - A2 B1 - B2 C1 - C2 TCM1 TCM1 TCM2 TCM1 TCM2 TCM3 TCM1 TCM2 TCM1 TCMi TCM OH field not in use TCMi TCM OH field in use TCM2 TCM3 TCM4 TCM5 TCM6 TCM2 TCM3 TCM4 TCM5 TCM6 TCM3 TCM4 TCM5 TCM6 TCM3 TCM4 TCM5 TCM6 TCM4 TCM5 TCM6

 HO ODUk () Client interface Transport entity Physical interface HO ODUk () HO ODUk () ODUflex

Flow (VLAN)

ODUflex

Flow (VLAN)

Phy HO ODUk () ODUflex ODUj Phy Phy Phy ODUflex Phy

slide-6
SLIDE 6

connect • communicate • collaborate

OTN benefits: cont.

ODUk protection standardized

1+1 SNCP APS-based schemes (1:1; 1:n shared protection, etc.) TCM-based SNCP(with sub- layer monitoring with SF/SD conditions per TCM level)

OCH/OMS SPRing protection

Work in progress – survivability at the analogue layer!!!! The challenge – APS channel implementation

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

CP

6

Control Plane

GMPLS-compatible Automatic topology discovery Automatic protection/restoration Bandwidth on demand Vertical integration across layers CAPEX and OPEX savings!

slide-7
SLIDE 7

connect • communicate • collaborate

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

slide-8
SLIDE 8

connect • communicate • collaborate

OTN tests

Client mapping and ODU switching ODU 0 and ODU Flex Multi-stage multiplexing, sub-flow switching Survivability Protection and Restoration GMPLS-assisted survivability Cross-domain OAM TCM TCM Delay measurements GMPLS control plane support Topology discovery Automatic service establishment/tear down Automated restoration

8

slide-9
SLIDE 9

connect • communicate • collaborate

Test setups ADVA CIENA

9

NSN

slide-10
SLIDE 10

connect • communicate • collaborate

Test results

Client signal mapping High-speed signal mapping – 10GE and 40 GE (GFP, GMP, BMP) ODU 0 – demonstrated ODU Flex – no vendor had it available (only a lab demo) ODU switching and multi-stage ODUk Mapping MUX path: ODU0-ODU1-ODU2-ODU3 ODU 0 – switched in the middle 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

slide-11
SLIDE 11

connect • communicate • collaborate

Test results cont.

Survivability Many standardized schemes available

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

  • verhead

– 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

Conclusions Standardized ODUk survivability Control-plane assisted survivability Mesh-based recovery Explicit control of backup path via costs Automatic – saves OPEX Combined schemes – great flexibility, novel service

  • pportunities
slide-12
SLIDE 12

connect • communicate • collaborate

Test results cont.

TCM Client Provider Inter-provider link Results Very clear indication where the failure is No more “pointing fingers” – exact responsibility indicator Requires 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

slide-13
SLIDE 13

connect • communicate • collaborate

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

slide-14
SLIDE 14

connect • communicate • collaborate

Discussion

Is OTN a relevant technology for your network? Why? Internally for the NREN itself With respect to serving current and future clients With 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

slide-15
SLIDE 15

connect • communicate • collaborate

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

slide-16
SLIDE 16

connect • communicate • collaborate

JRA1 Task 1 Contributors

Contributors: Lars L. Bjørn – NORDUnet Kurosh Bozorgebrahimi – UNINETT Alberto Colmenero – NORDUnet (Task Leader) Rasmus Lund – NORDUnet Anna Manolova Fagertun – DTU Fotonik Please check the white paper and the final deliverable at the GN3 site

16

slide-17
SLIDE 17

connect • communicate • collaborate

Thank you for your attention

17