...

PNP-6130 [PRH] - if the PRH is unable to read the pnfRegistration VES message. In this case the schema might be incorrect which results in a mismatch with what the PNF sends and what the PRH expects. Thus, the PRH is unable to process the VES event properly. The PRH shall logs this error.

STEP 3 PUBLISH EVENT- The Event to DMaaP Bus.

foo

STEP 4 RETRIEVE EVENT - PRH gets the Event

foo

STEP 5 INVENTORY QUERY - Querying 5 – INVENTORY ENTRY QUERY - ALT Flow: A&AI

foo

STEP 6 UPDATE PNF ENTRY - Update PNF Entry

foo

STEP 7 SERVICE UPDATE PROCEDURE - Update the Service

foo

STEP 8 MICROSERVICE ANALYSIS - Microservice analyzes event

foo

STEP 9 POLICY USE - A policy is invoked

foo

STEP 10 pnfUPDATE EVENT - Update event is issued on DMaaP

foo

STEP 11 QUERY A&AI - A&AI Query

foo

STEP 12 BPMN RECIPE - SO processes the pnfUPDATE Event

foo

STEP 13 RECONFIGURE PNF - PNF configuration is invoked

foo

STEP 14 PNF CONFIGURATION - Controller to PNF interaction

Query

PNP-6200 [PRH] – The PRH shall perform an A&AI inventory query when it receives the pnfRegistration VES event from the PNF. Note: it is expected that the PNF shall continue to send the VES event until it receives the service configuration request. After the Stage 2 Run-Time Service Instantiation occurs, there shall be an inactive A&AI entry for the PNF. This allows PRH to find that inactive A&AI entry and proceed with the rest of the Plug and Play procedure. PRH shall use the PNF-name (or correlation ID) to find the appropriate PNF A&AI entry.

PNP-6210 [A&AI] – A&AI shall return the entry for the PNF-id when queried. If not found A&AI shall return a negative acknowledgement. See the section on the A&AI PNF entry for more details about the fields that are relevant for the PNF.

PNP-6220 [PRH] - The PRH shall use the "sourcename" (pnf-ID) as the index to A&AI.

STEP 6 UPDATE PNF ENTRY - Update PNF Entry

PNP-6230 [PRH] – If PRH finds an A&AI entry for the PNF, it shall populate the IP address for that entry with the IP address provided in the pnfRegistration VES event sent from the PNF.

Note: The PNF is the master of its IP address and would over-write the IP address in the PNF A&AI entry with the one provided in the VES event.

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.

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-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 SERVICE UPDATE PROCEDURE - Update the Service

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 call the Service Update Micro-Service. PRH shall pass the pnf-ID of the re-registering PNF so that the Service Update Micro-Service can identify the PNF.

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.

STEP 9 POLICY USE - A policy is invoked

PNP-6290 [UpdateServiceMSvc] - A policy is invoked which performs the service update. The update service micro-service has the responsibility of by way of a Policy: (1) determining that a PNF is reregistering (2) identifying the PNF with its appropriate PNF-ID (3) Finding the associated service(s) that is/are associated with the PNF and (4) updating the service. (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 DMaaP

PNP-6400 [UpdateServiceMSvc] – 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 Topic.

PNP-6420 [UpdateServiceMSvc] – (Error Case) If the PRH is unable to publish the pnfReady event onto the DMaaP topic it shall log the error.

STEP 11 QUERY A&AI - A&AI Query

PNP-6430 [SO] – SO shall query A&AI upon receipt of the pnfUpdate Event. SO queries A&AI for a valid PNF entry associated with the pnf-Id in the pnfReady event.

STEP 12 BPMN RECIPE - SO processes the pnfUPDATE Event

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 (3) Update the states for that PNF. (4) Identify the appropriate controller for that PNF.

STEP 13 RECONFIGURE PNF - PNF configuration is invoked

PNP-6450 [SO] – SO shall lookup through Controller-to-NF association, the appropriate Controller for the PNF. Then, SO shall invoke the PNF controller to request a PNF configuration exchange to happen.

Note: SO interacts with the PNF controller with the Understanding the the GENERIC-RESOURCE-APIs

STEP 14 PNF CONFIGURATION - Controller to PNF interaction

PNP-6500 [CONTROLLER] – The PNF Controller shall sends a Service Configuration to the PNF.

Note: For each associated API there is an associated Directed Graph (which playbook should be called).

PNP-6510 (CONTROLLER) – (Error Case) If there is an error encountered trying to send the Service Configuration command exchange to the PNF, the Controller shall log the fault.

PNP-6520 (CONTROLLER) – (Recovery Case) If there is an error encountered trying to send the Service Configuration command exchange to the PNF, the Controller shall attempt to retry.

PNP-6530 (CONTROLLER) – (Recovery Case) If there is not acknowledgment or response from the PNF while trying to perform a service configuration exchange, the controller shall wait for a time-out period before aborting this attempt. Note: This might be caused by a transient network issue.

PNP-6540 [PNF] - The PNF MUST support the Anible protocol for a Service Configuration message exchange between the PNF and PNF Controller (in ONAP).

Note: this exchange may be either Ansible, Chef, or NetConf depending on the PNF. Note: The PNF Controller may be VF-C, APP-C or SDN-C based on the PNF and PNF domain. Note: for R3 (Casablanca) only Ansible is supported.

PNP-6550 [PNF] - The PNF MUST support the NetConf protocol for a Service Configuration message exchange between the PNF and PNF Controller (in ONAP).

PNP-6560 [PNF] - When the PNF receives a Service configuration from ONAP, the PNF shall cease sending the pnfRegistration VES Event.

PNP-6570 [PNF] - The PNF MAY support the optional parameters for Service Configuration Parameters.foo

STEP 15 CONFIGURATION RESPONSE - Configuration Responsefoo

PNP-6580 [Controller] – The Controller shall return a response to SO after service configuration

STEP 16 A&AI UPDATE - A&AI Updatefoo

PNP-6590 [Controller] – The PNF Controller shall update the PNF A&AI Entry with updated configuration information.

SUMMARY OF CASABLANCA PLUG AND PLAY ENHANCEMENTS

...