...
PRH needs to send additional information (additionalFields) coming in the PNF registration event that is BBS use case specific in the PNF_READY event (attachmentPoint, accessID, CVLAN, SVLAN).
PNF_Ready is published after AAI is updated with PNF relevant information.
It is initially agreed, that PRH will copy in 1:1 fashion the contents of VES.pnfRegistration.additionalFields structure/array/Map into the PNF_READY event, along with the correlationID parameter sent there already in ONAP/Casbalanca Casablanca release.
This allows other applications in the flow (BBS uS, SO,...) to react based on domain specific information sent in the pnfRegistration.additionalFields in addition to the standard PNF related attributes.
Service-instance-related information
...
| BBS Properties Per HSIA CFS Service Instance | Input Source | ONAP Components that must fetch the value from A&AI | Does it really need A&AI storage? | A&AI Metaname (for Metadata) |
|---|---|---|---|---|
| RG MAC Address | Service Order via Ext API It also comes in the CPE Authentication Event | bbs-event-processor DCAE microservice (it fetches existing value from A&AI to compare it with the new value coming from PNF CPE authentication event in order to deduce if there is any mismatch) | Yes, as metadata of CFS service instance | rgw-mac-address |
| Service Type | Service Order via Ext API | |||
| Access ID | PNF registration event | |||
| Upstream Speed | Service Order via Ext API | |||
| Downstream Speed | Service Order via Ext API | |||
OLT Name | PNF registration event (extracted from attachment point) | |||
| OLT PON port | PNF registration event (extracted from attachment point) | |||
| OLT PON slot | PNF registration event (extracted from attachment point) | |||
CVLAN | PNF registration event | |||
| SVLAN | PNF registration event | |||
| Expected ONT ID | ||||
| CPE Manufacturer | Onboarded to SDC for PNF | Yes, as property of PNF object | Not Applicable | |
| CPE Model | Onboarded to SDC for PNF | Yes, as property of PNF object | Not Applicable | |
| CPE Equipment Type | Onboarded to SDC for PNF | Yes, as property of PNF object | Not Applicable | |
| CPE Serial Number | Yes, as property of PNF object | Not Applicable | ||
| CPE SW Version | It comes in the CPE Authentication Event | Yes, as property of PNF object | Not Applicable | |
Attachment Point (Not a real BBS modeling property, since its constituent parts are captured in other model properties) | PNF registration event | bbs-event-processor DCAE microservice (it fetches existing value from A&AI to compare it with the new value coming from PNF re-registration event in order to deduce if it is a true relocation) | Yes, as value of link-name property of a logical-link bridged to the PNF object | Not Applicable |
ONT NNI Port | ||||
OLT NNI Slot | ||||
OLT NNI Port |
...