RedCap UE Random Access via Split PUCCH Configurations
Solution Overview
Problem
Existing wireless communication systems face challenges in efficiently supporting RedCap UEs (terminals with reduced capability) by providing them with system information and enabling access to New Radio cells.
Innovation Solution
A method and apparatus for a RedCap UE to receive System Information Block1 from a base station and perform a random access procedure using specific timeAlignmentTimer and pucch-ConfigCommon configurations in the uplink configurations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If existing wireless communication systems use standard access procedures for all terminals, then general terminals can access the network normally, but RedCap UEs cannot efficiently obtain system information and access New Radio cells due to their reduced capabilities
Solution Approach 1:
The patent segments the uplink configuration into two distinct parts: a first uplink configuration containing first pucch-ConfigCommon for general terminals, and a second uplink configuration containing second pucch-ConfigCommon specifically for RedCap UEs. This segmentation allows RedCap UEs to access only the relevant configuration information tailored to their reduced capabilities, improving access efficiency while maintaining compatibility with general terminals.
Solution Approach 2:
The patent applies local quality by providing different PUCCH common configuration information to different terminal types. RedCap UEs receive a simplified second pucch-ConfigCommon with parameters appropriate for their reduced capability, while general terminals receive the full first pucch-ConfigCommon. This localized optimization ensures each terminal type operates efficiently with parameters matched to their specific capabilities.
2Reliability
If the system provides comprehensive uplink configuration information to all terminals, then general terminals can operate with full functionality, but RedCap UEs receive unnecessary information increasing processing overhead
Solution Approach 1:
The patent extracts the essential PUCCH common configuration information needed by RedCap UEs into a separate second pucch-ConfigCommon, isolating it from the comprehensive first pucch-ConfigCommon provided to general terminals. This extraction allows RedCap UEs to obtain only the necessary configuration parameters for their reduced capability operations, reducing the quantity of information they must process while maintaining reliability of the essential functions.
Solution Approach 2:
The patent implements dynamic configuration information provision where the base station selectively provides different uplink configuration information based on terminal type. RedCap UEs receive the simplified second pucch-ConfigCommon containing only necessary parameters, while general terminals receive the complete first pucch-ConfigCommon. This dynamic adaptation optimizes the balance between information completeness and quantity for different terminal capabilities.
3Reliability
If RedCap UEs use the same timeAlignmentTimer as general terminals, then timing alignment is maintained for all terminals, but RedCap UEs experience unnecessary timing constraints reducing their operational flexibility
Solution Approach 1:
The patent changes the timeAlignmentTimer parameter specifically for RedCap UEs, providing a second timeAlignmentTimer that is adapted to their reduced capability and processing speed. This parameter change allows RedCap UEs to maintain adequate timing alignment for reliable operation while having extended flexibility compared to general terminals, accommodating their slower processing capabilities and reduced functionality.
Data Source
AI summary
A method and apparatus for accessing a NR cell in a mobile communication system are provided. Method for accessing a NR cell includes receiving in a first cell, by a terminal from a base station, a System Information Block1 and performing, by the terminal, random access procedure based on a timeAlignmnetTimer in the first uplink configuration and a second pucch-ConfigCommon in the second uplink configuration.


