WIXLIB

ONF Transport APIOpening up Disaggregated Optical TransportApplications *Karthik Sethuraman, NECAndrea Mazzini, NokiaStephane St Laurent, InfineraLyndon Ong, CienaDec 3, 2018*animated slides

ONF TAPIIntroduction & Overview2

Transport API – Simple Problem StatementNetworkOrchestratorAPPOpenStandard T-APIONOS APIsONOSODL APIsODLProprietary APIsProprietary

ONF Transport API (TAPI): Functional ArchitectureApplicationNENESDN NEControllerNETransport API or Other NBIsTopologyServiceConnectivityServiceOAM ServicePath ComputationServiceVirtual NetworkServiceShared Network Information ContextTransport API or Other SBIsNetworkNEElementsSDN NEControllerNENotificationService

TAPI RI - Prototyping Controller-agnostic APITAPI Client (Python)Transport APITopologyServiceConnectivityServiceONOS NBI MapperOAM ServicePath ComputationServiceODL NBI MapperVirtual NetworkServiceNotificationServiceTAPI Server BackendTAPI Server (Python)Network Domain (ODTN)Available /Shortly AvailableNetwork Domain (UniMgr)TAPI Reference NetworkDB (JSON)

OIF Transport API Interop Demo (2014, 2016, 2018)Test CarriersOSS/App/OrchestratorTAPI AgentMulti-Domain ControllerTransport APITAPI AgentCommonAbstractionmodelMulti-Domain ControllerTransport APITechnology,VendorSpecificmodelsTAPI AgentDomainControllerTAPI AgentDomainControllerTAPI AgentDomainControllerTest Vendors

MEF 3.0 Optical Transport Implementation Project

ONF ODTN (Open Disaggregated Transport) ArchitecturesWith OLS Controller (Current Ph 1.5)TAPIONOSTAPIHas topologyOLS NOpen Line System (OLS)Without OLS Controller (Future Ph 2.0)TAPIONOSTBDOpenConfigTRNMUXWSSAMPOpen Disaggregated SystemOpenConfigWSSMUXTRN

Confluence of Standards and Open SourceONF OTCCTAPI FRSUse cases & RequirementsTAPI UMLInformation ModelONF OIMTONF Core Information ModelTAPI YANGData SchemaONF TechnologySpecification ModelsONF TAPI SDKOpen ModelProfileUML-YANGGeneration ToolYANG-OpenAPIGeneration ToolOpenAPI (RESTConf)SchemaETH(ITU-T G.8052)OTN(ITU-T G.874.1)Photonic(ITU-T G.807.1*)Technology Generic Core Model(ITU-T G.7711)Python StubGeneration ToolCodePython ReferenceImplementationEAGLE Modeling ToolsITU-T SG15OIFMEFNRMMEF ModelsNRPOpticalTransportPacketWANMEF 3.0 ImplementationsMulti-carrierT-SDN InteropImplementationAgreements &CertificationInterop Implementations

TAPI Feature SetTAPI SDK 2.x (H2 2018)TAPI SDK 1.x (H2 2016) Topology Service– Connectivity Service– Create, Update, Delete Virtual NetworktopologiesNotification Framework––Subscription and filteringAutonomous/Push mechanismNode Constraints– Multi-layer, Multi-DomainBased on use cases under discussionOAM/Monitoring/PM– Ability to specify connectivity/blockingconstraintsResilience & Protection––Request for Computation & Optimizationof pathsVirtual Network Service– Retrieve & Request P2P, P2MP, MP2MPconnectivity (Across all layers)Path Computation Service– Logical (abstract/virtual) Topology,Node, Link & Edge-Point (Across allayers)Consistent Multi-layer abstraction andmodel – tonic Media spec modelsETH & OTN enhancementsMicroware TBD

