[srsran-users] [srsUE] Problems connecting to srsENB/srsEPC with bladeRF

Mon Dec 19 12:03:50 UTC 2022

Hi Robert,
thank you for the reply.
I might have caused a misunderstanding: the commercial eNodeB I’m trying to connect to is in a testing environment I have access to and I have control over the die configuration of the “commercial” eNodeB where I set to use this dl_earfcn. Also the COTS UEs which can connect to the eNodeB are using those SIM-Credentials. I have configured the testing environment to accept those credentials.

I did duplicate the testing environment to and exchanged the “commercial” eNodeB with srsenb and srsepc using a bladeRF-RF-Frontend. Configured it to use the same dl_earfcn and the SIM credentials.
Again, the COST UEs could connect and communicate with the srsenb but srsue (with bladeRF) would not.

I hope this makes the problem a bit clearer.

Best regards,
Philipp

–
Dipl.-Ing. Philipp Neher
Wissenschaftlicher Mitarbeiter „Echtzeitkommunikation und Steuerungshardware“

Institut für Steuerungstechnik der Werkzeugmaschinen und Fertigungseinrichtungen (ISW)
Universität Stuttgart

Seidenstraße 36 / Zi. 4.025
70174 Stuttgart

Tel: +49 711 685-84499
E-Mail: philipp.neher at isw.uni-stuttgart.de
Web: http://www.isw.uni-stuttgart.de<http://www.isw.uni-stuttgart.de/>

Von: srsran-users <srsran-users-bounces at lists.srsran.com> Im Auftrag von Robert Falkenberg
Gesendet: Montag, 19. Dezember 2022 12:37
An: srsran-users at lists.srsran.com
Betreff: Re: [srsran-users] [srsUE] Problems connecting to srsENB/srsEPC with bladeRF

Hi Philipp,

some pointers regarding the commercial eNB:

First, attaching to a commercial eNB requires proper network credentials to register into the network. In other words, you will have to use a card reader and a valid uSIM (hardware) of the operator you want to connect.
Using the default credentials in the soft SIM won’t work:

#####################################################################

# USIM configuration

#

# mode:   USIM mode (soft/pcsc)

# algo:   Authentication algorithm (xor/milenage)

# op/opc: 128-bit Operator Variant Algorithm Configuration Field (hex)

#         - Specify either op or opc (only used in milenage)

# k:      128-bit subscriber key (hex)

# imsi:   15 digit International Mobile Subscriber Identity

# imei:   15 digit International Mobile Station Equipment Identity

# pin:    PIN in case real SIM card is used

# reader: Specify card reader by it's name as listed by 'pcsc_scan'. If empty, try all available readers.

#####################################################################

[usim]

mode = soft

algo = milenage

#opc  = 63BFA50EE6523365FF14C1F45F88737D

#k    = 00112233445566778899aabbccddeeff

#imsi = 001010123456780

imei = 353490069873329

imsi = 258990800000001

k   = 0123456789abcdef0123456789abcdef

opc = ffffffffffffffffffffffffffffffff

#reader =

#pin  = 1234

Moreover, to connect to a network, you will have to find out the proper frequency or dl_earfcn of the cell.
In your config file you have

#####################################################################

# EUTRA RAT configuration

#

# dl_earfcn:   Downlink EARFCN list.

#

# Optional parameters:

# dl_freq:            Override DL frequency corresponding to dl_earfcn

# ul_freq:            Override UL frequency corresponding to dl_earfcn

# nof_carriers:       Number of carriers

#####################################################################

[rat.eutra]

dl_earfcn = 3100

#nof_carriers = 1

However, if you are based in Germany, I don’t think that 3100 this is a valid center frequency of any operator: https://de.wikipedia.org/wiki/Long_Term_Evolution#2,6-GHz-Frequenzband_(E-UTRA_Band_7_und_Band_38)

To find a proper frequency, you can either do a cell search, or you could take a look into 3rd party map services, e.g. https://www.cellmapper.net/map?MCC=262&MNC=3&type=LTE&latitude=48.78127549999999&longitude=9.165835567939325&zoom=16&showTowers=true&showIcons=true&showTowerLabels=true&clusterEnabled=true&tilesEnabled=true&showOrphans=false&showNoFrequencyOnly=false&showFrequencyOnly=false&showBandwidthOnly=false&DateFilterType=Last&showHex=false&showVerifiedOnly=false&showUnverifiedOnly=false&showLTECAOnly=false&showENDCOnly=false&showBand=0&showSectorColours=true&mapType=roadmap&darkMode=false

