RAN Intelligent Controller Lock-Based Conflict Mitigation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Operational conflicts between applications (xApps) deployed on a radio access network (RAN) can lead to performance degradation and system instability, as different xApps may attempt to configure or control the same network parameters without proper coordination.

Innovation Solution

A computer-implemented method and system that manage operational conflicts by determining whether a request from one xApp to configure a control parameter is permitted by another xApp that has control over that parameter. The system adjusts the parameter only if permission is granted and denies the request if permission is denied or if the adjustment would conflict with an existing configuration.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple xApps are allowed to independently configure control parameters, then system adaptability and functionality are improved, but operational conflicts and system stability deteriorate

Engineering Contradiction:
Improvesystem adaptabilityVSAvoidsystem stability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces a conflict management system that acts as an intermediary between multiple xApps and the control parameters they seek to configure. This mediator detects potential conflicts before they occur and resolves them through a structured process, allowing multiple xApps to coexist and configure parameters without directly interfering with each other, thus maintaining both adaptability and stability

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If access to control parameters is restricted through permission checks, then system stability is improved, but operational complexity and processing time worsen

Engineering Contradiction:
Improvesystem stabilityVSAvoidoperational complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The conflict management system performs preliminary detection and resolution of potential conflicts before xApps actually configure control parameters. By checking for conflicts in advance and establishing a resolution process beforehand, the system avoids the need for complex real-time permission checks during parameter configuration, reducing operational complexity while maintaining stability

Inventive Principle:
Principle #10Preliminary action

3Reliability

If conflict detection and resolution processes are implemented, then system stability is improved, but processing time and operational efficiency worsen

Engineering Contradiction:
Improvesystem stabilityVSAvoidoperational efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system applies preliminary anti-action by detecting and preventing conflicts before they can negatively impact system operation. The conflict management system proactively identifies potential conflicts and resolves them through a structured process that includes detecting conflicts, determining which xApp should have priority, and preventing the conflicting configuration from being applied, thus maintaining stability without requiring continuous monitoring and intervention

Inventive Principle:
Principle #9Preliminary anti-action

Data Source

PatentUS20250119761A1Lock-based conflict mitigation of a radio access network intelligent controller
Publication Date: 2025.04.10 DELL PROD LP
  • US20250119761A1 patent drawing
  • US20250119761A1 patent drawing
  • US20250119761A1 patent drawing

AI summary

The described technology is generally directed towards conflict management of applications implemented on a radio access network (RAN) network. Control of an operational parameter can be assigned to a first xApp such that in the event of a second xApp is configured to adjust the parameter, the effect of applying the second xApp to the parameter is assessed based on whether the second xApp positively or negatively affects the configuration initially applied by the first xApp to the parameter. In the event of the second xApp negatively affecting the parameter, implementation of the second xApp can be denied. In the event of the second xApp positively or neutrally affects the parameter configuration applied by the first xApp, implementation of the second xApp can be approved. While implementation of the second xApp undergoes review, an access lock can be placed on the parameter to prevent another xApp from accessing the parameter.