"Received RRC Release" at UE in ZMQ mode

[Zplusless]

Hi, I'm testing the latest master branch (4d9f223) in zmq mode. The UE received "Received RRC Release" shorly after a successful attachment like below:

However, if I using previous version of gnb (like 0b2702c which is updated on 20240115), both gnb and ue works well.

Below are configs and logs:
20240323 Received RRC Release.zip

[Zplusless]

Another strange thing. I ping 10.45.0.1 from UE immediately after UE attachment, the ping works well and no "Received RRC Release". However, if I stop the ping process, "Received RRC Release" shows up at UE in less than 3 seconds. Hope this can help for debugging.

[herlesupreeth]

Thats because in the latest code the inactivity timeout is reduced to 5 seconds. i.e if the UE has no activity for 5 seconds then RRC is released

[Zplusless]

hi @herlesupreeth, thanks for your reply. Since it's not a bug. If UE starts sending data after an RRC release, how to reestablish the RRC? In our case, after the release, the UE cannot send data anymore. It seems that RRC reestablishment is not applicable for srsRAN gnb + srsue.

[Zplusless]

I find several parameters relating to RRC timer in the Configuration Reference. Will changing these parameters help? 5 seconds is not enough. In current version, if srsue fails to send any data after UE attachment in 5 seconds, we will have to kill srsue and gnb and restart again.

[pgawlowicz]

@Zplusless you need this parameter:

cu_cp:
  inactivity_timer: 7200            # Sets the UE/PDU Session/DRB inactivity timer to 7200 seconds. Supported: [1 - 7200].

[Zplusless]

@pgawlowicz Thank you very much. I will close this discussion as resolved.