Page Comparison

When the PNF registers, PRH should update the A&AI entry with the information in the VES event.

PRH shall update A&AI with all fields from pnfRegistration VES event into all corresponding fields of A&AI entry. See the 5G - PNF Plug and Play wiki

DEVELOPMENT STATUS:

PRH support for the Re-Registration Use Case in PNF PnP (for BBS Nomadic ONT PNF Re-registration Use Case). Which fields to compare in mapping field to determine a reregistration PNF.

DEVELOPMENT STATUS:

API CHANGE:

New field for event publishing on pnfReady topic & pnfUpdate topic enhanced with additional fields as received in pnfRegistration event (a 1-to-1 copy). Was reviewed & agreed with BBS U/C team and change made in code (continuous integration system). Mar 14, 2019

New A&AI schema adaptations: 5G - PNF Plug and Play (Casablanca carry-over items) found a discrepancy between PNFs and VNFs; VNFs are identified via VNF-ID (UUID), and PNFs - via PNF-name.
So PNF-id should be used for Identities. This differentiates the way that PRH is searching for PNFs in A&AI, when PRH does the PNF registration in A&AI (may also require SO change).

A PNF-name parameter will be used to search a relevant PNF instance, and then CRUD operations will be executed using the PNF-ID value obtained from that previous instance search.

PNF-id = UUID;

PNF-name = Correlation ID.

PRH use search API to find PNF instance based on PNF-name then get the PNF-id.

pnfRegistration VES Event to get the Key to search A&AI. use "sourcename" (part of VES Common header). Take value of sourcename search A&AI to find a PNF entry.
In R3/Casablanca search against PNF-name = sourcename (search for object get PNFid); In R4/Dublin search against PNF-name = sourcename (with a different API). search for object. Change in primary key in A&AI.

Added March 13th 2019 → AAI team got a recommendation from architecutre committee to defer this item to ONAP/El Alto release.

ASSOCIATED DEVELOPMENT:

See task A&AI1 and SO4.
This work is to be covered here: