/
O-DU High Tests with Stubs

O-DU High Tests with Stubs

Owned by Former user (Deleted)

Delivery Status

DO NOT EDIT

Only the Integration PTL should edit the delivery status table to track the release validation progress



OTFOAMNONRTRICRICPRICAPPO-DUO-CUTest ResultNotes
Deployment Artifacts

Docker Container







O-DU-RIC-STUB is not available in OSC Nexus
Helm Charts








Deployment scripts








E2E Flows

E2 UE Attach Procedure









The CU stub and RIC stub is also used in the O-DU-high and O-DU-low integrated flow

This page describes running O-DU High using test stubs, namely CU Stub and RIC Stub. O-DU High also uses Phy Stub in the absence of O-DU Low. However, Phy Stub is built as a part of the O-DU High image itself.

Execution of below steps yields successful UE Attach procedure and message exchanges required for Traffic Steering use-case on the E2 interface. These can be verified on wireshark by capturing SCTP packets.

  1. Prepare environment

    sudo apt-get install libpcap-dev libsctp-dev

  2. Cloning code

    mkdir odu_high
cd odu_high
git clone "https://gerrit.o-ran-sc.org/r/o-du/l2"

  3. Compilation of O-DU

    cd odu_high/l2/build/odu
make clean_odu odu MACHINE=BIT64 MODE=FDD

  4. Compilation of CU Stub

    cd odu_high/l2/build/odu
make clean_cu cu_stub NODE=TEST_STUB MACHINE=BIT64 MODE=FDD

  5. Compilation of RIC Stub

    cd odu_high/l2/build/odu
make clean_ric ric_stub NODE=TEST_STUB MACHINE=BIT64 MODE=FDD

  6. Execution - Assign IP addresses

    ifconfig <interface name>:ODU “192.168.130.81”
ifconfig <interface name>:CU_STUB “192.168.130.82”
ifconfig <interface name>:RIC_STUB “192.168.130.80”

  7. Running CU Stub

    cd odu_high/l2/bin/cu_stub
sudo ./cu_stub

  8. Running RIC Stub

  9. cd odu_high/l2/bin/ric_stub
sudo ./ric_stub

  10. Running O-DU

    cd odu_high/l2/bin/odu
sudo ./odu

    Note:

    1. Each of the above binaries must be run in separate terminals

    2. CU Stub and RIC Stub images must be run before O-DU image. 





Related content