...

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. 

...

Following is an example of RG Activation notification received from Access Edge SDN M&C - the domain controller.

...

The moving ONT associated (through pnfName) service ID is looked up in A&AI and enriched in the A&AI portion of the above DCAE_CL_OUTPUT Event which trigger the operational policy in the operational policy defined below.  

...

Update Service Micro-service

A new micro-service, ONAP Micro-Service or ONAP SM SDK, that handles RG Online (or activation) notification will be introduced to consume a new type of VES event. This event is converted from RG Activation notification by VES Mapper.

...

        - run A&AI query A&AI  enrichment logic 

The BBS Update Service MS could be built on top of DCAE service SDK ( https://gerrit.onap.org/r/#/admin/projects/dcaegen2/services/sdk - R4).  A MS blueprint could be is defined at DCAE-DS and this service can be deployed from CLAMP or can be instantiated as a standalone container as when DCAE is deployed.

Another option of handling RG Activation Registration Event is to have it directly trigger Policy Engine to take further action.Both pnfUpdate and CPE Authentication events will be consumed by this micro-service. HSIA re-provisioning action is triggered through Policy executing Nomadic ONT operational policy, while  CPE Authentication event triggers HSIA service update by marking it as activated. 

RG Activation(CPE Authentication) Event 

This event is converted from the RG Activation notification by VES Mapper.  Upon receiving this event BBS UpdateService MS will look up for the associated HSIA service and trigger Policy engine to mark (calling SO API?) it as activated. the service as activated. 

Example in VES StateChange domain

The CPE Authentication Event is defined here in VES StateChange domain.  It indicates if the ONT/CPE is successfully authenticated at the Edge after the ONT/CPE relocation is completed. 

Example in VES Fault domain

Following is the example CPE Authentication event and schema if this event is defined in  VES Fault domain.

{
    "event": {
        "commonEventHeader": {
            "sourceId": "Gateway/sn=83575443FA637D1A", // from 'traget' field
            "startEpochMicrosec": 1413378172000000,
            "eventId": "ab305d54-85b4-a31b-7db2-fb6b977766",
            "sequence": 0,
            "domain": "fault",
            "lastEpochMicrosec": 1413378172000033,
            "eventName": "Fault_CPE_AUTH_Status",
            "sourceName": ""Gateway/sn=83575443FA637D1A", // 'Target' from the restconf notification.
            "priority": "High",
            "version": 3.0,
            "reportingEntityName": "Domain_Contorller"
        },
        "faultFields": {
            "eventSeverity": "CRITICAL",
            "alarmCondition": "Route_Status",
            "faultFieldsVersion": 2.0,
            "specificProblem": "Fault_RG_Status",
            "alarmAdditionalInformation": [
                {
                "name": "gatewaySN",                   
                "value": "83575443FA637D1A"              
                },
                {
                "name": "mac",                   
                "value": "28-6E-D4-89-34-DD"               
                },              
                {
                "name": "ip",                   
                "value": "10.68.52.158"              
                },
                {
                "name": "state",
                "value": "OnLine"
                },
                {
                "name": "ontSN",
                "value": "48575443FA637D1A"
                }
            ]
            "eventSourceType": "other",
            "vfStatus": "Active"
        }
    }
}

...