1. Introduction to Models, Interfaces, Guidelines & Tooling from ONF Open Information Model & Tooling (OIMT) project and ONF Open Transport Configuration & Control (OTCC) project
Andrea MAZZINI (Nokia) Kam LAM (FiberHome / CICT) Karthik SETHURAMAN (NEC) Nigel DAVIS (Ciena)
Beijing

2. Agenda Brief context setting P1: ONF interface model – TAPI
P2: ONF core model – TR-512
P3: ONF interface model – TAPI
P4: Guidelines & Tooling – TR-514, -514, -531, -543, -544

3. Aspects of the OIMT and OTCC projects
Approach
Model of semantics independent of implementation
Evolvable, extendable interface implementation
Focus on code and round trip
Focus on agile processes and close working
Closing the loop models and realization
Focus on tooling and automation of development
Elements of the projects
The Core Model
Canonical models of key areas of the problem space
Tooling to assist model transformation and remove mechanical steps
Interface definition
Reference Implementations
Stimulation of, and support for, PoCs

4. ONF Models, Interfaces, and Guidelines & Tooling
See slide notes
The core model is published as ONF TR-512
The model is built on many years of standards and implementation experience
TR-512 includes a suite of documents and the XMI-encoded UML information model developed using the open source Papyrus tooling in the Eclipse environment
The model structure and tooling usage follow the IISOMI guidelines
The core model is an interconnected set of domain canonical models (see details in later pack). It is intentionally devoid of:
Implementation specific details (related to interface encoding)
Forwarding technology details (related to the network technology such as OTN)
To construct an interface model (in UML), the core model is Pruned & Refactored to match the needs of the purpose of the view provided by the targeted interface
Pruning and refactoring is a significant intellectual exercise
IISOMI Tooling is being developed to support the process (currently prototype)
Examples are TAPI (Transport API) and Microwave Interface (sometimes known as WDAPI – Wireless Device API),
To add forwarding technology details, the technology models from ITU-T etc. are Pruned & Refactored to form API augmenting specifications
The same IISOMI tooling applies to this process
The Interface model is coded using IISOMI tooling that follows appropriate IISOMI mapping guidelines
Current tooling produces TANG and JSON from the UML models
Developing tooling for Protobuf and considering TOSCA
Core model: TR-512 v1.4 (11/2018)
v1.4 can be found in (in “Current Versions” list, click “+ PROJECT: INFORMATION MODELING”, download the zip file of “Core Information Model (CoreModel) v1.4”)
TAPI: SDK v2.2
Microwave model: TR-532 (12/2016)
Can be found in (in “Current Versions” list, click “+ PROJECT: OPEN TRANSPORT”, download the zip file of “Microwave Information Model”)
UML Modeling Guidelines: TR-514 v1.3 (07/2018)
UML Profiles and Style Sheets:
OpenModelProfile, v0.2.17
OpenInterfaceModelProfile, v0.0.10
ProfileLifecycleProfile, v0.0.4
Style sheet for class diagrams
Papyrus
Papyrus Guidelines: TR-515 v1.3 (07/2018)
UML to YANG Mapping Guidelines: TR-531 v1.1
UML to YANG Mapping Tool:
Github repository:

5. ONF API Modeling
ONF Open Information Modeling and Tooling (OIMT) Project
Core Information Model - TR-512 v1.4
Technology agnostic core modeling framework – patterns and methods (IISOMI)
TR-513, TR-514, TR-515, TR-531, TR-543, TR-544
OTCC sub-Project – Transport API (TAPI)
CIM pruned and refactored for Transport SDN NBI/SBI – TR-527 & SDK
OTCC sub-Project – Open Transport Information Modeling
Models for wireline transport technologies
Ethernet, MPLS-TP, OTN, Photonic Media, Synchronization Models
OTCC sub-Project – Wireless Transport model
CIM-aligned models for wireless transport – TR-532
PoCs testing interoperability of TR-532 implementations
OTCC sub-Project – Device Management Interface Profile
Profile/Requirements for Netconf – TR-545
Interoperability Requirements based on PoC Testing

6. Questions?
Thank you 