RedCap Initial DL BWP Configuration for Lower UE Power Use
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing wireless communication systems face challenges in optimizing power savings for RedCap UEs in the initial downlink bandwidth part, leading to increased power consumption and potential communication delays.
Innovation Solution
The solution involves configuring a dedicated initial downlink bandwidth part (iBWP) for RedCap UEs, allowing them to perform OSI reception, RRM measurements, and SSB receptions within this bandwidth, thereby reducing the need for frequency hopping and BWP switching, which minimizes power consumption and communication delays.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If RedCap UEs perform OSI reception, RRM measurements, and SSB receptions in the common initial DL BWP, then compatibility with legacy UEs is maintained, but frequency hopping and BWP switching are required which increases power consumption
Solution Approach 1:
The patent divides the initial downlink BWP into two separate BWPs: a common initial DL BWP for legacy UEs and a dedicated initial DL BWP for RedCap UEs. This segmentation allows each UE type to operate in its own optimized bandwidth part, avoiding the need for RedCap UEs to perform frequency hopping and BWP switching while maintaining compatibility with legacy UE operations in the common BWP.
Solution Approach 2:
The patent applies local quality by providing different BWP configurations tailored to specific UE types. The dedicated initial DL BWP is specifically optimized for RedCap UEs with appropriate bandwidth, subcarrier spacing, and resource allocation, while the common initial DL BWP serves legacy UEs. This localized optimization reduces power consumption for RedCap UEs without affecting legacy UE operations.
2Use of energy by moving object
If a dedicated initial DL BWP is configured for RedCap UEs, then power consumption is reduced by eliminating frequency hopping, but device complexity increases due to multiple BWP configurations
Solution Approach 1:
The patent enables RedCap UEs to autonomously identify and access the dedicated initial DL BWP through specific signaling mechanisms. The UE determines its capability and self-configures to use the appropriate BWP without requiring complex network-controlled switching, thereby reducing device complexity while maintaining power savings.
Solution Approach 2:
The patent changes key BWP parameters (bandwidth, subcarrier spacing, frequency location) to create a dedicated initial DL BWP optimized for RedCap UEs. By adjusting these parameters according to RedCap UE capabilities, the system achieves power efficiency without requiring complex real-time switching logic in the UE.
3Productivity
If RedCap UEs switch between BWPs for OSI reception and other operations, then resource utilization is optimized, but communication delays increase due to switching overhead
Solution Approach 1:
The patent performs preliminary action by pre-configuring the dedicated initial DL BWP with all necessary resources for OSI reception, RRM measurements, and SSB receptions. This advance configuration eliminates the need for time-critical BWP switching during operations, thereby reducing communication delays while maintaining efficient resource utilization.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. Methods and apparatuses for operating in different bandwidth parts (BWPs). A method includes receiving a first synchronization signal and physical broadcast channel (SS/PBCH) block in a first BWP; determining, based on information provided by the first SS/PBCH block, a first control resource set (CORESET) in the first BWP; and receiving a first physical downlink control channel (PDCCH) in the first CORESET. The PDCCH provides a first downlink control information (DCI) format that schedules a reception of a first physical downlink shared channel (PDSCH) providing a system information block (SIB1). The method further includes receiving the first PDSCH, determining a second BWP based on information provided by the SIB1, and receiving a second SS/PBCH block in the second BWP. The second BWP does not include a bandwidth of the first SS/PBCH block. The second BWP does not include a bandwidth of the first CORESET.