This use case shows an implementation example of asynchronous fault notifications between O-RAN components and ONAP as SMO using the VES message format.

ONAP/O-RAN Fault management (VES) Network Service Management and Orchestration (SMO) (e.g. ONAP) NTSim NTSim VES Collector VES Collector DMaaP DMaaP SDN-R SDN-R [01]REST: VES:fault [02]REST: Publish eventunauthenticated.SEC_FAULT_OUTPUT [03]REST: Get topicunauthenticated.SEC_FAULT_OUTPUT [04]REST: fault [05]REST to "DeviceManager"LicenseApache 2.0Thanks to plantUml!2019-11-21 | onap.org | o-ran-sc.org

This use case shows an implementation example of asynchronous fault notifications between network function and ONAP as SMO using NetConf notifications.

ONAP/O-RAN Fault management (NetConf) Network SMO-O1-Controller(e.g. ONAP CCSDK/SDNC/SDN-R) SMO O1-EventCollector(e.g. ONAP VES Collector) SMO MessageBus(e.g. ONAP DMaaP) xNF xNF NetConf Client NetConf Client O1-xNF-Adapter(e.g. DeviceManager) O1-xNF-Adapter(e.g. DeviceManager) VES Provider VES Provider VES Collector VES Collector Message Router Message Router [01]notification for faults/alarms/problemsNetConf/YANG [02]ODL-MDSAL [03]ODL-MDSAL [04]convertion/model-translation(xml->ves) [05]REST: Send topicunauthenticated.SEC_FAULT_OUTPUT [06]REST: Publish eventunauthenticated.SEC_FAULT_OUTPUTLicenseApache 2.0Thanks to plantUml!2020-06-17 | onap.org | o-ran-sc.org

  • No labels