RedCap UE Capability Reporting for Accurate Network Handovers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing 3GPP networks face challenges in managing reduced capability user equipment (redcap UEs) due to their limited capabilities, leading to issues such as incorrect handovers and configurations when these devices operate as legacy UEs in bands or frequency ranges they cannot support, resulting in operational errors.
Innovation Solution
Implement signaling aspects that allow redcap UEs to operate in both legacy and redcap-supporting networks by reporting capabilities per band or frequency range, using DNS indications and embedded content to differentiate their support, enabling seamless handovers and configurations based on actual capabilities.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If redcap UEs operate as legacy UEs in existing 3GPP networks, then network compatibility is improved, but operational errors occur due to incorrect handovers and configurations in unsupported bands
Solution Approach 1:
The capability report is segmented into two distinct sections: a first section with fields indicating non-support for legacy operation (DNS indication) and a second section with fields indicating actual redcap capabilities. This segmentation allows the network to distinguish between bands the UE cannot support and bands it can support with reduced capabilities, preventing incorrect handovers while maintaining compatibility.
Solution Approach 2:
The capability report acts as an intermediary mechanism between the redcap UE and the network. By including both DNS indications and actual capability information, it mediates the interaction to ensure the network makes informed decisions about handovers and configurations, avoiding operational errors while maintaining network compatibility.
2Reliability
If redcap UEs report full capabilities, then handover decisions are improved, but configuration errors occur due to unsupported bands
Solution Approach 1:
The capability information is divided into two segments: DNS indication fields showing which bands are not supported, and actual capability fields showing which bands are supported with redcap limitations. This segmentation ensures accurate handover decisions while maintaining proper network compatibility by clearly indicating supported and unsupported bands.
Solution Approach 2:
Different parts of the capability report serve different functions: the DNS indication section provides negative information (what is not supported) while the actual capability section provides positive information (what is supported). This local differentiation ensures that handover decisions are made with precise knowledge of UE capabilities and limitations.
3Device complexity
If redcap UEs use simplified capability reporting, then device complexity is reduced, but network configuration accuracy deteriorates
Solution Approach 1:
The capability reporting structure is segmented into two clear sections with distinct purposes. This segmentation maintains relatively simple device implementation while achieving high configuration accuracy, as the network can clearly distinguish between unsupported bands (DNS indication) and supported bands with specific capabilities.
Solution Approach 2:
The DNS indication extracts and separates the negative capability information (what the UE cannot do) from the positive capability information (what the UE can do). This extraction allows the network to quickly identify unsupported bands and avoid configuration errors, maintaining high precision without excessive complexity.
Data Source
AI summary
The present application relates to devices and components including apparatuses, systems, and methods for managing reduced capability user equipments in wireless networks.