Section: A.25 Evaluation of long inactivity timer
Content: The services from the point of view the time between the newly successful RRC connection setup and the last RRC Connection Release can be divided into the two groups. First group is build from the services the time is quite long (tens of minutes or hours) while for the second group it is tens of seconds. Typical example of the service from the first group can be VoLTE call with a common characteristic that data transmission is accumulated into the time period the call is active without any long interruptions and sufficiently long period between the two consequent calls from the same UE. A second type of service can be web browsing with a common characteristic that data transmission is accumulated into the smaller time periods the service is active i.e. with long interruptions between data transmissions. In the past operators had only option to set the inactivity timer commonly for all kind of services. This may lead to the situation that for the services from the first group UE had to spend ineffectively longer time in RRC Connected state which had negative impact on UE’s battery live. On the other hand for the services from the second group the inactivity timer setting can be insufficient which then may lead to significant increase of the UE movements from RRC Idle to RRC Connected state. Operators shall therefore accurately tune the inactivity timers to avoid some bottlenecks in the RRC Connection setup on one side and prolongation of the UE’s battery life on the second side. Especially regarding the services where long inactivity timer applies operator needs to have an option to estimate how intended prolongation of the long inactivity timer is going to decrease the number of RRC Connection Setups on one side and prolong the UEs’ state in RRC Connected state on second side, using the "Number of successful RRC connection setups in relation to the time between successful RRC connection setup and last RRC connection release".