The OAM project focus on the following topics:

Provide complete implementation for OAM functions (FCAPS).


  • update of O-RAN WG10 VES message bodies
  • update of O-RAN WG4 optional VES bodies
  • update of OAM-Controller to OpenDaylight version Potassium-SR1
  • support of other O-RAN-SC projects (e.g. SMO, Non-RT-Ric, O-DU, INT) based on RSAC and other input.
  • support of OAI and nephio integration with O-RAN-SC related to OAM


The following Specifications needs to be considered for software updates:

  • O-RAN Architecture Description 10.0 - October 2023
  • O-RAN Use Cases Detailed Specification 12.0 - October 2023
  • O-RAN Operations and Maintenance Architecture 10.0 - October 2023
  • O-RAN Operations and Maintenance Interface Specification 11.0 - October 2023
  • O-RAN Topology Exposure and Inventory Management Services Use Cases and Requirement Specification 1.0- June 2023
  • O-RAN Information Model and Data Models Specification - Yang Models 6.0 - October 2023
    O-RAN.WG10.Information Model and Data Models.1-R003-v06.00
  • O-RAN Management Plane Specification 13.0 - October 2023
  • O-RAN Management Plane Specification - YANG Models 13.0 - October 2023
  • O-RAN Conformance Test Specification 9.0 - October 2023
    O-RAN.WG4.CONF.0-R003-v08.00 (just management-plane)
  • O-RAN O1 Interface specification for O-DU 8.0 - October 2023

  • O-RAN O1 Interface specification for O-CU-UP and O-CU-CP 6.0 - October 2023
  • O-RAN O1 Interface specification for O-DU - YANG Models 8.0 - October 2023

  • O-RAN O1 Interface specification for O-DU - Configuration Tables 8.0 - October 2023

  • O-RAN O1 Interface for O-CU-UP and O-CU-CP - YANG Models 4.0 - October 2022

  • O-RAN Management interfaces for Transport Network Elements 7.0 - October 2023

VES JSON-Schemas

  • ONAP VES 7,2.1
  • 3GPP TS 28.532 V17.1.1
    (according to O-RAN Operations and Maintenance Interface Specification 10.0 and its 'Harmonized VES format')  
    • Annex B (Informative):
      Guidelines for the integration of 3GPP MnS notifications with ONAP VES
    • Configuration Management Notifications
      • notifyMOIAttributeValueChanges
      • notifyMOICreation
      • notifyMOIDeletion
      • notifyMOIChanges
    • Fault Management Notifications
      • notifyNewAlarm
      • notifyChangedAlarmGeneral and/or
      • notifyChangedAlarm
      • notifyCorrelatedNotificationChanged

      • notifyAckStateChanged

      • notifyClearedAlarm
      • notifyAlarmListRebuilt
    • FileReady Notification (as part of Performance Monitoring)
      • notifyFileReady
    • PM Streaming
      • based on WebSockets and ASN.1 (no contributions expected)
    • Software Management
      • 3GPP-specified notifyFileDownload vs O-RAN-specified o1NotifyFileDownload
    • Heartbeat
      • notifyHeartbeat
  • O-RAN Operations and Maintenance Interface Specification 10.0 June 2023
    • PNF Registration
      • o1NotifyPNFRegistration
        Idea: WordTable → YANG → OpenAPISpecification
    •  CNF Registration
      • o1NotifyCloudNFRegistration
        (reference to: 'O-RAN Information Model and Data Models Specification' which does not include o1NotifyCloudNFRegistration yet)
  • O-RAN Management Plane Specification 12.0 June 2023
  • O-RAN-SC PM-Measurement streaming


Source of Data model O-RAN-SC

Fault3GPP: _3gpp-common-fm
(Fallback from Bronze RFC8632: ietf-alarms)
Configuration(see next lines)
  • interfaces and/or termination points

O-RAN-FH: RFC8343: ietf-interfaces

  • synchronization

(see next lines)

-- Network Time Protocol

RFC7317: ietf-system,yang

-- Precision Time Protocol

RFC8575: ietf-ptp,yang
(check if new IEEE standard was adopted)
  • DCN
    • OAM IF

  • Ehternet OAM
  • Loopback config 
  • Link supervision
  • others
to be updated based on SDO progress
Accountingnot scope of O-RAN and O-RAN-SC - listed just for completeness of FCAPS
Performance3GPP-xml, file, VES


(see next lines)
  • Protocol TLS (for Rest, RestConf and NetConf)
RFC8446: Transport Layer Security
  • User Management

RFC7317: ietf-system,yang

Open: o-ran-user-management

Inventory (hardware)

RFC8348: ietf-hardware,yang and iana-hardware.yang
and of cause o-ran-hardware@2019-07-03.yang for the O-RAN identities.

Open: only for O-RU and O-DU; O-DU anyhow optional

Software Management

Management interfaces:

Use case:

Start with and xRan-fronthaul radio unit and perform and upgrade to an o-ru with the OpenFronthaul M-plane and upgrade further to an O-RU with an O-RAN/3GPP common O1 management interface.

Backup and restoreOpenROADM manifest file
xApp onboarding (from O1 point of view)under development by WG2 and Near-RT-RIC project
Subscription for VES

Reference to docker images 

SMO Area

Short name



commonidentitydb bitnami/postgresql13   1.1.18
appsflows  nodered/node-redv3.0.2 4.0.6
  • No labels

1 Comment

  1. Hi Martin Skorupski ,

    Can you please tell ,which O-RAN spec's does J release OAM support, I see all above listed specs are the marked as future scope.