Dynamic Inactivity Timer Thresholds for Radio Connection Closure
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing wireless communication networks face challenges in efficiently detecting the end of service to close radio connections promptly, especially when multiple services are active or data is sent sporadically, leading to resource wastage.
Innovation Solution
Implementing dynamic inactivity timer thresholds for each flow, where the inactivity timer threshold for a first flow is determined based on the inactivity timer thresholds of second flows mapped to it, allowing for timely detection of inactive flows and closure of radio connections.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If a fixed inactivity timer threshold is used for all flows, then the system is simple to implement, but the radio connection cannot be closed promptly when services end, leading to resource wastage
Solution Approach 1:
The patent divides the single inactivity timer mechanism into multiple flow-specific inactivity timers, each tracking inactivity periods for individual flows separately. This segmentation allows the system to detect end-of-service conditions more precisely for each flow, enabling timely radio connection closure while maintaining manageable complexity through structured organization of timer instances.
Solution Approach 2:
The patent implements dynamic inactivity timer thresholds that adapt based on flow characteristics and service types rather than using fixed thresholds. The timer values are adjusted dynamically according to the specific service requirements and traffic patterns, allowing optimal resource release timing without requiring complex manual configuration for each scenario.
2Loss of time
If inactivity timers are monitored at a high level without flow-specific tracking, then the implementation is straightforward, but the delay in detecting end of service increases, wasting communication resources
Solution Approach 1:
The patent segments the monitoring function by creating separate inactivity timer instances for each flow, allowing independent tracking of inactivity periods. This enables the system to detect when individual flows become inactive without waiting for aggregate conditions, significantly reducing end-of-service detection delay while organizing complexity through consistent per-flow treatment.
Solution Approach 2:
The patent establishes inactivity timers for each flow at the beginning of service, performing preliminary tracking setup before service completion needs to be detected. This preliminary action ensures that when services end, the system has already been accumulating inactivity data, enabling immediate detection and prompt resource release without additional processing delay.
Data Source
Figure 1
Figure 2
Figure 3A~3B
AI summary
Techniques to detect for end of service using dynamic inactivity timer thresholds are described. An access terminal establishes a radio connection for one or more applications. Data and signaling for the application(s) may be sent on one or more first flows (e.g., RLP flows) that may carry any number of second flows (e.g., IP flows). The access terminal determines a dynamic inactivity timer threshold for each first flow, e.g., based on at least one inactivity timer threshold for at least one second flow mapped to that first flow. The access terminal determines whether each first flow is inactive based on the inactivity timer threshold for that first flow, e.g., declares each first flow to be inactive if no activity is detected on that first flow for a period exceeding the inactivity timer threshold. The access terminal closes the radio connection when all first flow(s) are determined to be inactive.