BBS Modeling
Model Overview
BBS use case aims at using ONAP for the design, creation and activation of the High Speed Internet Access CFS.
Model Design
Gliffy Diagram is only supported by the cloud editor
Because Forge macros arent supported by the legacy editor, you'll need to convert this content to the cloud editor to display this macro properly. Find out more about converting to the cloud editorRepresentation in SDC
Resource Representations
Modeled Resource | SDC Representation | A&AI object | TOSCA file |
|---|---|---|---|
ONT NNI | Connection Point | cp | ontNni.yaml & ontNni.json (for import) |
PON UNI | Connection Point | cp | ponUni.yaml & ponUni.json (for import) |
OLT NNI | Connection Point | cp | oltNni.yaml & oltNni.json (for import) |
ODN Connection | VNF Virtual Link | N/A |
|
Access Connectivity | Virtual Function Component | generic-vnf | accessConnectivity.yaml |
Internet Profile | Virtual Function Component | generic-vnf | internetProfile.yaml |
CPE (PNF) | Virtual Function Component | pnf | cpePnf.yaml |
Composition of services
Service | Composed Of |
|---|---|
HSIA CFS (BBS E2E Service) | CPE VF* ONT-NNI CP ODN Connection Vnf Virtual Link PON-UNI CP Access Connectivity VF OLT-NNI CP
Internet Profile VF
(*) with workaround to model PNF in SDC |
Representation in A&AI
Gliffy Diagram is only supported by the cloud editor
Because Forge macros arent supported by the legacy editor, you'll need to convert this content to the cloud editor to display this macro properly. Find out more about converting to the cloud editorModel Parameter Life-cycle
Table on information model 'storage' and discovery-inventory analysis for BBS use case parameters
BBS Parameter Table
ONAP Awareness | SDNC (Access Discovery) | SDN-C (Edge Discovery) | SDC (Service Creation from Portal) | DCAE Registration PNF | SDN-C (Access Service) | DCAE CPE Auth | A&AI |
|---|---|---|---|---|---|---|---|
Service (HSIA) | |||||||
RG MAC Add |
|
| Input |
|
|
| Input |
Service Type |
|
| Input |
|
|
| Input |
Upstream Speed |
|
| Input |
|
|
| Input |
Downstream Speed |
|
| Input |
|
|
| Input |
Remote ID |
|
| Input (Optional) | Input |
| Input (used to find the CFS associated with PNF) | Input |
Orch Status |
|
|
|
| Derived - Obtained from CFS associated with PNF in PNF Registration | Derived - Obtained from CFS associated w PNF and MAC Address | Input |
HSIA Access | |||||||
CPE/ONT PNF | |||||||
PNF Name |
|
| Input (CorrelationID) | SourceName |
| SourceName | Input |
MAC Address |
|
|
| Input |
| Input | Input |
Manufacturer |
|
| Onboarded CSAR Artifact | Input |
|
| Input |
Serial Number |
|
|
| Input |
|
| Input |
Model |
|
|
| Input |
|
| Input |
Type |
|
| Onboarded CSAR Artifact | Input |
|
| Input |
SW Version |
|
|
| Input (Optional) |
| Input (Optional) | Input |
Attachment Point (new field) |
|
|
| Input |
|
| Input |
CPE Authentication State |
|
|
|
|
| Input (Used to derive the CFS orchestration status) |
|
ONT NNI (PORT) |
|
|
|
| Input from response when access connectivity is created |
| Input |
ODN Virtual Link |
|
|
|
| Input from response when access connectivity is created |
| Input |
Access Connectivity | |||||||
Service Type |
|
|
|
| Input (from CFS) |
|
|
Upstream Speed |
|
|
|
| Input (from CFS) |
|
|
Downstream Speed |
|
|
|
| Input (from CFS) |
|
|
PON UNI | |||||||
CVLAN |
|
| Input (Optional) | Input | Input when access connectivity is created or CFS if not in DCAE Reg |
| Input |
Expected ONT ID |
|
| Input (Optional) |
| Input (from CFS) |
| Input |
OLT Name | Input |
|
| Derived (Attachment Point) |
|
| Input |
OLT PON Slot | Input |
|
| Derived (Attachment Point) |
|
| Input |
OLT PON Port | Input |
|
| Derived (Attachment Point) |
|
| Input |
OLT NNI | |||||||
SVLAN | Input |
| Input (Optional) | Input | Input when access connectivity is created or CFS if not in DCAE Reg |
| Input |
OLT Name | Input |
|
|
|
|
| Input |
OLT NNI Slot | Input |
|
|
|
|
| Input |
OLT NNI Port | Input |
|
|
|
|
| Input |