AAI R4 Use Case and Functional Requirements Impacts

PNF Plug and Play (Casablanca carry-over items)

Moderate

• Potential schema changes:
  • PNF
    • Using the pnf-id (instead of pnf-name) as the index for PNF into A&AI. Achieve naming indexing consistency between PNFs and VNFs.
    • Migration for previously created PNFs
      
    • Impacts all API calls/all clients interacting with PNFs
  • Cloud-region
    • Tracking the Cloud Home Server (CLLI, Cloud ID); is the association with the COMPLEX Object sufficient?
      

• Ingest and use 5G NF Packages (CSAR file), PNF Artifacts, Definitions, TOSCA-Metadata - Requires changes to A&AI model loader
• Run-time catalog update to associate artifacts to a PNF
• ONAP Run Time Activities: 5G Service Instantiation

Advanced 5G functionality, for Network Slicing development and early steps in long-lead development.  Service slicing allows advanced steering of services, based on policy, GW loading, and other criteria. 

Impacts:
• A&AI shall store vSSF inventory (and associated EMS inventory) and forward it to downstream systems (eg, DCAE, AOTS-M).  (Assumes ONAP will use a vSSF software product and a supporting EMS from some vendor.)
• Radio PNF’s are deployed and configured ( RA, TA’s & cells) and shall be persisted in A&AI.
• A&AI shall also contain inventory of available data centre sites with associated constraints.

• Retrieve VNF level ipv4-oam-address. generic-vnf.ipv4-oam-address (existing property)
• Change in the VNF model to introduce an dt-anchor-point capability to vnf of vf. (new property in generic-vnf)
• Change in the VNF model to introduce an dt-destination-point capability to vnf of vf. (new property in generic-vnf)
• Perhaps there is a need to hold pairs of (dt-anchor-point, dt-destination-point) to allow ScaleIn for any VNF in Virtual service. (new properties in generic-vnf)

Performance Measurements 5G RAN Bulk Upload, Casablanca Carry-over items

No A&AI impact

Schedule Optimization with Automated Conflict Avoidance

• Retrieve VNF level ipv4-oam-address.
  generic-vnf.ipv4-oam-address (existing property)
• Change in the VNF model to introduce an dt-anchor-point capability to vnf of vf. (new property in generic-vnf)
• Change in the VNF model to introduce an dt-destination-point capability to vnf of vf. (new property in generic-vnf)
• There is a need to hold pairs of (dt-anchor-point, dt-destination-point) to allow ScaleIn for any VNF in Virtual service. (new properties in generic-vnf)

SO verifies and queries A&AI for the appropriate PNF entry. (existing functionality).

• A&AI Entry of the PNF is updated with the appropriate software versions. Update Software Version in A&AI
pnf.sw-version property (existing property)