Advancements in ONF Transport API for Orchestration of Multi … · 2019. 9. 2. · Orchestration of Multi-layer Connectivity Service Andrea Mazzini, Nokia Karthik Sethuraman, NEC

Advancements in ONF Transport API for Orchestration of Multi-layer Connectivity

ServiceAndrea Mazzini, Nokia

Karthik Sethuraman, NEC

September 2019*animated slides

ONF Transport API (TAPI): Functional Architecture

2

Topology Service

Connectivity Service

Path Computation Service

Shared Network Information Context

Virtual Network Service

Notification Service

NENetwork ElementsNENESDN Controller

NENESDN ControllerNENEApplication

Transport API or Other SBIs

Transport API or Other NBIs

OAM Service Equipment Inventory Service

Industry Adoption: Functional Interface solution that best fulfills conflicting requirements of stability (future proof, interoperability) & flexibility/agility (technology evolution)

OIF Transport API Interop Demo (2014, 2016, 2018)

3

Domain Controller

Domain Controller

Domain Controller

Multi-Domain Controller

Technology, Vendor Specificmodels

TAPI Agent

OSS/App/Orchestrator

Common Abstraction model

Transport API

Test Vendors

Test Carriers

Transport APITAPI Agent

Multi-Domain Controller

TAPI AgentTAPI Agent

TAPI AgentTransport API

MEF: Lifecycle Service Orchestration Reference Architecture (LSO RA)

4

MEF Common Resource Model

ONF TAPI Model

MEF: Service Provider, Operators, ICM Domains, UNI, ENNI, INNI (1)

5

UNI

Service Provider

Operator Operator

ICM Domain ICM Domain

ENNI

Service Provider

Operator Partner Operator

ICM Domain

ENNI

ICM Domain ICM Domain

INNIOLS

DomainUNI

MEF: Service Provider, Operators, ICM Domains, UNI, ENNI, INNI (3)

6

Service Orchestration Functionality (SOF), SP Domain

SOF, Operator Domain SOF, Partner Operator Domain

INTE

RLUD

EPR

ESTO

LEGA

TO

Infrastructure Control & Mng (ICM) ICM ICM

NodeNodeNode

UNIUNI

E-NNI I-NNI

Create L1 OVC

Create Connectivity Service

Create L1 VC

Create L1 OVC

Create Connectivity Service Create Connectivity Service

Create Connectivity Service

Open Line System ICM

OLS Node

MEF: Layer 1 Service across different Operators & Management Domains

L1 VC (the end-to-end Layer 1 Service)

L1 OVC L1 OVC

ConnectivityService ConnectivityService

Connection

NodeNode

Connection Connection

Node UNI

managed object classes at Service level (appearing at Legato, Interlude Management

IRPs)

ONF TAPI managed object classes at Resource level(appearing at Presto for provisioning purposes)

ONF TAPI managed object classes at Resource level(appearing at Presto for discovery purposes, e.g.

topology)

MEF Resource managed object classes augmenting TAPI

L1ConnectivityEndPointResource

L1UniNResource L1EnniNResource

ConnectivityService

UNI

L1InniN Resource

L1Connectivity Resource

L1ServiceLevelSpecification

SIP

CSEP

SIP

CSEP

SIP

CSEP

SIP

CSEP

SIP

CSEP

SIP

CSEP

E-NNI I-NNI OLS Node

NEP

CEP

NEP

CEP

NEP

CEP

NEP

CEP

NEP

CEP

NEP

CEP

EVC MIP

EVC up MEP OVC Up MEP UNI Down MEP

ENNI Down MEPOVC Up MEP

SIP

CSEP CEP

Service Interface Point

Connectivity Service End Point

NEP Node Edge Point

Connection End Point

ONF ODTN (Open Disaggregated Transport) Architecture

8

OLS Controller

WSS TRN

Open Line System (OLS)

OpenConfig OpenConfig

MUX WSSAMP MUXTRN

ONOS

With OLS Controller

TAPI

Has topology

TAPI

RDM2

RDM1

RDM4RDM3 RDM5OLS Domain

I-NNI2

I-NNI1

I-NNI3

Operator Domain Topology

9

Operator SOF view

Operator ICM View

OLS View

UNI

TPD3

TPD1TPD2 E-NNIOLS Node

ICM-OLS TAPI Context

SOF-ICM TAPI Context (LSO Presto)

Node Edge Point (Network Internal)Node Edge Point (Network Edge)Service Interface Point

Logical Termination Points shown


Connection / Connection End PointPhotonic ConnectionPhotonic Media Channel

