PUSCH Occasion Validation Under Dynamic RACH and SSB Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In wireless communications systems, dynamic adaptation of random access channel (RACH) occasions and synchronization signal block (SSB) resources can lead to increased latency during two-step RACH procedures due to overlapping or invalid PUSCH occasions, making it difficult for user equipment (UE) to identify valid transmission occasions.

Innovation Solution

The UE performs a validation procedure to determine the validity of PUSCH occasions based on updates to RACH occasions and SSB resources, including dropping or invalidating occasions that overlap with added or removed resources, and maintaining or adapting mappings between PUSCH and RACH occasions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If dynamic adaptation of RACH occasions and SSB resources is performed, then system flexibility and resource optimization are improved, but latency increases and PUSCH occasion validity becomes difficult to determine

Engineering Contradiction:
Improveresource adaptation flexibilityVSAvoidRACH procedure latency
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The network pre-configures multiple PUSCH occasions with associated RACH occasions and SSB resources before the actual random access procedure. This preliminary configuration allows the UE to quickly identify valid PUSCH occasions without real-time validation delays, reducing latency while maintaining adaptability through pre-planned resource sets.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements dynamic validation rules that automatically determine PUSCH occasion validity based on current RACH occasion and SSB resource configurations. When RACH occasions or SSB resources are updated, the validation procedure dynamically adjusts which PUSCH occasions remain valid, allowing flexible adaptation without manual intervention or excessive latency.

Inventive Principle:
Principle #15Dynamics

2Reliability

If validation procedure is performed to determine PUSCH occasion validity, then transmission reliability is improved, but processing complexity increases

Engineering Contradiction:
Improvetransmission reliabilityVSAvoidvalidation processing complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The validation procedure is segmented into distinct checks: first verifying RACH occasion availability, then checking SSB resource compatibility, and finally determining PUSCH occasion validity. This segmentation allows the UE to perform systematic validation without overwhelming processing complexity, as each segment handles a specific aspect of validity determination.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The network provides pre-configured templates or patterns for valid PUSCH occasion structures. Instead of performing complex real-time validation, the UE can compare actual occasions against these pre-established templates, significantly reducing processing complexity while maintaining high reliability in determining valid transmission occasions.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS20250351124A1Validating physical uplink shared channel (PUSCH) resource occasions
Publication Date: 2025.11.13 QUALCOMM INC
  • US20250351124A1 patent drawing
  • US20250351124A1 patent drawing
  • US20250351124A1 patent drawing

AI summary

Methods, systems, and devices for wireless communications are described. In some examples, a user equipment (UE) may receive first control signaling that indicates a set of physical uplink shared channel (PUSCH) occasions, a set of random access channel (RACH) occasions, a set of synchronization signal block (SSB) resources, or a combination thereof. Additionally, the UE may receive second control signaling indicating an update to the set of RACH occasions, an update to the set of SSB resources, or both. Accordingly, the UE may perform a validation procedure to determine whether to invalidate or validate at least a first PUSCH occasion of the set of PUSCH occasions based on the update to the set of RACH occasions, the update to the set of SSB resources, or both. Based on performing the validation procedure, the UE may communicate via the set of PUSCH occasions according to the results of the validation procedure.