Network-Side Mobility Context Timer for Signaling Reduction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The absence of a specified value for storing the mobility management context at the network side leads to increased signaling consumption and network load, as mobility management contexts are either deleted too early or too late, affecting resource utilization.
Innovation Solution
Implementing a context timer system on the network-side device to manage mobility management contexts, where a first timer is started after network congestion and the context is kept or deleted based on whether requests are accepted or rejected before the timer expires, and a second timer is used to differentiate between accepted and rejected terminals.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If the mobility management context is deleted at the network side too early, then network load is reduced, but signaling consumption increases due to repeated interactions with HSS/HLR
Solution Approach 1:
The network side performs preliminary actions by storing the mobility management context in advance and setting a context timer, so that when the UE reattaches, the context is already available and no additional signaling with HSS/HLR is needed. This preliminary preparation resolves the contradiction by having the context ready beforehand, reducing both network load and signaling consumption.
Solution Approach 2:
The patent replaces the mechanical signaling interaction between MME/SGSN and HSS/HLR with a stored context mechanism. Instead of repeatedly querying HSS/HLR (mechanical system), the network side uses a local context storage system with timer-based management, substituting the complex signaling mechanism with a simpler storage-and-retrieval approach.
2Loss of information
If the mobility management context is kept for a long period, then signaling consumption is reduced, but network load increases due to stored context data
Solution Approach 1:
The patent applies dynamics by making the context storage duration flexible rather than fixed. The context timer is dynamically adjusted based on network conditions and UE behavior, allowing the system to optimize between keeping context longer (reducing signaling) and deleting it sooner (reducing network load). This dynamic adjustment resolves the contradiction.
Solution Approach 2:
The patent changes the parameter of context storage time from a static value to a configurable parameter controlled by the context timer. By adjusting the timer value, the network can optimize the balance between signaling consumption and network load based on current conditions, resolving the contradiction through parameter optimization.
3Device complexity
If no context timer is used, then device complexity is reduced, but resource utilization deteriorates due to inappropriate context retention
Solution Approach 1:
The context timer enables the system to serve itself by automatically managing context retention without external intervention. The timer self-regulates the context lifecycle, deleting contexts that are no longer needed and retaining those that might be useful, thereby optimizing resource utilization with minimal additional complexity.
Solution Approach 2:
The context timer acts as an intermediary between the context storage mechanism and the network resources. It mediates the retention decision, balancing the need to keep context for potential reuse against the cost of storing it, thereby optimizing resource utilization without significantly increasing system complexity.
Data Source
AI summary
Embodiments of the present application relate to the technical field of wireless communications, relating specifically to a method and a device for handling a mobility management context, for use in solving the problem in the prior art of an increase in signaling consumption or network load due to the absence of a defined duration of storage for the mobility management context on a network side. The method comprises: upon a network congestion and rejecting a request from a terminal, a network side device activating a first context timer for the terminal; if the request of the terminal is received and accepted before the first context timer times out, the network side device retaining a mobility management context corresponding to the terminal; if the request of the terminal is not received, or is received but not accepted before the first context timer times out, the network side device deleting the mobility management context corresponding to the terminal. As the duration of storage is defined for the mobility management context on the network side, the signaling consumption and the network load are thereby reduced.