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.
DCAE
Restconf Collector
ONT Registration Notification
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.