You can also use tools like gqrx to check if you have a strong signal in the spectrogram.

Hope it helps.

Best regards,
Robert
On 16.12.22 19:35, Neher, Philipp Albert wrote:

Hi Everybody,

somehow I made some progress.

I know can connect with COTS-UEs to an enB running srsRAN and using a bladeRF as Frontend.

But with the same setup a srsUE (using another bladeRF) won't connect to srsenB, it also won't connect to a commercial enB.

I have attached the ue.log and die ue.conf of the test with the commercial enB (ue_commerical_enb.log) and the logs and confs from the tests between srsUe and srsenB/srsEPC.

Also sometimes the logs just stop for a bit and it seems like a minute or so is missing, what could be the cause of this?

Has anybody a clue why the setup works with COTS UEs but not the srsUE?

Help would be greatly appreciated.

Thank you.

Philipp

–

Dipl.-Ing. Philipp Neher

Wissenschaftlicher Mitarbeiter „Echtzeitkommunikation und Steuerungshardware“

Institut für Steuerungstechnik der Werkzeugmaschinen und Fertigungseinrichtungen (ISW)

Universität Stuttgart

Seidenstraße 36 / Zi. 4.025

70174 Stuttgart

Tel: +49 711 685-84499

E-Mail: philipp.neher at isw.uni-stuttgart.de<mailto:philipp.neher at isw.uni-stuttgart.de>

Web: http://www.isw.uni-stuttgart.de

-----Ursprüngliche Nachricht-----

Von: srsran-users <srsran-users-bounces at lists.srsran.com><mailto:srsran-users-bounces at lists.srsran.com> Im Auftrag von Neher, Philipp Albert

Gesendet: Freitag, 16. Dezember 2022 16:08

An: Andre Puschmann <andre.puschmann at srs.io><mailto:andre.puschmann at srs.io>; srsran-users at lists.srsran.com<mailto:srsran-users at lists.srsran.com>

Betreff: Re: [srsran-users] [srsUE] Problems connecting to srsENB/srsEPC with bladeRF

HI andre,

thank you for the reply.

With the benchmark tool I mean the provided application in /srsRAN/build/lib/src/radio/test/benchmark_radio.

Any idea what could be the problem resulting in the overflows?

Thank you

philipp

–

Dipl.-Ing. Philipp Neher

Wissenschaftlicher Mitarbeiter „Echtzeitkommunikation und Steuerungshardware“

Institut für Steuerungstechnik der Werkzeugmaschinen und Fertigungseinrichtungen (ISW) Universität Stuttgart

Seidenstraße 36 / Zi. 4.025

70174 Stuttgart

Tel: +49 711 685-84499

E-Mail: philipp.neher at isw.uni-stuttgart.de<mailto:philipp.neher at isw.uni-stuttgart.de>

Web: http://www.isw.uni-stuttgart.de

-----Ursprüngliche Nachricht-----

Von: Andre Puschmann <andre.puschmann at srs.io><mailto:andre.puschmann at srs.io>

Gesendet: Freitag, 16. Dezember 2022 15:38

An: Neher, Philipp Albert <philipp.neher at isw.uni-stuttgart.de><mailto:philipp.neher at isw.uni-stuttgart.de>; srsran-users at lists.srsran.com<mailto:srsran-users at lists.srsran.com>

Betreff: Re: [srsran-users] [srsUE] Problems connecting to srsENB/srsEPC with bladeRF

Hi Philipp,

all your logs are full of "RF overflows". That will cause issues and all rx/tx timing is wrong. you need to get rid of those.

what exactly do you mean by benchmark tool??

Thanks

andre

On 16/12/22 14:59, Neher, Philipp Albert wrote:

Hi All,

sorry for reposting, but after much more trying I’m still stuck on the

same point, the srsUE won’t connect to the eNB.

Since the last post I also tried with another commercial eNB and with

a “normal (non-RT) Kernel”, but with the same problem.

With the commercial eNB I got the benchmark tool to return “OK” after

500s. But no attach, and no Error-Messages in the EPC-Logs.

Has someone please an idea?

Thank you

Philipp

–

Dipl.-Ing. Philipp Neher

Wissenschaftlicher Mitarbeiter „Echtzeitkommunikation und

Steuerungshardware“

Institut für Steuerungstechnik der Werkzeugmaschinen und

Fertigungseinrichtungen (ISW) Universität Stuttgart

Seidenstraße 36 / Zi. 4.025

70174 Stuttgart

