Deduplication Logic for Accurate Fault Attribution in IP Call Monitoring

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current network monitoring systems inaccurately attribute fault for failed internet protocol-based calls, leading to duplicated blame and skewed performance statistics, which increases the mean time to repair and operational costs.

Innovation Solution

A deduplication monitoring system that applies deduplication logic to accurately attribute fault to only one call end of a failed call, using a computer-implemented method and system that monitors communication systems and updates logged information to prevent duplicate blame, allowing for accurate output data generation and display via a graphical user interface.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If separate monitoring of different call ends is performed, then comprehensive fault detection is achieved, but duplicate fault attribution occurs leading to skewed performance statistics

Engineering Contradiction:
Improvefault detection accuracyVSAvoidperformance statistic accuracy
Core Design Contradiction:
Measurement precisionVSLoss of information

Solution Approach 1:

The patent introduces an intermediary component (fault attribution logic/mediator system) that sits between the separate call end monitors and the performance statistics generation. This intermediary receives fault information from both call ends, applies deduplication logic to determine the actual fault source, and then attributes fault to only one call end. This resolves the contradiction by maintaining comprehensive fault detection while preventing duplicate attribution that skews statistics.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements feedback mechanisms where fault information from both call ends is continuously monitored and compared. The deduplication logic uses feedback from both sides to make intelligent decisions about actual fault attribution. This feedback loop ensures that while both ends are monitored comprehensively, the final attribution is accurate and non-duplicate, preserving performance statistic integrity.

Inventive Principle:
Principle #23Feedback

2Reliability

If both call ends are penalized for call failure, then thorough investigation is prompted, but mean time to repair increases due to false positives

Engineering Contradiction:
Improvecall failure investigationVSAvoidmean time to repair
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by implementing deduplication logic that determines the actual fault source before fault attribution is finalized. Instead of immediately penalizing both call ends upon detecting a failure, the system first performs preliminary analysis to identify which call end is actually at fault. This preliminary determination prevents false positives and reduces unnecessary investigation time, directly addressing the contradiction between thorough investigation and quick repair.

Inventive Principle:
Principle #10Preliminary action

3Measurement precision

If separate KPI reporting is performed for each call end, then detailed performance tracking is achieved, but false positives are generated confusing resolution plans

Engineering Contradiction:
Improveperformance tracking detailVSAvoidfault attribution accuracy
Core Design Contradiction:
Measurement precisionVSLoss of information

Solution Approach 1:

The patent merges the separate fault attribution processes into a unified deduplication logic system. While KPI tracking remains detailed and separate for each call end, the fault attribution is merged and coordinated through the deduplication mechanism. This ensures detailed performance tracking is maintained while false positives are eliminated, as the merged attribution logic correctly identifies the single actual fault source.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentEP3393084B1System and method for accurate reporting of fault for failed internet protocol-based calls
Publication Date: 2019.08.21 NETSCOUT SYSTEMS INC
  • EP3393084B1 patent drawingFigure 1
  • EP3393084B1 patent drawingFigure 2
  • EP3393084B1 patent drawingFigure 3

AI summary

A system and method to identify a call end associated with a problem that caused failure of an internet protocol-based call. The method includes accessing a first call detail record (CDR) set including at least one CDR associated with a first call end of the failed call, determining from the first CDR set indicators of failure attribution of the failed call, determining whether fault for failure of the failed call is attributed to the first call end based on the indicators of failure attribution; outputting an indication that the fault is attributed to the first call end if it was determined that the fault is attributed to the first call end, and outputting the indication to indicate the first call end is acquitted of the fault if it was determined the fault is not attributed to the first call end.