RedCap UE BWP Operation Using Separate CORESETs and Aligned UL/DL
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current 3GPP specifications for 5G NR restrict the configuration of a common control resource set (CORESET) for reduced capability (RedCap) UEs, necessitating a separate downlink initial bandwidth part (DL iBWP), and alignment issues between uplink and downlink BWPs cause retuning and increased power consumption.
Innovation Solution
Configuring a common CORESET outside the bandwidth of CORESET #0 and allowing RedCap UEs to monitor paging on one DL iBWP and random access response on another aligned DL iBWP, enabling separate BWPs for RedCap and non-RedCap UEs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a separate DL iBWP is configured for RedCap UEs with a common CORESET not contained in CORESET #0 bandwidth, then coexistence of RedCap and non-RedCap UEs is enabled, but specification restrictions prevent proper CSS monitoring configuration
Solution Approach 1:
The patent segments the CORESET configuration by introducing a separate common CORESET (not contained in CORESET #0 bandwidth) specifically for RedCap UEs. This allows independent configuration of CSS for RedCap UEs on a separate DL iBWP, enabling coexistence with non-RedCap UEs without interfering with existing CORESET #0 configurations.
Solution Approach 2:
The patent extends the CORESET configuration space by allowing common CORESET to be configured outside the bandwidth of CORESET #0. This dimensional extension in frequency domain enables separate DL iBWP configuration for RedCap UEs while maintaining compatibility with non-RedCap UE configurations.
2Adaptability or versatility
If UL iBWP and DL iBWP are not aligned in frequency domain, then separate BWPs can be configured for different purposes, but UE must re-tune causing extra processing time and power consumption
Solution Approach 1:
The patent aligns the center frequencies of UL iBWP and DL iBWP to create frequency domain equipotentiality. This alignment eliminates the need for frequency retuning between uplink and downlink BWPs, reducing processing time and power consumption while maintaining the flexibility to configure separate BWPs for different purposes.
3Ease of manufacture
If common CORESET is restricted to be contained in CORESET #0 bandwidth, then specification implementation is simplified, but separate DL iBWP for RedCap UEs cannot be properly configured
Solution Approach 1:
The patent segments the CORESET hierarchy by introducing a top-level common CORESET that is separate from CORESET #0. This segmentation allows the common CORESET to be configured outside CORESET #0 bandwidth, enabling separate DL iBWP for RedCap UEs while maintaining the existing CORESET #0 structure for non-RedCap UEs.
Solution Approach 2:
The patent extends the frequency domain configuration space by allowing common CORESET to occupy resources outside the bandwidth of CORESET #0. This dimensional extension enables proper configuration of separate DL iBWP for RedCap UEs without violating the containment restriction, thus supporting RedCap adaptability while maintaining specification simplicity.
Data Source
AI summary
Various solutions for supporting enhanced bandwidth part (BWP) operation for reduced capability (RedCap) user equipment (UE) are described. An apparatus may receive system information from a network node. The system information includes configuration of a common control resource set (CORESET) that is not contained in a bandwidth of a CORESET with an identifier (ID) of zero. The apparatus may monitor a common search space (CSS) with the configuration of the common CORESET that is not contained in the bandwidth of the CORESET with the ID of zero.