Using srsUE with USRP #549

arman-maghsoudnia · 2024-04-08T12:55:23Z

arman-maghsoudnia
Apr 8, 2024

Hi, I am trying to use srsUE with USRP (b210) but encountering some problems. I use srsRAN 5G software alongside a USRP as the gNB part of the network. I also use srsUE with another USRP as the UE part of the network. But when I try to run the srsUE, I get this message:
Do you have any idea what could be the cause of the problem?

root@srs-ue-latest:/opt# /opt/srsRAN_4G/build/srsue/src/srsue /opt/ue.conf
Active RF plugins: libsrsran_rf_uhd.so libsrsran_rf_zmq.so
Inactive RF plugins:
Reading configuration file /opt/ue.conf...
WARNING: cpu0 scaling governor is not set to performance mode. Realtime processing could be compromised. Consider setting it to performance mode before running the application.

Built in Release mode using commit eea87b1d8 on branch master.

Opening 1 channels in RF device=uhd with args=default
Supported RF device list: UHD zmq file
[INFO] [UHD] linux; GNU C++ version 9.2.1 20200304; Boost_107100; UHD_3.15.0.0-2build5
[INFO] [LOGGING] Fastpath logging disabled at runtime.
Opening USRP channels=1, args: type=b200,master_clock_rate=23.04e6
[INFO] [UHD RF] RF UHD Generic instance constructed
[INFO] [B200] Detected Device: B210
[INFO] [B200] Operating over USB 3.
[INFO] [B200] Initialize CODEC control...
[INFO] [B200] Initialize Radio control...
[INFO] [B200] Performing register loopback test...
[INFO] [B200] Register loopback test passed
[INFO] [B200] Performing register loopback test...
[INFO] [B200] Register loopback test passed
[INFO] [B200] Asking for clock rate 23.040000 MHz...
[INFO] [B200] Actually got clock rate 23.040000 MHz.
Waiting PHY to initialize ... done!
Attaching UE...
RF status: O=25, U=0, L=0

My srsUE config is as follows:

[rf]
freq_offset = 0
tx_gain = 3
#rx_gain = 1
srate = 23.04e6
nof_antennas = 1

device_name = uhd #zmq
device_args = #tx_port=tcp://127.0.0.1:2001,rx_port=tcp://127.0.0.1:2000,base_srate=23.04e6

[rat.eutra]
dl_earfcn = 2850
nof_carriers = 0

[rat.nr]
bands = 3
nof_carriers = 1
max_nof_prb = 106
nof_prb = 106

[pcap]
enable = none
mac_filename = /tmp/ue_mac.pcap
mac_nr_filename = /tmp/ue_mac_nr.pcap
nas_filename = /tmp/ue_nas.pcap

[log]
all_level = debug
phy_lib_level = none
all_hex_limit = 32
filename = /tmp/ue.log
file_max_size = -1

[usim]
mode = soft
algo = milenage
opc  = ***
k    = ***
imsi = ***
imei = ***

[rrc]
release = 15
ue_category = 4

[nas]
apn = internet
apn_protocol = ipv4

[gw]
netns = ue1
ip_devname = tun_srsue
ip_netmask = 255.255.255.0

[gui]
enable = false

My gNB config is as follows: But I guess at this point the gNB config should not be important since the UE does not even start searching for the gNB. But for the sake of complicity and further debugging I provide the gNB log as well.

gnb_id: 107

slicing:
 - sst: 1
   sd: 0

amf:
  addr: 10.43.212.207
  bind_addr: 10.42.0.129

ru_sdr:
  device_driver: uhd
  device_args:
  # clock:
  # sync:
  srate: 23.040
  otw_format: sc16
  tx_gain: 80
  rx_gain: 40

cell_cfg:
  dl_arfcn: 650000
  band: 78
  channel_bandwidth_MHz: 20
  common_scs: 30
  plmn: "00102"
  tac: 1
  pci: 1
  tdd_ul_dl_cfg:
    dl_ul_tx_period: 4
    nof_dl_slots: 2
    nof_dl_symbols: 7
    nof_ul_slots: 1
    nof_ul_symbols: 6
  nof_antennas_ul: 1
  nof_antennas_dl: 1
  pdsch:
    mcs_table: qam256
  pusch:
    mcs_table: qam64
  pucch:
    sr_period_ms: 2

