...
- This project will describe and define the APIs between ONAP and External Systems, including ONAP northbound interfaces ONAP interfaces targeted on BSS/OSS, peering, B2B, etc.
- Proposed initial focus may be on the Common Northbound APIs Common APIs between ONAP and BSS/OSS.
Common Northbound APIs between ONAP and BSS/OSS allow Service Providers to utilize the capabilities of ONAP using their existing BSS/OSS environment with minimal customization.
...
- Deliver points of interoperability between ONAP and External Systems
- Initial focus on ONAP Northbound APIs to BSS/OSS
- May support the following capabilities:
- Service feasibility;
- Service provisioning configuration & activation;
- Usage events & metrics;
- License accounting;
- Service performance & quality;
- Service Trouble management;
- Service policy;
- Capacity engineering;
- Address allocation management
initial focus is likely to be: “Service provisioning configuration & activation”, "Licence management", and “Address allocation management”
Definition of Use Cases, Interactions, and Information Model engaging service providers and BSS/OSS vendors
- API development
- Well defined specifications for the NB APIs (e.g., JSON Swagger).
- ONAP implementation of these APIs
- Model Driven approach: a cohesive way to have a shared view of information across ONAP external interfaces that can be used for or be input into a model driven process whereby the cost of delivering platform functionality is drastically reduced and the time to delivery is dramatically decreased.
- Explore use of Model Driven Tool Chain to automatically generate APIs based on models
...
- How does this project fit into the rest of the ONAP Architecture?
- What other ONAP projects does this project depend on?
- This project will also analyze the functionality of the implemented set of APIs in ONAP components that are relevant to providing the described Northbound external interface functionality. Mapping and alignment between this project and the ONAP components implementing the supporting APIs is essential since functional API gaps and potential enhancements will be identified based on the functional analysis. This project also allows the pertinent ONAP component specific Northbound external API artifacts (e.g., JSON/Swagger) to be collected and referenced.
- Define Northbound external API capabilities to support the Change Management project
- Service Orchestrator
- A&AI
- DCAE
- SD&C
- Controllers
- DMaaP
- Reference VNFs (related Use Cases)
- What other ONAP projects does this project depend on?
- How does this align with external standards/specifications?
- Base service abstraction Information Model on best in breed standard models (e.g., TM Forum SID, MEF 7.3 Service Info Model, etc.)
- MEF LSO Legato (MEF 7.3 Service Info Model)
- TM Forum SID
- TM Forum Zoom effort and related TM Forum APIs where applicable. TM Forum APIs to consider include:
...