Linux Foundation Analytics

Scope

According to the O-RAN-SC-OAM-Architecture document, all ManagedElements (near-real-time-RIC, O-CU-CP, O-CU-UP, O-DU and O-RU) implement the O1-interface.

The O-RAN-OAM-interface specification defines

a NETCONF-Server for Configuration Management (CM) and
a http-client for Fault Management (FM), Performance Management (PM) and other events

on each Management-Service-Provider (MnS-Provider) running on the ManagedElement (ME).

The O-RAN-SC-OAM project provides reference implementation according to the O-RAN OAM (WG1) documents. In addition we provide a common MnS-Consumer for development and module test purposes. The assumption is that the projects for the ManagedElements can concentrate on the more important user-plane.

Of course each project needs its own OAM repo to address the specific needs of the ManagedElement.

OAM Architecture

Messenger

You can find us on Slack: https://o-ran-sc-lf.slack.com/archives/C07DA74C2PN

Linux Foundation Analytics

Scope

According to the O-RAN-SC-OAM-Architecture document, all ManagedElements (near-real-time-RIC, O-CU-CP, O-CU-UP, O-DU and O-RU) implement the O1-interface.

The O-RAN-OAM-interface specification defines

a NETCONF-Server for Configuration Management (CM) and
a http-client for Fault Managment (FM), Performance Management (PM) and other events

on each Management-Service-Provider (MnS-Provider) running on the ManagedElement (ME).

The O-RAN-SC-OAM project provides reference implementation according to the O-RAN OAM (WG1) documents. In addition we provide a common MnS-Consumer for development and module test purposes. The assumption is that the projects for the ManagedElements can concentrate on the more important user-plane.