expert_phy:
  max_proc_delay: 2


e2:
  enable_du_e2: false
  e2sm_kpm_enabled: true
  addr: 127.0.0.1
  bind_addr: 10.42.3.88
  port: 36421

log:
  filename: /tmp/gnb.log
  all_level: debug

pcap:
  mac_enable: false
  mac_filename: /tmp/gnb_mac.pcap
  ngap_enable: false
  ngap_filename: /tmp/gnb_ngap.pcap

Answered by arman-maghsoudnia

Apr 10, 2024

Now I am using two separate machines. At first, the UE could not connect again. I noticed that I forgot to add the clock = external in the gNB configuration (I used to just add sync = external). But after adding it, it works and it connects. I put the new config here (
gnb.txt) so other readers of this discussion can use it in the future.
But I still want to continue this discussion because I want to run both gNB and UE on the same machine to do more precise measurements (I need the time and clock sync). Now when I try to run them at the same machine, I get this output when I try to run the srsUE:

Active RF plugins: libsrsran_rf_uhd.so libsrsran_rf_zmq.so
Inactive RF plugins:
Reading conf…

View full answer

pgawlowicz · 2024-04-08T13:09:19Z

pgawlowicz
Apr 8, 2024
Maintainer

Hi, srsUE supports only SCS=15kHz.
You can check this tutorial: https://docs.srsran.com/projects/project/en/latest/tutorials/source/srsUE/source/index.html

29 replies

pgawlowicz Apr 9, 2024
Maintainer

could you run this script on both gnb and srsUE hosts? https://github.com/srsran/srsRAN_Project/blob/main/scripts/srsran_performance

Could you check the cpu load on srsUE hostmachine? e.g. with htop

arman-maghsoudnia Apr 9, 2024
Author

I am using a single machine for both. I executed the script you sent. The message is not there anymore, but the UE does not connect either. I will attach the logs. Note that before using the external clock, the UE connected and then disconnected. But now it does not connect at all.
gnb.log
ue.log

pgawlowicz Apr 9, 2024
Maintainer

could you use two separate machines?

arman-maghsoudnia Apr 10, 2024
Author

Now I am using two separate machines. At first, the UE could not connect again. I noticed that I forgot to add the clock = external in the gNB configuration (I used to just add sync = external). But after adding it, it works and it connects. I put the new config here (
gnb.txt) so other readers of this discussion can use it in the future.
But I still want to continue this discussion because I want to run both gNB and UE on the same machine to do more precise measurements (I need the time and clock sync). Now when I try to run them at the same machine, I get this output when I try to run the srsUE:

Active RF plugins: libsrsran_rf_uhd.so libsrsran_rf_zmq.so
Inactive RF plugins:
Reading configuration file /opt/ue-suggest.conf...

Built in Release mode using commit ec29b0c1f on branch master.

Opening 1 channels in RF device=uhd with args=clock=external
Supported RF device list: UHD zmq file
[INFO] [UHD] linux; GNU C++ version 9.2.1 20200304; Boost_107100; UHD_3.15.0.0-2build5
[INFO] [LOGGING] Fastpath logging disabled at runtime.
Opening USRP channels=1, args: type=b200,master_clock_rate=23.04e6
[INFO] [UHD RF] RF UHD Generic instance constructed
[INFO] [B200] Detected Device: B210
[INFO] [B200] Operating over USB 2.
[INFO] [B200] Initialize CODEC control...
[INFO] [B200] Initialize Radio control...
[INFO] [B200] Performing register loopback test...
[INFO] [B200] Register loopback test passed
[INFO] [B200] Performing register loopback test...
[INFO] [B200] Register loopback test passed
[INFO] [B200] Asking for clock rate 23.040000 MHz...
[INFO] [B200] Actually got clock rate 23.040000 MHz.
Setting manual TX/RX offset to 300 samples
Waiting PHY to initialize ... done!
Attaching UE...
RF status: O=155, U=1, L=5
RF status: O=160, U=0, L=254
RF status: O=160, U=0, L=381
RF status: O=159, U=0, L=328
RF status: O=155, U=0, L=494
RF status: O=160, U=0, L=318
RF status: O=158, U=0, L=379
RF status: O=158, U=0, L=383
RF status: O=157, U=0, L=431

It seems to be many Os and Ls as the RF status. I'm not sure what can be the cause of it. When I try to run them in 2 separate machines, this does not happen and everything works fine. Do you have any idea what could be the cause of it when running in the same machine?

Answer selected by arman-maghsoudnia

Zplusless Apr 10, 2024

can you use htop to check if there are processes of gnb and srsue running on the same cpu core? Core contentions will deteriorate the performance, especially for phy processes. btw,how many cpu cores does your server have?

pgawlowicz Apr 11, 2024
Maintainer

@arman-maghsoudnia you will need a powerful machine, and then you might try to assign separate cores to gnb and srsUE.
Please check the expert_execution in gnb config: https://docs.srsran.com/projects/project/en/latest/user_manuals/source/config_ref.html

For srsUE, you will need to set phy.worker_cpu_mask and phy.sync_cpu_affinity. Please check here:
https://github.com/srsran/srsRAN_4G/blob/master/srsue/src/main.cc#L264-L271

It is worth trying, but it is not guaranteed that it will work.

Zplusless Apr 11, 2024

Hi @pgawlowicz , wondering if using tasksec -c to bind gnb and srsUE to different cores can work?

pgawlowicz Apr 11, 2024
Maintainer

Yes, it is also an option, then you do not have to change the configs. I would put at least 4 core for gnb (8 cores would be better) and 4 for srsUE:

sudo taskset -c 0-3 ./gnb -c ./gnb.yaml
sudo taskset -c 4-7 ./srsue ./ue.conf

Zplusless · 2024-04-09T02:41:31Z

Zplusless
Apr 9, 2024

Have you tried connecting the two USRPs directly with SMA cable?

3 replies

arman-maghsoudnia Apr 9, 2024
Author

No, I have not. What two ports exactly do I need to connect?

Zplusless Apr 10, 2024

Maybe you can try using two separate machines first. If the problem still exists, you can try SMA calbe. Just remove the antenna and connecting the tx rx interfaces of USRPs.

arman-maghsoudnia Apr 10, 2024
Author

Thanks, it is a good suggestion to eliminate the channel effects. But currently, I guess it should make not much difference since the two radios are quite close to each other. Thanks again for the help.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Using srsUE with USRP #549

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 2 comments 32 replies

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

Select a reply

Using srsUE with USRP #549

arman-maghsoudnia Apr 8, 2024

Replies: 2 comments · 32 replies

pgawlowicz Apr 8, 2024 Maintainer

pgawlowicz Apr 9, 2024 Maintainer

arman-maghsoudnia Apr 9, 2024 Author

pgawlowicz Apr 9, 2024 Maintainer

arman-maghsoudnia Apr 10, 2024 Author

Zplusless Apr 10, 2024

pgawlowicz Apr 11, 2024 Maintainer

Zplusless Apr 11, 2024

pgawlowicz Apr 11, 2024 Maintainer

Zplusless Apr 9, 2024

arman-maghsoudnia Apr 9, 2024 Author

Zplusless Apr 10, 2024

arman-maghsoudnia Apr 10, 2024 Author

arman-maghsoudnia
Apr 8, 2024

Replies: 2 comments 32 replies

pgawlowicz
Apr 8, 2024
Maintainer

pgawlowicz Apr 9, 2024
Maintainer

arman-maghsoudnia Apr 9, 2024
Author

pgawlowicz Apr 9, 2024
Maintainer

arman-maghsoudnia Apr 10, 2024
Author

pgawlowicz Apr 11, 2024
Maintainer

pgawlowicz Apr 11, 2024
Maintainer

Zplusless
Apr 9, 2024

arman-maghsoudnia Apr 9, 2024
Author

arman-maghsoudnia Apr 10, 2024
Author