Versions Compared

Old Version 10

changes.mady.by.user Zu Qiang

Saved on

compared with

New Version 11

changes.mady.by.user Zu Qiang

Saved on

Key

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

...

More details, 5G - PNF Software Update & 5G - PNF SW Upgrade (Casablanca carry-over items)

Related Meeting Links

...

Candidate Enhancements for PNF Software Upgrade

R5 CANDIDATE ENHANCEMENTS

IMPACTDescriptions

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.

Image Removed

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

NetConf support

xyz

Update Coverage Analysis

xyz

Post/Pre Event W/F

xyz

VNF-PNF in place S/W upgrade alignment

xyz

VID Support

xyz

3GPP Alignment

...

software upgrade with direct Netconf/Yang interface with PNF

  • Enhancement and additions of PNF in-place software update.
  • Support direct PNF NETCONF interface with the vendor-specific YANG model.
  • Enhance SO in-place software upgrade workflow with generic SO building blocks, which can be used for workflow design in the design time.
  • Using CDS self-service API between SO and controller with the support of PNF in-place software upgrade
  • Enhance VID to demonstrate single PNF in-place software upgrade
  • Enhance SO procedure to support AAI update after the software upgrade completion.

Enable service level LCM operations

  • Updating the design time service template using vendor provided onboarding package
  • Upgrading a run time service instance based on the updated service template
  • Updating the run time catalog at software upgrade completion

Enhancement on the PNF upgrade using Ansible protocol