Control Node for Automated KPI Reliability Verification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current approaches for monitoring Key Performance Indicators (KPIs) across multiple Mobile Network Operators (MNOs) are cumbersome, requiring manual agreements and lacking in accuracy, as they rely on manual interconnectivity and lack automated mechanisms to verify the reliability of reported KPIs.

Innovation Solution

A method and apparatus that utilize a distributed ledger to store subscriber and network slice information, enabling automated KPI reporting and reliability verification through a control node that receives requests for performance indicators, determines their reliability using a performance indicator profile, and performs actions based on this determination.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual agreements and interconnectivity are used to monitor KPIs across multiple MNOs, then connectivity service can be provided across geographical boundaries, but the process becomes cumbersome and lacks accuracy in verifying KPI reliability

Engineering Contradiction:
Improvecross-MNO connectivity serviceVSAvoidmanual agreement process
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

A control node is introduced as an intermediary between third-party nodes and communication networks. The control node receives requests for performance indicator values from third-party nodes, automatically retrieves these values from multiple communication networks, and provides them to the third-party node. This automated intermediary eliminates the need for manual agreements and interconnectivity setup between MNOs, while maintaining the ability to provide cross-MNO connectivity services.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If automated KPI reporting is implemented across multiple MNOs, then monitoring efficiency is improved, but verifying the reliability of reported KPIs becomes challenging

Engineering Contradiction:
ImproveKPI monitoring efficiencyVSAvoidKPI reporting accuracy
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The control node implements a feedback mechanism where it receives performance indicator values from communication networks and provides them back to third-party nodes that requested them. This automated feedback loop enables continuous monitoring of KPIs across multiple MNOs with improved efficiency. The system maintains reliability by having the control node directly retrieve values from source networks, ensuring accurate transmission of KPI data without manual intervention errors.

Inventive Principle:
Principle #23Feedback

3Adaptability or versatility

If trust domains are established between multiple operators for capability exposure, then service capability can be shared across networks, but the setup and management becomes technically complex

Engineering Contradiction:
Improveservice capability exposureVSAvoidtrust domain configuration
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The control node serves multiple functions: it acts as a gateway for capability exposure, a data collection point for KPIs, and a communication interface between third-party nodes and multiple communication networks. By consolidating these functions in a single multi-functional node, the system enables service capability sharing across networks without requiring complex individual trust domain configurations between each pair of operators.

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

Data Source

PatentUS20240388945A1Reliability of reported performance indicators
Publication Date: 2024.11.21 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US20240388945A1 patent drawing
  • US20240388945A1 patent drawing
  • US20240388945A1 patent drawing

AI summary

According to an aspect, there is provided a method of operating a control node, the method including receiving, from a third party node, a request for a value of a first performance indicator relating to one or more subscribers or to a first network slice; receiving, from a first communication network, a first value of the first performance indicator relating to the one or more subscribers in the first communication network or to the first network slice in the first communication network; determining a reliability of the received first value using a performance indicator profile; and performing an action with respect to the received request based on the determined reliability of the received first value.