Transport API SummaryTAPI Next StepsGeneral Benefits Provides functions necessary for multidomain orchestration–––– ––Topology view and abstractionConnectivity establishmentHierarchical AbstractionMigration path for legacy systems–Abstract Node (single, edge, sliced, etc)Abstract LinkComplete (1-to-1) internal topology Packet Transport (Ethernet, MPLS-TP)Optical Transport (OTN, DWDM)Interoperability on North-SouthOrchestrator/Controller interfacePhotonic Model updates based on ODTN feedbackETH, L1 & OAM alignment due to interaction withMEF (NRM-OAM/SOAM, L1) projectsYANG & OpenAPI/RESTConf Best Practices– Based on MEF-PRESTO (ODL), ODTN (ONOS)and OIF (TAPI Interop) activity feedbackTAPI 3.0 Items (Current)–Supports multiple transport technologies–– TAPI 2.x fixes & enhancementsDifferent types of topology abstraction––– ––Equipment Inventory & configuration– Equipment, Holders (Rack/Shelf, etc),Connectors, Fiber, etcTopology Pacs/Datatypes (Capacity, Cost, Latency,Risk parameters) enhancementsRationalize/tune the component-system patternfor Topology & Connectivity

ONF TAPILogical Topology & Forwarding Concepts with Photonic Example12

Simple Physical Network Example to illustrate 4(200G)RDM2OLS DomainTPD DomainAbbreviationsTPD – Transponder NodeRDM – ROADM NodeUNI – User-Network InterfaceNNI – Network-Network InterfaceNMC – Network Media ChannelNMCA – NMC AssemblyOTSi – Optical Tributary SignalOTSiA – OTSi Assembly A Network Provider with 2 operator domains : Transponder domain OLS/ROADM domainAnd with two Customers (Red and Green) connected to TranspondersNo Switching on TPD Nodes - DSRs are mapped into ODU into OTSiOnly Photonic switching assumed on ROADMSLogical Termination Points shownService Interface PointNode Edge Point (Network Edge)Node Edge Point (Network Internal)Connectivity Service End Point

Example T-API Contexts(based on ONF Architecture v1.1)TPD ControllerAdmin APPBlueClient Controller GREENResource GroupResource GroupClientTAPITAPITAPIResource GroupResource GroupResource GroupCustomer ContextREDCustomer ContextGREENAdmin ContextBLUE.AdminTAPI Provider SDN ControllerOrchestration / VirtualizationTAPI Provider Internal Context Resource GroupsDevice ContextTPD1Device ContextTPD2Device ContextTPD3Controller ContextOLSTPD-1TPD2TPD3OLSOther Admin InterfacesClient ApplicationREDServerClientServer

Example 1: Hierarchical TAPI Control Domains & Abstracted OLS TopologyCustomer(s) viewUNI 1Network Provider ViewTAPIContext-GUNI 3UNI2TAPIContext-RUNI 4Transponder Domain ControllerAbstraction & OrchestrationUNI1NNI1UNI3NNI3TPD1OLS NodeTPD3TPD2UNI2NNI2TPD DomainNNI 1OLS Operator ViewTPD3OLS DomainNNI 2OLS TAPIContextNNI 3Logical Termination Points shownOLS Domain ControllerAbbreviationsTPD – Transponder NodeRDM – ROADM NodeUNI – User-Network InterfaceNNI – Network-Network InterfaceNMC – Network Media ChannelNMCA – NMC AssemblyOTSi – Optical Tributary SignalOTSiA – OTSi AssemblyService Interface PointNode Edge Point (Network Edge)Node Edge Point (Network Internal)Connectivity Service End PointAbstraction & OrchestrationNNI1RDM1NNI3NNI2RDM2RDM3OLS DomainUNI4RDM4RDM5

