Background

Each time a new PNF is connected to the network, or reseted to factory settings, a PNF registration process is expected to happen.
Within this process, a VES pnfRegistration event is sent from a PNF instance to the ONAP/DCAE/VES collector.
In order to support Nomadic PNF use-case of a broder BBS use-case, an initial registration of a PNF needs to be distinguished from a re-registration.

Initial reogstration happens, when a PNF instance registers with ONAP for the first time (it was not used as a resource in any active service instance before).
Generally re-registration happens, when a PNF, that has been used previously to deliver a service is re-connected or reseted, and attempts to register again with ONAP.

Goal

The goal of this page is to summarize and prioritize the criteria, when a registration attempt is considered a Re-Registration.
All registration cases, which do not match with re-registration criteria will be considered "initial registrations".

Re-Registration criteria

The following criteria need to be applied (in teh order given here), when evaluation, if a registration attempt is a Re-Registration:

1. If a registration attempt is executed for a PNF Instance, which has an existing entry in the ONAP/AAI, and when that PNF instance is associated with an active (orchestration-status==active) service instance
   → Re-Registration