...
This page is intended to capture the ongoing study and discussion in the Ext-API project related to the inter-CSP BSS/OSS interaction enabled through the MEF interlude Legato specification. This is related to the JIRA item planned in the Casablanca cycle. While it is essential to carry out a detailed study on the inter-provider interactions and overall impact on ONAP as a solution, the scope of this page will be limited to the impact on External API. Additionally, while the focus is on the MEF interlude Legato specification, there is some good amount of work being done in many SDOs to address the scope of inter-provider BSS/OSS management interactions - notably TMForum, ETSI, NGMN, ONF, IETF etc. It is worth noting the scope and outcome of these SDOs and analyze some best practices that ONAP can incorporate. It is also worthwhile to note how other opensource communities like OSM, 5GPPP/5GEx etc tackled this issue. Further, the page also captures the short term and long term requirements to support Interlude like inter-provider Legato interaction.
| Expand | ||
|---|---|---|
| ||
| Expand | ||
|---|---|---|
| ||
| Expand | ||||||
|---|---|---|---|---|---|---|
| ||||||
Characteristic | ETSI | MEF | TMF | NGMN | ONF | IETF |
Use Case | NFVIaaS | Access E-Line + MEF-62 (May 2018) | NaaS | 5G Slicing | Inter Cluster ONOS Network Application (Collaboration withONOS) | Mainly transport network traffic engineering based on the multi-domain path computation |
Focus Area | Federation across MANO (virtualization domain) and ZSM Management Domains | Service Orchestration Function Federation – Focus on Service Layer | ODA : Autonomic Management interoperability across AD or Operational Domain interoperability – Focus on Service Layer | Slicing Management function interoperability, resource, and service Layer interoperability | •Cross Stratum Orchestration – end-to-end orchestration, abstraction and resource optimization across different SDN Controllers serving specific domains. | ACTN (Abstraction and Control of Traffic Engineered Networks ): Coordination of network resources across multiple independent networks, multiple technology layers, SDN & Non-SDN, Network abstraction, Network Slicing | Scope | Interaction between MANO instances in different administrative domains , interaction across management domain in ZSMInteraction between SOF function between operator and partner domains in LSO architecture | Interaction between Operational Domains through TMF Open API, Interaction between autonomic management functions | Interoperability between Slice management functions , service and resource layers | Orchestration of connectivity service that includes resources from several different domains, Coordinate service activation , monitor ongoing service | Multi-domain coordination, Network abstraction, Customer request mapping, virtual service coordination | Standard Interfaces/Reference points | Define a new Or-Or interface for inter orchestrator federation | MEF Interlude Reference point | Open API for inter-domain interaction – specifically TMF 641, 640, 645, 656, 653, 677, 633 | None | MPI – Interface between Multi-domain network controller and provisioning network controller – use NetConf Yang |
Relevance in ONAP | Interaction between NFVOs across Administrative domains assumingCatalogueis synchronized – ETSI Os-Ma or Or-Or interface | Interaction between SOF (ONAP Ext-API + SO) in two administrative domains through TMF APIs | Mostly Open API for interaction across Administrative Domains | General vision on Slicing across multiple domains | View on interaction between Orchestration and Controller functions across administrative domains. Use of Yang Models and TAPI | View on the interaction between Controllers in multiple administrative domains. May not be relevant for Ext-API but may be useful for ONAP in general |
Characteristic | OSM | ONAP | 5GEx | |||
Use Case | No specific use case | CCVPN | Many (NFVIaaS, VNFaaS, SlicingaaS etc) | |||
Focus Area | Interoperability between functional blocks across different domains | Federation across two operators ONAP instances for Service instantiation enabled through Ext-API | Federation in a multi-domain multi-layer orchestration scenario | |||
Scope | Interoperability between federated Functional blocks at different layers – i.e SO and RO, SO and SO etc. | Interoperability between Orchestration function and Ext-API across operator domains | Covers federation across multiple layers including business, orchestration and resource layers | |||
Standard Interfaces/Reference points | No standard interfaces, but SO expose SOL005 interfaces as of Release 3 | TMF 641 exposed by Ext-API | At NFVO layer 5GEx suggests the ETSI MANO specific interfaces, At RO layer, suggests NetConf/Yang | |||
| Expand | ||||||
| ||||||
| Expand | ||
|---|---|---|
| ||
| Expand | ||
|---|---|---|
| ||
Requirements Dependency on other projects |
| Expand | ||
|---|---|---|
| ||
| Section |
|---|
Links to other SDO and Opensource Work |