srsran / srsRAN_4G

Open source SDR 4G software suite from Software Radio Systems (SRS) https://docs.srsran.com/projects/4g
https://www.srsran.com
GNU Affero General Public License v3.0
3.49k stars 1.15k forks source link

4G end-to-end network : [PHY] Synchronisation problem #1123

Open CatiaS11 opened 1 year ago

CatiaS11 commented 1 year ago

Issue Description

I am trying to establish end-to-end 4G network and I have encountered an issue with SFN synchronization running the UE. After the message that SFN is not yet synchronized I get the message about SNR and RSRP status.

Setup Details

The setup I’m using is : 2 PC + 2 bladeRF -> 1st PC – running the UE -> 2nd PC – running the ENB and EPC in separate consoles

Expected Behavior

I want to connect the 1st PC to 4G network of the 2nd PC.

Actual Behaviour

UE Synchronozation error message [PHY] SFN not yet synchronized, sending out-of-sync [PHY] SNR = 2.3 dB RSRP = -86.8 dBm, sync=out-of-sync from channel estimator

Log UE : log_ue

Log EPC : log_epc

Log ENB : log_enb

Steps to reproduce the problem

I have tried to change different parameters in ue.conf file testing different tx and rx gains but without success. Also I put the same usim informations in user_db.csv file and I named the APN the same way in ue.conf and epc.conf file. I have ip_forwarding activated on both computers and I switched cpu on performance mode. I’ve tried to use srate=11.52e6 in ue.conf file but it gets even worse. Here are the pictures of my logs and ue.conf files.

UE.conf file : ue_conf1

ue_conf2

ue_conf3

ue_conf4

ue_conf5

Additional Information

Before using 2 bladeRFs, I managed to connect to 4G network using a cellphone Pixel 6 with a programmable sim as UE, so the problem is probably in my UE.conf file.

Egwel commented 1 year ago

can you expound for me how you managed to connect the phone and which programmable sim you used.

otherwise i am also facing a syncronisation issue : and i can't attach it to the network

the srsue log file looks like this

2023-04-12T11:19:33.004544 [UE ] [I] Using binary srsue with arguments: --rf.device_name bladeRF 2023-04-12T11:19:34.292402 [UE ] [I] Built in Release mode using commit 5a4eb5d6c on branch master. 2023-04-12T11:19:34.550017 [STCK ] [E] Unknown PCAP option true 2023-04-12T11:19:35.306403 [PHY ] [W] [ 33] SYNC: radio time seems to be going backwards (rx_time=0.024460, tti_ts=0.140761) 2023-04-12T11:19:35.457575 [MAC ] [W] [ 4514] RA response not received within the response window 2023-04-12T11:19:35.477578 [MAC ] [W] [ 4534] RA response not received within the response window 2023-04-12T11:19:35.497540 [MAC ] [W] [ 4554] RA response not received within the response window 2023-04-12T11:19:35.517542 [MAC ] [W] [ 4574] RA response not received within the response window 2023-04-12T11:19:35.537469 [MAC ] [W] [ 4594] RA response not received within the response window 2023-04-12T11:19:35.557556 [MAC ] [W] [ 4614] RA response not received within the response window 2023-04-12T11:19:35.577600 [MAC ] [W] [ 4634] RA response not received within the response window 2023-04-12T11:19:35.597483 [MAC ] [W] [ 4654] RA response not received within the response window 2023-04-12T11:19:35.617471 [MAC ] [W] [ 4674] RA response not received within the response window 2023-04-12T11:19:35.637500 [MAC ] [W] [ 4694] RA response not received within the response window 2023-04-12T11:19:35.637502 [MAC ] [E] [ 4694] RA: Rx: Maximum number of transmissions reached (10) 2023-04-12T11:19:35.637503 [RRC ] [W] MAC indicated RA problem but either T300, T301, T304 or T311 is running. Ignoring it. 2023-04-12T11:19:37.432537 [RRC ] [W] Proc "Connection Request" - Timer T300 expired: ConnectionRequest timed out 2023-04-12T11:19:37.432615 [RRC ] [W] Could not establish connection. Deallocating dedicatedInfoNAS PDU 2023-04-12T11:19:50.362060 [NAS ] [W] Timer T3410 expired after attach attempt 1/5: starting T3411 2023-04-12T11:20:00.361049 [PHY ] [W] [ 8952] SYNC: TTI jump of 125452 limited to 1000

CatiaS11 commented 1 year ago

Hello,

