...
| Gliffy Diagram | ||||||
|---|---|---|---|---|---|---|
|
Figure 1. Nomadic ONT Flow Diagram
Here are the flow by steps:
- Access SDN M&C reports the ONT registration event to DCAE/PRH
- 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
- DCAE/PRH publishes an PNF Re-registration event with that CFS id from AAI on DMAAP
- , post pnfUpdate events on DMAAP
The BBS MS consumes pnfUpdate event, carries on ONT PNF updates in A&AI and publishes a Nomadic ONT event/DCAE_CL_Event with that CFS id from AAI on DMAAP- Policy engine will call SO API upon the DCAE_CL event based on the BBS ONT moving Policy engine will call SO API upon the DCAE_CL event based on the BBS ONT Re-Registration operational policy pre-deployed to it
- SO serviceModification API initiates the service re-provisioning procedure per ONT location change.
- Upon receiving CPE Authentication event from DMAAP, BBS MS calls SO API
to update the HSIA service based on the RG/CPE attributes within the event body.
DCAE
Restconf Collector
The APIs to Access SDN M&C leverage those specified in CCVPN Closed Loop.
...
The output of Restconf Collector for the RG Activation is the above JSON message being published on DMAAP with topic of RestConf_RG_Activation.
DC=Domain Controller RCC=Restconf Collector UVA=Universal VES Adaptor SSE=SSE Connection
ORN=ONT Registration Notification R_ORN=Restconf ORN topic PNF_R=PNF Registration Event
RAN=RG Activation Notification R_RAN=Restconf RAN topic CPE_A=CPE Authentication Event
Figure 2. Logic flow of Restconf Collector vs VES Mapper_Activation.
VES Mapper
Restconf2VES Mapping
...
| Code Block | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
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 ONT/PNF definition in ONT modeling.
PNF pnfUpdate Event
PNF pnfUpdate Event
This event is the output of PRH active service detection and is consumed by BBS MS.
| Code Block | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
Nomadic ONT Event/DCAE_CL_Event
This event triggers Policy engine to call SO API to modify 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.
...
- run A&AI query A&AI enrichment logic
This generic ONAP The BBS 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.
...
This event is converted from the RG Activation notification by VES Mapper. Upon receiving this event BBS MS will look up for the associated service and mark (calling SO API?) it as activated.
| Field | Type | Required? | Description |
|---|---|---|---|
Version | number | Yes | Version of the event header (currently: 3.0): 3.0 |
eventName | string | Yes | rgActivation_vendor_pnfName where pnfName is specified by the vendor and is a PNF type; e.g. rgActivation_Huawei_xxxx |
domain | string | Yes | Event domain enumeration: ‘fault’, ‘heartbeat’, ‘measurementsForVfScaling’, ‘mobileFlow’, ‘other’, ‘sipSignaling’, ‘stateChange’, ‘syslog’, ‘thresholdCrossingAlert’, ‘voiceQuality’, ‘pnfRegistration’ |
eventId | string | Yes | Event key that is unique to the event source activate_yyyyyyyy where yyyyyyyy is an integer starting at 0 and incremented by 1 for every cpeAuthentication event sent by this ONT/RG. The key must be unique within notificaiton life cycle similar to EventID from 3GPP. It could be a sequential number, or a composite key formed from the event fields, such as domain_sequence. The eventId should not include whitespace. |
eventType | string | No | rgActivation |
sourceId | string | No | UUID identifying the entity experiencing the event issue (note: the AT&T internal enrichment process shall ensure that this field is populated) Not used |
sourceName | string | Yes | Name of the entity experiencing the event issue PNF-name (unique PNF correlation ID = pnf-name stored in AAI ; e.g. NOK6061ZW3) |
reportingEntityId | string | No | UUID identifying the entity reporting the event, for example an OAM VM (note: the AT&T internal enrichment process shall ensure that this field is populated) Not used |
reportingEntityName | string | Yes | Name of the entity reporting the event, for example, an EMS name. May be the same as the sourceName. For synthetic events generated by DCAE, it is the name of the app generating the event. PNF-name (unique PNF correlation ID = pnf-name stored in AAI ; e.g. NOK6061ZW3) |
priority | string | Yes | Processing priority enumeration: ‘High’, ‘Medium’, ‘Normal’, ‘Low’ Normal |
startEpochMicrosec | number | Yes | the earliest unix time aka epoch time associated with the event from any component--as microseconds elapsed since 1 Jan 1970 not including leap seconds current time |
lastEpochMicrosec | number | Yes | the latest unix time aka epoch time associated with the event from any component--as microseconds elapsed since 1 Jan 1970 not including leap seconds current time |
sequence | integer | Yes | Ordering of events communicated by an event source instance (or 0 if not needed) 0 |
internalHeader Fields | Internal Header Fields | No | Fields (not supplied by event sources) that the VES Event Listener service can use to enrich the event if needed for efficient internal processing. This is an empty object which is intended to be defined separately by each provider implementing the VES Event Listener. Empty. Not used |
| vesEventListenerVersion | string | Yes | Version of the VES event listener API Spec that this event is compliant with (As "#" or "#.#" or "#.#.#" where # is a digit. |
| timeZoneOffset | string | No | Offset to GMT to indicate local time zone for device formatted as 'UTC+/-hh.mm'; see https://en.wikipedia.org/wiki/List_of_time_zone_abbreviations for UTC offset examples |
stateChange FieldsVersion | number | Yes | Version of the stateChangeFields block as "#.#", where # is a digit (currently: 1.0). See the VES Event Specification for the correct digits to use. |
serialNumber | string | Yes | TS 32.692 serialNumber = serial number of the unit; e.g. 6061ZW3 |
vendorName | string | Yes | TS 32.692 vendorName = name of manufacturer; e.g. Nokia. Maps to AAI equip-vendor. |
macAddress | string | Yes | MAC address of OAM interface of the unit. |
softwareVersion | string | No | TS 32.692 swName = active SW running on the unit; e.g. 5gDUv18.05.201. |
manufactureDate | string | No | TS 32.692 dateOfManufacture = manufacture date of the unit in ISO 8601 format; 2016-04-23. |
lastServiceDate | string | No | TS 32.692 dateOfLastService = date of last service in ISO 8601 format; e.g. 2017-02-15. |
additionalFields | hashMap | No | Additional registration fields if needed, provided as key-value pairs. |
...