Random Access Partition Reporting for RACH Congestion Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current RACH optimization in 5G networks does not consider RA resource partitioning based on use cases, features, services, or network slicing, leading to sub-optimal network performance due to limited visibility into the conditions that trigger RACH resource congestion and collisions.

Innovation Solution

UEs are configured to log and report RA information including feature combinations and network slices that triggered the RA procedure, allowing RAN nodes to adjust and optimize RA resource partitions based on this information, reallocating resources to balance load and reduce contention.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If RA resource partitioning is implemented based on use cases, features, services, or network slicing, then network performance and resource allocation efficiency are improved, but device complexity and configuration complexity increase

Engineering Contradiction:
Improvenetwork performanceVSAvoidconfiguration complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments RA resources into multiple partitions, where each partition is dedicated to specific use cases, features, services, or network slices. This segmentation allows the network to allocate RA resources more precisely according to different traffic types and service requirements, improving overall network performance while maintaining manageable complexity through structured organization

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements dynamic RA resource partitioning where the network can flexibly configure and adjust partition parameters based on real-time network conditions, service requirements, and traffic patterns. This dynamic approach enables the system to adapt to changing demands without requiring complete reconfiguration, balancing performance optimization with operational simplicity

Inventive Principle:
Principle #15Dynamics

2Ease of operation

If RA resource partitioning is implemented without visibility into triggering conditions, then configuration is simpler, but RACH resource congestion and collisions increase

Engineering Contradiction:
Improveconfiguration simplicityVSAvoidRACH resource collision rate
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent implements feedback mechanisms where UEs report information about their RA procedures, including which partition was used and what triggered the RA. This feedback loop provides the network with visibility into triggering conditions and partition utilization patterns, enabling data-driven optimization of RA resource allocation to reduce collisions and congestion

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent enables the network to pre-configure multiple RA resource partitions with different parameters before actual RA procedures occur. By preparing these partitions in advance based on anticipated service requirements and traffic patterns, the network can immediately direct UEs to appropriate partitions, reducing collision probability without requiring complex real-time decision-making

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20260032065A1Reporting Random Access Partition Information
Publication Date: 2026.01.29 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US20260032065A1 patent drawing
  • US20260032065A1 patent drawing
  • US20260032065A1 patent drawing

AI summary

Embodiments include methods for a user equipment (UE) configured to operate in a radio access network (RAN). Such methods include performing a random access (RA) procedure to a cell in the RAN. The RA procedure is performed using resources selected from a RA resource partition based on one or more of the following: a feature or feature combination that triggered the RA procedure, and one or more network slices, slice groups, or slice types associated with the RAN. Such methods include logging and storing in a RA report identifiers of at least one of the following: the RA partition, the feature or feature combination that triggered the RA procedure, and the one or more network slices, slice groups, or slice types associated with the RAN. Such methods include sending the RA report to a RAN node. Other embodiments include complementary methods for a RAN node.