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

Compare with Current View Page History

« Previous Version 6 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). 

CM with VES 


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 O1-xNF-Adapter(e.g. DeviceManager) O1-xNF-Adapter(e.g. DeviceManager)Log or CSP Log or CSP VES Provider VES Provider VES Listener VES Listener RestConf Server RestConf Server VES Collector VES Collector Message Router Message RouterSMO µService, rAppor OLDUX in browser SMO µService, rAppor OLDUX in browser Start the engines [01]NETCONFestablish session<hello> [02]Connected! (including yang-capabilities [03]IF device supports'VES-subscription' [04]NETCONF<VES-subscription> [05]NETCONF<create-subscription> Trigger a valid configuration [06]REST PUT or POST request for xNF [07]ODL-MDSAL [08]<edit-config> [09]<rpc-reply> [10]ODL-MDSAL [11]HTTP RESPONSE Related notification flow [12]send VES messaged CM-Notify [13]REST: Publish eventunauthenticated.VES_CM_NOTIFY_OUTPUT [14]fetch VES event [15]forward event [16]store eventLicenseApache 2.0Thanks to plantUml!2020-06-17 | onap.org | o-ran-sc.org

CM with NetConf notification

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 O1-xNF-Adapter(e.g. DeviceManager) O1-xNF-Adapter(e.g. DeviceManager)Log or CSP Log or CSP VES Provider VES Provider RestConf Server RestConf Server VES Collector VES Collector Message Router Message RouterSMO µService, rAppor OLDUX in browser SMO µService, rAppor OLDUX in browser Start the engines [01]NETCONFestablish session<hello> [02]Connected! (including yang-capabilities [03]IF device supports'create-subscription' [04]NETCONF<create-subscription> [05]NETCONF<create-subscription> Trigger a valid configuration [06]REST PUT or POST request for xNF [07]ODL-MDSAL [08]<edit-config> [09]<rpc-reply> [10]ODL-MDSAL [11]HTTP RESPONSE Related notification flow [12]CM-notificationNetConf/YANG [13]ODL-MDSAL [14]ODL-MDSAL [15]store event [16]convertion/model-translation(xml->ves) [17]REST: send VES Messageunauthenticated.SEC_NOTIFICATION_OUTPUT [18]REST: Publish eventunauthenticated.VES_NOTIFICATION_OUTPUTLicenseApache 2.0Thanks to plantUml!2020-06-17 | onap.org | o-ran-sc.org

  • No labels