Introduction

The BBS approach is to take advantages of the existing ONAP implementation as much as we can.  In Nomadic ONT scenario,  ONT is logically modeled to PNF. Restconf collector introduced in R3 is reused to collect ONT relocation notification. The notification will be converted into VES pnf registration event by VES Mapper micro service.  PRH, which is the generic PNF Registration Handler micro service in ONAP, is enhanced to cover PNF re-registration logic.  This newly defined PNF re-registration event triggers Policy engine to take actions over  SDNC component to fulfill the ONT relocation procedure.

Nomadic ONT Flow (Original)

The following diagram reflects the complete Nomadic ONT flow with Policy triggering SO (instead of SDNC) at ONT moving (i. e., PNF Re-registration) detection.  We will modify this for SDNC to take the service update per ONT relocation.  

Here  are the flow by steps:

1. Access SDN M&C reports the ONT registration event to DCAE/PRH
2. DCAE/PRH checks if there is an existing PNF entry in AAI for the ONT and if the service associated with this ONT is activated. Updates the ONT info in AAI 
3. DCAE/PRH publishes an PNF Re-registration event with that CFS id from AAI  on DMAAP
4. Policy engine will call SDN-C API upon the event based on the BBS ONT Re-Registration operational policy pre-deployed to it
5. SDN-C triggers the re-configuration of the ONT and the OLT by the Access SDN M&C
6. SDN-C triggers the creation/re-configuration of the RFS Internet Access (e.g. customer's speed profile)
7. SDN-C updates CFS HSIA info in AAI.
8. RG becomes online and initiates the CFS HSIA activation procedure
9. Access SDN M&C reports via DCAE the successful activation of the RG to SO 
10. SO updates CFS HSIA status to 'active' in AAI
11. SO reports service 'active' status to OSS/BSS via External API

DCAE

Restconf Collector

ONT Registration Notification

RG Online Notification

VES Mapper

Restconf2VES Mapping

PNF Registration Event

PRH Extension

PNF Re-registration Detection

PNF for ONT in A&AI

PNF Re-registration Event

DCAE_CL_Event

A&AI Enrichment

Policy 

Apex Engine Triggering

Pdp-D Option

Operational Policy

SDNC Recipe

Notes:

Interestingly,  this is the first case where DCAE/Policy seem playing roles together in a non-closed/loop or service assurance in sense of usage/solution in ONAP domain,  However,  this does not really matter in the sense of micro services since service is a service as long as it provides the functionality that meets the requirements in a solution, An argument could be that Policy engine does not have to be introduced in this case, However, the important functionality for policy engine is to decouple actions takers from the trigger pullers and ultimately establish robust policy driving on this platform w/o code change.