2. T-API: A Confluence of Standards and Open Source
TAPI
Use cases & Requirements
TAPI UML
Information Model
TAPI YANG
Data Schema
OpenAPI (RESTConf)
Schema
ONF Core Information Model
ONF Technology Specific
Models
UML-YANG
Generation Tool
YANG-OpenAPI
Generation ToolONF TAPI
SDK
EAGLE Modeling Tools
Open Model
Profile
Code
OTN
(ITU-T
G.874.1)
ETH
(ITU-T
G.8052)
Photonic
(ITU-T
G.807.1*)
Python Reference
Implementation
Python Stub
Generation Tool
MEF
Multi-carrier
T-SDN Interop
Implementation
Agreements &
Certification
OIF
Interop Implementations
MEF 59
NRM
MEF 60
NRP
ONF OIMT
Multiple Groups
ITU-T SG15
Technology Generic Core Model
(ITU-T G.7711)
IISOMI
OAM
Etc.
TIP
Open
OLS
Model
3. ONF T-API Standardization
• ONF Open Transport Config & Control Project (OTCC):
• Goal: promote common configuration and control interfaces for transport networks in SDN, defining these interfaces with open
source software and software-defined standards.
• Steering Team: AT&T, Ciena, China Mobile, CTCC, Fiberhome, Huawei, Infinera, NEC, Nokia, SIAE, Telefonica
• Focus on API development and implementation, application of core information model to specific transport technologies (packet,
optical and wireless) – working closely with OIF on requirements and interoperability testing for optical networks
• Subprojects:
• Transport API Sub-Project (Karthik Sethuraman, NEC)
• Open Transport Information Modeling (Kam Lam, FiberHome)
• Wireless Transport (Giorgio Cazzaniga, SIAE)
• Device Management Interface Profile (Thorsten Heinze, Telefonica)
• ONF Open Information Modeling & Tooling Project (OIMT):
• Goal: evolve industry-wide Open Information Models and associated open source tooling software that guides/supports the
development of Software Defined Networks
• Steering Team: Ciena, DT, Fiberhome, NEC, ZTE
• Focus on development of Detailed but compact canonical networking models in UML
• Focus on development of tooling for automated translation of UML to YANG, OpenAPI and TOSCA
4. ONF Transport API (TAPI): Functional Architecture
Topology
Service
Connectivity
Service
Path Computation
Service
Shared Network Information Context
OAM Service
Virtual Network
Service
NENetwork Elements
NENESDN Controller
NENESDN Controller
NENEApplication
SBIs
Transport API
Notification
Service
Transport API
5. TAPI Evolution
• Topology Service
– Logical (abstract/virtual) Topology, Node,
Link & Edge-Point (Across al layers)
• Connectivity Service
– Retrieve & Request P2P, P2MP, MP2MP
connectivity (Across all layers)
• Path Computation Service
– Request for Computation & Optimization of
paths
• Virtual Network Service
– Create, Update, Delete Virtual Network
topologies
• Notification Framework
– Subscription and filtering
– Autonomous/Push mechanism
• Node Constraints
– Ability to specify connectivity/blocking
constraints
• Resilience & Protection
– Multi-layer, Multi-Domain
– Based on use cases under discussion
• OAM/Monitoring/PM
– Consistent Multi-layer abstraction and
model – L0-L2
• Alarm/TCA/Counter
• ETH/OTN Spec Models
• Photonic Media Spec Model
– Support of Optical Transport Disagg
– Separation of Media Channel and
Transponder Control
TAPI SDK 1.x (2016) TAPI SDK 2.1 (2018)
6. OIF Transport API Interop Demos (2014, 2016, 2018)
Domain
Controller
Domain
Controller
Domain
Controller
Multi-Domain Controller
Technology/
VendorSpecific
models
TAPI Agent
OSS/App/Orchestrator
CommonAbstraction
model
Transport API
Test Vendors
Test
Carriers
Transport API
TAPI Agent
Multi-Domain Controller
TAPI AgentTAPI Agent
TAPI Agent
7. MEF Lifecycle Service Orchestration Presto IF
Tested at Multiple MEF Hackathon
Events
8. ONF ODTN (Open Disaggregated Transport) Project
Open Disaggregated System
OLS Controller
WSS TRN
Open Line System (OLS)
OpenConfig OpenConfig
MUX WSSAMP MUXTRN
ONOS
Partial Disaggregation With OLS Controller (Current ODTN Ph 1.5)
TAPI with Photonic Media Model
ROADM
topology
TAPI
Demonstrated in OFC 2019 Demo Zone
Abstracted
topology
Detailed
topology
9. TAPI Future Directions
• Provides functions necessary for multi-
domain orchestration
– Abstraction and Virtualization
– Multilayer Topology
– Interoperability of the North/South SDN
Controller interface
• Supports multiple transport technologies
– Packet Transport (Ethernet, MPLS-TP)
– Optical Transport (OTN)
– Wireless Transport
– Photonic Media Channel
• TAPI 2.2 Items (projected)
– Equipment Inventory & Configuration
– Equipment, Holders (Rack/Shelf, etc),
Connectors, Span, etc
– LLDP Model
– Cross-layer discovery
– Other Enhancements
– Topology Pacs/Datatypes (Capacity, Cost,
Latency, Risk parameters) enhancements
– Further tune the component-system
pattern for Topology & Connectivity
General Benefits TAPI Next Steps