...
| Code Block | ||
|---|---|---|
| ||
@startuml box "ONAP" #LightGray participant DCAE participant SO participant AAI participant SDNC participant APPC end box box " " #LightGreen participant SEBA end box box "OSAM Gateway" #LightCyan participant "NEM Adaptor Layer" as NAL participant "Core Adaptor Layer" as CAL participant "Distributed Cache" as DC end box box "OSAM Core" #LightBlue participant "GW Adaptor Layer" as AL participant "GW Locator" as GWL database "OSAM DB" as ODB end box DCAE -> SO: 1.0 Update PNF workFlow\nwith PNF_READY event SO -> AAI : 1.1 Query PNF for controller(APPC) SO -> SDNC : 1.2 Network Assignment SO -> APPC : 1.3 Configure PNF APPC -> SEBA : 1.4 Sends PNFId and necessary\nconfigurations(To be defined) SEBA -> NAL : 1.5 Registers itself to GW NAL -> CAL : 1.6 Sends PNfId, PNF IpAddress and\nGW IPAddress to OSAM CORE CAL -> AL : 1.7 Conveys event to the GW Locator NAL -> DC : 1.8 Caches the PNFId and PNF IpAddress AL -> GWL : 1.9 Triggers to store GW and PNF relations GWL -> ODB : 1.10 Stores PNF information and its\nrelation with GW loop Periodically SEBA -> NAL : 1.11 Delivers current existing OLT devices NAL -> DC : 1.12 Updates the OLTs devices which belongs to PNFId end loop APPC -> AAI : 1.13 Updates configuration data APPC -> SO : 1.14 Service configured SO -> DCAE : 1.15 Publishes service ready\nmessage @enduml |
- 1.0 DCAE reports that PNF is ready for configuration state to SO.
- 1.1 SO looks for selected Controller from AAI. APPC will be reported as a controller from AAI.(APPC has chosen according to this flow...)
- 1.2 SDNC applies required network assignments such as a relationship between OSAM GW and SEBA.
- 1.3 SO delivers required configuration parameters to APP-C.
- 1.4 Apply the required configurations to SEBA. Configuration types will be decided in the future releases.
- 1.5 Seba registers itself to OSAM Gateway with its IP address and PNF Id.
- 1.6 NEM Adapter Layer takes the given IP address and PNF Id of SEBA and conveys it to Core Adapter Layer.
- 1.7 Core Adapter Layer notifies to OSAM CORE about new incoming SEBA POD with the PNF Id and, IP address of itself.
- 1.8 Caches the PNF Id and PNF IP address.
- 1.9 GW Adapter Layer triggers to store GW and PNF relations.
- 1.10 GW Locator sends the PNF information and its relationship with GW to the OSAM DB to store.
- 1.11 SEBA delivers access device to OSAM GW.
- 1.12 Updates the OLT devices related to PNFId
- 1.13 Updates PNF entry with applied configurations in AAI
- 1.14 APPC sends a callback that reports POD is ready.
- 1.15 So publishes an event that the service is ready.
2-ONT Registration Flow
| Code Block | ||
|---|---|---|
| ||
@startuml actor Admin box "OSAM Core" #LightBlue participant "OSAM UI" as OUI participant "Portal FW" as PF participant "Service Flow\nManager" as SFM database "OSAM DB" as ODB end box Admin -> OUI : 2.0 Registers ONT's Serial\nNumber to PNF OUI -> PF : 2.1 Sends ONT's Serial Number\nwith PNFId PF -> SFM : 2.2 Conveys ONT's Serial\nNumber with PNFId SFM -> ODB : 2.3 Saves ONT's Serial Number\nand its relation to PNFId in DB note right #LightGreen: Assuming that PNF ip address \n already exists for PNFId @enduml |
...