High Priority SR Multiplexing on Low Priority PUSCH

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current wireless communication systems face limitations in flexibility and efficiency, particularly in handling scheduling requests (SR) on physical uplink shared channels (PUSCH), where high priority SRs often result in channel dropping, leading to dropped high priority HARQ-ACKs and inefficient resource management.

Innovation Solution

The system enables SR multiplexing on PUSCH by determining based on RRC parameters whether to transmit or drop channels, allowing for simultaneous reporting of high priority SRs and UCI on PUSCH, even when overlapping with low priority PUSCH, using separate coding chains and reserved resources to manage SRs effectively.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If high priority SR is transmitted on PUCCH separately, then SR reliability is improved, but resource overhead increases and channel dropping occurs for low priority PUSCH

Engineering Contradiction:
ImproveSR transmission reliabilityVSAvoidchannel management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges the high priority SR transmission with the low priority PUSCH by enabling SR multiplexing on the PUSCH. Instead of transmitting SR separately on PUCCH, the system multiplexes the SR indication bits with the PUSCH data transmission, allowing both to share the same time-frequency resources. This resolves the contradiction by reducing resource overhead and avoiding channel dropping while maintaining SR reliability through proper multiplexing techniques.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The low priority PUSCH is given multi-functionality by enabling it to carry both data transmission and high priority SR indication. The PUSCH serves dual purposes: delivering user data and conveying SR status information when multiplexing is enabled. This universal usage of the PUSCH eliminates the need for separate SR channels and reduces overall system resource consumption.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Productivity

If SR multiplexing is enabled on low priority PUSCH, then resource efficiency is improved, but SR reporting flexibility is reduced

Engineering Contradiction:
Improveresource utilization efficiencyVSAvoidSR reporting flexibility
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The system implements dynamic SR multiplexing where the gNB can configure multiplexing behavior based on current transmission conditions. The multiplexing is not fixed but can be adjusted dynamically - enabling when resources are available and optimal, disabling when flexibility is needed. This dynamic approach allows the system to optimize resource utilization efficiency while maintaining adaptability through configurable multiplexing parameters and conditional activation.

Inventive Principle:
Principle #15Dynamics

3Reliability

If channel dropping is applied to low priority PUSCH, then high priority SR transmission is ensured, but communication reliability decreases

Engineering Contradiction:
Improvehigh priority SR transmissionVSAvoidoverall communication efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent converts the potential harm of channel dropping into a benefit by using the dropped PUSCH resources for SR multiplexing. Instead of simply dropping the low priority PUSCH and losing its transmission, the system repurposes those same time-frequency resources to multiplex the high priority SR indication with the PUSCH data. This transforms the harmful effect of resource conflict into a beneficial multiplexing opportunity, ensuring SR transmission while maintaining PUSCH data transmission.

Inventive Principle:
Principle #22Blessing in disguise (Convert harm into benefit)

Data Source

PatentUS20240324001A1Methods of multiplexing a high priority SR on a low priority pusch
Publication Date: 2024.09.26 SHARP KK
  • US20240324001A1 patent drawing
  • US20240324001A1 patent drawing
  • US20240324001A1 patent drawing

AI summary

A user equipment (UE) is described. The UE also includes transmitting circuitry configured to, if at least one physical uplink control channel (PUCCH) for high priority (HP) scheduling request (SR) overlaps with a low priority (LP) PUSCH, and if HP SR multiplexing on LP PUSCH is enabled, and if a positive HP SR is triggered, report the SR in reserved resource element (RE) resources for the SR.