Two-Phase RAN Slice Configuration for Dynamic Network Conditions

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing technologies lack efficient methods for RAN configuration in slice-based networks, particularly in New Radio (NR) networks, as they fail to address dynamic situations such as channel availability, user mobility, and isolation requirements, leading to suboptimal RAN behavior and service provision.

Innovation Solution

The proposed solution involves a two-phase RAN configuration approach, comprising a pre-configuration phase during network deployment and an adaptation phase for dynamic adjustments, utilizing a Slice Management entity and RAN entity to abstract context information, map traffic flows to appropriate RAN configurations, and adapt to changes in traffic and RAN characteristics.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If pre-configured RAN settings are used for all slices, then device complexity is reduced and ease of operation is improved, but adaptability to different slice requirements and dynamic RAN conditions deteriorates

Engineering Contradiction:
ImproveRAN configuration managementVSAvoidSlice-specific RAN configuration adaptation
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The RAN configuration is segmented into common parameters applicable to all slices and slice-specific parameters that can be individually customized. This allows the system to maintain simple common configurations while enabling specialized adaptations for different slice requirements through separate configuration sets.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The RAN configuration system transitions from static pre-configured settings to dynamic adaptive configurations. The network can now adjust RAN parameters in real-time based on slice-specific requirements and changing RAN conditions, with configurations that can be modified without complete reconfiguration.

Inventive Principle:
Principle #15Dynamics

2Adaptability or versatility

If detailed slice-specific RAN configurations are implemented, then adaptability to different slice requirements is improved, but device complexity and configuration management difficulty increase

Engineering Contradiction:
ImproveSlice-specific RAN configurationVSAvoidRAN configuration management
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

Common RAN configuration parameters are pre-configured and stored as template settings that can be rapidly deployed across multiple slices. This preliminary configuration reduces the need for detailed manual configuration of each slice while maintaining the ability to customize slice-specific parameters when needed.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

A configuration management intermediary layer is introduced that handles the complexity of slice-specific RAN configurations. This intermediary manages the mapping between slice requirements and appropriate RAN configuration parameters, shielding the complexity from operators while enabling detailed customization.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Stability of the object's composition

If RAN configuration is statically pre-configured, then configuration stability is improved and operational simplicity is maintained, but responsiveness to changing RAN conditions and traffic patterns deteriorates

Engineering Contradiction:
ImproveRAN configuration stabilityVSAvoidDynamic RAN configuration adaptation
Core Design Contradiction:
Stability of the object's compositionVSAdaptability or versatility

Solution Approach 1:

The RAN configuration system enables dynamic adaptation to changing conditions while maintaining stability for common parameters. Slice-specific parameters can be adjusted in response to traffic patterns, channel conditions, and RAN state changes, allowing the system to remain stable overall while adapting locally where needed.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

A feedback mechanism is implemented that monitors RAN conditions and slice performance, automatically triggering configuration adjustments when thresholds are exceeded. This feedback loop maintains configuration stability under normal conditions while enabling adaptive responses to changing conditions without manual intervention.

Inventive Principle:
Principle #23Feedback

4Manufacturing precision

If manual RAN configuration adjustment is used, then configuration precision is improved, but response time to changing conditions and productivity deteriorate

Engineering Contradiction:
ImproveRAN configuration precisionVSAvoidConfiguration deployment speed
Core Design Contradiction:
Manufacturing precisionVSProductivity

Solution Approach 1:

The RAN configuration system incorporates self-service capabilities that automatically adjust configurations based on monitored conditions and slice requirements. This self-configuration maintains precision by using validated configuration parameters while dramatically improving deployment speed by eliminating manual configuration steps.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

Validated RAN configuration templates and parameter sets are prepared in advance through preliminary configuration activities. These pre-validated configurations can be rapidly deployed with high precision, combining the accuracy of careful configuration with the speed of automated deployment.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP3596961B1Techniques for radio access network (RAN) configuration in slice-based networks
Publication Date: 2025.08.06 HUAWEI TECH CO LTD
  • EP3596961B1 patent drawingFigure 1
  • EP3596961B1 patent drawingFigure 2
  • EP3596961B1 patent drawingFigure 3

AI summary

The disclosure relates to a Slice Management entity (700, 222) for a Radio Access Network (RAN) (230), the Slice Management entity (700, 222) comprising a processor (701), configured: to receive RAN Slice information (703, 401), in particular at least one Key Performance Indicator (KPI) (221), a Slice Identifier (ID), and/or Network Slice Selection Assistance Information (NSSAI) (226) and the context changes, to determine a configuration (704), in particular a pre-configuration (402), for at least one Slice of the RAN (230) based on the RAN Slice information (703, 401), and to transmit a RAN Slice configuration message (224, 403) to the RAN (230) based on the configuration (704).