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

Compare with Current View Page History

Version 1 Next »

O-RAN Alliance OpenFronthaul specifications define for O-RU and O-DU management plane traffic the usage of NetConf Notifcations.

The message flow in ONAP defines for notifications the VES messages format send to DMaaP VES collector to be forwared to DMaaP Message Router.


ONAP NetConf CM notification Network SDN-R: CCSDK - ODL SDN-R: SDNC - wireless technologies DMaaP µService Device Device TR069 Adapter TR069 Adapter NetConf Client NetConf ClientMDSAL(config) MDSAL(config) MDSAL(state) MDSAL(state) genericDeviceManager genericDeviceManager MountpointStateProvider MountpointStateProvider specificDeviceManager specificDeviceManager NotificationProvider NotificationProvider Message Router(data < 1MB) Message Router(data < 1MB) NotificationConsumer NotificationConsumer Start the engines loop[pull for messages for topic'CM_NOTIFY' and 'MOUNTPOINT_STATE'] [01]check for message [02]response [03]subscription [04]subscription [05]OnBoarding [06]NETCONFestablish session<hello> [07]Connected! NetConf Connection State [08](JAVA) onStateChangeincluding yang-capabilities [09](JAVA) mountpointStateupdates(connected) [10]MountpointState updates [11]check for message [12]response with MountpointState NetConf Subscription [13]Instanciation [14]IF device supports'create-subscription' [15]NETCONF<create-subscription> [16]NETCONF<create-subscription> Configuration Change Notification [17]SOAPHTTP POST [18]NETCONF:<notification> [19]notification [20](JAVA) notification [21]translation [22]VES cmNotify [23]check for message [24]response with cmNotifyLicenseApache 2.0Thanks to plantUml!2020-05-08 | onap.org | o-ran-sc.org

  • No labels