Tel: +49 711 685-84499

E-Mail: philipp.neher at isw.uni-stuttgart.de<mailto:philipp.neher at isw.uni-stuttgart.de>

Web: http://www.isw.uni-stuttgart.de

<http://www.isw.uni-stuttgart.de/><http://www.isw.uni-stuttgart.de/>

*Von:*srsran-users <srsran-users-bounces at lists.srsran.com><mailto:srsran-users-bounces at lists.srsran.com> *Im Auftrag

von *Neher, Philipp Albert

*Gesendet:* Donnerstag, 1. Dezember 2022 16:41

*An:* srsran-users at lists.srsran.com<mailto:srsran-users at lists.srsran.com>

*Betreff:* [srsran-users] [srsUE] Problems connecting to srsENB/srsEPC

with bladeRF

Hi,

I’m just starting out with srsran but for the last few days I’m stuck.

I hope somebody can point me in the right direction:

I just can’t get srsUE to connect to srsENB/srsEPC.

To my understanding it sees the cell but does not connect.

I tried the same config files with the zmq device and that does work

so I think that the problem lies in the RF-part.

I start both srsenb and srsue with the –rf.device_name=bladeRF and

–expert.lte_sample_rates=true options, since I read on the archived

mailing list that that might help.

On the UE PC I used the the “benchmark_radio” and the “pdsch_ue” tool.

The benchmark tool always returns “failed” after a 1000s run with “ 2

gaps, 0 late timestamps, 2 overflows, 0 underflows” but pdsch_ue

report

pdsch_misses=0 and pdsch_BLER=0.

My setup:

2x PCs (i7-7700 16GB RAM) with Xubuntu 22 and 5.15 Kernel

2x BladeRF micro A9

Both BladeRF connected to each other (TX1 to RX1) using RF-cables and

a 20dB attenuator

srsRAN compiled from source (git tag 22.10)

Logfiles and config-files are attached.

Has someone a hint?

Thank you

Philipp

–

Dipl.-Ing. Philipp Neher

Wissenschaftlicher Mitarbeiter „Echtzeitkommunikation und

Steuerungshardware“

Institut für Steuerungstechnik der Werkzeugmaschinen und

Fertigungseinrichtungen (ISW) Universität Stuttgart

Seidenstraße 36 / Zi. 4.025

70174 Stuttgart

Tel: +49 711 685-84499

E-Mail: philipp.neher at isw.uni-stuttgart.de<mailto:philipp.neher at isw.uni-stuttgart.de>

<mailto:philipp.neher at isw.uni-stuttgart.de><mailto:philipp.neher at isw.uni-stuttgart.de>

Web: http://www.isw.uni-stuttgart.de

<http://www.isw.uni-stuttgart.de/><http://www.isw.uni-stuttgart.de/>

_______________________________________________

srsran-users mailing list

srsran-users at lists.srsran.com<mailto:srsran-users at lists.srsran.com>

https://lists.srsran.com/mailman/listinfo/srsran-users

--

Andre Puschmann

Software Radio Systems (SRS)

https://www.srs.io

andre at srs.io<mailto:andre at srs.io>

PGP/GnuPG key: 0x204A85DFEA324D58

fingerprint: 3924 1C60 D52E 81A2 1F2E 0C9D 204A 85DF EA32 4D58

_______________________________________________

srsran-users mailing list

srsran-users at lists.srsran.com<mailto:srsran-users at lists.srsran.com>

https://lists.srsran.com/mailman/listinfo/srsran-users

_______________________________________________

srsran-users mailing list

srsran-users at lists.srsran.com<mailto:srsran-users at lists.srsran.com>

https://lists.srsran.com/mailman/listinfo/srsran-users

--
Robert Falkenberg

Senior Engineer

Software Radio Systems

[Das Bild wurde vom Absender entfernt.]

robert at srs.io<mailto:robert at srs.io>

[Das Bild wurde vom Absender entfernt.]

www.srs.io<file://www.srs.io>

[Das Bild wurde vom Absender entfernt.]

Dortmund, Germany

[Das Bild wurde vom Absender entfernt.]

[Das Bild wurde vom Absender entfernt. twitter]<https://twitter.com/srssystems>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.srsran.com/pipermail/srsran-users/attachments/20221219/a81c7f67/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ~WRD0001.jpg
Type: image/jpeg
Size: 823 bytes
Desc: ~WRD0001.jpg
URL: <https://lists.srsran.com/pipermail/srsran-users/attachments/20221219/a81c7f67/attachment-0001.jpg>