Is this page helpful?

Part 4. Validate the Setup#

In this section, you will validate the ATB setup using bi-directional UDP.

Step 1: Add the SIM User Profile#

Modify the following files:

  • oai_db.sql

    There are 3 UEs pre-configured in this file. To find them, search for 001010000000001 and add or edit them as needed.

  • ./targets/PROJECTS/GENERIC-NR-5GC/CONF/gnb-vnf.sa.band78.273prb.aerial.conf

    Modify this file on the gNB server if you want to change the MCC and MNC in the gNB config file.

Step 2: Setup the UE and SIM Card#

For reference, use the following: SIM cards – 4G and 5G reference software (open-cells.com)

Program the SIM Card with the Open Cells Project application “uicc-v2.6”, which can be downloaded here.

Use the ADM code specific to the SIM card. If the wrong ADM is used 8 times, the SIM card will be permanently locked.

sudo ./program_uicc --adm 12345678 --imsi 001010000000001 --isdn 00000001 --acc 0001 --key fec86ba6eb707ed08905757b1bb44b8f --opc C42449363BBAD02B66D16BC975D77CC1 -spn "OpenAirInterface" --authenticate
Existing values in USIM
ICCID: 89860061100000000191
WARNING: iccid luhn encoding of last digit not done
USIM IMSI: 208920100001191
USIM MSISDN: 00000191
USIM Service Provider Name: OpenCells191
Setting new values
Reading UICC values after uploading new values
ICCID: 89860061100000000191
WARNING: iccid luhn encoding of last digit not done
USIM IMSI: 001010000000001
USIM MSISDN: 00000001
USIM Service Provider Name: OpenAirInterface
Succeeded to authentify with SQN: 64
set HSS SQN value as: 96

Commercial UE Configuration Setup#

Install the “Magic IPERF” application on the UE:

  1. To test with commercial UE, a test SIM card with Milenage support is required. The following must be provisioned on the SIM card and must match the Core Network settings: mcc, mnc, IMSI, Ki, OPc.

  2. The APN on the commercial UE should be configured according to the Core Network settings.

  3. Start the DNS. Core Network should assign a mobile IP address and DNS. If DNS is not assigned, set the DNS with the other Android app.

Step 3. Running End-to-End OTA#

This section describes how to run end-to-end (E2E) traffic from the UE to the edge Core Network.

Note

The UE can connect as close as 2-3 meters, with a maximum range of 10-15 meters. The connection distance outside of buildings has not been verified.

CUE Connecting to 5G Network#

Take the commercial UE out of airplane mode to start attaching the UE to the network. Make sure that the CUE is in airplane mode before starting OAI L2 stack.

Observe 5G Connect Status#

Refer to the Preamble log in the cuphycontroller console output.

Check the Core Network log or commercial UE log to determine whether NAS authentication and PDU session succeeded.

Run E2E Iperf Traffic#

Start ping, iperf, or other network app tests after the PDU session connects successfully.

You can install and run the “Magic IPerf” Android application on the commercial UE for this purpose.

Ping Test#

Ping the UE from the CN:

docker exec -it oai-ext-dn ping 10.0.0.2

Ping from the UE to the CN:

ping -I 10.0.0.2 192.168.70.135

Monitor the CN5G Logs#

docker logs oai-amf -f

You can also retrieve logs from all the CN functions with the below script.

cd ~/openairinterface5g/doc/tutorial_resources/oai-cn5g
./getLogs.sh

Capture PCAPs#

docker exec -it oai-amf /bin/bash
tcpdump -i any -w /tmp/amf.pcap

Then copy the .pcap file out from the container.

docker cp oai-amf:/tmp/amf.pcap .