Self-Organizing Network Coordination via Priority and Impact Analysis

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In self-organizing networks, coordinating multiple independent self-organizing functions from different vendors across various domains is challenging due to the complexity of managing vendor-specific configurations and ensuring conflict-free operations without human intervention.

Innovation Solution

Implementing a mechanism that assigns priorities, impact areas, and impact times to self-organizing network functions, allowing for evaluation and potential locking out of other functions to prevent conflicts, using a network level coordinator and domain level coordinators to manage and coordinate SON functions across different vendor domains.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If parameter values of self-organizing network functions are checked for coordination, then conflict avoidance is achieved, but processing capacity consumption increases and coordination speed decreases

Engineering Contradiction:
Improveconflict avoidanceVSAvoidcoordination speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent extracts the essential coordination attributes from the complex parameter values of SON functions. Instead of checking all parameter values, it identifies and checks only the critical attributes (priority, impact area, impact time) that determine conflicts. This extraction principle reduces the coordination overhead while maintaining conflict avoidance effectiveness.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent segments the coordination check into distinct attribute comparisons rather than evaluating complete parameter values. By dividing the coordination process into separate checks for priority, impact area, and impact time attributes, the system achieves faster coordination while maintaining comprehensive conflict detection.

Inventive Principle:
Principle #1Segmentation

2Reliability

If comprehensive parameter values of self-organizing network functions are exchanged for coordination, then accurate conflict detection is achieved, but information exchange requirements increase

Engineering Contradiction:
Improveconflict detection accuracyVSAvoidinformation exchange overhead
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent extracts only the necessary coordination attributes (priority, impact area, impact time) from the complete parameter values of SON functions. This selective extraction minimizes information exchange between domain level coordinators while preserving the ability to accurately detect conflicts between functions from different vendors.

Inventive Principle:
Principle #2Taking out (Extraction)

3Device complexity

If vendor-specific domains are organized independently without coordination, then device complexity is reduced, but network-wide coordination capability is lost

Engineering Contradiction:
Improvedomain management complexityVSAvoidnetwork-wide coordination
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The patent introduces domain level coordinators as intermediary entities that manage vendor-specific domains independently while enabling network-wide coordination. These coordinators act as mediators that translate and coordinate between different vendor domains using a common attribute-based interface, preserving both domain independence and overall network coordination capability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS9985819B2Coordination in self-organizing networks
Publication Date: 2018.05.29 NOKIA SOLUTIONS & NETWORKS OY
  • US9985819B2 patent drawing
  • US9985819B2 patent drawing
  • US9985819B2 patent drawing

AI summary

To decide, whether or not a SON function instance is allowed to execute, a priority, an impact time and an impact area for the SON function instance is determined, and priorities of other SON function instances scheduled to be run during the impact time of the requesting SON function instance and having an overlapping impact area are compared to the priority of the requesting SON function instance.