PUCCH Configuration for Unlicensed Spectrum Resource Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current wireless communication systems lack a standardized method for indicating the number of resource blocks (RBs) and mapping types for physical uplink control channel (PUCCH) configuration, particularly in unlicensed spectrum scenarios, which affects peak to average power ratio (PAPR) and power spectral density (PSD) management.

Innovation Solution

The proposed solution involves indicating the number of RBs and mapping types before radio resource control (RRC) connection using a predefined table, and dynamically adjusting these parameters during RRC connected mode, incorporating long sequence and frequency domain repetition to achieve a trade-off between multiplexing and coverage gains, while adhering to PSD limitations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If a predefined table with first and second parameters is used for PUCCH configuration in idle mode, then device complexity is reduced, but adaptability deteriorates

Engineering Contradiction:
ImprovePUCCH configuration complexityVSAvoidPUCCH configuration adaptability
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

A predefined table containing first parameters (number of RBs) and second parameters (mapping types) is prepared in advance for idle mode operation. This allows the UE to quickly select PUCCH configuration without complex real-time calculations, reducing device complexity while maintaining basic adaptability through pre-configured options.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system transitions from static predefined tables in idle mode to dynamic RRC-specified parameters in connected mode. When the UE enters connected mode, the network can dynamically adjust the PUCCH configuration based on current network conditions and requirements, thereby improving adaptability when needed.

Inventive Principle:
Principle #15Dynamics

2Adaptability or versatility

If dedicated PUCCH resource configuration is received in RRC connected mode, then adaptability improves, but device complexity increases

Engineering Contradiction:
ImprovePUCCH configuration adaptabilityVSAvoidPUCCH configuration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

In connected mode, the network provides dedicated PUCCH resource configuration through RRC signaling, allowing dynamic adjustment of first parameters (number of RBs) and second parameters (mapping types) based on real-time network conditions, traffic patterns, and interference levels. This improves adaptability while the network manages the complexity burden.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system implements feedback mechanisms where the network monitors PUCCH transmission performance and adjusts the configuration parameters accordingly. This allows the network to optimize PUCCH resources based on actual channel conditions and UE performance, maintaining high adaptability while managing complexity through centralized control.

Inventive Principle:
Principle #23Feedback

3Reliability

If frequency domain repetition is applied to achieve coverage gain, then reliability improves, but PAPR increases

Engineering Contradiction:
ImprovePUCCH transmission reliabilityVSAvoidPAPR
Core Design Contradiction:
ReliabilityVSObject-generated harmful factors

Solution Approach 1:

The system changes the mapping type parameter between type 0 (long sequence) and type 1 (frequency domain repetition) based on channel conditions. When coverage is sufficient, mapping type 0 is used to maintain lower PAPR. When coverage becomes limiting, mapping type 1 is selected to provide coverage gain through frequency domain repetition, accepting the associated PAPR increase.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The mapping type is dynamically selected based on channel conditions, UE location, and network requirements. This dynamic adaptation allows the system to optimize between reliability and PAPR by choosing the appropriate mapping type for each transmission scenario, rather than using a fixed configuration.

Inventive Principle:
Principle #15Dynamics

4Productivity

If the number of RBs is increased to improve multiplexing gain, then productivity improves, but PSD increases

Engineering Contradiction:
Improvemultiplexing gainVSAvoidPSD
Core Design Contradiction:
ProductivityVSObject-generated harmful factors

Solution Approach 1:

The system adjusts the first parameter (number of RBs) based on network conditions, UE power class, and interference levels. By dynamically changing this parameter, the system can optimize multiplexing capacity while controlling PSD to comply with regulatory requirements and protect other users in the unlicensed spectrum.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

Different numbers of RBs are allocated to different UEs or different time/frequency resources based on local conditions such as channel quality, interference levels, and network traffic requirements. This localized resource allocation allows the system to achieve high multiplexing gain in favorable conditions while maintaining PSD control in congested or interference-prone areas.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS20240276500A1Communicating a number of resource blocks (RBS) parameter and a mapping types parameter for physical uplink control channel (PUCCH) configuration
Publication Date: 2024.08.15 LENOVO (SINGAPORE) PTE LTD
  • US20240276500A1 patent drawing
  • US20240276500A1 patent drawing
  • US20240276500A1 patent drawing

AI summary

Apparatuses and methods for communicating a number of resource blocks (RBs) 502 parameter and a mapping types parameter for physical uplink control channel (PUCCH) configuration. An apparatus 102 determines connection status. In response to determining that the connection status is not connected. the apparatus 102 selects one of first parameters indicating a number of RBs 502 and one of second parameters indicating mapping types included in a previously received configuration for the transmission of PUCCH having a predefined table with the first and second parameters. In response to determining that connection status is connected. the apparatus 102 receives a dedicated PUCCH resource configuration (radio resource control (RRC) message) having a third parameter indicating a number of RBs 502 and a fourth parameter indicating a mapping type. The apparatus 102 generates a PUCCH transmission responsive to the selected first and second parameters or the received third and fourth parameters.