RRC Reconfiguration Verification for Abnormal Parameter Handling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In 5G networks, UE fails to verify RRC reconfiguration messages, leading to call interruptions due to abnormal parameter values in the messages.
Innovation Solution
The method involves verifying RRC reconfiguration messages by ignoring or updating abnormal parameter values in the messages, ensuring successful verification and reducing the likelihood of RRC reconfiguration failures.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If the terminal device strictly verifies RRC reconfiguration messages against stored configuration items, then verification accuracy is improved, but call reliability deteriorates when abnormal parameter values are present
Solution Approach 1:
The patent changes the verification parameter from strict equality comparison to abnormal value detection. Instead of failing when parameter values differ, the system identifies abnormal values (those outside expected ranges) and handles them specially, allowing verification to proceed while flagging potential issues. This resolves the contradiction by maintaining verification accuracy for normal parameters while preventing call failures due to abnormal parameter variations.
Solution Approach 2:
The patent converts the harmful effect of abnormal parameter values into a beneficial verification mechanism. Rather than treating parameter mismatches as verification failures, the system uses abnormal value detection to identify and handle edge cases, transforming what would be rejection criteria into acceptance criteria with enhanced reliability. This allows the system to maintain strict verification for normal cases while being tolerant of abnormal variations.
2Reliability
If the terminal device ignores abnormal parameter values during verification, then call reliability is improved, but verification precision deteriorates
Solution Approach 1:
The patent applies local quality by treating different parameter values differently based on their nature. Normal parameter values are verified strictly, while abnormal parameter values are handled with special tolerance. This localized differentiation allows the system to maintain high verification precision for valid parameters while ensuring call reliability by accommodating abnormal variations in specific parameters.
Solution Approach 2:
The verification process becomes dynamic rather than static. The system adjusts its verification stringency based on the parameter state: strict verification for normal values, flexible handling for abnormal values. This dynamic verification approach resolves the contradiction by adapting the verification precision level to the current parameter conditions, ensuring both reliability and appropriate precision.
3Measurement precision
If the terminal device performs strict verification of RRC reconfiguration messages, then message accuracy is improved, but call continuity deteriorates when verification fails
Solution Approach 1:
The patent implements beforehand cushioning by pre-establishing abnormal value handling mechanisms before verification occurs. The system pre-identifies which parameters can tolerate abnormal values and prepares special verification logic in advance. This cushioning approach allows strict verification to maintain message accuracy while preventing verification failures from interrupting call continuity, as abnormal values are handled gracefully rather than causing rejection.
Data Source
AI summary
This application provides a method for a call, a device, a chip system, and a storage medium. The method is applied to a terminal device. Verification is performed on first information in a first RRC reconfiguration message currently received from a first cell, a first parameter in a locally stored first configuration item, and a value corresponding to the first parameter, and when a value corresponding to the first parameter is abnormal, an abnormal value corresponding to the first parameter is ignored, so that the first RRC reconfiguration message is successfully verified, thereby ensuring that the terminal device can complete RRC reconfiguration and reducing a probability of an RRC reconfiguration failure.


