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.
Role | Version | Commit & Date | OS | CPU (Min) |
Mem (Min) |
HDD (Min) |
---|---|---|---|---|---|---|
C-Plane | 2.7.2+ | 5dc3905c39fd6ccd6d82f769e2c0d6f208caf0cf 2024.10.16 |
Ubuntu 24.04 |
1 | 2GB | 20GB |
UPF | 2.7.2+ | 5dc3905c39fd6ccd6d82f769e2c0d6f208caf0cf 2024.10.16 |
Ubuntu 24.04 |
1 | 1GB | 20GB |
Role | Version | Commit & Date | OS | CPU (Min) |
Mem (Min) |
HDD (Min) |
---|---|---|---|---|---|---|
C-Plane | 3.4.3+ | 9675d563ac90ec2193ccbbdd700b0fb534a4165b 2024.10.11 (Latest nightly build on 2024.10.14) |
Ubuntu 24.04 |
1 | 2GB | 20GB |
UPF | 1.2.3+ | 6b73d126b8b29b4d17ff744c31ef50634ee64164 2024.10.11 |
Ubuntu 24.04 |
1 | 1GB | 10GB |
gtp5g (UPF) |
0.8.10 | 3ee1a5262c5b4dc2ba118b7cb1ed0ba842d3b07b 2024.06.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 | 0f704deaca67766733a447f4680cf4d77e638934 2024.05.01 |
Ubuntu 24.04 |
1 | 2GB | 20GB |
Role | Version | Commit & Date | OS | CPU (Min) |
Mem (Min) |
HDD (Min) |
---|---|---|---|---|---|---|
RAN & UE | 3.2.6+ | 528061fe10389876da58d3bd15e8cba6d7c152a9 2024.08.27 |
Ubuntu 24.04 |
1 | 1GB | 10GB |
Role | Version | Commit & Date | OS | CPU (Min) |
Mem (Min) |
HDD (Min) |
---|---|---|---|---|---|---|
RAN | 24.10 | 9d5dd742a70e82c0813c34f57982f9507f1b6d5d 2024.10.14 |
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+ | 32a08fa9fb2d83b654628b5187a0244a66b737b2 2024.06.24 |
Ubuntu 24.04 |
1 | 1GB | 10GB |
gtp5g (RAN) |
0.8.6 | d8818ee80a9a004ea0fac3715415395810666921 2024.02.18 |
-- | -- | -- | -- |
0.9.2 [1] | 0ec00843e79ff4660a43fbeddf2ae730414dee5c 2024.10.11 |
-- | -- | -- | -- |
-
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
tun_srsue
interface of srsRAN_4G UE as follows.# ip link set tun_srsue mtu 1450