AbbreviationsTPD – Transponder NodeRDM – ROADM NodeUNI – User-Network InterfaceNNI – Network-Network InterfaceDSR – Digital Signal RateOTSi – Optical Tributary SignalOTSiA – OTSi AssemblyMC – Media Channel

100G

100G

100G

100G

100G

100G

100G

100G

RDM2

RDM1


I-NNI2

I-NNI1

I-NNI3

Operator Domain Connectivity Service & Resources(1)

10

Operator SOF view

Operator ICM View

OLS View Photonic Connectivity Service 1

UNI

TPD3


OTSi 1-1

OTSi 1-1OTSi 1-2

OTSi 1-2

OTSiA1 200GDSR1 100G

OTSi-MC1

OTSi-MC2

OTSi-MC1

OTSi-MC2








100G

100G

100G

100G

100G

100G

100G

DSR Connectivity Service 1 (100G)

100G

RDM2

RDM1


I-NNI2

I-NNI1

I-NNI3

Operator Domain Connectivity Service & Resources (2)

11

Operator SOF view

Operator ICM View


UNI

TPD3


OTSi 1-1

OTSi 1-1OTSi 1-2

OTSi 1-2


OTSi-MC1

OTSi-MC2

OTSi-MC1

OTSi-MC2







DSR2 100G


100G

100G

100G

100G

100G

100G

100G

DSR Connectivity Service 1 (100G)DSR Connectivity Service 2 (100G)

100G

RDM2

RDM1


I-NNI2

I-NNI1

I-NNI3

Operator Domain Connectivity Service & Resources (3)

12

Operator SOF view

Operator ICM View


Photonic Connectivity Service 2

UNI

TPD3


OTSi 1-1

OTSi 1-1OTSi 1-2

OTSi 1-2

OTSi 2-1

OTSi 2-1

OTSi 2-2OTSi 2-2


DSR3 100GOTSiA2 200G

OTSi-MC1

OTSi-MC3

OTSi-MC2

OTSi-MC4

OTSi-MC1

OTSi-MC3

OTSi-MC2

OTSi-MC4







DSR2 100G


100G

100G

100G

100G

100G

100G

100G




100G

Photonic Logical Terminations, Connectivity Service, Step 1ROADMTRANSPONDER

OMS Link

OMS

MC

OTS

OMS

Add/Drop Port1..2

1

C/L bands

OTS Link

OMS Link

Degree Port

1

XMC

This MC SIP refers to MCs NEPs, each MC NEP representing the spectrum available on an OMS.

• MC spectrum/bandwidth only, Create MCA ConnectivityService with the following input parameters:

1. MC SIPs2. MC CSEPs with required spectrum (or only bandwidth, delegating spectrum allocation)The agent will create:1. proper edge-to-edge MC Connection(s), MC XCs, MC CEPs and client OTSiMC NEPs, each

MC CEP includes the MCA Id

MC

Media Channel CEP{lowerFreq, upperFreq}

Node Edge Point

Connection End Point (TTP + CTP)

Connection End Point (CTP only)

Connection End Point (Inverse mux CTP only)

Connection End Point (TTP only)

MIP

Down MEP

Up MEP

OPM

Connection




Non Intrusive MonitoringNo Specific OAM signalingOptical Power Monitoring

Link


OMS Link

OMS

MC

OTS

OMS

MCMCA

Add/Drop Port

MC

s

1..2

1

C/L bands

s`

OTS Link

OMS Link

1:1 1:1

Degree Port

MC

1

XMC

Two MC CEPs have been created, representing disjoint portions of spectrum where the OTSiA will be routed

2

OTSiMC

2

B BMC

guar

dban

d

guar

dban

d

guar

dban

d

guar

dban

d

MC

OTSiMC

MCA Connectivity Service

MCA

Spectrum

MC


Node Edge Point





MIP

Down MEP

Up MEP

OPM

Connection





Link


OMS Link

OMS

MC

OTS

OMS

MCMCA

Add/Drop Port

MC

s

1..2

1

C/L bands

s`

OTS Link

OMS Link

1:1 1:1

Degree Port

MC

1

XMC

2

OTSiMC

2

B BMC

guar

dban

d

guar

dban

d

guar

dban

d

guar

dban

d

MC

OTSiMC

MC Connectivity Service

MCA

Spectrum

• Create OTSiMCA ConnectivityService with the following input parameters:1. MC SIPs2. OTSiMC CSEPs with required bandwidth (and spectrum) in the existing MCAThe agent will create:1. proper edge-to-edge OTSiMC Connection(s), OTSiMC XCs, OTSiMC CEPs, each one

including the OTSiMCA Id

MC


