PNF SOFTWARE UPGRADE in R6 Frankfurt

"Base" PNF Software Upgrade Wiki: 5G - PNF Software Update

R5 Candidate Enhancements for PNF Software Upgrade

R5 CANDIDATE ENHANCEMENTS	IMPACT
PNF Reporting its S/W version (NetConf)	PNF sends information regarding its Software Version directly to ONAP through a VES event. (possibly already covered with PNF Registration)
Support of NetConf & Yang models	PNF Software Upgrade using NetConf for direct ONAP to PNF communication.
Software Update Coverage Analysis	Find out what services, control loops, etc. are impacted during and post software update before the PNF software update
Post/Pre PNF SW Update Event Workflows	Deregistration, re-registration
VNF & PNF in-place software upgrade processes alignment	Unifying PNF and VNF entries in A&AI
VID support	Execute the E2E run time software upgrade workflow.
3GPP Alignment	3GPP TS32.532 Automated/non-Automated S/W mgmt. API between manager & managed entity (south-bound of controller).

Including more components, until now it was in the controller, in R6 it might include more components such as DCAE, PRH, A&AI.

IP@ in A&AI resulting from a PNF S/W Upgrade

the controller for the PNF, what does the IP@ configuration to the PNF is it SDN-C or APP-C?

IP@ of the PNF needs to be provided, sending request directly to PNF

using a EMS, ONAP would need the IP@ of the EMS (ESR Object). (in R4 that's an input parameter to the controller).

In the future, this might be fetched from A&AI. SO would do the lookup and pass to the controller.

PNF S/W version reporting

xyz

xyz

xyz

xyz

xyz

xyz

xyz