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

Compare with Current View Page History

Version 1 Next »

Objective

Typically network-functions supporting NetConf Callhome do not support at the same time the VES event 'pnfRegistration'. In order inform the µServices within the SMO, a functionality as OAM-Controller level should be implemented. This function should send a VES pnfRegistration event to the VES-Collector when a new mount-point is created which is listed in the allowed devices.


Sequence Diagram

NetConf/Callhome to VES-PNF-RegistrationOpenDaylight Aluminium SSH only User space SMO O-RU Operator Operator Message-Router Message-Router VES-Collector VES-Collector OAM-Controller OAM-Controller NetConf-Server-OFH NetConf-Server-OFH init [01]SET NetConfServer params for CallhomeOAM-Controller listen on port 6666 [02]GET publicKey [03]SET allowed devices with publicKey loop[Listen to pnfRegistration] [04]VES subscription use case [05]NETCONF Callhome SSH [06]NETCONF <hello/>Exchange capabilitiesincluding YANG modules for OpenFronthaul [07]create mount pointin network-topology=topology-netconf [08]VES:domain=notificationNetConf connection statuschanged to "connected" [09]publish event if mount-point:node-id is in "alloved devices" [10]VES:domain=pnfRegistrationwith 'reporter=OAM-Controller-id' [11]publish event [12]fetch pnfRegistration if 'reporter=OAM-Controller-id' [13]ignore!!! if <create-subscription/> supported [14]NETCONF Notification SubscriptionThanks to PlantUml!License: Apache 2.02021-02-06 | o-ran-sc.org



  • No labels