...
The following flow diagram shows the steps for this use case
STEP 1 AUTHENTICATE CONNECTION - The PNF Authenticates its connection
...
PNP-6260 [PRH] – (Error Case) If the PRH is unable to update the A&AI entry with the PNF information it shall log the error.
STEP 7 pnfUpdate EVENT = SERVICE UPDATE PROCEDURE - Update the ServicePRH sends pnfUpdate event
PNP-6270 [PRH] - PRH shall treat a PNF that is sending a pnfRegistration VES Event that already has an A&AI entry as a PNF that is re-registering. If the PRH has been identified as a PNF that is re-registering, PRH shall publish a pnfUpdate event on the DMaaP bus. This will call the Service Update Micro-Service (that is listening for pnfUpdate event). PRH shall pass the pnf-ID of the re-registering PNF so that the Service Update Micro-Service can identify the PNF. The Update Service Micro-service is listening for the pnfUpdate event.
Note: for the BBS Use Case, the Additionalfield in the pnfRegistration message contains vital application information that needs to be preserved. This information should either be copied into a new field in the A&AI entry for the PNF, or it should be passed to the UpdateService Micro-service when PRH calls it. The recommendation from the BBS team is to pass the entire pnfRegistration body content into the micro-service.
PNP-6410 [DMaaP] – There shall be created a static pnfUpdate DMaaP Topic.
STEP 8 MICROSERVICE ANALYSIS - Microservice is invoked
PNP-6280 [UpdateServiceMSvc] - The purpose of the Update Service Micro-service is that it can identify an associated resource (PNF, VNF) of a service given the identifier, and process a reregistration procedure by updating the service associated with that resource. For example, suppose a PNF have been moved, the associated service needs to be updated. The Update Service Micro-service is listening for the pnfUpdate event.
STEP 9 POLICY USE - A policy framework is invoked
PNP-6290 [UpdateServiceMSvcPolicy] - The Update Service Micro-service issues a special EVENT which will be consumed by POLICY framework. A policy is invoked which performs the service update. The update service micro-service has the responsibility of by way of a Policy:Policy Framework will find a specific policy to handle the request based on the PNF that is being updated. And it will call SO with a (new) Service Update API. The Policy has the responsibility of:
(1) determining that a PNF is reregistering (1) determining that a PNF is reregistering
(2) identifying the PNF with its appropriate PNF-ID
...
(5) Publishing on the DMaaP bus the pnfUpdate Event which will cause SO to update the Service.
STEP 10 pnfUPDATE EVENT- Update event is issued on DMaaPMODIFY SERVICE INSTANCE - Policy calls SO through a Modify Service API
PNP-6400 [UpdateServiceMSvcPolicy] – After the PRH write the IP address of the PNF in the A&AI entry, the PRH shall publish a pnfUpdate event on the DMaaP topic. Note: This pnfUpdate event shall be processed by SO to process a PNF Update procedure.PNP-6410 [DMaaP] – There shall be created a static pnfUpdate DMaaP TopicPolicy invokes a Modify Service API towards SO. This has the effect to directly calling SO to perform the final steps of the service update associated with the PNF undergoing re-registration.
PNP-6420 [UpdateServiceMSvcPolicy]– (Error Case) If the PRH is unable to publish the pnfReady event onto the DMaaP topic it shall log the error.
...
PNP-6430 [SO] – SO shall query A&AI upon receipt invocation of the pnfUpdate EventModify Service API (from Policy). SO queries A&AI for a valid PNF entry associated with the pnf-Id in the pnfReady event. SO subscribes to certain events, it performs a get off the DMaaP bus, and the pnfUpdate event and has a BPMN recipe associated with that pnfUpdate event. Note: In design-time a service designer creates a (set) of BPMN recipes for SO.
...
STEP 12 BPMN RECIPE - SO processes the pnfUPDATE Modify Service request (from Policy) Event
PNP-6440 [SO] -SO will process a BPMN Recipe for the pnfUpdate eventModify Service request from Policy. The purpose of this is to determine that the PNF is re-registering, and the invoke the appropriate actions to process a pnfUpdatethe modify service. 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.
...