RedCap UE 2-Step RACH Resource Association

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The challenge lies in determining PUSCH resources for RedCap UEs during a 2-step RACH procedure, especially when these resources are shared with non-RedCap UEs, without separate ROs for RedCap UEs in the same PRACH slot for non-RedCap UEs.

Innovation Solution

RedCap UEs receive dedicated MsgA RACH configurations and reuse PUSCH resources configured for non-RedCap UEs by associating their PRACH resources with those of non-RedCap UEs, either through shared indices in the time domain or subsequent PRACH resources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If RedCap UEs use separate PRACH resources for 2-step RACH procedure, then access control and scheduling control can be improved, but resource allocation complexity increases

Engineering Contradiction:

Improveaccess controlVSAvoidresource allocation

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies universality by enabling RedCap UEs to use the same PRACH resources configured for non-RedCap UEs. The base station configures PRACH resources that can be universally used by both RedCap and non-RedCap UEs for the 2-step RACH procedure, eliminating the need for separate dedicated resources while maintaining access control through identification mechanisms.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Productivity

If RedCap UEs share PUSCH resources with non-RedCap UEs, then resource efficiency improves, but resource determination difficulty increases

Engineering Contradiction:

Improveresource efficiencyVSAvoidresource determination

Core Design Contradiction:

ProductivityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent applies local quality by establishing specific association relationships between PRACH resources and PUSCH resources for RedCap UEs. When a base station configures PRACH resources for RedCap UEs, it simultaneously configures the corresponding PUSCH resources through defined associations (such as time-domain relationships or explicit mapping), allowing RedCap UEs to determine their specific PUSCH resources from the shared resource pool based on their PRACH resource selection.

Inventive Principle:

Principle #3Local quality

3Reliability

If separate ROs are configured for RedCap UEs in the same PRACH slot, then access control improves, but time resource consumption increases

Engineering Contradiction:

Improveaccess controlVSAvoidtime resource

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent applies merging by combining RedCap UE PRACH resources with non-RedCap UE PRACH resources in the same time-frequency resources. Instead of configuring separate ROs for RedCap UEs within the same PRACH slot, the system merges the resource pools and uses UE identification (such as different preamble sequences or base station identification of UE type) to distinguish and control access for different UE types, thereby saving time resources while maintaining access control.

Inventive Principle:

Principle #5Merging (Combining)

Data Source

PatentUS20250185077A1Methods and apparatuses of a 2-step RACH procedure for redcap ues and non-redcap ues

Publication Date: 2025.06.05 LENOVO (BEIJING) LTD

AI summary

Embodiments of the present application relate to methods and apparatuses of a 2-step random access channel (RACH) procedure for reduced capability (RedCap) user equipments (UEs) and non-RedCap UEs. According to an embodiment of the present application, a user equipment (UE) includes a processor and a transceiver coupled to the processor; and the processor is configured: to receive physical random access channel (PRACH) configurations via the transceiver; to determine a PRACH resource based on the PRACH configurations; and to determine a set of PUSCH resources for the UE based on at least one of: an association of the PRACH resource with a further PRACH resource within a set of PRACH resources, or an association of the PRACH resource with a set of further PUSCH resources.