Msg3 PUSCH Repetition Resource Allocation in 5G RACH

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In the context of 5G new radio (NR) wireless communication systems, the existing 4-step random access channel (RACH) procedure for Msg3 physical uplink shared channel (PUSCH) repetitions lacks efficient mechanisms to differentiate and allocate resources for UEs that support Msg3 PUSCH repetition, particularly in shared PRACH occasions, leading to suboptimal coverage and performance.

Innovation Solution

Configuring separate PRACH occasions and preambles for UEs requesting Msg3 PUSCH repetition, with specific parameter settings for synchronization signal blocks and random access channel occasions, allowing for improved detection performance and resource allocation, such as allocating PRACH preambles after CBRA 4-step RACH for enhanced UEs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If separate PRACH occasions and preambles are configured for UEs requesting Msg3 PUSCH repetition, then detection performance and coverage are improved, but device complexity and resource allocation complexity increase

Engineering Contradiction:

Improvedetection performanceVSAvoidresource allocation complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the PRACH resources by creating separate PRACH occasions and preambles for UEs requesting Msg3 PUSCH repetition versus those not requesting repetition. This segmentation allows the network to differentiate between UE types and allocate appropriate resources, improving detection performance for cell-edge UEs while managing complexity through structured resource separation.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent applies local quality by providing different PRACH configurations to different UE groups based on their specific needs. UEs requesting Msg3 PUSCH repetition receive optimized PRACH occasions and preambles tailored to their coverage enhancement requirements, while other UEs use standard configurations, thereby improving overall system efficiency.

Inventive Principle:

Principle #3Local quality

2Reliability

If separate PRACH occasions are configured for Msg3 PUSCH repetition, then coverage is improved, but loss of time for random access procedure increases

Engineering Contradiction:

ImprovecoverageVSAvoidrandom access procedure time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent implements preliminary action by having UEs indicate their Msg3 PUSCH repetition requirement during the initial PRACH preamble transmission phase. The network detects this indication and pre-configures appropriate PRACH occasions and parameters before the actual Msg3 transmission, enabling coverage-enhanced UEs to receive optimized resources in advance without extending the overall random access timeline.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS20240172272A1Msg3 physical uplink shared channel (PUSCH) repetition requests

Publication Date: 2024.05.23 INTEL CORP

AI summary

Various embodiments herein are directed to the request of Msg3 physical uplink shared channel (PUSCH) repetitions. In order to improve the coverage, repetition is supported for Msg3 PUSCH during the 4-step RACH procedure. In this case, either separate PRACH occasions or shared PRACH occasions with separate PRACH preambles may be configured to differentiate the enhanced UE that requests the Msg3 PUSCH repetition and legacy UEs that do not.