1. Alla Goldner (outcomes from brainstorming meetings) Sept, 2017
Functional requirements for R2 Prioritized proposals for further consideration
Alla Goldner (outcomes from brainstorming meetings)
Sept, 2017

2. The list
PNF requirements category -   management of application  ( e.g. discover the presence, monitor, change configuration, do not manage physical hardware).
ONAP shall… - the requirement should be for ONAP’s support of PNFs (and eventually this may be translated into building an adaptation layer)
Modeling – harmonization of information/data model for services and resources.
Onboarding  - TOSCA onboarding support  - to complete onboarding VNFs/NSs by using TOSCA templates
Monitoring – multiVIM telemetry, working in the same way, independently of specific VIM, collecting and normalizing
VNF Homing optimization (including affinity/non-affinity rules)
Change management
Model driven interaction between the micro-services and the bus
External controller and interfaces to OSS/BSS – to specify standardized northbound/southbound interfaces 

3. PNF support https://wiki.onap.org/display/DW/PNF+Modelling+Capability
Support for PNF - Onboarding
Support for PNF - Data Collection & Monitoring
Support for PNF - Configuration & Control

4. Modeling
Harmonization of information and of data model for services and resources

5. Onboarding
TOSCA onboarding support  - to complete onboarding VNFs/NSs by using TOSCA templates
Support real-world   service design in SDC with standard based TOSCA model
Supported to some degree already in R1, used in the VoLTE use case, but not all Tosca constructs are supported, and not the latest Tosca version.

6. Monitoring
multiVIM telemetry, working in the same way, independently of specific VIM
By collecting and normalizing

7. Change management VNF image management
Locking mechanism
Platform capabilities exposure

8. VNF Homing

9. Model driven interaction between the micro-services and the bus
Will enable limiting the amount of pair-wise transactions between ONAP modules to minimum, resulting in a more robust software architecture, and more track-able and traceable transactioning

10. External controller and interfaces to OSS/BSS
OSS/BSS Integration
ONAP service   provision and activation system/function
External Controller Integration
Integration of external controller to Resource Orchestration – API, adapters
Integration of external controller to DCAE for events, metrics
Import of services, resources supported by external controller to VNF SDK/Onboarding and SDC
Representation/reference of services, resources supported by external controller in A&AI
Lifecycle management of external controller – Turn up, monitoring, scaling, termination

11. Yet to be determined and decided on
5G/Network slicing is considered to be a high priority requirement
Slice management – yet to be finalized and decided whether network slices introduces some new requirements or can be considered as any other Network service
In case of latter, will be recommended as a Use case for implementation/showing ONAP Platform capabilities for Beijing Release

12. Thank You!