RACH Resource Partitioning for Feature-Specific Random Access Triggering

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current communication technologies face challenges in efficiently determining trigger conditions for random access in wireless communication systems, particularly in recognizing features such as coverage enhancement and reduced capability features by the network side.

Innovation Solution

The method involves determining a feature for triggering random access, selecting a random access channel (RACH) resource partition, and determining whether the selected RACH resource supports the feature. The network side configures specific RACH resource partitions to enable the terminal to select resources that support specific features, allowing the terminal to determine if the trigger condition is met based on the selected resource.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If specific RACH resources are configured for each feature, then the network side can recognize features early, but the device complexity and resource configuration overhead increase

Engineering Contradiction:
Improvefeature recognition accuracyVSAvoidresource configuration complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The RACH resources are segmented into different partitions, where each partition is associated with specific feature(s). The terminal selects a partition based on its detected feature, enabling feature-specific resource allocation without requiring the network to configure separate resources for every possible feature combination. This segmentation approach maintains early feature recognition while reducing configuration complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Each RACH resource partition is designed to support multiple features or feature combinations. For example, a partition may be configured to support both coverage enhancement and reduced capability features simultaneously. This multi-functionality allows the system to recognize and handle multiple features using a unified resource structure, reducing the overall number of configurations needed.

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

2Adaptability or versatility

If multiple RACH resource partitions are configured for different features, then feature-specific random access is enabled, but the loss of time for resource selection and determination increases

Engineering Contradiction:
Improvefeature-specific resource allocationVSAvoidresource selection time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The network side pre-configures multiple RACH resource partitions with specific feature associations before the terminal needs to perform random access. The terminal also pre-detects its applicable features and identifies the corresponding partition in advance. When random access is triggered, the terminal can immediately select the pre-identified partition without performing time-consuming feature detection or resource search at the moment of access, thus reducing time loss while maintaining adaptability.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20250151119A1Trigger condition determination method and apparatus, and resource partition configuration method and apparatus
Publication Date: 2025.05.08 BEIJING XIAOMI MOBILE SOFTWARE CO LTD
  • US20250151119A1 patent drawing
  • US20250151119A1 patent drawing
  • US20250151119A1 patent drawing

AI summary

A method for determining a trigger condition, performed by a terminal, includes: determining a feature for triggering a random access; selecting a random access channel (RACH) resource partition, and determining whether a selected RACH resource supports the feature; determining that a trigger condition of the feature is met in response to the selected RACH resource supporting the feature; and determining that the trigger condition of the feature is not met in response to the selected RACH resource not supporting the feature.