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

Compare with Current View Page History

« Previous Version 6 Next »

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 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

  • No labels