RACH Priority Payload for Latency Reduction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current wireless communication systems lack mechanisms to prioritize random access channel (RACH) procedures effectively, leading to increased latency in urgent situations such as handover or beam failure recovery, as they do not differentiate between RACH procedures based on priority.

Innovation Solution

The implementation of a method where user equipment (UE) generates a payload in the preamble message to indicate a higher priority for specific RACH procedures, such as handover or beam failure recovery, allowing for shorter response windows and different power-ramping steps, enabling quicker uplink timing synchronization and grant acquisition.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If all RACH procedures are treated equally without priority differentiation, then the system maintains simplicity in procedure handling, but latency increases in urgent scenarios such as handover or beam failure recovery

Engineering Contradiction:
ImproveRACH procedure latencyVSAvoidRACH procedure management complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The patent introduces priority parameters (e.g., priority indicators, urgency flags) that modify the behavior of RACH procedures. Different priority levels trigger different response window durations, power-ramping steps, and procedural handling, allowing urgent procedures to be expedited without fundamentally changing the overall RACH framework

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The patent segments RACH procedures into different priority categories (e.g., high priority for handover/beam failure recovery, normal priority for initial access). This segmentation allows the system to apply different handling rules to different procedure types while maintaining a unified RACH mechanism

Inventive Principle:
Principle #1Segmentation

2Reliability

If the response window duration is extended to accommodate all RACH procedures, then reliability of response reception improves, but latency increases for high-priority procedures that require faster response

Engineering Contradiction:
Improveresponse reception reliabilityVSAvoidresponse window latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies different response window durations based on the local characteristics of each RACH procedure's priority level. High-priority procedures receive shorter response windows with expedited handling, while normal-priority procedures use standard response windows, optimizing both speed and reliability for each case

Inventive Principle:
Principle #3Local quality

3Reliability

If power-ramping steps are increased to ensure successful preamble transmission, then reliability of uplink synchronization improves, but energy consumption increases

Engineering Contradiction:
Improveuplink synchronization reliabilityVSAvoidUE transmission energy consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent implements dynamic power-ramping adjustments based on RACH procedure priority and previous transmission outcomes. High-priority procedures may use more aggressive power-ramping to ensure rapid successful transmission, while normal-priority procedures use conservative power-ramping to minimize energy consumption, adapting the strategy to each situation

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS12075492B2System and method for prioritization of random access procedures
Publication Date: 2024.08.27 QUALCOMM INC
  • US12075492B2 patent drawing
  • US12075492B2 patent drawing
  • US12075492B2 patent drawing

AI summary

In an aspect of the disclosure, a first method, a first computer-readable medium, and a first apparatus are provided. The first apparatus may be a UE. The first apparatus may generate a payload of a first preamble message associated with a first RACH procedure, and the payload may indicate a first priority of the first RACH procedure that is relatively higher than a second priority of a second RACH procedure. The first apparatus may send the first preamble message including a RACH preamble and the payload to a base station, and the first preamble message may indicate an identifier (ID) of the first apparatus.