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 SO API upon the DCAE_CL event based on the BBS ONT Re-Registration operational policy pre-deployed to it
5. SO initiates the service re-provisioning procedure per ONT location change.  

DCAE

Restconf Collector

The APIs to Access SDN M&C leverage those specified in CCVPN Closed Loop. 

In case of BBS Nomadic ONT, Restconf collector subscribes both of ONT Registration and RG Activation notifications through separate SSE connections with Access SDN M & C , each of the connection handler is assigned at design time to build JSON message with different topics of Restconf_Notification with certain Restconf2VES XML file indicator (in OID field for the time being ). The SB domain controller IP/port, authentication information and produced topic could be assigned at design time at blue print creation through DCAE-DS and configurable at control loop creation time from CLAMP.

ONT Registration Notification

Following is an example of ONT Registration notification received from Access SDN M&C - the domain controller.

[
    {
     “notification” :
        {
         “event-time”: ”2018-03-15T08:15:32.000Z”,
         “notification-id”:  ”2541256”,
         “message”:
            {
                “topic”：“resource”,
                “object-type”：“ont”,               
                “version”: ”v1”,
                “operation”: “Create”,
                “target”: ”ont/ont=23hk1231231232”,
                “content”:
                   {
                    “ont”:
                       {                        
                        “ontSN”：“48575443FA637D1A”,            
                        “neName”：“MA5800T-001”,
                        “neUNIPort”：“0/1/6”,
                        “onuID”：“101”,                                                              
                        “accessID”：“HG65875420001”,                        
                        “remark”：“”,
                     }
                }
            }
        }
    }
]

The output of Restconf Collector for the ONT Registration is the above JSON message being published on DMAAP with topic of RestConf_ONT_Registration. 

RG Activation Notification

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

  [
      {
          “notification”
          {
              “event-time”:  ”2018-04-15T08:15:32.000Z”,
              “notification-id”:  ”2541256”,
              “message”:
              {
                  “topic”：“resource”,
                  “object-type”：“Gateway”,
                  “version”: ”v1”,
                  “operation”: “Create”,
                  “target”:
                  "Gateway/sn=83575443FA637D1A”,
                  “content” :
                  {
                      “Gateway”:
                      {
                          “gatewaySN”：“83575443FA637D1A”,                                   
                          “mac”：“28-6E-D4-89-34-DD”,               
                          “pppoeUserName”: ”587564@163.com”,                
                          “ip”: 10.68.52.158””,
                          “state”:”OnLine”,
                          “ontSN”：“48575443FA637D1A”                            
                      }                
                  }
              }
          }
      }           
  ]

The output of Restconf Collector for the RG Activation is the above JSON message being published on DMAAP with topic of RestConf_RG_Activation. 

VES Mapper

Restconf2VES Mapping

The Restconf2VES mapping rule (*.xml) is provided by the vendor for certain type of notification for ONT and defined as the following:  

The default mapping artifact (xml file) name is specified at the design time in VES Mapper micro-service blueprint at DCAE-DS and it is configurable through CLAMP at control loop creation time. The pre-condition is that the mapping file with correct naming convention should be available or on-boarded and stored in ONAP at design time. When the Nomadic ONT control loop is deployed, the mapping files retrievable and loaded to VES Mapper working space.

PNF Registration Event

VES Mapper converts the ONT Registration notification JSON message from DMAAP into the following PNF Registration event.

This pnfRegistration Event definition can be found at link:
https://wiki.onap.org/display/DW/5G+-+PNF+Plug+and+Play#id-5G-PNFPlugandPlay-STAGE3-PNFREGISTRATIONVESEVENT

PRH Extension

PNF Re-registration Detection

Refer to PNF Re-registration detection logic handled in 5G use case by extension of PRH micro-service.

PNF for ONT in A&AI

Refer to ONT/PNF definition in ONT modeling. 

PNF pnfUpdate Event

This event is the output of PRH PNF re-registration handling and is used to trigger Policy engine to taking for actions on the associated HSIA service.

DCAE_CL_Event

A&AI Enrichment

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_Event which trigger the operational policy in the operational policy defined below.  

New 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.

The characters of this generic micro- service could be the following: 

        - hold a set of REST APIs

        - consume VES events from DMAAP and the consumed event types will be configurable at both the design time and run time

        - publish VES events to DMAAP and the published event types will be configurable at both the design time and run time

        - run A&AI query A&AI  enrichment logic 

This generic ONAP 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 defined at DCAE-DS and this service can be deployed from CLAMP or can be instantiated as a standalone container as DCAE is deployed.

Another option of handling RG Activation Registration Event is to have it directly trigger Policy Engine to take further action.

RG Activation(CPE Authentication) Event (WIP)

This event is converted from the RG Activation notification by VES Mapper.

Policy

Apex Engine Triggering

PDP-A Configuration (JSON)

Policy Schema

Logic Artifacts

Pdp-D Option

Operational Policy

SO Recipe

Design Time

DCAE-DS

Micro-service Blueprints

CLAMP

Control Loop (Micro-service) Orchestration

There are basically 2 ways of CL creation and micro-service orchestration in BBS Nomadic ONT scenario.

1.  Restconf collector + VES Mapper + PRH + Policy Engine
2. VES Collector + PRH + Policy Engine

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 action takers from the trigger pullers and ultimately establish robust policy driving on this platform w/o code change.