...
- Lifecycle Support: ONAP must support a complete life cycle management of software-defined network functions / services: from VNF/PNF On-Boarding, Resources / Service Definition, VNF / PNF Service Instantiation, Monitoring, Change Management, Software Upgrade, to retirement
- Standardization: ONAP must support a common approach to manage various network functions from different vendors
...
- Vendor & Service Agnostic: ONAP Platform must be PNF / VNF, Resources, Products, and Service agnostic. Each service provider or integrator that uses ONAP can manage their specific environment (Resources, PNFs / VNFs, Products, and services) by creating necessary meta-data / artifacts using Design Studio to support their needs / environment.
- Common Information Model approach: ONAP should define a standardized common information model for all vendors to follow. This will allow ONAP users to quickly onboard and support new VNFs.
- Pluggable Modules: The ONAP architecture should develop and promote PNF / VNF standards to allow delivery of Lego block-like pluggable modules, with standard interfaces for all aspects of lifecycle management (e.g. instantiation, configuration, telemetry collection, etc.).
- Integrated & Centralized Design Studio: All artifacts required for ONAP components should be able to be designed from a central ONAP design studio.
...