Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

srsRAN gNB with srsUE over usrp b210 frontends #933

Open
thaxir opened this issue Nov 13, 2024 · 7 comments
Open

srsRAN gNB with srsUE over usrp b210 frontends #933

thaxir opened this issue Nov 13, 2024 · 7 comments

Comments

@thaxir
Copy link

thaxir commented Nov 13, 2024

Issue Description

I'm following the recent tutorial 'srsRAN gNB with srsUE' from here https://docs.srsran.com/projects/project/en/latest/tutorials/source/srsUE/source/index.html. However, the UE (srsue) never obtains an IP from srsgnb staying at this :

RF status: O=3, U=0, L=0
Scheduling request failed: releasing RRC connection...
Random Access Transmission: prach_occasion=0, preamble_index=0, ra-rnti=0x39, tti=1934

Setup Details

e.g. Network configuration, Operation System, Hardware, RF front-end, library and driver versions

  • 2 USRP b210 as RF frontend
  • 2 NUCs
  • Open5gs
  • srsRAN_Project for gnb
  • srsRAN_4G for the UE
  • Internal clock/no GPSDO
  • UHD_3.15. in both nucs

Expected Behavior

Cannot use srsue since it is not properly connected to the gnb

Actual Behaviour

[What happens instead e.g. error message]
Seems like UE attempted a scheduling request but didn't receive a response from the gNB. Not sure though
image

Steps to reproduce the problem

Additional Information

[Any additional information, configuration or data that might be necessary to reproduce the issue]
gnb.log.txt
ue.log.txt

ue.conf.txt

gnb-config.yml.txt

@pgawlowicz
Copy link
Collaborator

UL signal is too strong at the gnb. Please try to tune down srsUE tx_gain and gnb rx_gain.

@thaxir
Copy link
Author

thaxir commented Nov 14, 2024

Hi @pgawlowicz thank you for the reply.
I have experimented with a lot of changes in both srsUE and gnb as you said but could have any significant result. The only thing i managed to see traffic in the UL was with the tx gain 75 rx gain 35 (see screeshot below) .Other that these i had received one prb with txgain/rxgain at 48/38 but that it only one. The two usrps are very close to each other like 10 cm .

image

srsue :
image

Attached are also the latest logs of gnb and srsue and the confs.
ue.log.2.txt

gnb.log.2.txt

gnb.conf.txt
srsue.conf.txt

@thaxir
Copy link
Author

thaxir commented Nov 19, 2024

any suggestions on this topic ??

@pgawlowicz
Copy link
Collaborator

could you try to apply the patch from this comment to srsUE, recompile and try again?
#826 (comment)

@thaxir
Copy link
Author

thaxir commented Nov 21, 2024

@pgawlowicz Piotr we have done the changes you suggested .
After restarting serveral times srsue and gnb the srsue logs are changed as you see in the snapshot below
image

Gnb reports this:
image

and amf in open5gs which is in the same machine with gnb reports this :
image

which seems that amf rejects the srsue . Do you know why? (

And another question is why do i need to restart several times both srsue and gnb in order to have this connection open and not the Scheduling request failed : releasing RRC connection?
I attach also the logs for ue and gnb.
ue.log.3.txt
gnb.log.3.txt

gnb.log.3.txt

@thaxir
Copy link
Author

thaxir commented Nov 26, 2024

Any suggestions on this?

@pgawlowicz
Copy link
Collaborator

it seems the problem is on the core network side, did you add the UE to the subscriber database?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants