5G test process

Documentation Links:

Open 5Gs docs

UERANSIM docs

Environment Setup:

We used raspberry Pi 3 b+'s and a Intel NUC 12 Pro Mini acting as the core and a Intel NUC 11PH as our radio tower that we connected via ethernet switch for our tests.

Click on the link for the hardware setup instructions below:

Raspberry Pi

Intel Nuc

Test Process

Note: Commands to run are in bold

Setup the Nuc(s) and Pi cluster

1. Connect everything to power – the Nuc(s) Pi cluster, and external hard drive adapter.
2. Connect the external hard drive to the 5g core Nuc.
3. Verify that these steps have been completed.
   1. Each Pi has all of the correct files mentioned in the setup stage.
   2. Each Pi has the correct imsi located in /home/ubuntu/scripts/script_config/open5gs-ue(#).yaml
      1. Pi1 should have an imsi that ends 11, pi2 imsi 21, pi3 imsi 31 etc. you can check localhost:3000 to see what all the imsi’s are for each pi.
   3. Check to make sure the appropriate Nuc has the correct files mentioned in the setup stage.
   4. Go to localhost:3000 and verify that every pi has an imsi associated with it.

Check that UE and gNB are connected to the network

1. On the Core, verify that the 5g core is running by running the following command: /home/ubuntu/ldrd/scripts/restart_core.sh
2. On the NugNB, verify that gNB is running.

   1. If it is not run the following command on the NugNB:

      sudo UERANSIM/build/nr-gnb -c UERANSIM/config/open5gs-gnb.yaml

Start the servers on the piFS

On the piFS run the following commands in two different shell tabs:

1. For the download server.
   1. cd /home/ubuntu/fs/files
   2. sudo python3 -m http.server 80
   3. Keep this tab open until all tests are complete.
2. For the upload server.
   1. cd /home/ubuntu/fs/upload
   2. sudo python3 -m uploadserver 8000
   3. Keep this tab open until all tests are complete.
3. Check that the data directory on the core was backed up and emptied from the previous runs (see step "Backup")

Run all Tests

Note: All tests should be ran from the core.

1. Run the following commands in a new shell tab on the core:
2. cd /home/ubuntu/ldrd/
3. ./run_tests_parallel.sh -s 1 -e 15 -p 6
   1. -s is the configuration ID we are starting at.
   2. -e is the configuration ID we are ending at.
   3. -p is the maximum number of concurrent raspberry Pis to use.
4. Once all tests have finished Generate the summary.csv files on the core.
   1. Run the following commands in a new shell tab on the core:
      1. cd /home/ubuntu/ldrd/scripts
      2. source /home/ubuntu/ldrd/env/bin/activate
      3. ./process_configuration_range.sh -s 1 -e 15
         1. -s is the configuration ID we are starting at
         2. -e is the configuration ID we are ending at
   2. Once this script has finished spot check a few directories in /home/ubuntu/ldrd/data for summary.csv files.

Backup the Data

1. Check that the external hard drive is connected to the core (/media/ubuntu/qos_ldrd_data_5g)
2. Make a new directory for the run #
3. Copy all data from /home/fs/ldrd/data/* into the new run directory you created.
4. Verify that the data is all copied over to the external drive.
5. Delete all data inside /home/fs/ldrd/data/

Troubleshooting

Throughout this process we have touched the following configuration files:

AMF component: /etc/open5gs/amf.yaml

UPF component: /etc/open5gs/upf.yaml

gNB component: UERANSIM/config/open5gs-gnb.yaml

UE component: UERANSIM/config/open5gs-ue(various).yaml

The system is set up in the way described below so if you are having trouble connecting any piece you will want to check the above configuration files.

From open5gs doc:

Interfaces

There are 3 main interface in UE/RAN perspective:

1. Control Interface (between RAN and AMF)
2. User Interface (between RAN and UPF)
3. Radio Interface (between UE and RAN)

The UE connects to the gNB which then connects to the 5g core via the AMF for authentication or the UPF if you need to reach outside the network which in our case was where the file server was located.

If you need to change the IP address of the individual UE's you will want to set them under localhost:3000 by clicking the edit icon on the UE ISMI number to set the desired IP address for each UE.