Versions Compared

Old Version 17

changes.mady.by.user Cem Turker

Saved on

compared with

New Version Current

changes.mady.by.user Cem Turker

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Code Block
collapsetrue
@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.12 Network Assignment
SO -> APPC : 1.23 Configure PNF
APPC -> SEBA : 1.34 Sends PNFId and necessary\nconfigurations(To be defined)
SEBA -> NAL : 1.45 Registers itself to GW
NAL -> CAL : 1.56 Sends PNfId, PNF IpAddress and\nGW IPAddress to OSAM CORE
CAL -> AL : 1.67 Conveys event to the GW Locator
NAL -> DC : 1.78 Caches the PNFId and PNF IpAddress
AL -> GWL : 1.89 Triggers to store GW and PNF relations
GWL -> ODB : 1.910 Stores PNF information and its\nrelation with GW
loop Periodically
SEBA -> NAL : 1.1011 Delivers current existing OLT devices
NAL -> DC : 1.1112 Updates the OLTs devices which belongs to PNFId
end loop
APPC @enduml-> 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.4 5 Seba registers itself to OSAM Gateway with its IP address and PNF Id.
  • 1.5 6 NEM Adapter Layer takes the given IP address and PNF Id of SEBA and conveys it to Core Adapter Layer.
  • 1.6 7 Core Adapter Layer notifies to OSAM CORE about new incoming SEBA POD with the PNF Id and, IP address of itself.
  • 1.7 8 Caches the PNF Id and  PNF IP address.
  • 1.8 9 GW Adapter Layer triggers to store GW and PNF relations.
  • 1.9 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
collapsetrue
@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

...

Code Block
collapsetrue
@startuml

box " " #LightGreen
participant SEBA as SEBA
End box


box  "OSAM GATEWAY" #LightCyan
participant "NEM Adaptor Layer" as NAL
participant "VES AGENT" as VES
end box


box "ONAP" #LightGray
    participant VES_COLLECTOR as Cltr
    participant DMAAP as Dmp

    note over of Dmp #LightGreen: contains kafka

    participant TCA

    note over of Cltr
        collects the
        data and filter
        data for operator
        systems concerns
    end note

End box

box "OPERATOROSAM ENVIRONMENTCore"
    participant "OPERATORService Flow SYSTEMManager" as sysSFM
End     database "OSAM DB" as ODB
    participant "Portal FW" as PF
    participant "OSAM UI" as OUI
End box


==configurationConfiguration==
    note over of Cltr
         configure ves if any
         additional event add
    end note

==eventEvent handling==
loop peridically
   NAL <-- SEBA : 7.0 Send systemalert and datastats
   VES <-- NAL : 7.1 Send systemalert and datastats
   VES --> Cltr : 7.2 Send collected data
   note right #LightGreen: measurement \nevents\n,alarms , faults..
   Cltr --> Dmp : 7.3 Dataconvey eventdata
   Dmp -> Dmp : 7.4 Filter eventthe events endaccording 
@enduml

...

to OSAM topic
   Dmp -> TCA : 7.5 Send event data to store
end

==Collect Events==
loop predically
   SFM -> TCA : 7.6 Collects event data
   TCA -> SFM : 7.7 Returns the events
   SFM -> ODB : 7.8 Updates the event stores
   SFM -> PF : 7.9 Notify the UI about events
   PF -> OUI : 7.10 Pop up alert or information
end
@enduml
  • 7.0   SEBA sends the measurement information and alarm which generated in the real-time to the NEM Adapter Layer.
  • 7.1   Nem Adapter Layer conveys the virtual event streams, collected from SEBA to VES Agent.
  • 7.2   VES Agent collects and sends data to the VES Collector to deliver data to ONAP system
  • 7.3   VES Collector verifies the format of the data and sends it to the DMaaP.   
  • 7.4   DMaaP filters the necessary data and stores it on the Kafka.
  • 7.5   TCA collects data which are interested according to data's topic to analyze, store and create the crossing alarms according to thresholds.
  • 7.6   Service Flow Manager collects the event data from TCA
  • 7.7   TCA returns the requested event data.
  • 7.8   Service Flow Manage updates the store if needed
  • 7.9   Service Flow Manage conveys the events to Portal FW.
  • 7.10 Portal FW pushes the events to OSAM UI.

8-Fetch Technology Profile

Image Added

Code Block
collapsetrue
@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
participant "GW Locator" as GWL
participant "GW Adaptor Layer" as AL
end box


box  "OSAM Gateways" #LightCyan
participant "Core Adaptor Layer" as CAL
participant "Distributed Cache" as DC
participant "NEM Adaptor Layer" as NAL
end box


box " " #LightGreen
participant SEBA
end box

Admin -> OUI : 8.0 Selects a Access POD
OUI -> PF : 8.1 Asks for technology profiles\nof POD
PF -> SFM : 8.2 Delivers request to SFM
note right  #LightGreen: We should add caching for\ntech profile. Assume that requested\nTech profile is not in cache for PNFId
SFM -> AL : 8.4 Conveys request to Adaptor Layer
AL -> GWL : 8.5 Ask for PNF GW's ip
GWL -> ODB : 8.6 Query for PNF GW's ip
ODB -> GWL : 8.7 Returns the ip
GWL -> AL : 8.8 Conveys the PNF GW's ip
AL -> CAL : 8.9 Sends request to query technology\nprofile with PNFId
CAL -> NAL : 8.10 Conveys new the technology profile\nconfigurations and PNFIds
NAL -> DC : 8.11 Query for PNF Ip Address which associated with PNFId
NAL <- DC : 8.12 Sends PNF Ip Address which associated with PNFId
NAL -> SEBA : 8.13 Asks for technology profiles\nof POD
SEBA -> NAL : 8.14 Receives the technology profiles.
NAL -> CAL : 8.15 Conveys the technology profiles.
CAL -> AL : 8.16 Conveys the technology profiles.
AL -> SFM : 8.17 Conveys the technology profiles.
SFM -> PF : 8.18 Writes its cache and\nconveys the technology profiles.
PF -> OUI : 8.19 Returns the technology profiles\nof the POD
@enduml