Multipriority Backoff Timer Control for Wireless Communication Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current wireless communication systems face inefficiencies in managing network congestion for machine-type communication (MTC) devices, particularly in configuring backoff timers for terminals with multiple priority levels, leading to ambiguous operations and reduced system performance.
Innovation Solution
A method for user equipment (UE) configured for multipriority, where a non-access stratum (NAS) request message is transmitted without an access point name (APN) to a network node, initiating a session management (SM) backoff timer, and permitting new NAS requests not set to the first priority level while the SM backoff timer is running.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a single priority level is configured for terminals, then the system operation is simple, but the system cannot effectively manage network congestion for multipriority MTC devices
Solution Approach 1:
The patent segments the backoff timer mechanism into two distinct timers: MM backoff timer for mobility management operations and SM backoff timer for session management operations. This segmentation allows independent control of different operation types, enabling fine-grained priority management for multipriority MTC devices without requiring a complete redesign of the congestion control system.
Solution Approach 2:
The patent introduces dynamic priority-based timer selection where the applicable backoff timer (MM or SM) is determined based on the priority level of the operation and current network conditions. High-priority operations can bypass certain timer restrictions while low-priority operations are subject to stricter backoff controls, creating a dynamic adaptation mechanism that responds to changing network states.
2Reliability
If backoff timers are used to distribute network load, then network congestion is reduced, but terminal operations are restricted during timer running period
Solution Approach 1:
The patent applies different backoff timer restrictions to different operation types based on their priority levels. Mobility management operations and session management operations are subject to different timer constraints (MM backoff timer vs. SM backoff timer), allowing critical operations to maintain higher flexibility while non-critical operations are more strictly controlled during congestion periods.
Solution Approach 2:
The patent changes the backoff timer parameters dynamically based on operation priority and network congestion state. The timer values and applicability are adjusted according to the specific operation type and current network conditions, allowing the system to optimize between congestion control and operation flexibility by modifying timer parameters rather than using fixed restrictions.
3Adaptability or versatility
If priority is configured per terminal with only two levels, then the configuration is simple, but the system cannot handle diverse priority requirements of multipriority MTC devices
Solution Approach 1:
The patent adds a new dimension to priority management by introducing operation-type-based timer differentiation. Instead of only increasing the number of priority levels, the system creates a two-dimensional control space: one dimension for traditional priority levels and another dimension for operation type (MM vs. SM operations). This allows multipriority devices to maintain fine-grained control without requiring an excessive number of priority levels.
Data Source
AI summary
A method of controlling a backoff timer at a user equipment (UE) configured for dual priority, the method includes transmitting a non access stratum (NAS) request message without an access point name (APN) including a low priority indicator set to a first value to a network node, wherein the first NAS request message without the APN is an attach request message transmitted along with a packet data network (PDN) connectivity request without the APN; receiving a reject message for the NAS request message from the network node, and wherein a cause in the reject message is set to insufficient resources; setting the low priority indicator to a second value; and initiating a new attach procedure without the APN, while a session management (SM) backoff timer is running, wherein the first value of the low priority indicates that the UE is configured for NAS signaling low priority.


