Network Fault Detection via Connection Release Ratios

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In dynamic hardware allocation systems, accurately identifying faulty elements is challenging due to erratic behavior and the difficulty in determining which element is faulty when one element's failure affects the entire functionality of a path.

Innovation Solution

A method involving selecting network elements, attempting to establish connections, counting dropped connections, and determining faulty elements based on higher counts of connection releases, which can be performed by a central management node or the elements themselves, allowing self-diagnosis.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If dynamic hardware allocation is used to allow flexible path selection, then adaptability is improved, but fault detection capability deteriorates because faulty elements cannot be accurately identified

Engineering Contradiction:
Improvepath selection flexibilityVSAvoidfaulty element identification
Core Design Contradiction:
Adaptability or versatilityVSDifficulty of detecting and measuring

Solution Approach 1:

The system implements feedback by monitoring connection establishment attempts and tracking which connections are released due to faults. Each network element reports back information about connection failures, allowing the management node to accumulate data and identify faulty elements based on patterns in the feedback information.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

A management node acts as an intermediary between network elements and the fault detection process. This intermediary collects connection attempt data from multiple elements, processes the information centrally, and identifies faulty elements by analyzing the aggregated data, thereby solving the identification problem that individual elements cannot solve alone.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If multiple network elements are used to establish dynamic paths, then system versatility is improved, but the complexity of fault detection increases due to erratic faulty behavior

Engineering Contradiction:
Improvesystem flexibilityVSAvoidfault detection complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The fault detection process is segmented into distinct steps: selecting network elements, attempting connection establishment, monitoring connection releases, and analyzing results. This segmentation breaks down the complex fault detection problem into manageable, systematic operations that can be performed sequentially.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system changes parameters by tracking the number of connection attempts versus connection successes for each network element. By monitoring these quantitative parameters and identifying significant deviations (elements with unusually high failure rates), the system can objectively identify faulty elements without complex diagnostic procedures.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS8582444B2Method for detecting hardware faults by determining a ratio of released connections
Publication Date: 2013.11.12 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US8582444B2 patent drawing
  • US8582444B2 patent drawing
  • US8582444B2 patent drawing

AI summary

The present invention provides a method of detecting a faulty network element in a network, the network comprising at least a plurality of first network elements having a first network element type, and at least a plurality of second network elements having a second network element type. The method comprises the steps of: a) selecting one of the plurality of first network elements and one of the plurality of second network elements; b) attempting to set up a connection between said selected first network element and said selected second network element; c) repeating steps a) and b) for further selected first and second network elements; d) for each of the plurality of first network elements and for each of the plurality of second network elements, counting a number of connections that are released as the result of a fault; and e) for a particular one of the first or second network elements, on the basis of said number of connections that are released in said particular network element as a result of a fault, determining whether said particular network element is faulty.