Example 1: E2E Connectivity Request Flow (Omnipotent view)DSR Connectivity Service 1Photonic Connectivity Service 1UNI1OTSi 1-1DSR1 100GOTSiA1NNI1UNI3NNI3OTSi 1-2TPD1TPD2OTSi 1-2RDM1RDM2OTSi 2-1NMCA2OTSi 2-1UNI2OTSi 1-1NMCA1OTSi 2-2NNI2OTSi 2-2RDM4RDM3TPD3RDM5TPD3UNI4OTSiA2DSR2 100GOLS DomainTPD DomainPhotonic Connectivity Service 2DSR Connectivity Service 2AbbreviationsTPD – Transponder NodeRDM – ROADM NodeUNI – User-Network InterfaceNNI – Network-Network InterfaceNMC – Network Media ChannelNMCA – NMC AssemblyOTSi – Optical Tributary SignalOTSiA – OTSi AssemblyLogical Termination Points shownService Interface PointNode Edge Point (Network Edge)Node Edge Point (Network Internal)Connectivity Service End Point

Example 1: E2E Connectivity Request Flow (actual TAPI Contexts view)Customer(s) viewNetwork Provider ViewDSR Connectivity Service 1UNI 1UNI1UNI2UNI 3TAPI Context-GDSR Connectivity Service 2TAPI Context-RUNI 4DSR ConnectivityService1TransponderDomainControllerDSR Connectivity Service 2NNI1UNI3NNI3TPD1OLS NodeTPD3TPD2UNI2NNI2TPD DomainPhotonic Connectivity Service 1OLS TAPI ContextPhotonic Connectivity Service 2NNI 1OLS Operator ViewAbbreviationsTPD – Transponder NodeRDM – ROADM NodeUNI – User-Network InterfaceNNI – Network-Network InterfaceNMC – Network Media ChannelNMCA – NMC AssemblyOTSi – Optical Tributary SignalOTSiA – OTSi AssemblyTPD3OLS DomainNNI 2NNI 3Photonic Connectivity Service 1Photonic Connectivity Service 2Logical Termination Points shownService Interface PointNode Edge Point (Network Edge)Node Edge Point (Network Internal)Connectivity Service End PointNNI1RDM1NNI2RDM2RDM3OLS DomainRDM4UNI4RDM5

Example 1: Connectivity Request Flow /w provisioned ConnectivityCustomer(s) viewNetwork Provider ViewResourcesDSR Connectivity Service 1UNI 1UNI2UNI 3TAPI Context-GDSR Connectivity Service 2TAPI Context-RUNI 4DSR Connectivity Service 1DSR 1 100GOTSiA1UNI1OTSi 1-1NNI3OTSi 1-2NMCA1NNI1TPD1TPD2OTSi 2-1NMCA2OTSi 2-1OTSi 2-2TPD3OTSiA2DSR2 100GPhotonic Connectivity Service 1OLS TAPI ContextPhotonic Connectivity Service 2NNI 1NNI 2Logical Termination Points shownService Interface PointNode Edge Point (Network Edge)Node Edge Point (Network Internal)Connectivity Service End PointNNI1NMCA1RDM1NMCA2RDM2RDM3OLS DomainRDM4UNI4NNI 3Photonic Connectivity Service 1Photonic Connectivity Service 2NNI2TPD3OTSi 2-2OLS DomainUNI2AbbreviationsTPD – Transponder NodeRDM – ROADM NodeUNI – User-Network InterfaceNNI – Network-Network InterfaceNMC – Network Media ChannelNMCA – NMC AssemblyOTSi – Optical Tributary SignalOTSiA – OTSi AssemblyOTSi 1-2OLS NodeNNI2OLS Operator ViewUNI3OTSi 1-1RDM5

