Skip to end of metadata
Go to start of metadata

This page contains step by step tutorials to get you started with installing and running the Bronze Release features.


SMO Installation

The goal of this tutorial is to install and run the Service Management Orchestrator

Near Realtime RIC Installation 

The goal of this tutorial is to install and run the Near Realtime RIC 

Hello World xApp Use Case Flows

This is a step by step tutorial to on-board, deploy and run a Hello World xApp in a Near Realtime RAN Intelligent Controller (RIC) instance.

How to onboard, deploy and run a Hello World xApp on RIC Video (18 minutes)

Running A1 and O1 Use Case Flows

The goal of this tutorial is to run the A1 and O1 interfaces 

Figure 1: Demo deployment architecture

Bronze Demonstrations

Deployment

Minimum deployment for running Bronze use case demos.

SMO Cluster:

  • ONAP "Lite" (Minimalistic for running SDNC/SDNR for RSAC Bronze O1)
    • Minimum replicas
    • VES collector is deployed standalone in ricaux namespace (w/o rest of DCAE, using a helm chart derived from the ONAP VES Cloudify Blueprint)
  • Non RT RIC

Near RT RIC Cluster:

  • Near RT RIC Platform
  • Near RT RIC Applications

Videos

Figure 2: O-RAN architecture overview

In the O-RAN architecture, the radio side includes Near-RT RIC, O-CU-CP, O-CU-UP, O-DU, and O-RU. The management side includes Service Management and Orchestration Framework that contains a Non-RT-RIC function.

O-RAN Alliance Components Definition

For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].

near-RT RIC: O-RAN near-real-time RAN Intelligent Controller: a logical function that enables near-real-time control and optimization of O-RAN elements and resources via fine-grained data collection and actions over E2 interface.

non-RT RIC: O-RAN non-real-time RAN Intelligent Controller: a logical function that enables non-real-time control and optimization of RAN elements and resources, AI/ML workflow including model training and updates, and policy-based guidance of applications/features in near-RT RIC.

NMS: A Network Management System

O-CU: O-RAN Central Unit: a logical node hosting RRC, SDAP and PDCP protocols

O-CU-CP: O-RAN Central Unit – Control Plane: a logical node hosting the RRC and the control plane part of the PDCP protocol

O-CU-UP: O-RAN Central Unit – User Plane: a logical node hosting the user plane part of the PDCP protocol and the SDAP protocol

O-DU: O-RAN Distributed Unit: a logical node hosting RLC/MAC/High-PHY layers based on a lower layer functional split.

O-RU: O-RAN Radio Unit: a logical node hosting Low-PHY layer and RF processing based on a lower layer functional split. This is similar to 3GPP’s “TRP” or “RRH” but more specific in including the Low-PHY layer (FFT/iFFT, PRACH extraction).

O1: Interface between management entities in Service Management and Orchestration Framework and O-RAN managed elements, for operation and management, by which FCAPS management, Software management, File management shall be achieved.

O1*: Interface between Service Management and Orchestration Framework and Infrastructure Management Framework supporting O-RAN virtual network functions.

xAPP: Independent software plug-in to the Near-RT RIC platform to provide functional extensibility to the RAN by third parties.

  • No labels

7 Comments

  1. Hello, Is there O-DU LOW guidance?

    1. Because O-DU LOW code needs a special building environment which did not get completed in Bronze time frame, there is no additional info, other than the scripts and dockerfile in the o-du/phy repo, available at this point.  

  2. Anonymous

    Hi all,

    Could someone please provide the detail instructions on how to build and execute O-DU High and make it interact with RIC?

    1. You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.
  3. There are two places you can find such info:

    1.  o-du/l2 repo, docs directory, README file;

    2. it/dep repo, demos/bronze directory, odu-high.sh demo script.


    Lusheng

  4. Anonymous

    Hi All,


    I am trying to build the sample application for ODU L1 Low. In the build steps I could see this step "export XRAN_DIR=`pwd`/flexran_xran", but I couldnt find any such folder from the git repo. Could you please let me know if I am using the correct repo (https://github.com/o-ran-sc/o-du-phy.git)


    I am getting the following error when building fhi_lib. Could you please help me with this.

    [root@localhost fhi_lib]# sh build.sh
    Number of commandline arguments: 0
    MLOG folder is set. Enable MLOG (MLOG_DIR=/root/flexran_l1_sw/libs/mlog)
    Building xRAN Library
    LIBXRANSO = 0
    MLOG = 1
    ============================================================================================
    Building ./build/libxran.so
    RTE_TARGET = x86_64-native-linuxapp-icc
    ============================================================================================
    [BUILD] lib : libxran
    [DEP] libxran.dep
    In file included from /root/o-du-phy/fhi_lib//lib/ethernet/ethdi.c(67):
    /root/o-du-phy/fhi_lib//lib/api/xran_mlog_lnx.h(28): catastrophic error: cannot open source file "mlog_lnx.h"
    #include <mlog_lnx.h>
    ^

    make: *** [__dep__/root/o-du-phy/fhi_lib//lib/ethernet/ethdi.c] Error 4
    "make $COMMAND_LINE MLOG=${MLOG} LIBXRANSO=${LIBXRANSO}" command exited with code 2.


    Thanks and Regards,

    Abhilash


  5. Anonymous

    Hi all,

    Is there anyway to simulate packet flow in O-DU HIGH? There seems to be only some initialization requests and establishment of protocols when the application is run.

    Also is it possible to integrate the CU from OAI with O-DU from ORAN? Since the CU already exists in OAI with the F1 interface.

    Thanks and Regards,

    Wen Kai