Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

PNP-1320 [PNF] - [FUTURE R4] The PNF Vendor shall provide a PNF Descriptor for Design time SDC Design Studio input based on ETSI-NFV-IFA014v242 (see 48534348 5G-PNFPlugandPlay-STAGE1-PNFDESCRIPTOR for more details)

PNP-1330 [PNF] - The PNF Vendor MAY provide software Version(s) to be supported by PNF for SDC Design Studio PNF Model. This is set in the PNF Model property software_versions.

...

PNP-4210 [PNF] – The PNF MUST support sending a pnfRegistration VES event. This is detailed in the “PNF Registration VES Event” section of the Plug and Play wiki page at: 48534348 5G-PNFPlugandPlay-STAGE3-PNFREGISTRATIONVESEVENT

Note: See the Vendor PNF PNP Deliverables (in the ONAP DOC Project) URL/Wiki: https://onap.readthedocs.io/en/latest/submodules/vnfrqts/requirements.git/docs/Chapter7/PNF-Plug-and-Play.html

...

Note: These are detailed in the Stage 5 PnP Use Case at: 48534348 5G-PNFPlugandPlay-STAGE5-PNFACTIVATIONREQUIREMENTS

Note: These parameters are optional, and not all PNFs will support any or all of these parameters, it is up to the vendor and service provider to ascertain which ones are supported up to an including all of the ones that have been defined. Note: It is expected that there will be a growing list of supported configuration parameters in future releases of ONAP.

...

Note: The exact criteria, when to classify a pnfRegistration message as "initial registration" or "re-registration" are stored here: PNF Re-Registration criteria

PNP-6410 [DMaaP] – There shall be created a static pnfUpdate DMaaP Topic.

...

STEPDESCRIPTION
x

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.

y

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.


SUMMARY OF R3 CASABLANCA PLUG AND PLAY ENHANCEMENTS


The follow describes a summary of the Casablanca Enhancements for Plug and Play

...

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.


Plug and Play Overview Slides, Demos and Talks (R2-R9)

The following table has some of the Plug and Play overview slides, demos and talks

DescriptionFile

PnP Overview Presentation & Talk

(from R7 Guilin Release)

PnP Overview Presentation & TalkUse Case Realization Call: February 19, 2020


ROADMAP - PNP Plug and Play Evolution per Release (R2 Beijing - R8 Honolulu)

The following table are Links to the PnP in different releases:

ReleaseWiki Link
R2/R3 Beijing Casablanca48534348 5G - PNF Plug and Play (This base page)
R4 Dublin5G - PNF Plug and Play (Casablanca carry-over items)
R5 El AltoMaintenance Release
R6 FrankfurtPNF PLUG and PLAY in R6 Frankfurt
R7 GuilinR7 PNF Plug and Play PnP
R8 HonoluluR8 PNF Plug and Play Use Case
R9 Istanbul(No new development)
R10 Jakarta(No new development)
R11 Kohn(No new development)

The following table show the PnP Roadmap

PnP Flow STEP

BEIJING (R2)

CASABLANCA (R3)

DUBLIN (R4) 5G - PNF Plug and Play (Casablanca carry-over items)

FRANKFURT (R6) PNF PLUG and PLAY in R6 Frankfurt

1 Resource Definition

Initial Development

No S/W Change; First Integration

This is now handled with the PNF Pre-onboarding/Onboarding use case:

5G - PNF Pre-Onboarding & Onboarding


2 Service Definition

Initial Development

SDC: new PNF model parameters



3 Type Modeling Artifacts

Initial Development

No S/W Change; First Integration



4 Resource Declaration

Initial Development

Alt Operator`s Inventory Management system supported



5 Create A&AI PNF Entry

Initial Development

Alt Operator`s Inventory Management system supported

PNF Schema change from PNFID (new) and redacting (PNF-name old)


13 ONAP Compliant S/W

Initial Development

No S/W Change; First Integration



15 Work Order to SO

Initial Development

SO: First R2 Integration

VID enhancements with new Presentation Layer

Controller to NF association architecture (development in El Alto)


16 Service Instantiation

Initial Development

SO: First R2 Integration



17 Homing OOF Sniro

Initial Development

SO: First R2 Integration



18 Resource RLF

Initial Development

SO: First R2 Integration



19 Check A&AI Entry

Initial Development

SO: First R2 Integration

A&AI Schema update using PNF-ID instead of PNF-name


20 Create A&AI Entry

Initial Development

SO: First R2 Integration



21 Subscribe VES Event

Initial Development

SO: First R2 Integration



22 RLF Thread Terminates to Wait State

Initial Development

SO: First R2 Integration



25 Authenticates PNF Connection

Initial Development

Enhanced ONAP Security developed. TLS, Certificate support, Authentication

Certificate Authentication for HTTPS/TLS


26, 28 PNF Registration VES Events

Initial Development

New pnfRegistration domain, Static DMaaP topics

A new EPIC the PNF Re-Registration Use Case is introduced (see this Wiki)

485343485G-PNFPlugandPlay-PNPREREGISTRATIONUSECASE


27 Inventory Query (A&AI)

Initial Development

New pnfRegistration domain

A&AI Schema update using PNF-ID instead of PNF-name


29 Inventory Query (A&AI)

Initial Development

New pnfRegistration domain



30 Update PNF Entry

Initial Development

New pnfRegistration domain



31 PNF Ready

Initial Development

New pnfRegistration domain



34 Update PNF WF

Initial Development

SO: First R2 Integration



35 Network Assignments

Initial Development

SDN-C: PNF PnP Development



36 Configure

Initial Development

SO: First R2 Integration



37 Service Configuration

Initial Development

PNF Controller development

Controller to NF association architecture (development in El Alto)

New API between SO to SDNC.

NETCONF support for Configuration (see the Netconf Use Case)

5G - Configuration with NETCONF


38 SO Updates w/ Assignments

Initial Development

No S/W Change; First Integration



39 Controller Replies

Initial Development

No S/W Change; First Integration



40 Service Running

Initial Development

No S/W Change; First Integration



41 Monitors Service

Initial Development

No S/W Change; First Integration



42 Inform OSS

Initial Development

No S/W Change; First Integration



...


DEPLOYMENT DIAGRAM

TEST CASES 

...