You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Scope

This page discusses the OAM parts of the D-Release RASC use case for a closed loop use case.

Please see follow up also the related expectations, recommendations and descriptions by RASC:

https://wiki.o-ran-sc.org/download/attachments/3604609/OSC-2020.06.08%20OSC-D-Cherry-v1.pptx?api=v2


Component diagram 

The following component diagram is made from OAM point of view. O-RAN component internals are abstracted and simplified. 


Component diagram for O-RU recovery use case (OAM view) SMO µService Communication Bus OAM O-RAN Topology Service OAM topology O-DU O-RU Connection-Trigger Message-Router OAM-Controller VES-Collector EP_O1_NetConf* EP_O1_VES* EP_OFH* NetConf-Server-O1 NetConf-Client-OFH VES-Provider NetConf-Server-OFH Thanks to PlantUml!License: Apache 2.02021-01-18 | o-ran-sc.org

Sequence diagram


Sequence diagram for O-RU recovery use case (OAM view) User space SMO O-DU O-RU µServiceConnection-Trigger µServiceConnection-Trigger Topology Service Topology Service Message-Router Message-Router OAM-Controller OAM-Controller VES-Collector VES-Collector NetConf-Server-O1 NetConf-Server-O1 NetConf-Client-OFH NetConf-Client-OFH NetConf-Server-OFH NetConf-Server-OFH Init [01]NETCONF Callhome [02]NETCONF Callhome [03]NETCONF Notification Subscription [04]GET OpenFronthaul Topology [05]RESPONSE OpenFronthaul Topology [06]UPDATE OpenFronthaul Topology use case [07]SEND ALARM - connection loss [08]Convert NetConf Notification to VES [09]Fetch for VES fault events [10]GET O-DU of related O-RU [11]SEND re-connection trigger [12]SEND re-connection trigger [13]convert and forward [14]re-establish connectionThanks to PlantUml!License: Apache 2.02021-01-18 | o-ran-sc.org



  • No labels