View on GitHub Star

Gradiant 5G Charts

A curated collection of 5G/6G related Helm Charts

Open5GS and srsLTE

4G end to end communication demo with Open5GS and srsRAN.

This setup uses 2 helm charts generated by Gradiant: open5gs and srs-lte. These charts are packaged and available at Gradiant’s DockerHub repo:

If you want to have the repo in local you can pull it:

helm pull oci:// --version 2.0.8
helm pull oci:// --version 0.1.3

Deployment EPC and registration of subscribers

First, deploy the EPC (open5gs) using the epc-values.yaml file provided in order to overwrite some of the default values of the Open5GS chart:

helm install open5gs oci:// --version 2.0.8 --values 

These new values will:

Once this deployment has been completed, the subscriber’s registration can be verified following 2 different approaches:

kubectl exec deployment/open5gs-mongodb -ti -- bash


use open5gs


Deployment RAN

Now, deploy the RAN (srs-lte) using the lte-values.yaml file provided in order to overwrite some of the default values of the srs-lte chart:

helm install srs-lte oci:// --version 0.1.3 --values 

Thus, this deployment will not only launch the eNodeB and connect it to the Open5GS EPC, but it will also enable the launching of 1 UE.

It is important to notice that the default values of MCC, MNC, and TAC set for the eNB match those configured in the open5gs chart. Also, the IMSI, KI and OPc given for the UE match the ones provided in the open5gs-dbctl command.

In addition, take into account that the value given for enb.mme must match the name of the corresponding MME service deployed by the open5gs chart. Therefore, in case you use a differente release name for the open5gs chart, make sure that this value is set accordingly.

Verify deployment

Connection between PGW-C and PGW-U (C-Plane and U-Plane of EPC)

Check that the PGW-C (SMF component) gets associated with the PGW-U’s (UPF component) address:

kubectl logs deployment/open5gs-smf -f

Connection between MME and eNodeB

Check that the MME accepts and adds the eNodeB:

kubectl logs deployment/open5gs-mme -f

UE’s connectivity

Check that the eNodeB senses UE’s presence and the UE gets connected to the network:

kubectl logs srs-lte-srs-lte-0 enb -f

UE connectd to eNodeB

Check that the UE got successfully attached to the network:

kubectl logs srs-lte-srs-lte-0 ue -f

UE attached to network

Hence, check that the UE created a tunnel interface (tun_srsue):

kubectl exec srs-lte-srs-lte-0 -c ue -ti -- bash

ip addr

UE's tunnel interface

Check that the UE has connectivity through this interface:

ping -I tun_srsue

UEs connectivity

Moreover, if using traceroute, check that the first hop is (PGW-U’s side of the tunnel created):

traceroute -i tun_srsue

UEs connectivity

Therefore, the UE’s traffic can be captured in the PGW-U (UPF). The installation of tcpdump in the corresponding pod is needed in order to complete this check:

kubectl exec deployment/open5gs-upf -ti -- bash

apt update && apt install tcpdump

tcpdump -i ogstun

Capturing traffic in the PGW-U


Clean the deployment for this demo by uninstalling the 2 helm charts previously installed:

helm uninstall srs-lte

helm uninstall open5gs