Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Table of Contents
Table of Contents | ||
---|---|---|
|
Subpages
Child pages (Children Display) | ||
---|---|---|
|
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.
| |
|
Implementation
The generated topology for about 7000 NRCellDus is too big to discuss the details of hierarchical and hybrid OAM Architectures.
We just need two O-RUs - let’s assume each O-RU implements just one NRCellDU and that the related O-DU in an edge cloud at the next tower.
The following figure shows 2 cells at one tower. At a second tower the O-DU-Edge-Cloud is located. Both towers are visualized as a dot. The cells are visualized by as polygon show the coverage. The overlap between both cells are for handover.
Image AddedIn this simple topology we have two towers with just 3 RAN nodes
1x O-DU at the top of the image
2x O-RUs at the bottom of the image.
We assume that the O-Cloud resource pools for O-CU, Near-RT-Ric, 5G-Core and SMO are also located close to the northern tower.
The topology described according ietf-network-topology as json encoding (RFC7951) looks like this:
References
https://lf-o-ran-sc.atlassian.net/wiki/download/attachments/29491658/2024-10-ofh-m-plane.pptx?api=v2
O-RAN Architecture Description 12.0 O-RAN.WG1.OAD-R003-v12.00 June 2024
O-RAN Operations and Maintenance Architecture 12.0 O-RAN.WG10.OAM-Architecture-R003-v12.00 June 2024
O-RAN Management Plane Specification - YANG Models 15.0 O-RAN.WG4.MP-YANGs-R003-v15.00 June 2024