Application Assurance Using Flow-Defined Network Impact Detection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing network performance monitoring systems struggle to reliably identify which applications are affected by network outages or degradations and cannot predict potential impacts on applications, making it difficult for NetOps teams to prioritize remediation and prevent failures.

Innovation Solution

The application assurance system uses flow definitions to identify a set of network nodes and links relevant to specific applications, applying telemetry and analytics to detect current and potential performance issues, and outputs alerts to assist NetOps in proactive management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If network performance monitoring systems detect issues with network elements and attempt to identify affected applications, then network infrastructure monitoring capability is improved, but the ability to reliably identify affected applications and predict potential impacts deteriorates

Engineering Contradiction:
Improvenetwork infrastructure monitoring capabilityVSAvoidapplication impact identification reliability
Core Design Contradiction:
Measurement precisionVSReliability

Solution Approach 1:

The patent inverts the traditional monitoring approach by starting with application flow definitions and identifying relevant network nodes, rather than starting with network node monitoring and trying to identify affected applications. This inversion enables reliable application impact identification by establishing a direct causal link from network elements to specific applications through flow definitions.

Inventive Principle:
Principle #13The other way round (Inversion)

Solution Approach 2:

The system performs preliminary actions by pre-defining application packet flows and pre-identifying the set of network nodes and links relevant to each application before failures occur. This allows the system to predict potential impacts on applications proactively, rather than reactively identifying affected applications after network issues arise.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If traditional network performance monitoring approaches are used, then network device monitoring is improved, but proactive application performance assurance and failure prevention capability deteriorates

Engineering Contradiction:
Improvenetwork device monitoringVSAvoidMean Time to Recover (MTTR) and Mean Time Between Failures (MTBF)
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by continuously monitoring the operational state of network nodes and links relevant to applications and predicting potential performance issues before they cause failures. This enables proactive remediation, reducing Mean Time to Recover (MTTR) and Mean Time Between Failures (MTBF) by addressing issues before they impact applications.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback by continuously monitoring network node operational states, comparing them against expected states for application performance, and generating alerts when deviations are detected. This feedback loop enables proactive application performance assurance by notifying operators of potential issues before they degrade application performance.

Inventive Principle:
Principle #23Feedback

3Loss of information

If network monitoring systems attempt to monitor all network nodes and links, then comprehensive network visibility is improved, but the ability to focus on application-relevant infrastructure deteriorates due to information overload

Engineering Contradiction:
Improvenetwork visibility completenessVSAvoidmonitoring system complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent extracts only the network nodes and links that are relevant to specific applications by using flow definitions to identify the subset of network infrastructure that actually transports application packet flows. This extraction eliminates information overload from unrelated network elements while maintaining complete visibility into application-relevant infrastructure.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system applies local quality by providing different levels of monitoring detail for different network elements based on their relevance to applications. Network nodes and links that are relevant to applications receive detailed monitoring and analysis, while unrelated elements are excluded, optimizing the monitoring system's focus and reducing complexity.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS12355613B1Application assurance
Publication Date: 2025.07.08 JUNIPER NETWORKS INC
  • US12355613B1 patent drawing
  • US12355613B1 patent drawing
  • US12355613B1 patent drawing

AI summary

This disclosure describes techniques for providing application assurance by validating expected packet flows for an application against a model of a network that is to transport the expected packet flows. For example, a method includes obtaining, by an application assurance system, a flow definition that describes a packet flow for an application; determining, by the application assurance system by querying a network model of a network system that transports packet flows for applications, using the flow definition, a set of network nodes and links of the network system that are expected to transport or process the packet flow for the application; obtaining, by the application assurance system, an indication that a network node or link, from the set of network nodes and links, is in an operational state that could affect performance of the application; and in response to obtaining the indication, by the application assurance system, outputting an alert.