Base Station Connection Resume Reject Handling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current communication technologies face issues where user equipment (UE) fails to interpret rejection messages from base stations, leading to resource wastage and increased power consumption due to improper operations after connection resume requests are rejected.
Innovation Solution
Implementing a method where base stations send connection resume reject messages to UE with specific cause values indicating rejection reasons, allowing UE to perform appropriate processing and reducing power consumption by informing it of rejection causes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If base station sends rejection message without cause value, then message structure is simple, but UE cannot interpret rejection properly leading to resource waste and increased power consumption
Solution Approach 1:
The rejection message is segmented into essential components: a basic rejection indication and an optional cause value field. This segmentation allows the message to convey minimal information (rejection status) while optionally including additional information (cause value) when needed, thus resolving the contradiction between information completeness and message simplicity.
Solution Approach 2:
The cause value field is implemented as an optional partial action - it is included only when specific rejection scenarios require additional information. This partial inclusion of information allows the system to maintain simple message structures for common cases while providing enhanced information when necessary, balancing message complexity with information completeness.
2Reliability
If UE continuously attempts connection without understanding rejection cause, then connection resumption may eventually succeed, but power consumption increases and resources are wasted
Solution Approach 1:
The cause value in the rejection message provides feedback to the UE about why the connection resumption was rejected. This feedback enables the UE to understand the rejection reason (such as integrity check failure, network overload, or prohibited access) and adjust its behavior accordingly, rather than blindly retrying connections and wasting power.
Solution Approach 2:
The UE uses the cause value information to self-adjust its connection resumption strategy. For example, upon receiving an integrity check failure cause, the UE can autonomously discard the resume message and initiate a new connection procedure, or upon receiving network overload indication, it can delay retry attempts. This self-service capability reduces unnecessary power consumption while maintaining connection reliability.
3Reliability
If base station detects multiple rejection causes, then connection security is improved, but message size increases
Solution Approach 1:
Multiple rejection causes are merged into a single cause value field within the rejection message. Rather than sending separate messages or multiple cause indicators, the system consolidates all relevant rejection information into one compact field, maintaining security through comprehensive cause indication while minimizing message data volume.
Data Source
AI summary
A method for implementing network connection, applied to a base station, includes: receiving a connection resume request message sent by user equipment (UE); detecting, according to the connection resume request message, that at least one rejection cause of rejecting connection resumption is met; and sending a connection resume reject message to the UE, wherein the connection resume reject message carries a cause value indicating the at least one rejection cause.