RRC connection Request /release

[eta004]

Hi,

Do RRC connection request and release base on application type.?

Eg. I am using an app to play a video, but before opening the app , some background data initiated rrc connection request - est cause mo-data

So will my video app request RRC connection request again or the one already in place is enough?


Similarly, for rrc connection release, the background app stopped its data traffic but my video is still playing ..So does it mean I will have only one rrc release in logs pertaining to the last data activity ...In other words, does RRC connection release solely depend on UE inactivity timer instead of whether the app stopped it data traffic or not??

[rimeka]

RRC connection is only one for a Ue. RRC is connection between Ue and eNodeB only.

Beside RRC for signaling, Ue also setup ERAB for data radio bearer (DRB). DRB is bearer from UE to SGW/PGW.
Ue can have more than one DRB depend on QOS needed. Its upto 8 bearer for a single Ue . During attach procedure Ue will have one default bearer (1 DRB). When Ue need another bearer with different QoS (example for volte call) it will request another DRB that named dedicated bearer.
When volte call end, the dedicated bearer is release. RRC connection is still there. When Ue has no activity after RRC inactivity timer expired, enodeB will release the RRC.

[eta004]

Okay RRC is clear , So for eg. For data browsing or video streaming if the QoS set by operator is Same for both , then there won't be a new DRB?