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

Compare with Current View Page History

« Previous Version 2 Next »

The user triggers a configuration, which will be forwarded to the O-RAN components. The flow is successfully passed when the corresponding VES message is available on DMaaP and can be processed by any other ONAP components.

Note: The VES notification syntax for a new ves-domain "cmNotify" is currently not available (state: 2019-11-21). 

ONAP/O-RAN Configuration management 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) User space xNF xNF NetConf Client NetConf Client RestConf Server RestConf Server O1-xNF-Adapter(e.g. DeviceManager) O1-xNF-Adapter(e.g. DeviceManager)Log or CSP Log or CSP VES Provider VES Provider VES Collector VES Collector Message Router Message RouterSMO µService, rApp\or OLDUX in browser SMO µService, rApp\or OLDUX in browser [01]REST PUT or POST request for xNF [02]ODL-MDSAL [03]<edit-config> [04]<rpc-reply> [05]ODL-MDSAL [06]HTTP RESPONSE [07]CM-notificationNetConf/YANG [08]ODL-MDSAL [09]ODL-MDSAL [10]store event [11]convertion/model-translation(xml->ves) [12]REST: Send topicunauthenticated.SEC_NOTIFICATION_OUTPUT [13]REST: Publish eventunauthenticated.SEC_NOTIFICATION_OUTPUTLicenseApache 2.0Thanks to plantUml!2020-06-17 | onap.org | o-ran-sc.org

  • No labels