...
PNP-6080 [DCAE/DMaaP/DR] - When the PNF sends the pnfRegistration Event to the DCAE VES Event Listener, DCAE shall publish the VES event received from the PRH onto the DMaaP/DR. The VES event should be using the pnfRegistration domain (Casablanca)
STEP 3 3 - pnfREGISTRATION ONTO DMaaP
PNP-6090 [DMaaP] – There shall be created a static pnfRegistration DmaaP Topic. Note: That a static as opposed to a dynamic DMaaP topic is needed because it is not known what PNF service will be needed when the PNF registers.
STEP 4 - pnfREGISTRATION EVENT RETRIEVED BY PRH
...
PNP-6220 [PRH] - The PRH shall use the "sourcename" (pnf-ID) as the index to A&AI.
STEP 6 6 - UPDATE PNF ENTRY - Update PNF Entry in A&AI
PNP-6230 [PRH] – If PRH finds an A&AI entry for the PNF, it shall populate the A&AI PNF object fields with as many parameters received as possible, especially the OAM IP address for that entry with the OAM IP address provided in the pnfRegistration VES event sent from the PNF. Fields in AdditionalText
In case of additionalFields received within pnfRegistration event, those fields will not be used to update the PNF object parameters (they`re assumed to be domain-specific, while PRH operates of PNF generic parameters).
LOGICAL LINK OBJECT (BBS use-case specific aspect) - Create object in A&AI: "Logical-Link". Use Relation of the A&AI between the PNF instance and the Logical Link instance. This relation can be used by (BBS) microservice to identify the attachment point and cf. w/ storage in inventory to differentiate the case: registration or re-registration.
Instance: PNF ↔ A&AI: PNF (object) ↔ Relationship (objection) ↔ Logical Link (object)
REREGISTRATION RE-REGISTRATION CRITERIA: PRH does search in A&AI for the PNF. The Criteria to differentiate between initial registration & re-registration. q.v. PNF Re-Registration criteria so that policies ONAP Policy or other micro-service may also reuse this mechanism. use this mechanism to react in case of re-registration, by implementing changes specific to the domain, where that specific PNF operates.
(To be removed in Dublin) Macro flow building blocks. Migration of sub-W/F.(To be removed in Dublin)
Note: The PNF is the master of its IP address and would over-write the OAM IP address(es) in the PNF A&AI entry with the one ones provided in the VES event (there is v4 and v6 addresses provided and stored in AAI for a PNF object).
PNP-6240 [DUBLIN][PRH] - The PRH shall enter the following information into the A&AI entry for the PNF extracting the corresponding information from the incoming pnfRegistration VES message. The PRH shall populate A&AI`s PNF ONAP associated object record information with information coming in from the pnfRegistration VES event, including the Additional information.
| A&AI PNF ENTRY | BASED ON pnfREGISTRATION VES FIELD |
|---|---|
| serial-number | serialNumber |
| equip-vendor | vendorName |
| equip-model | modelNumber |
| equip-type | unitType |
| pnf-name | sourceName |
| pnf-id | |
| ipaddress-v4-oam | oamV4IpAddress |
| ipaddress-v6-oam | oamV6IpAddress |
| software_versions | software_versions [1] { softwareVersion (from pnfRegistration) activeSw = "True" } |
...
PNP-6250 [PRH] – If the PRH encounters a situation that there is a PNF entry in A&AI (without IP address), but the VES event itself does not have an PNF IP address it shall log the error.
Note: if the PNF does not send its IP address in the VES event this could be from a variety of reasons from a software error to a communication failure.
...