[srsran-users] COTS UE does not see the 5G network

Tue May 31 09:15:48 UTC 2022

Never mind then! My comment applies only if you have a 5G SIM. 4G SIM will work for 5G networks, too.

Looking at the PLMNwAct, are you sure that 5G is enabled there? Seems like you have entries for URAN (0x8000), E-UTRAN (0x4000), and GSM (0x80). NG-RAN would be 0x800 I think. I think sysmocom-ISIM-SJA2 defaults are to set the AcT to 0xffff (enabling all access technologies).

(I’m not even sure if that’s important, just comparing with the USIM that I was using. See here for a dump: https://github.com/osmocom/pysim/blob/master/pysim-testdata/sysmoISIM-SJA2.ok <https://github.com/osmocom/pysim/blob/master/pysim-testdata/sysmoISIM-SJA2.ok> )

Merlin

> On 30. May 2022, at 15:59, Mehdi Jafarizadeh <mehdi at shabodi.com> wrote:
> 
> Hi Merlin,
>  
> Shall we use a 5G-enabled ISIM? Our first guess was that the UE can work with a USIMs, so tried a generic one from Amazon.ca <http://amazon.ca/>: OYEITIMES LTE Cards Program kit SIM Card Tools 1 MCR3516 SIM Card Reader Writer Programmer+5PCS Blank Programmable 4G LTE USIM Cards+5G 5.9.13 Ver. Software Tools : Amazon.ca: Electronics <https://www.amazon.ca/OYEITIMES-MCR3516-Programmer-Programmable-Personalize/dp/B089FJGDFG>
> It comes with a software (that is claimed to be 5G compatible) to configure the parameters; here is ours:
>  
> <3E63FEC5037C44279B344130BAA6CF3A.png>
>  
> If USIM works, is there any parameter that is required to be set other than 1- IMSI, 2- KI, and 3- OPC? 
> (Going to order couple of ISIMs and try them as well anyway)
>  
> Thanks Merlin for your response
> -- Mehdi
>  
> From: Merlin Chlosta <mailto:merlin.chlosta+srslte-users at rub.de>
> Sent: May 30, 2022 4:58 AM
> To: Mehdi jafarizadeh <mailto:mehdi at shabodi.com>
> Cc: srsran-users at lists.srsran.com <mailto:srsran-users at lists.srsran.com>; Nitin Sood <mailto:nitin at shabodi.com>; Harpreet Geekee <mailto:harpreet at shabodi.com>
> Subject: Re: [srsran-users] COTS UE does not see the 5G network
>  
> Hi Mehdi,
>  
> If you’re using a 5G-enabled SIM, try to disable the 5G-related files (or populate them with a valid config). The sysmcom-ISIM comes with all 5G-related files *present and active* but empty. That is not a valid combination particularly for 5G SUCI and Routing Indicator. In my case, the UE threw “USIM Errors” and basically shut down the 5G part of the modem.
>  
> The sysmcom manual (Section 8.1, “Disabling DF_5GS files and services”) suggests this script:
> $ ./pySim-shell.py -p0 --script ./scripts/deactivate-5g.script
>  
> I wrote down my steps a while back: https://gist.github.com/mrlnc/01d6300f1904f154d969ff205136b753 <https://gist.github.com/mrlnc/01d6300f1904f154d969ff205136b753>
>  
> Viele Grüße
> Merlin
>  
> On 28. May 2022, at 01:05, Mehdi jafarizadeh <mehdi at shabodi.com <mailto:mehdi at shabodi.com>> wrote:
>  
> Hi srsRAN Team, <>
>  
> As a new srsRAN user, I followed the instructions in docs.srsran.com <http://docs.srsran.com/> to setup end-to-end LTE as well asSA/NSA 5G labs with a COTS UE:
> Core- Open5Gs v2.4.5
> Radio- BladeRF xA4
> O-RAN- srsRAN
> UE- Samsung Galaxy S21+ 5G (SM-G996W)
>  
> Here is the outcome- The end-to-end LTE network works fine. Though some “GTP Failed” warnings appeared in Open5Gs, the UE found and connected to the LTE network successfully. However, in either SA or NSA 5G networks, the UE could not connect to the network. In both cases, the srsRAN successfully established the connection with MME, but it seems that UE could not find the network.
>  
> Here is our configuration for nr_cell in rr.conf:
> nr_cell_list =
> (
>   {
>     rf_port = 0;
>     cell_id = 1;
>     root_seq_idx = 1;
>     tac = 7;
>     pci = 500;
>     dl_arfcn = 526200;
>     band = 7;
>   }
> );
>  
> And here is the output from srsRAN console:
> Active RF plugins: libsrsran_rf_soapy.so libsrsran_rf_blade.so
> Inactive RF plugins: 
> ---  Software Radio Systems LTE eNodeB  ---
> 
> Reading configuration file enb.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 f2dff0b7a on branch master.
> 
> Opening 1 channels in RF device=default with args=default
> Supported RF device list: soapy bladeRF file
> Trying to open RF device 'soapy'
> NG connection successful
> No Soapy devices found.
> Unable to open RF device 'soapy'
> Trying to open RF device 'bladeRF'
> Opening bladeRF...
> [INFO @ host/libraries/libbladeRF/src/helpers/version.c:79] Firmware version (v2.4.0) is newer than entries in libbladeRF's compatibility table. Please update libbladeRF if problems arise.
> Set RX sampling rate 1.92 Mhz, filter BW: 1.92 Mhz
> RF device 'bladeRF' successfully opened
> 
> ==== eNodeB started ===
> Type <t> to view trace
> Set RX sampling rate 11.52 Mhz, filter BW: 9.22 Mhz
> Setting frequency: DL=2631.0 Mhz, UL=2511.0 MHz for cc_idx=0 nof_prb=52
> set TX frequency to 2631000000
> set RX frequency to 2510999998
> 
> And the tail of the Open5Gs logs:
> 05/27 18:44:28.797: [amf] INFO: gNB-N2 accepted[127.0.1.1]:50078 in ng-path module (../src/amf/ngap-sctp.c:105)
> 05/27 18:44:28.797: [amf] INFO: gNB-N2 accepted[127.0.1.1] in master_sm module (../src/amf/amf-sm.c:619)
> 05/27 18:44:28.797: [amf] INFO: [GNB] max_num_of_ostreams : 30 (../src/amf/context.c:854)
> 05/27 18:44:28.797: [amf] INFO: [Added] Number of gNBs is now 1 (../src/amf/context.c:869)
> 
>  
> Unlike LTE, the logs does NOT reflect that the UE tries to connect. So, I suspected maybe UE operates in a different band from those that are supported by srsRAN. However we tried all the supported bands (nr3, nr7, and nr20) and none worked. Any help to find the root cause of this problem is really appreciated.
> 
> Thanks
> -- 
> Mehdi Jafarizadeh
> 5G Application Developer @ Shabodi
> 
> _______________________________________________
> 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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.srsran.com/pipermail/srsran-users/attachments/20220531/77de8395/attachment-0001.htm>