...
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.
| 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.
...
PNP-6440 [SO] -SO will process a BPMN Recipe for the pnfUpdate event. The purpose of this is to determine that the PNF is re-registering, and the invoke the appropriate actions to process a pnfUpdate. This means that
(1) it will determine that this is an existing PNF that is reregistering. See the description of the reregistration use case to see why a reregistration occurs (A) Rehoming (B) Disconnection/Reconnection (C) Physical Relocation (D) Nomadic PNF.
(2) Identify services that are currently depending on this service(s)
(3) Update the states for that PNF. This means that the associated resources of the associated service(s) of that PNF need to be updated (i.e. the PNF is now available). An analysis must be done that says that this PNF is no longer associated with the service (a policy rule with an algorithm assessment would be used to determine this).
(4) Identify the appropriate controller for that PNF.
Note: the Controller might be updated when the PNF re-registered.
STEP 13 RECONFIGURE PNF - PNF configuration is invoked
...