| Discussion and conclusion:
Not Handled.
TD S2 160187 (DISCUSSION) Discussion on Inactivity timer for eDRX. (Source: Alcatel-Lucent, Alcatel-Lucent Shanghai Bell).
Abstract: This paper discusses how to keep E-UTRAN and UTRAN RRC connection alive long enough to allow the Core Network or an application (such as SMS-MT) to send signalling or data after the detection of the UE by the Core Network. It also discusses the specific case of GERAN as in that case, the MS that should remain in READY state long enough.
Decision:
The document was noted.
TD S2 160525 23.401 CR2957R1 (Rel 13, 'F'): Inactivity timer for eDRX. (Source: Alcatel-Lucent, Alcatel-Lucent Shanghai Bell). (Revision of TD S2 160188).
Abstract: Summary of change: For a UE for which eDRX has been enabled, if the MME is aware that some signalling or data is pending in the network for that UE (e.g. pending MT SMS at the SMS Service Center, or an application has subscribed to UE reachability), the MME should include a 'minimum user inactivity time' in the next Initial Context Setup Request message towards the eNB. The eNB shall not release the RRC connection due to user inactivity before expiration of the 'minimum user inactivity time' (the RRC connection may be released before that expiration for other causes such as Radio Connection With UE Lost). For the cases when the UE is handed over to another eNB shortly after the UE-CN connectivity is established, the 'minimum user inactivity timer' should also be sent in the Handover Request message. With this solution, the user inactivity period may be extended only for the scenarios where there is pending MT signalling or data for a UE. In all other scenarios (e.g. MO signalling w/o pending MT signalling), there won't be any change, i.e. the existing user inactivity timer is used.
Parallel discussion: Should be opened only if some offline agreement can be made on this issue.
Dostları ilə paylaş: |
