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

Compare with Current View Page History

« Previous Version 3 Current »

Summary


The PNF PnP sub-flow allows simple mangement operations on PNFs, as long as service orchestration is concerned.
The following tasks are executed with the PNF PnP sub-workflow:

  • AAI entry creation for a new PNF instance (identified based on correlationID)
  • Hibernation of a workflow instance in case an AAI entry is incomplete (missing PNF`s OAM IP addresses)
  • Re-Hydration upon reception of a pnfRegistration event from a PNF
    • In Beijing release, the VES event is used - domain "other"

Beijing release

Initional version of the PNF PnP flow was contributed in the Beijing release.
This flow is checking, if an AAI entry exists (if not - this entry is created), and then it checks, if there is at least a single IP address available for that entry.
If there is one, the control is passed to higher-level workflow; if not - the workflow is hibernates, and continues, when a pnfReady notification reaches SO.

PNF PnP algorithm block diagram - Beijing release

SO PNF PnP algorithm - Beijing release


  • No labels