RedCap CORESET #0 Configuration for NR Bandwidth Mismatch

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing 5G NR technologies have not addressed the implementation of Control Resource Set Zero (CORESET #0) for Reduced Capability (RedCap) devices, leading to potential failures in initial cell selection and handover due to bandwidth mismatches between Rel-15 CORESET #0 and RedCap UEs.

Innovation Solution

The solution involves configuring CORESET #0 with time and frequency resources based on the bandwidth configuration of RedCap UEs, allowing them to receive and decode system information and control channels, and partitioning or subsetting Rel-15 CORESET #0 to fit within RedCap UE bandwidth capabilities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If Rel-15 CORESET #0 bandwidth configuration is used for RedCap UEs, then normal UEs can access the network, but RedCap UEs experience bandwidth mismatch and fail initial cell selection and handover

Engineering Contradiction:

Improveinitial cell selection and handover successVSAvoidbandwidth configuration compatibility

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The CORESET #0 bandwidth configuration is segmented into different versions: one for normal UEs and another for RedCap UEs. The network configures separate bandwidth parameters (controlResourceSetZero and searchSpaceZero) that are specifically adapted to the reduced bandwidth capabilities of RedCap devices, allowing each UE type to access appropriate resources without interference

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Different bandwidth quality characteristics are assigned to different UE types. Normal UEs receive full-bandwidth CORESET #0 configurations while RedCap UEs receive narrowed bandwidth configurations that match their processing capabilities and antenna requirements, optimizing performance for each device category

Inventive Principle:

Principle #3Local quality

2Reliability

If reduced bandwidth configuration is implemented for RedCap UEs, then RedCap devices can perform initial access and handover, but system complexity increases due to dual configuration management

Engineering Contradiction:

ImproveRedCap UE initial access and handoverVSAvoidCORESET configuration management

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The network side acts as an intermediary by configuring different CORESET #0 bandwidth parameters for different UE types. The gNB maintains separate configuration sets (controlResourceSetZero and searchSpaceZero) and selectively applies them based on UE capability indications, abstracting the complexity from UEs while enabling RedCap support

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The bandwidth parameters of CORESET #0 are changed based on UE type. The system modifies controlResourceSetZero and searchSpaceZero configuration parameters to create appropriate bandwidth allocations for RedCap UEs versus normal UEs, enabling adaptive support without fundamental system redesign

Inventive Principle:

Principle #35Parameter changes

Data Source

PatentUS12621853B2Control resource set zero for reduced capability new radio devices

Publication Date: 2026.05.05 PANASONIC INTELLECTUAL PROPERTY CORP OF AMERICA

AI summary

The present disclosure provides communication apparatuses and communication methods for implementation of Control Resource Set Zero (CORESET #0) for Reduced Capability (RedCap) New Radio Devices. The communication apparatuses include a communication apparatus which comprises a receiver, which in operation, receives a physical downlink control channel (PDCCH) on a control resource set zero (CORESET #0) of which time and frequency resources are defined based on a bandwidth configuration of reduced capacity user equipments (RedCap UEs), and receives a system information block type 1 (SIB1) physical downlink shared channel (PDSCH) which is scheduled based on the CORESET #0; and circuitry, which in operation, determines control information and parameters from the PDCCH on CORESET #0 to read SIB1 for initial access, handover, or beam failure recovery.