You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Greetings!
We are 3rd year students from PES University, Bangalore. We are currently working to get the Open5gs core, gNB and UE set up for our final year project.
As such while doing so we have run into problems. We have followed the documentation present on the open5gs wiki.We have also used UERANSIM for the gNB and UE. (https://github.com/aligungr/UERANSIM.git)(UERANSIM version 3.2.6)
These are the instructions we followed to set up UE and gNB:
install all the dependencies:
sudo apt install make gcc g++
sudo apt install libsctp-dev lksctp-tools iproute2
sudo snap install cmake --classic
Configuration
Go to the config folder using cd config
Configure the UE.
Open the open5gs-ue.yaml file in the config folder using
sudo nano open5gs-ue.yaml
The gnbSearchList must have the IP address of the device running UERANSIM(ue and gnb).
Make sure the supi has the same imsi value as the one registered in the device running open5gs.
open5gs-ue.yaml now looks like this:
image.png
Configure the gNB
Open the open5gs-gnb.yaml in the config folder using
sudo nano open5gs-gnb.yaml
The linkIP, ngapIP and the gtpIP must be the IP address of the device running UERANSIM(ue and gnb).
The address in amfConfigs must be the IP address of the device running the core network(open5gs)
open5gs-gnb.yaml now looks like this:
image.png
Build UE and gNB
To build the gNB use
sudo ./build/nr-gnb -c config/open5gs-gnb.yaml
To build the UE open another terminal and use
sudo ./build/nr-ue -c config/open5gs-ue.yaml
The problem is that while a SCTP connection is being established, the core is not able to register our UE. We have double checked the subscriber page on the core side.
Please be advised that we have the core running on a seperate machine and the gNB and UE on one machine.
We have attached to this e-mail the logs extracted from the core, gNB and the UE.
Greetings!
We are 3rd year students from PES University, Bangalore. We are currently working to get the Open5gs core, gNB and UE set up for our final year project.
As such while doing so we have run into problems. We have followed the documentation present on the open5gs wiki.We have also used UERANSIM for the gNB and UE. (https://github.com/aligungr/UERANSIM.git)(UERANSIM version 3.2.6)
These are the instructions we followed to set up UE and gNB:
install all the dependencies:
sudo apt install make gcc g++
sudo apt install libsctp-dev lksctp-tools iproute2
sudo snap install cmake --classic
Clone UERANSIM repository:
git clone https://github.com/aligungr/UERANSIM
Build UERANSIM
cd UERANSIM
make
Configuration
Go to the config folder using cd config
Configure the UE.
Open the open5gs-ue.yaml file in the config folder using
sudo nano open5gs-ue.yaml
The gnbSearchList must have the IP address of the device running UERANSIM(ue and gnb).
Make sure the supi has the same imsi value as the one registered in the device running open5gs.
open5gs-ue.yaml now looks like this:
image.png
Configure the gNB
Open the open5gs-gnb.yaml in the config folder using
sudo nano open5gs-gnb.yaml
The linkIP, ngapIP and the gtpIP must be the IP address of the device running UERANSIM(ue and gnb).
The address in amfConfigs must be the IP address of the device running the core network(open5gs)
open5gs-gnb.yaml now looks like this:
image.png
Build UE and gNB
To build the gNB use
sudo ./build/nr-gnb -c config/open5gs-gnb.yaml
To build the UE open another terminal and use
sudo ./build/nr-ue -c config/open5gs-ue.yaml
The problem is that while a SCTP connection is being established, the core is not able to register our UE. We have double checked the subscriber page on the core side.
Please be advised that we have the core running on a seperate machine and the gNB and UE on one machine.
We have attached to this e-mail the logs extracted from the core, gNB and the UE.
Request you to please assist us in getting the system up and running.
corelog (1).txt
uelog (1).txt
gnblog (1).txt
The text was updated successfully, but these errors were encountered: