Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Table of Contents

Subpages

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.png

  • 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.png

Implementation

References

  • No labels