Automated Network Node Debugging via Event Correlation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Debugging network nodes often requires extensive human and computing resources, leading to misdiagnoses and inefficiencies due to the overwhelming amount of debugging information, especially as the number of network nodes increases.

Innovation Solution

A system and method that detects networking malfunctions, determines potential causes, identifies and performs debugging templates to diagnose the issue, and determines the root cause, thereby reducing the need for human interaction and improving resource efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual debugging procedures are used by human operators, then diagnostic capability can be applied, but the amount of required human and computing resources increases significantly

Engineering Contradiction:
Improvediagnostic capabilityVSAvoidhuman and computing resources
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system enables self-service debugging by automatically detecting computing events, determining potential causes, identifying debugging templates, and executing debugging steps without requiring human operator intervention. The network node itself performs the debugging operations that previously required external human expertise and resources.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent replaces the mechanical system of human operators manually analyzing debugging information with an automated computing system that detects events, determines causes, and executes debugging procedures through software-based event correlation and template matching mechanisms.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Reliability

If extensive debugging information is collected from multiple network nodes, then comprehensive diagnosis is achieved, but the information becomes overwhelming and difficult to handle manually

Engineering Contradiction:
Improvecomprehensive diagnosisVSAvoidinformation handling
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system extracts only the relevant debugging information by automatically detecting specific computing events and correlating them with potential causes. Instead of presenting all available debugging data, the system extracts and presents only the correlated events and debugging steps that are directly relevant to diagnosing the specific malfunction.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces an intermediary automated system that sits between the raw debugging information from multiple network nodes and the human operator. This intermediary automatically collects, correlates, and processes the information, transforming overwhelming raw data into structured debugging templates and relevant findings that are easy to interpret.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Measurement precision

If human operators attempt to reproduce network configurations to collect additional information, then more diagnostic data may be obtained, but extensive resources and time are consumed

Engineering Contradiction:
Improvediagnostic dataVSAvoiddebugging time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system performs preliminary actions by automatically detecting computing events and determining potential causes before human operators can intervene. The automated detection and correlation processes are initiated immediately when malfunctions occur, eliminating the need for time-consuming manual reproduction of network configurations and capturing diagnostic information in real-time.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent enables continuous automated debugging operations that run uninterrupted alongside normal network operations. The system continuously monitors for computing events, performs real-time correlation with potential causes, and executes debugging steps without requiring the network to be taken offline or configurations to be reproduced, maintaining continuous useful diagnostic action.

Inventive Principle:
Principle #20Continuity of useful action

4Adaptability or versatility

If more network nodes are added to the network, then network capability increases, but the amount of debugging information increases to an unmanageable level

Engineering Contradiction:
Improvenetwork capabilityVSAvoiddebugging information
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent implements a universal debugging system that can handle debugging information from any number of network nodes through a single automated platform. The event correlation engine and debugging template system are designed to scale universally, processing events from multiple nodes simultaneously using the same automated mechanisms, regardless of network size.

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

Solution Approach 2:

The system changes the parameter of information processing from manual to automated, fundamentally altering how debugging information is handled. This parameter change enables the system to manage exponentially increasing amounts of debugging information from expanding networks by transforming the processing capability rather than being limited by human capacity.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10169133B2Method, system, and apparatus for debugging networking malfunctions within network nodes
Publication Date: 2019.01.01 JUNIPER NETWORKS INC
  • US10169133B2 patent drawing
  • US10169133B2 patent drawing
  • US10169133B2 patent drawing

AI summary

The disclosed computer-implemented method for debugging network nodes may include (1) detecting a computing event that is indicative of a networking malfunction within a network node, (2) determining, based at least in part on the computing event, one or more potential causes of the networking malfunction, (3) identifying one or more debugging templates that each define debugging steps that, when performed by a computing system, enable the computing system to determine whether the networking malfunction resulted from any of the potential causes, (4) performing a set of debugging steps defined by one of the debugging templates that corresponds to one of the potential causes, and then (5) determining, based at least in part on the set of debugging steps defined by the debugging template, that the networking malfunction resulted from the potential cause. Various other methods, systems, and apparatuses are also disclosed.