Yes, I got to know this from Huawei guys. I even don’t know timer name.
In many documents, inactive to idle transition is labeled as FFS (For further study).
Other network guys, any idea what value Ericsson, Nokia & Samsung use?
In the latest release of 38.331, I don’t see any FFS, it says only way for UE to move from Inactive to Idle is after Resume Request or RRC Release.
Hello dears.
I’ve read all this conversation (>40 replies), and now i would like to ask exact steps the way UE goes to idle.
Is it like gNB will send direct rrc-release to UE (let’s say which is on inactive state) upon data inactivity around 1500s?
Or during inactivity UE sends RRC resume request & then gNB respond with RRC release or RRC reject?
So on RRC inactive state any of the 5 senario can happen looks like if S1 executes it will go to Connected if S4 executes it will be on inactive only.
If S3 triggered then only ue can go to idle , now seems like this scenario can happen only after 1500s (correct me if i wrong here.
Hi NR Experts.
So how UE move from RRC inactive to RRC idle - Is it via RRC resume or directly?
Resume is when UE moves from RRC_INACTIVE to RRC_CONNECTED.
RRC_INACTIVE to RRC_IDLE, only reason I could think of is abnormal release.
Thanks!
Just checking… is there any way to move directly from RRC inactive to RRC idle without RRC resume?
Any possibility?
There is one possibility…expiry of t380 and also if gNB has some configured maximum inactivity time for an UE.
In the both the cases, gNB can send UE from RRC_Inactive to RRC_IDLE.
If RRC Inactive state is enabled in gNB and UE also support it, then RRC Connected->RRC Inactive transition can be done as follows
gNB check DRB Inactivity timer and SRB inactivity timer/RRC Inactivity timer. if both are expired , then UE is RRC released with suspend config in it. (RRC Connected → RRC Inactive)
In RRC Inactive state , If UE have UL data to send, it will initiate RRC resume request.
If UE have DL data, RAN paging will happen.
If there is no DL/UL data for UE, it will keep doing periodic RNA update every T380.
If UE spent 1500 s (vendor specific) without any DL/UL data, gNB will release UE context and when UE performs next RNA update gNB will send RRC release to UE.
If UE initiate any UL data while RRC inactive and gNB has already released UE context, then gNB will initiate RRC setup in response to RRC resume by UE. This is to setup UE context again.
1 Like
Ok thanks!
So it’s like without RRC resume as required for RNA update UE can’t move from RRC inactive to RRC idle.
It’s like RRC inactive → RRC resume for RNA update → RRC release
Correct!
I’m considering like RRC inactive → RRC idle can be possible without RRC resume in between.
It’s not possible directly.
Because RRC Release has to be communicated to UE by gNB.
UE cannot do RRC release autonomously.
Yes, still in RRC inactive considering no activity no RNA update then does UE remain there?
RNA update is periodic.
Till then if no data activity UE remain in Inactive state.
And what will happen if (UeInactivityTimer)=0 on the NR side?On the 4G side UeinactivityTimer for QCI 1=60s and for others QCIs 10s. I had an issue that UE without any DL/UL data didn’t go to idle state on 4G side for more than 10s, more than 15s. Any idea?
Any update?