Mobile Terminal Timer Expiration Period Optimization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Recent mobile terminals frequently transition between connected and idle states due to periodic application communications, leading to an increased load on mobile core networks as they process a high number of control signals, which is not effectively managed by existing timer expiration period adjustments based solely on communication frequency and battery power.
Innovation Solution
A method to determine the expiration period of a timer for transitioning from a connected to an idle state in mobile terminals, considering parameters such as connection frequency, load on control signal processing, movement between base stations, and software installed on the terminal, to adjust the number of control signals processed by the mobile core network.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Use of energy by moving object
If the timer expiration period is shortened to enable mobile terminals to quickly transition to idle state and save power, then power efficiency is improved, but the number of control signals processed by the mobile core network increases due to frequent CONNECTED-IDLE transitions
Solution Approach 1:
The patent applies dynamics by making the timer expiration period adjustable rather than fixed. The mobility management node dynamically changes the timer expiration period based on the terminal's communication characteristics and network conditions, allowing the system to adapt between power saving and control signal reduction scenarios
Solution Approach 2:
The patent changes the parameter of timer expiration period based on multiple factors including communication frequency, network load, terminal mobility, and QoS requirements. This parameter adjustment resolves the contradiction by optimizing the balance between power efficiency and control signal processing load
2Productivity
If the timer expiration period is lengthened to reduce control signal processing load, then network load is reduced, but power efficiency deteriorates as terminals remain in connected state longer than necessary
Solution Approach 1:
The system dynamically adjusts the timer expiration period based on real-time network conditions and terminal behavior patterns, preventing both excessive power consumption and unnecessary control signal processing
Solution Approach 2:
The mobility management node monitors terminal communication patterns and network load, using this feedback to continuously optimize the timer expiration period setting for each terminal, achieving optimal balance between power efficiency and network load
3Device complexity
If the timer expiration period is adjusted based solely on communication frequency and battery power, then power management is simplified, but the system cannot effectively manage high control signal loads from periodic application communications
Solution Approach 1:
The patent extends the timer adjustment mechanism to consider multiple factors beyond just communication frequency and battery power, including terminal mobility, network load, and QoS requirements, making the system universally applicable to diverse communication scenarios
Solution Approach 2:
The patent segments the timer expiration period determination into multiple independent factors (communication frequency, network load, terminal mobility, QoS), allowing each factor to be evaluated and weighted separately for optimal decision making
Data Source
AI summary
A network node (300) determines an expiration period of a timer (101) based on a predetermined parameter. The timer (101) is used to determine a transition from a CONNECTED state to an IDLE state of a mobile terminal (200) connected to a core network (20) through a radio access network (10). The predetermined parameter includes at least one of (a) a parameter regarding a frequency of connection of the mobile terminal (200) to the core network (20), (b) a parameter regarding a load on control signal processing by a mobility management node (300) arranged in the core network (20), (c) a parameter regarding a frequency of movement of the mobile terminal (200) between base stations (100), and (d) a parameter regarding software installed in the mobile terminal (200).


