Overview
- Extend CCVPN use case for Optical ( L0) and L1
- This project aims to provide end to end multi-layer(L0/L1) and multi-vendor service orchestration across multiple optical transport domains
- This project also aims to enable service orchestration over multiple 5G transport network management systems across FH and MH/BH domains
Dublin Goals
- Enable T-API based service provisioning for SDN-C for L0/L1
- service orchestration over optical domain
- PNF collectors for DCAE
Business Requirements
Adding supportfor optical layer to CCVPN gives operators the flexibility to dynamically configure and create end to end service. Operators will be allowed to configure optical layer for different slicing requirements (in case of 5G ).
Operators will have additional capabilities for monitoring Quality of services for Optical layer
T-API is a common standardized API that allows access to domain/vendor specific attributes without the need of vendor specific API. Enabling T-API based provisioning for SDN-C will allow operators to deploy ONAP across multi-domain, multi-vendor infrastructure enabling end to end Programmability for their networks for speed of deployment, efficiency and revenue generating services.
Service provider priority for Dublin
Components | SP priority Dublin |
DCAE | External API enhancements |
SDN-C | Service modelling extensions for T-API |
AAI | External API enhancements |
SDC | Service design template extensions for Service design |
MSO | orchestration over multiple optical domains |
Participating companies
Scope
- Provide Optical restoration capabilities leveraging ONAP SDN-C
- APIs/interfaces
- Transport-API (T-API 2.X) – NBI enhancements for L0
- MEF 60 APIs – NBI enhancement for L1 services
- OpenROADM / IETF models – L0/L1 Device models
- xRAN – 5G Fronthaul devices
- Testing and integration plans
- E2E Openroadm and ONAP testing and integration
- Features and functionality
- Can be extended across multiple service provider networks
Use case presentation
Use case meetings
Impacts
SDN-C
- T-API 2.0 Interface support (REST API)
- MEF 60 support for L1 service provisioning
- Potential Virtuora Plugin contribution
A&AI
- T-API support to for topology across network domains
- Registration mechanisms for Transport NEs
SDC
- Sample Service template for E2E service creation & monitoring across optical transport domains (RAN & Core)
- Incorporating network requirements for topology, path computation, restoration etc.
- Policy Policy definition for closed-loop automation & event handling
DCAE
- Enhance current PNF collector [VES compliant enhancements to for PM/Alarms streaming from Optical network elements]
- Analytics Application / Micro-service
MSO
- Workflow definition to orchestrate services across multiple optical transport domains
Project Commitments
- T-API Interface support from SDN controller to A&AI
- Defining Service template
- Optical requirements (SRG/Degree)
- Network slicing requirements
- SBI interface to SDN controller
- Usage of simulators & HW modelling
- OpenROADM / OpenConfig
- IETF models
- External controller Plugin / API into SDN-C
- External controller support for T-API
- PNF collector (VES formatted) into DCAE for Alarms/PMs management
- Policy definition for closed-loop automation and event handling
- Portal / UI & external interface display for control & monitoring
Resources
Contact person: Ravi Rao Ravi.Rao@us.fujitsu.com Initial Committers ?Ravi Rao Ravi.Rao@us.fujitsu.com ?Toshimichi Fukuda t_fukuda@jp.fujitsu.com ?Triloshini Thoppekrishnakumar Thiriloshini.ThoppeKrishnakumar@us.fujitsu.com ?Ayumu Ueha ueha.ayumu@jp.fujitsu.com ?Takuya (Mitch) Miyashita Takuya.miyashita@us.fujitsu.com ?Raghavan Subramanian Raghavan.Subramanian@us.fujitsu.com ?Karthik Jeevanige Karthik.Jeevanige@us.fujitsu.com