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.
Role | Version | Commit & Date | OS | CPU (Min) |
Mem (Min) |
HDD (Min) |
---|---|---|---|---|---|---|
C-Plane | 2.7.1+ | 2a4d8db72eac25dcd29ed313e82dcc347cca7d43 2024.05.25 |
Ubuntu 24.04 |
1 | 2GB | 20GB |
UPF | 2.7.1+ | 2a4d8db72eac25dcd29ed313e82dcc347cca7d43 2024.05.25 |
Ubuntu 24.04 |
1 | 1GB | 20GB |
Role | Version | Commit & Date | OS | CPU (Min) |
Mem (Min) |
HDD (Min) |
---|---|---|---|---|---|---|
C-Plane | 3.4.1+ | b0abf3dbe2c7571db6fc938b4107c034357bf080 2024.04.24 |
Ubuntu 24.04 |
1 | 2GB | 20GB |
UPF | 1.2.2+ | 922281ba58b6ca42d73be218671c8feae3658420 2024.05.11 |
Ubuntu 24.04 |
1 | 1GB | 20GB |
gtp5g (UPF) |
0.8.9 | 6657a0a2084486f499d951d169fb3c0232f6b454 2024.05.03 |
-- | -- | -- | -- |
Role | Version | Commit & Date | OS | CPU (Min) |
Mem (Min) |
HDD (Min) |
---|---|---|---|---|---|---|
UPF | 1.13.0 | dfdf64000566d35955d7c180720ff66086bd3572 2024.03.25 |
Ubuntu 22.04 |
2 | 8GB | 20GB |
Role | Version | Commit & Date | OS | CPU (Min) |
Mem (Min) |
HDD (Min) |
---|---|---|---|---|---|---|
UPF | 0.6.4+ | ec283f5c857cd81a05c47d643c49c84adc4df41f 2024.05.07 |
Ubuntu 24.04 |
1 | 2GB | 20GB |
Role | Version | Commit & Date | OS | CPU (Min) |
Mem (Min) |
HDD (Min) |
---|---|---|---|---|---|---|
RAN & UE | 3.2.6+ | 85a0fbfdd166da84c39ed5b4a5435afd40725878 2024.04.17 |
Ubuntu 24.04 |
1 | 1GB | 10GB |
Role | Version | Commit & Date | OS | CPU (Min) |
Mem (Min) |
HDD (Min) |
---|---|---|---|---|---|---|
RAN | 24.04+ | c33cacba7d940e734ac7bad08935cbc35578fad9 2024.06.10 |
Ubuntu 24.04 |
2 | 4GB | 10GB |
Role | Version | Commit & Date | OS | CPU (Min) |
Mem (Min) |
HDD (Min) |
---|---|---|---|---|---|---|
RAN & UE | 23.11+ | ec29b0c1ff79cebcbe66caa6d6b90778261c42b8 2024.02.01 |
Ubuntu 22.04 |
1 | 2GB | 10GB |
Role | Version | Commit & Date | OS | CPU (Min) |
Mem (Min) |
HDD (Min) |
---|---|---|---|---|---|---|
RAN & UE | 20240521 | 2bbcc24fa2ebf14335d6eec8737291f2205b91a1 2024.05.19 |
Ubuntu 24.04 |
1 | 1GB | 10GB |
gtp5g (RAN) |
0.8.6 | d8818ee80a9a004ea0fac3715415395810666921 2024.02.18 |
-- | -- | -- | -- |
0.8.9 [1] | 6657a0a2084486f499d951d169fb3c0232f6b454 2024.05.03 |
-- | -- | -- | -- |
-
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)
Below are the results of confirming the operation of ping and iperf3 in my environment.
UE | RAN | C-Plane | UPF | N3/N4/N6 | Ping | iPerf3 |
---|---|---|---|---|---|---|
UERANSIM | UERANSIM | Open5GS | Open5GS | Separate | OK | OK |
Same | OK | OK | ||||
UPG-VPP | Separate | OK | OK | |||
eUPF | Separate | OK | OK | |||
free5GC | free5GC | Separate | OK | OK | ||
Same | OK | OK | ||||
UPG-VPP | Separate | OK | OK | |||
eUPF | Separate | OK | OK | |||
srsRAN_4G | srsRAN_Project | Open5GS | Open5GS | Separate | OK | OK |
Same | OK | OK | ||||
UPG-VPP | Separate | OK [2] | OK [2] | |||
eUPF | Separate | OK | OK [3] | |||
free5GC | free5GC | Separate | OK | OK | ||
Same | OK | OK | ||||
UPG-VPP | Separate | OK [2] | OK [2] | |||
eUPF | Separate | OK | OK [3] | |||
PacketRusher | PacketRusher | Open5GS | Open5GS | Separate | OK | OK |
Same | OK | OK | ||||
UPG-VPP | Separate | OK | OK | |||
eUPF | Separate | OK [1] | OK [1] | |||
free5GC | free5GC | Separate | OK | OK | ||
Same | OK | OK | ||||
UPG-VPP | Separate | OK | OK | |||
eUPF | Separate | OK [1] | OK [1] |
UE | RAN | C-Plane | SGW-U | PGW-U (UPF) | S5u/Sxb/SGi | Ping | iPerf3 |
---|---|---|---|---|---|---|---|
srsRAN_4G | srsRAN_4G | Open5GS | Open5GS | Open5GS | Separate | OK | OK |
Same | OK | OK | |||||
UPG-VPP | Separate | OK | OK | ||||
eUPF | Separate | OK | OK [3] |
-
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. -
To avoid IP fragmentation, change the MTU of both N6 or SGi interface of eUPF and
tun_srsue
interface of srsRAN_4G UE as follows.For N6 or SGi interface of eUPF:
# ip link set <N6 or SGi interface of eUPF> mtu 1450
For
tun_srsue
interface of srsRAN_4G UE:# ip link set tun_srsue mtu 1400