REQUEST LICENSES - The PNF, for example 5G RAN PNF (DU) contacts the License Service to request licenses.

Note: This step is optional. This step is labeled "X" because it can be initiated any time after stage 3 in the Plug and Play flow.

RESPONSE WITH LICENSES - The License Service responds to the request for licenses to the originating PNF.

Note: This step is optional. This step is labeled "Y" because it can be initiated any time after stage 3 in the Plug and Play flow.

TOPIC

DESCRIPTION

PNF Registration Handler (PRH) Improvements

pnfRegistration Domain - New VES Event domain for PNF registration with corresponding support in VES collector, DMaaP and PRH.

PRH & AAF Integration – intra-ONAP security improvements

Integration – Integration of Beijing software deliveries.

DU Simulator Update – Support of new domain and updates to the DU simulator to match changes made in Casablanca.

SO Workflow enhancements

Integration - Introduction of dedicated 5G use case work-flow. While the PnP Work-flow was coded in Beijing it was not delivered in that time frame.

PNF Controller Interaction – SO to the PNF controller interaction is developed in Casablanca (R3).

Service Configuration Improvement

PNF Controller – Service configuration improvements from PNF Controller to PNF after PNF registration to PRH. Five optional parameters are requested to be supported with the Casablanca release (R3).

Security Enhancements

Security Enhancements – Authentication, Certificates, User name & password and intra-ONAP security are used by the Plug and Play Use case.

Modeling enhancements

PNF Model – Modeling enhancements to support 5G PNF in ONAP with support for the new SoftwareVersionList parameter.

PNF Onboarding / Package

PNF Package - Defining PNF Onboarding Package. Extending framework to work with PNFs. Defining PNF Package framework. The PNF package artifacts will be delivered in Dublin such as the PM dictionary and FM Yaml dictionary. The definition of these are explored in Casablanca.