COTS dropping connection to gNB #100
-
Hi I have a problem when using the gNB when connected to COTS handsets, in that the handset seems to drop the connection to the gNB for no obvious reason. My set up is a X310, externally locked to a gps reference clock with the Open5GS core. I have two phones and the behaviour is slightly different for each. I can connect a google Pixel 6a to the gNB. It is happy and I get really good signal to noise ratios in the uplink (around 30dB) and downlink (around 28dB). and I see really clean constellations. It works fine, I can stream video etc, then after 3 minutes I see the "5G" connection disappear from the phone screen. After a short while the gNB issues a UeContextReleaseRequest. I see no errors or warnings in any of the Open5GS or gNB logs. If I put the handset in flight mode, then back out, it immediately reconnects to the gNB, and it is happy for 3 minutes again before losing the connection to the gNB. I have also tried a OnePlus phone. The situation here is slightly different in that the phone will connect to the gNB but lose the connection after a few seconds. I have also used the previous code base in https://github.com/srsran/srsRAN_4G running as a 5G SA network and the OnePlus phone will work in that setup and will remain connected for many hours. Everything else is the same in this setup, the X310 connected to external references and the Open5GS core. I'm struggling to see any reason why the phone disconnects in the new https://github.com/srsran/srsRAN_Project code base. Has anyone seen a similar situation? |
Beta Was this translation helpful? Give feedback.
Replies: 16 comments 12 replies
-
Hi @jonniebeeb , Thanks for your feedback. Can you send us gnb logs in info and pcap captures? You can enable them in the gnb.yml config file. |
Beta Was this translation helpful? Give feedback.
-
Hi @ismagom I have also captured for the OnePlus. This disconnects after a few seconds. Hope these help you diagnose the issue. Please let me know if you need any more captures. Thanks [gnb_pixel_info.zip](https://github.com/srsran/srsRAN_Project/file gnb_mac_pixel_1.zip gnb_ngap_pixel.zip |
Beta Was this translation helpful? Give feedback.
-
I think I see where the pixel disconnects in the log file at around 2023-06-20T09:55:06.029334. I see good snr in the PUSCH (around 32dB) then there is a sudden drop in snr to about -23dB and crc failures. There is no obvious cause for this. 2023-06-20T09:55:06.029334 [SCHED ] [I] [ 634.3] Slot decisions cell=0 t=6us: UL: ue=0 rnti=0x4601 h_id=0 ss_id=2 prb=[3..4) rv=0 tbs=76 |
Beta Was this translation helpful? Give feedback.
-
Thank you for your reply. I think you may be looking at the wrong log files :-/ I don't see any lines as you've pasted above, and my log files were taken on the 20th, not the 19th. I noticed one of my links has got mangled. The log file links are gnb_pixel_info.zip Note, I already have VoLTE turned off on the phones. Thanks |
Beta Was this translation helpful? Give feedback.
-
Hi @jonniebeeb , I also can't see anything at first sight. What kind of traffic are you doing? Can you send logs with |
Beta Was this translation helpful? Give feedback.
-
Hi @Ismagon I am streaming video, it is using about 10Mbits/sec. I am using the main branch of the code that was updated 3 weeks ago. I have also tried the release 23.5 tag - the behaviour is the same in either case. I am using the phone in a screened box so I don't believe it is signal variation that is causing the connection failure. The pixel phone seems to disconnected after 3 minutes every time. It's as if something times out. I have attached my gnb.yaml file and some logs with phy_level = debug. [gnb_rf_n310_fdd_n3_20mhz_j.zip](https://github.com/s gnb_mac_pixel_21.z03.zip Thanks |
Beta Was this translation helpful? Give feedback.
-
one of the urls got mangled again. The gnb.yaml file |
Beta Was this translation helpful? Give feedback.
-
Hi @jonniebeeb , the problem in the two phones is different. In the oneplus, the problem seems to be here:
The gNB is releasing the UE because it can't find the 5QI 5. You can try adding that 5QI to the
I would also recommend to upgrade to the latest release (from last monday) since there are improvements in handling a second bearer. Regarding the pixel6, we are still investigating. The signal looks good in DL and UL and there is no signalling coming from the network to indicate a Release to the UE. For some reason it just disconnects abruptly. Can you try with other type of traffic such as ping? thanks |
Beta Was this translation helpful? Give feedback.
-
Hi @ismagom I have tried a few things. I have pulled the latest code and rebuilt. I have tried the pixel6 again, this time just sending pings from the UE to the upf and from the upf to to the UE. It still disconnects after 3 minutes. I also removed the 5QI 5 with the OnePlus. This has removed the previous "No valid config for 5QI 5" error. It still disconnects after a short while. I have attached the log files for each thanks |
Beta Was this translation helpful? Give feedback.
-
What's the exact OnePlus model? |
Beta Was this translation helpful? Give feedback.
-
It is a OnePlus Nord CE 2 (IV2201) . This phone worked well with the srsRAN_4G code base configured in a 5G SA mode. I could stream video for hours without interruption. |
Beta Was this translation helpful? Give feedback.
-
We can reproduce the issue with a Pixel 6 phone. It quietly disconnects 180sec after RRC Setup Request. We are investigating the issue. |
Beta Was this translation helpful? Give feedback.
-
The Pixel 6 drops the connection if IMS is not configured within 180sec after attach. Fortunately, you can change the timeout or disable this feature entirely via hidden IMS settings menu:
The settings are associated with the SIM card and persistent across reboots, i.e. the UE remembers the settings for each SIM separately. |
Beta Was this translation helpful? Give feedback.
-
Wow ! Well done for finding that. I am out of the lab today, but will be able to try that out on Monday. Many thanks for looking into this. |
Beta Was this translation helpful? Give feedback.
-
I apologize for asking about an unrelated matter. I am also using a Pixel 6a but I am not able to see the srsRAN network. I am using the same config file as the one provided by @jonniebeeb, adapted to use a b210 as RF frontend. How did you configure the smartphone to see the 5GSA cell? I tried a mix of everything: suggestions from the docs tutorial, root rights to force or exclude bands, etc. Nothing worked so far. |
Beta Was this translation helpful? Give feedback.
-
@robertfalkenberg Wanted to add to the conversation. My experience was different because the first thing I did when I obtaned the Google Pixel 6 phones was update to Android 13. All two of my Google Pixel Phones could not see the network at all so I spent a lot of time debugging. I had tested the Pixel 6 and it was the best perfoming UE so I was thinking it was my RAN config that was wrong. I then tested with the Huawei P40 which uses another system than Android and it connected. So I shifted the blame to Android 13. I wanted to roll back the update to maybe Android 10 but then unlike what you did, "I tried nothing but a factory reset to bring 5G back". So for individuals with nothing to lose on the phones, a reset is the faster way to try get your signal back. |
Beta Was this translation helpful? Give feedback.
The Pixel 6 drops the connection if IMS is not configured within 180sec after attach.
Fortunately, you can change the timeout or disable this feature entirely via hidden IMS settings menu:
*#*#0702#*#*
Both options work:
NR_TIMER_WAIT_IMS_REGISTRATION
from default180
to-1
SUPPORT_IMS_NR_REGISTRATION_TIMER
from default1
to0
The settings are associated with the SIM card and persistent across reboots, i.e. the UE remembers the settings for each SIM separately.