Currently no impact on AAI project expected based on the following assumptions:

• PNF and VNF inventory models already contain status attribute that can indicate when a new instance has been fully instantiated
  • orchestration-status is main candidate
  • At least for PNFs it is expected that the SO workflow must be updated to set this attribute
• AAI will send topology event on AAI-EVENT topic when status attributes are updated

Assumptions

• Current analysis indicates that CLAMP has support for model-driven UI to parametrize the configuration policy for the new PMSH mS. This basic functionality could be enhanced in later step.
• Both VNFs and PNFs can be supported

DCAEGEN2-1821

DCAEGEN2-1820        

• Addition of new PMSH micro-service supporting
  • Configuration policy to provide PM subscription parameters
  • Sending closed loop event to trigger operational policy for xNF PM configuration
  • Interaction with AAI to discover xNF instances and fetch needed information
  • (Stretch goal) DMaaP or similar interface to request activation/de-activation of subscription
• (Stretch goal) Optional capability to forward subscription data like measurement list to PM Mapper using appropriate mechanism (to be further discussed)

-------

Another enhancement

• CMPv2 for operator certificate enrollment for secure 5G Bulk PM. 

• Support APEX operational policy in combination with CDS actor (dependency)

• Workflow shall update status attribute in AAI when the VNF/PNF instance has been fully instantiated
  • orchestration-status is main candidate
  • At least for PNFs it is expected that the SO workflow must be updated to set this attribute (Jira issue defined)

• PM control e2e test case
• New/updated xNF simulator with demo YANG model for PM control
• Test artifacts:
  • CBA implementing new controller actions with transformation from xNF-agnostic subscription to xNF-specific YANG model
  • APEX operational policy to forward subscription configuration from PMSH to controller using the CDS Actor