Awesome

Simple Confirmed Information for Mobile Network

This is a memo of environment information when briefly confirming the operation of some functions of each open source. Please note that it may not work depending on the environment. Also, please note that there may be cases where I have not been able to confirm operation due to my settings being incorrect.

Sample Configurations and Miscellaneous for Mobile Network

<a id="toc"></a>

Table of Contents

• Version and Resource requirements
• Ping and iPerf3
  • For 5G
  • For 4G

<a id="version_resource"></a>

Version and Resource requirements

Open5GS

free5GC

UPG-VPP

eUPF

UERANSIM

srsRAN_Project

srsRAN_4G

PacketRusher

<a id="ping_iperf3"></a>

Ping and iPerf3

Below are the results of confirming the operation of ping and iperf3 in my environment.

<a id="5g"></a>

For 5G

<a id="4g"></a>

For 4G

1. In gtp5g v0.8.7 and later, GTP-U Sequence Number is enabled by default. In this case, eUPF will probably not be able to process GTP-U packets correctly. Therefore, if connecting to eUPF, please disable GTP-U Sequence Number of gtp5g used by PacketRusher as follows.

   # echo 0 > /proc/gtp5g/seq
   

   Also, UPF performance measurements using iperf3 tended to be better when GTP-U Sequence Number was disabled. (e.g. UPG-VPP)

2. UPG-VPP v1.13.0 does not support PDU Session container. Therefore, some gNodeBs such as srsRAN_Project, may not accept GTP traffic from UPG-VPP. In that case, please refer to this note. In these results, I applied this temporary patch and confirmed that it worked with the gNodeB of srsRAN_Project.

3. To connect Open5GS SMF to UPG-VPP, add the following parameter use_upg_vpp: true in smf.yaml. See here for the reason.

   smf.yaml

   global:
     parameter:
       use_upg_vpp: true
   

4. When connecting PacketRusher to eUPF and using iperf3, the following version was used for PacketRusher.

   RAN & UE	Version	Commit & Date
   PacketRusher	20240521+	32a08fa9fb2d83b654628b5187a0244a66b737b2<br>2024.06.24