Versions Compared

Old Version 2

changes.mady.by.user Martin Skorupski

Saved on

compared with

New Version 3

changes.mady.by.user Martin Skorupski

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Table of Contents
stylenone

Subpages

Child pages (Children Display)
allChildrentrue

Scope

This page describes the target use case for the OAM project to be demonstrated at the O-RAN Alliance face to face meeting in Montreal in the week Oct28 2024.

Objectives

This page is a working document to discussed and design the use cases and its components.

Use Case Description

Introduction

The O-RAN Alliance specifies two architectures or communications flows from O-RUs to the SMO for management traffic.

  • hierarchical
    All management traffic (OpenFronthaul Management Plane, OFHM) terminates at the O-DU. SMO OAM functions communicate with the O-RU only indirectly via the O-DU with the O-RU. Therefore the operations on O-RU data models are exposed by the O-DU using the RFC8528 YANG Schema Mount concept.

image-20240822-100834.pngImage Added

  • hybrid
    In such architecture some management traffic can by-pass the O-DU. SMO OAM functions can directly access the NETCONF Client of the O-RU. A typical use cases is software management.
    Which management traffic can by-pass the O-RU is handled by the Access Control configuration of the O-RU.

image-20240822-100914.pngImage Added

Implementation

References