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

Compare with Current View Page History

« Previous Version 9 Next »

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

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

SDN-R should close the gap for NetConf notifications and should make NetConf notification content available in a generic way for all ONAP µServices. Such function was already discussed based on  SDNC-887 - Getting issue details... STATUS . The VES domain "notification" could be used for Configuration Change Notification. However, once 3GPP has agreed on VES 'cmNofity' the now domain should be used.

Related components: Devicemanager cluster bundles

On SDN-R level the NetConf CM Notification Handling mechanism should be combinded with all kind for notfication from SDN-R to other ONAP components. Therefore all the functionality of the VES collector should be used instead of sending directly messaged to DMaaP.

The name of the component is "VES Provider".

Such notifications are:

Related Jiras

SDNC-1187 - Getting issue details... STATUS

SDNC-1188 - Getting issue details... STATUS

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! [08](JAVA)onStateChangeincluding yang-capabilities NetConf Subscription [09]Instanciation [10]IF device supports'create-subscription' [11]NETCONF<create-subscription> [12]NETCONF<create-subscription> NetConf Connection State [13](JAVA)mountpointStateupdates(connected) [14]MountpointState updates loop[pull for messages fortopic'MOUNTPOINT_STATE'] [15]check for message [16]responsewithMountpointState Configuration Change Notification [17]SOAPHTTP POST [18]NETCONF:<notification> [19]notification [20](JAVA) notification [21]translation [22]VES cmNotify loop[pull for messages for topic'CM_NOTIFY'] [23]check for message [24]response with cmNotifyLicenseApache 2.0Thanks to plantUml!2020-05-08 | onap.org | o-ran-sc.org

  • No labels