There are ready-made images in Colosseum NAS which include OAI RAN and 5G Core Network. These images can be selected in the Colosseum reservation page under the common section. The images of interest are

• RAN Image: oai-ran-2024-w13
• Core-network Image: oai-5gcore-2024

Make a reservation with n+2 SRNs out of which one Core-network image and n+1 RAN Images where n is the number of UEs in the test scenario.

Once the reservation is active, you can login to the SRNs. The password of root user is pass.

Run OAI 5G Core-network

In SRN running oai-5gcore-2024

cd oai-cn5g
docker compose up -d

This should start all the required docker containers for running the core-network.

Run OAI gNB

The image contains a python script to start the gNB and UE.

cd OAI-Colosseum
python3 ran.py -t donor -m sa

This will start the gNB process. If you get an FPGA compatibility number mismatch error, flash the USRP FPGA with the bitstream that matches your UHD driver version (compatibility 39.0 in this example).

colosseumcli usrp flash -f usrp_x310_fpga_HG_c39.bit

You only need to flash the FPGA once. For details on the flash option, see the colosseumcli guide. After the flash completes, you should be able to run the gNB without errors.

Start RF Scenario

Now we need to tell the MCHEM (Massive CHannel EMulator) to set up a channel between all the nodes in the current reservation. This can be done from any of the SRNs in the reservation. The following command starts an RF scenario with 0 dB path loss. (Please note that losses due to hardware impairments are still present.)

colosseumcli rf start -c 10011

Run OAI UE

Run the following commands.

cd OAI-Colosseum
python3 ran.py -t ue -m sa

If you get an FPGA compatibility number mismatch error, follow the same colosseumcli usrp flash command used for the gNB. If all goes well, the UE should connect to the gNB and the core network should have assigned an IP address to the UE. This can be verified by running ifconfig on the UE side and checking if the network interface named oaitun_ue has an IP assigned.

Sometimes the UE may continuously fail the Random Access (RA) procedure and not proceed beyond that point. If this happens, try changing the timing_advance value in the 106 PRB section of the conf.json file (increase or decrease in steps of 5).

IP Traffic

Ping the core-network from UE using ping 192.168.70.135 -I oaitun_ue. If the ping is successful, it means that an end-to-end connection between the UE and the 5G core network has been established. The user can push more traffic over the RAN using tools such as iperf3, or equivalent. On the core-network side, run docker exec -it oai-ext-dn iperf3 -s

Downlink Traffic

On the UE side, run iperf3 -c 192.168.70.135 -B <ip of oaitun_ue> -b 50M -u -R

Uplink Traffic

On the UE side, run iperf3 -c 192.168.70.135 -B <ip of oaitun_ue> -b 15M -u