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+ | 6d80d4322a6daf4420c39f2edb1d1d8585a577a0 2024.09.04 |
Ubuntu 24.04 |
1 | 2GB | 20GB |
UPF | 2.7.2+ | 6d80d4322a6daf4420c39f2edb1d1d8585a577a0 2024.09.04 |
Ubuntu 24.04 |
1 | 1GB | 20GB |
Role | Version | Commit & Date | OS | CPU (Min) |
Mem (Min) |
HDD (Min) |
---|---|---|---|---|---|---|
C-Plane | 3.4.3+ | 0d2cb87d33bb84ee898c3f46e2fb284e466614b7 2024.09.12 (Latest nightly build on 2024.09.23) |
Ubuntu 24.04 |
1 | 2GB | 20GB |
UPF | 1.2.3 | 922281ba58b6ca42d73be218671c8feae3658420 2024.05.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) |
---|---|---|---|---|---|---|
UPF | 0.1.1.109 | 6859de09d2ae0e363070e152489d9f8579085aa8 2024.08.16 |
Ubuntu 24.04 |
1 | 1GB | 10GB |
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.04+ | 4ac5300d4927b5199af69e6bc2e55d061fc33652 2024.07.31 |
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.1+ [1] | 02ac100d8fb71e8dd00d2421a4914dd504b913dd 2024.08.15 |
-- | -- | -- | -- |
-
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 | |||
OsmoUPF | Separate | NG | NG | |||
free5GC | free5GC | Separate | OK | OK | ||
Same | OK | OK | ||||
UPG-VPP | Separate | OK | OK | |||
eUPF | Separate | OK | OK | |||
OsmoUPF | Separate | NG | NG | |||
srsRAN_4G | srsRAN_Project | Open5GS | Open5GS | Separate | OK | OK |
Same | OK | OK | ||||
UPG-VPP | Separate | OK [2] | OK [2] | |||
eUPF | Separate | OK | OK [3] | |||
OsmoUPF | Separate | NG | NG | |||
free5GC | free5GC | Separate | OK | OK | ||
Same | OK | OK | ||||
UPG-VPP | Separate | OK [2] | OK [2] | |||
eUPF | Separate | OK | OK [3] | |||
OsmoUPF | Separate | NG | NG | |||
PacketRusher | PacketRusher | Open5GS | Open5GS | Separate | OK | OK |
Same | OK | OK | ||||
UPG-VPP | Separate | OK | OK | |||
eUPF | Separate | OK [1] | OK [1] | |||
OsmoUPF | Separate | OK | OK | |||
free5GC | free5GC | Separate | OK | OK | ||
Same | OK | OK | ||||
UPG-VPP | Separate | OK | OK | |||
eUPF | Separate | OK [1] | OK [1] | |||
OsmoUPF | Separate | OK | OK |
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] | ||||
OsmoUPF | Separate | OK | OK |
-
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