RACH Steering for Network Slice Load Balancing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing RACH resource configurations for network slicing in 5G wireless communication networks lead to increased complexity and fragmentation, necessitating a more efficient allocation and optimal fallback mechanisms to balance RACH load across different network slices.

Innovation Solution

A RACH steering mechanism is introduced, where a RAN node generates information indicating available RACH configurations, including network slice-specific, back-up, and common resources, along with their usage probabilities, to dynamically adjust RACH load and provide an optimal fallback framework.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If network slice-specific RACH configurations are introduced for different service categories, then service-specific performance requirements are met, but RACH resource fragmentation and system complexity increase

Engineering Contradiction:
Improveservice-specific performance optimizationVSAvoidRACH configuration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments RACH resources into network slice-specific resources and common resources. Each network slice (eMBB, URLLC, IoT) is assigned dedicated RACH configurations tailored to its service requirements, while common resources provide shared access. This segmentation enables service-specific optimization without requiring complete isolation, thus managing complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements a universal common RACH configuration that can be shared across multiple network slices. This common configuration serves as a fallback option for all slice types (eMBB, URLLC, IoT) and provides a standardized access mechanism, reducing the need for entirely separate configurations for each slice and thereby managing system complexity.

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

2Adaptability or versatility

If multiple RACH configurations and fallback mechanisms are provided for different network slices, then access flexibility is improved, but RACH resource fragmentation increases

Engineering Contradiction:
ImproveRACH access flexibilityVSAvoidRACH resource fragmentation
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent merges multiple RACH configurations (slice-specific and common) into a unified resource pool managed by a single RACH configuration index. This indexing mechanism allows the network to dynamically select and switch between different RACH configurations without requiring physically separate resource sets, thereby reducing resource fragmentation while maintaining access flexibility.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent introduces dynamic RACH configuration selection where the network can switch between slice-specific and common RACH configurations based on current network conditions, slice type, and service requirements. This dynamic allocation allows resources to be flexibly assigned without permanent fragmentation, as the same physical resources can serve multiple purposes at different times.

Inventive Principle:
Principle #15Dynamics

3Reliability

If comprehensive fallback mechanisms are implemented for switching between two-step and four-step RACH procedures, then access reliability is improved, but procedure complexity increases

Engineering Contradiction:
ImproveRACH access reliabilityVSAvoidfallback mechanism complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent configures fallback mechanisms in advance through pre-defined RACH configuration indices. The network prepares multiple RACH configurations (two-step and four-step procedures) ahead of time and assigns them specific indices. When a fallback is needed, the network simply switches to a pre-configured alternative, avoiding complex real-time decision logic and reducing procedural complexity.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback-based fallback mechanisms where the network monitors RACH procedure outcomes (success/failure) and dynamically switches between two-step and four-step procedures based on observed performance. This feedback-driven approach automates the fallback decision process, improving reliability while managing complexity through rule-based responses to specific conditions.

Inventive Principle:
Principle #23Feedback

Data Source

PatentEP4381877B1Random access channel steering based on network slicing
Publication Date: 2026.02.18 NOKIA TECHNOLOGIES OY
  • EP4381877B1 patent drawingFigure 1
  • EP4381877B1 patent drawingFigure 2
  • EP4381877B1 patent drawingFigure 3

AI summary

The present disclosure relates to a technique for steering a Random Access Channel (RACH) a wireless communication network supporting a set of network slices. More specifically, the technique involves generating, at a RAN node, RACH steering information for the set of network slices. The RACH steering information comprises an indication for a UE to select one of available RACH configurations with a RACH configuration-specific probability. In one embodiment, the RACH steering information may be defined based on at least one network slice-specific RACH policy or at least one network slice-specific resource sharing quota provided from a network management entity to the RAN node. In another embodiment, the RAN node may generate RACH steering information based on locally available information about the set of network slices. Once the RACH steering information is generated, the RAN node transmits it to the UE. By using the RACH steering information, it is possible to dynamically adjust a RACH load among multiple network slice-specific RACH configurations and common RACH configurations, thereby efficiently balancing the RACH load (i.e., RACH utilization rate) across the set of network slices.