...
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 5G-PNFPlugandPlay-STAGE1-PNFDESCRIPTOR 48534348 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: 5G-PNFPlugandPlay-STAGE3-PNFREGISTRATIONVESEVENT 48534348
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: 5G-PNFPlugandPlay-STAGE5-PNFACTIVATIONREQUIREMENTS 48534348
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.
...
PNP-5800 [SO] – SO shall inform the OSS that the PNF service is available and ready.
PNF DOWNLOAD & ACTIVATION
The final steps of PNF Plug and Play occur after the PNF has been registered. The ONAP PNF Software Use Case is also executed to update the software if necessary.
STEP 44 CONFIGURATION – The PNF can have additional configuration or parameters that can be sent to the PNF from ONAP or an external Element Management System. Additioanl configuration exchanges can happen between the PNF and ONAP through the standard Defined VES event as introduced by this use case: ONAP/3GPP & O-RAN Alignment-Standards Defined Notifications over VES
STEP 45 PNF SOFTWARE UPGRADE – Software download occurs which is described in this use case: 5G - PNF Software Update
STEP 45 READY FOR SERVICE – The PNF is ready for service.
PNP REREGISTRATION USE CASE
...
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: | |
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) | |
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) | |
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 |
...