Honestly, I’ve never had the issue of synchronization using the phone with a sim card, so I can’t really say how to solve your problem. However here are the steps I followed. 1/ Read your programmable card on sim reader 2/ Put the key, opc and IMSI in user_db.csv file with mil authentification algo 3/ Give a name to your apn in epc.conf file 4/ Create an APN point on your phone (the same name as you’ve given in the epc.conf file) 5/ You can also configure your preference for LTE network (it’s not mandatory though) 6/ Put your CPUs in performance mode 7/ Allow ip forwarding 8/ Run the masquerading script of wlan0 network 9/ Run srsEPC and then srsENB file Finally, if everything is ok, you should see the srsRAN network appear in the list of available networks.

Good luck, Ecaterina

De : Egwel @.> Envoyé : vendredi 14 avril 2023 15:03 À : srsran/srsRAN_4G @.> Cc : SCERBACOVA Ecaterina @.>; Author @.> Objet : Re: [srsran/srsRAN_4G] 4G end-to-end network : [PHY] Synchronisation problem (Issue #1123)

can you expound for me how you managed to connect the phone and which programmable sim you used.

otherwise i am also facing a syncronisation issue : and i can't attach it to the network

the srsue log file looks like this

2023-04-12T11:19:33.004544 [UE ] [I] Using binary srsue with arguments: --rf.device_name bladeRF 2023-04-12T11:19:34.292402 [UE ] [I] Built in Release mode using commit 5a4eb5dhttps://github.com/srsran/srsRAN_4G/commit/5a4eb5d6cd741e90ba0d0c96e187a442a849131e on branch master. 2023-04-12T11:19:34.550017 [STCK ] [E] Unknown PCAP option true 2023-04-12T11:19:35.306403 [PHY ] [W] [ 33] SYNC: radio time seems to be going backwards (rx_time=0.024460, tti_ts=0.140761) 2023-04-12T11:19:35.457575 [MAC ] [W] [ 4514] RA response not received within the response window 2023-04-12T11:19:35.477578 [MAC ] [W] [ 4534] RA response not received within the response window 2023-04-12T11:19:35.497540 [MAC ] [W] [ 4554] RA response not received within the response window 2023-04-12T11:19:35.517542 [MAC ] [W] [ 4574] RA response not received within the response window 2023-04-12T11:19:35.537469 [MAC ] [W] [ 4594] RA response not received within the response window 2023-04-12T11:19:35.557556 [MAC ] [W] [ 4614] RA response not received within the response window 2023-04-12T11:19:35.577600 [MAC ] [W] [ 4634] RA response not received within the response window 2023-04-12T11:19:35.597483 [MAC ] [W] [ 4654] RA response not received within the response window 2023-04-12T11:19:35.617471 [MAC ] [W] [ 4674] RA response not received within the response window 2023-04-12T11:19:35.637500 [MAC ] [W] [ 4694] RA response not received within the response window 2023-04-12T11:19:35.637502 [MAC ] [E] [ 4694] RA: Rx: Maximum number of transmissions reached (10) 2023-04-12T11:19:35.637503 [RRC ] [W] MAC indicated RA problem but either T300, T301, T304 or T311 is running. Ignoring it. 2023-04-12T11:19:37.432537 [RRC ] [W] Proc "Connection Request" - Timer T300 expired: ConnectionRequest timed out 2023-04-12T11:19:37.432615 [RRC ] [W] Could not establish connection. Deallocating dedicatedInfoNAS PDU 2023-04-12T11:19:50.362060 [NAS ] [W] Timer T3410 expired after attach attempt 1/5: starting T3411 2023-04-12T11:20:00.361049 [PHY ] [W] [ 8952] SYNC: TTI jump of 125452 limited to 1000

— Reply to this email directly, view it on GitHubhttps://github.com/srsran/srsRAN_4G/issues/1123#issuecomment-1508475002, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A6UMORK73UYGBGH4ZNSS3QDXBFDKBANCNFSM6AAAAAAWCUJ5A4. You are receiving this because you authored the thread.Message ID: @.***>


This email was sent from a company of the UTAC group which headquarters are located at UTAC Group, registered in France under number 888 609 963 and VAT number FR47888609963. This message is intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to us, and delete it permanently. Do not use, copy or disclose the information contained in this message or in any attachment. Thank you for your collaboration.

Ce message est envoyé par une société du groupe UTAC dont le siège social est UTAC Group, enregistrée en France sous le numéro 888 609 963 et numéro de TVA intracommunautaire FR47888609963. Ce message est à l’attention exclusive de son destinataire et peut contenir des informations confidentielles. Si vous avez reçu ce message par erreur, merci d’en aviser l’émetteur, et d’en détruire le contenu de manière définitive. Vous ne devez ni copier, ni utiliser, ni divulguer son contenu ou celui de toute pièce jointe à qui que ce soit. Merci de votre collaboration.