Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

Notes:


BUSINESS DRIVERS

This section describes Business Drivers for this Use Case.

Executive Summary - PNF software updates are routine for network upgrades to support new features, improve efficiency or increase capacity on the field, and to eliminate bugs. This use case positions ONAP as a vantage point in orchestrating and managing PNF software upgrades inline with the business and service objectives.   

Business Impact - Deployment and orchestration of new network services over both VNFs and PNFs in a model and software driven way simplifies the network management. As 5G networks will host a large number of PNFs from multiple vendors, streamlining service upgrades that involve PNF software changes through ONAP will reduce the OPEX substantially.  

Business Markets - Carriers both in the mobile and fixed-line space host PNFs at the edge of the network. New 5G deployments as well as legacy 4G systems in the mobile carrier space should be considered as target markets. 

Funding/Financial Impacts - Orchestrating PNF software updates via an ONAP deployment will enable better service planning, faster introduction of new network services over field-deployed PNFs, and reduce the operational costs.

Organization Mgmt, Sales Strategies - Harmonizing PNF and VNF software management in a model and workflow driven manner is essential in 5G systems where PNFs will continue to exist in large numbers and they are expected to have more frequent software upgrades (as they will have more capabilities that can be controlled or upgraded via software). Thus ONAP can be the "go-to" solution if this harmonization can be done successfully.



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

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

xyz


  • No labels