RRC Release Configuration Compliance Handling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In wireless communication networks, especially in LTE and NR, there is a challenge in handling configurations for wireless devices transitioning to dormant states, such as RRC_INACTIVE or RRC_IDLE, where the device may not be able to comply with all configurations received in RRCRelease or RRCResume messages, leading to potential misconfiguration and unexpected behavior.
Innovation Solution
A method where the wireless device determines its inability to comply with certain configurations in RRCRelease or RRCResume messages and performs recovery actions, such as initiating a connection re-establishment procedure, and notifies the network of the inability to apply specific configurations, ensuring consistent state transitions and synchronization of configuration contexts.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the network sends configuration in RRCRelease message to transition UE to dormant state, then the UE should enter dormant state with configured parameters, but the UE may be unable to comply with all configurations leading to misconfiguration and unexpected behavior
Solution Approach 1:
The patent applies preliminary action by having the UE proactively detect configuration compliance issues before transitioning to dormant state. The UE evaluates whether it can comply with received configurations (measIdleConfigDedicated, cellReselectionPriorities, suspendConfig, etc.) and only proceeds with state transition if compliance is confirmed, preventing misconfiguration from occurring in the first place.
Solution Approach 2:
The patent implements feedback by introducing a confirmation mechanism where the UE sends an RRCReleaseComplete message back to the network to indicate successful configuration application. Additionally, failure causes are reported to upper layers, creating a feedback loop that allows the network to detect and correct configuration issues, ensuring reliability in configuration compliance.
2Ease of operation
If the UE silently ignores configuration failures in dormant state transition, then device operation is simple, but configuration context becomes unsynchronized between network and UE
Solution Approach 1:
The patent uses feedback to prevent loss of configuration synchronization information. When the UE successfully applies configurations, it sends RRCReleaseComplete message with failure cause set to 'none'. When configuration compliance fails, the failure cause is reported to upper layers, ensuring that configuration status information is not lost and can be used for recovery actions.
Solution Approach 2:
The patent employs a signaling mechanism that changes the state indication based on configuration compliance status. The RRCReleaseComplete message acts as a status indicator, with the failure cause field effectively 'color-coding' the configuration application result (success vs. failure), allowing the network to quickly understand the UE's configuration state without complex additional signaling.
3Ease of manufacture
If the UE applies all received configurations regardless of compliance ability, then configuration application is straightforward, but unexpected behavior and misconfiguration occur
Solution Approach 1:
The patent applies preliminary action by evaluating configuration compliance before actual state transition occurs. The UE checks whether it can comply with received configurations (measIdleConfigDedicated, cellReselectionPriorities, suspendConfig, redirectedCarrierInfo, etc.) and only proceeds with dormant state transition if the compliance check passes, preventing misconfiguration and ensuring reliable state transitions.
Solution Approach 2:
The patent implements preliminary anti-action by preventing the UE from applying configurations it cannot comply with. Rather than allowing problematic configurations to be applied and then correcting issues, the system proactively blocks non-compliant configurations from being applied, using the failure cause mechanism to identify and prevent configuration mismatches before they cause unexpected behavior.
Data Source
AI summary
A method of operating a wireless device in a communication network includes receiving a message that indicates to the wireless device to enter a dormant state and that includes a configuration, determining that the wireless device is unable to comply with the configuration, and responsive to determining that the wireless device is unable to comply with the configuration, performing a recovery action. A method of operating a wireless network node includes sending an RRC release message instructing a wireless device to transition to a dormant state, the RRC release message including a configuration to be applied by the wireless device, and receiving a confirmation message indicating that the wireless device has properly applied the configuration, has not applied the configuration, or has partially applied the configuration. Related wireless devices and network nodes are disclosed.