Example 2: Alternate TAPI Control Domains – Orchestration architectureCustomer(s) viewUNI 1NetworkProvider ViewTAPITAPIUNI 3UNI2Context-GContext-RService OrchestratorUNI 4Abstraction & DM3NNI2NNI 1UNI 1Operators ViewUNI 2NNI 2TPD3NNI 3NNI 1UNI 3TPD TAPI ContextTPD Domain ControllerRDM4NNI 2TPD3RDM5UNI4NNI 3OLS TAPI ContextUNI 4OLS Domain ControllerAbstraction & OrchestrationTPD DomainAbstraction & NI2UNI2RDM2RDM3OLS DomainRDM4RDM5TPD3NNI3TPD3UNI4

Example 2: Alternate TAPI Control Domains – E2E Connectivity RequestCustomer(s) viewFlowDSR Connectivity Service 1UNI 1UNI 4TAPI Context-RUNI3NNI3TPD1TPD2RDM1RDM2UNI2Operators ViewDSR Connectivity Service 2NNI1UNI1UNI 2UNI2TAPI Context-GNetworkProvider ViewUNI 1UNI 3RDM3NNI2DSR CS 1-1DSR CS 2-1TPD3RDM4TPD3RDM5NNI 1NNI 3TAPI Context-GNNI 2Photonic Connectivity Service 1OLS TAPI ContextPhotonic Connectivity Service 2NNI 1NNI 2NNI 3DSR CS 1-2DSR CS 2-2UNI4UNI 3UNI 4TPD RDM2RDM3OLS DomainRDM4RDM5TPD3NNI3TPD3UNI4

Recursive Node & Topology aspects of TAPI Forwarding DomainTAPI Context à Network Domain ViewNode aspect of the FDTopology aspect of the FDObserverLinkAFD (Node)01.1AFD (Topology)0101MappingLTP (Service Interface Point)LTP (Node Edge Point)A.1131112AA.31401.n16Node-A appears aTopology of Nodes A.1 A.5 & Links betweenthemBA1701.1A.2Context appears as aTopology of one Node B andSIPs (off-networkrelationships/Links)1519A.4Node-B appears aTopology ofNodes A & C and LinkA-C0502.118B 20A.50403C0202.nNode-C appears as aTopology with NULLelements

Recursive Connectivity decomposition of TAPI Forwarding ConstructTAPI Context à Network Domain ViewNode aspect of the FDTopology aspect of the FDObserverLinkAFD (Node)01.1AFD (Topology)0101MappingLTP (Service Interface Point)LTP (Node Edge Point)A.1131112AA.31401.nNode-A appears a Topology ofNodes A.1 - A.5 & Connection(01-04) further decomposesinto 3 lowest-levelconnections (01-12), (17-18) &(20, 04)BA1701.116A.2Context appears as aTopology of one Node B anda Connection (01-02)1519A.4Node-B appears a Topology ofNodes A & C and Link A-C.Connection (01-02) decomposesinto 2 lower-level Connections(01-04) & (03-02)0502.118B 20A.50403C0202.n

TAPI 2.1 Photonic LTP Model (still under review for 2.2)TRANSPONDERODU(ODUCn)OTU(OTUCn)ROADMService Interface PointNode Edge Point1Node Edge Point GroupConnection End Point(TTP only)c FlexO1.cConnection End PointOTSiAOTSi(CTP only)1.rConnection End PointrOTSis*n1:1(TTP CTP)OTSiA1:1Connection End PointNMCANMC(Inverse mux CTP only)1:1OTSirNMCANMedia Channel CEPNMCANMCNMCn{lowerFreq, upperFreq}r n NMCN Media Channel AssemblyNMCA[{lowerFreq, upperFreq},{lowerFreq, upperFreq}, .]q qSMCASMC1:11:1SMCANot explicitlymodeledrepresentedSMCSMCOMS1:1SMCSss SMCS Up MEPSMCAMIPOPMp 11OMS LinkLine Port1:11:1pOMS1SMCASMCDown MEPAdd/Drop PortOMSOMS LinkC/L bands1.2OTSOTS LinkDegree PortNon Intrusive MonitoringNo Specific OAM signalingOptical Power Monitoring

ReferencesThank you J24