Hierarchical OAM functions Use Case

Owned by Alex Stancu
Last updated: Nov 01, 2024 by Martin Skorupski
1 min read

Table of Contents

Sub pages

STILL A PROPOSAL FOR "K" RELEASE, NOT YET DECIDED

Description

This Use Case aims to demonstrate hierarchical OAM functions. A simulated O-RU instance exposing the OpenFronthaul M-Plane would generate a random fault notification. That would, in turn, be received by a simulated O-DU instance which is connected to the O-RU. The O-DU would transform that into a VES stndDefined faultNotification that would be sent to the VES Collector, inside the SMO. The fault would be published on Kafka and then picked up by the ODLUX, such that the user can see in the GUI the fact that an alarm was received. The process could be repeated with a "cleared" alarm, from the O-RU, going all the way up to the SMO, the alarm disappearing from the GUI.

Functional blocks involved:

  • simulated O-RU that exposes the OpenFronthaul M-Plane interface and can generate an alarm via a NETCONF Notification
  • simulated O-DU that exposes the O1 interface, but also has a NETCONF Client that connects to the simulated O-RU. It receives the alarm and transforms in into VES stndDefined faultNotification that is pushed to the VES Collector
  • VES Collector that receives the alarm and publishes it on Kafka
  • ODLUX which picks up the alarm from Kafka and displays it

Architecture

References