M-Release

M-Release

The OAM project focus on the following topics:

Provide complete implementation for OAM functions (FCAPS).

Target

 

  • provide abstract docker services which centralized TLS termination (traefik) and centralized Authentication and Authorization (keycloak)

  • alignment with findings and suggestions of IOS-MCN project

    • PM-file-transfer from O-DU/O-CU-UP/O-CU-CP/NearRtRic to SMO-OAM

  • update of O-RAN WG10 VES message bodies

  • update of O-RAN WG4 optional VES bodies

  • update of OAM-Controller to OpenDaylight version Scandium-SR2 (https://docs.opendaylight.org/en/stable-scandium/release-notes/release-notes-scandium-sr2.html)

  • update of VES-Collector version to image: nexus3.onap.org:10001/onap/org.onap.dcaegen2.collectors.ves.vescollector:1.12.5

  • support of other O-RAN-SC projects (e.g. SMO, Non-RT-RIC, O-DU, INT, SIM) based on RSAC and other input.

  • support of OAI and nephio integration with O-RAN-SC related to OAM in collaboration with O-RAN OSFG.

Specifications

The specifications are available at O-RAN Alliance:

https://specifications.o-ran.org/specifications

The main specification by the O-RAN Alliance are the once from WG10 and WG4. Please see also all yang specifications.

The O-RAN Alliance does now reference 3GPP Specification R18. The implementations by OAM project are referening to https://forge.3gpp.org/rep/sa5/MnS/-/tree/Tag_Rel18_SA107?ref_type=tags

VES JSON-Schemas

  • ONAP VES 7,2.1

  • 3GPP TS 28.532 V18
    (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 15.0 June 2024

  • O-RAN-SC PM-Measurement streaming

 

 

Function

Source of Data model O-RAN-SC

Fault

3GPP: _3gpp-common-fm
(Fallback from Bronze RFC8632: ietf-alarms)

Configuration

(see next lines)

  • interfaces and/or termination points

O-RAN-FH: RFC8343: ietf-interfaces
3GPP: 

  • 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

Accounting

not scope of O-RAN and O-RAN-SC - listed just for completeness of FCAPS

Performance

3GPP-xml, file, VES

Security

(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 restore

OpenROADM manifest file

xApp onboarding (from O1 point of view)

under development by WG2 and Near-RT-RIC project

Subscription for VES

_3gpp-common-subscription-control

Open: RFC8639: ietf-subscribed-notifications augmented by opnfv-ves-push.yang

 

Reference to docker images 

SMO Area

Short name

Image

Version

oam

oam-controller

nexus3.o-ran-sc.org:10001/o-ran-sc/oam-oam-controller/sdnr-image

13.0.1

oam

odlux

nexus3.o-ran-sc.org:10001/o-ran-sc/oam-oam-controller/sdnr-web-image

13.0.1

oam

ves-collector

nexus3.onap.org:10001/onap/org.onap.dcaegen2.collectors.ves.vescollector

1.12.5

common

gateway

traefik

v3.3.6

common

identity

bitnamilegacy/keycloak

26.1.2

common

identitydb

bitnamilegacy/postgresql

13

common

persistence

mariadb

11.1.2

common

topology

nexus3.o-ran-sc.org:10002/o-ran-sc/smo-nts-ng-topology-server

1.5.2

common

kafka-bridge

quay.io/strimzi/kafka-bridge

0.25.0

common

kafka

quay.io/strimzi/kafka

0.35.0-kafka-3.4.0

common

kafka-ui

http://ghcr.io/kafbat/kafka-ui:b71a753

 

common

zookeeper

 quay.io/strimzi/kafka

0.35.0-kafka-3.4.0

apps

flows

  nodered/node-red

v3.0.2

apps

wireshark

lscr.io/linuxserver/wireshark 

4.0.6

apps

jenkins

jenkins/jenkins

2.401.2-lts-jdk11