Node Edge Point





MIP

Down MEP

Up MEP

OPM

Connection





Link


OMS Link

OMS

MC

OTS

OMS

MC

OTSiMC OTSiMC

OTSiMCA

OTSiMCA

MCA

Add/Drop Port

MC

s

1..2

1

C/L bands

2

s`

33

OTSiMC

OTS Link

OMS Link

1:1 1:1

Degree Port

MC

1

OTSiG-OOTSiMCG-O

XMC

OTSiMC

ATwo OTSi will be routed in first MC, the third OTSi in the second MC.

2

1 21

2

BBMC

MCA

OTSiMCA Connectivity Service

OTS

i -1

guar

dban

d

OTS

i -2

guar

dban

d

OTS

i -3

guar

dban

d

guar

dban

d

OTSiA: {OTSi-1, OTSi-2, OTSi-3}MCA Connectivity Service

Bw amount

Spectrum

AA

OTSiMCOTSiMCOTSiMC

MC


Node Edge Point





MIP

Down MEP

Up MEP

OPM

Connection





Link

A

Photonic Logical Terminations, Connectivity Service Incl. TransponderROADMTRANSPONDER

OMS Link

OMS

MC

OTS

OMS

MC

OTSiMC OTSiMC

OTSiMCA

OTSiMCA

MCA

Add/Drop Port

MC

s

1..2

1

C/L bands

2

s`

3

3OTSiMC

OTS Link

OMS Link

1:1 1:1

Degree Port

MC

1

OTSiG-OOTSiMCG-O

XMC

OTSiMC

ATwo OTSi will be routed in first MC, the third OTSi in the second MC.

2

1 21

2

B BMC

MCA

OTSiMCA Connectivity Service

OTS

i -1

guar

dban

d

OTS

i -2

guar

dban

d

OTS

i -3

guar

dban

d

guar

dban

d

OTSiA: {OTSi-1, OTSi-2, OTSi-3}

MCA Connectivity Service

A

A OTSiMCOTSiMCOTSiMC

MC

OTSi

OMS

Line Port

1

1..c

1

3

OTU (OTUCn)

c ~FlexO

ODU (ODUCn)

3

OTSiG-O

OMS-O

OTSiA

OTSiA Connectivity ServiceOTSi

OTSiOTSi

2

1OMS Link

YOMS

OTSi

C

Y

C

SpectrumBand:• upperFrequency• lowerFrequency• frequencyConstraint:

o adjustmentGranularityo gridType

Photonic Logical Terminations OLS Attributes

ROADMTRANSPONDER

OMS Link

OMS

MC

OTS

OMS

Add/Drop Port1..2

1

C/L bands

OTS Link

OMS Link

Degree Port

1

XMC

MC

supportableSpectrum (0..n)availableSpectrum (0..n)occupiedSpectrum (0..n)supportableMaximum/MinimumOutputPowertolerableMaximum/MinimumInputPower

supportableSpectrum (0..n)availableSpectrum (0..n)occupiedSpectrum (0..n)

occupiedSpectrummeasuredPowerIngressmeasuredPowerEgress


Node Edge Point





MIP

Down MEP

Up MEP

OPM

Connection





Link

capacitycentralFrequencyspectrumapplicationIdentifierModulationlaserControltransmitPowertotalPowerWarnThresholdUpper/Lower

CentralFrequencyBand:• lowerCentralFrequency• upperCentralFrequency• frequencyConstraint:

o adjustmentGranularityo gridType

supportableCentralFrequencyBand (0..n)supportableApplicationIdentifier (0..n)supportableModulation (0..n)totalPowerUpperWarnThresholdDefault/Min/MaxtotalPowerLowerWarnThresholdDefault/Min/Max

A

Photonic Logical Terminations Transponder Attributes

TRANSPONDER

OTSi

OMS

Line Port

1

1..c

1

3

OTU (OTUCn)

c ~FlexO

ODU (ODUCn)

1

3

OTSiG-O

OMS-O

OTSiA

OTSiOTSiOTSi

2

1OMS Link

YOMS

OTSi

C

Y

C

OTSiA Connectivity Service

numberOfOtsifecParameters

selectedCentralFrequencyselectedApplicationIdentifierselectedModulationselectedSpectrumtransmittedPowerreceivedPowerlaserProperties

Thank You

Follow Up Links:https://wiki.opennetworking.org/display/OTCC/TAPI

Documents

Advancements in ONF Transport API for Orchestration of Multi … · 2019. 9. 2. · Orchestration of Multi-layer Connectivity Service Andrea Mazzini, Nokia Karthik Sethuraman, NEC