...

• Scope of the ONAP platform
• Key guiding imperatives for ONAP modules
• Implementation Principles
• Deployment, Resiliencey and Scalability considerations

4. The ONAP Architecture Principles and Architecture Requirements

4.1 ONAP Architecture

...

Requirements

4.1.1 Lifecycle support:

ONAP must support a complete life cycle management of software-defined network functions and services:

...

ONAP Platform must be PNF / VNF, Resources, and Service agnostic.  Each service provider or integrator that uses ONAP can manage their specific environment (Resources, PNFs / VNFs,  and services) by creating necessary meta-data / artifacts using Design Studio to support their needs / environment.

4.1

...

.

...

4 .1.4 Strive for Standardization: 

...

Define ONAP as a layered architecture similar to the OSI model for the internet. ONAP will have an orchestration layer, multi-cloud layer, and application control and lifecycle management layer.  These layers interface with each other using defined abstract interfaces between the different layers to support information and request flowing between the layers in an implementation-independent manner.

4.3.6 Common Information Model approach:

ONAP should define a standardized common information model for complete life cycle management that all vendors must follow.  This will allow ONAP users to quickly onboard and support new resources (xNFs) and/or services.

4.3.7 Platform System Data Model:

Defines an abstract data model of the objects and entities to be managed by ONAP.

...