Link-Based Loop Free Alternates Edge Core Classification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional link-based Loop Free Alternates (LFAs) techniques are inefficient in network topologies with many loop opportunities, failing to provide adequate protection coverage and are complex to implement, while prefix-based LFAs offer better protection but at the cost of performance impact.

Innovation Solution

A method to efficiently determine acceptable link-based LFAs by distinguishing between network edge devices and core devices, using BGP configuration and IGP messages to identify edge and core devices, and computing a shortest path tree to find acceptable LFAs that do not loop back to edge devices, thus expanding protection coverage without cumbersome manual configuration.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional link-based LFA techniques are used, then implementation is simpler, but protection coverage is inadequate in network topologies with many loop opportunities

Engineering Contradiction:
Improveprotection coverageVSAvoidimplementation complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the network into two distinct types: edge devices and core devices. This segmentation allows the LFA determination to focus specifically on whether alternate paths loop back to edge devices, rather than evaluating all possible loops in the network. By dividing the network topology into these functional segments, the patent achieves better protection coverage without requiring complex analysis of the entire network topology.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies local quality by making the LFA determination criterion specific to edge devices rather than applying uniform loop-free requirements to all network devices. The key insight is that loops to core devices are acceptable, while only loops to edge devices need to be avoided. This localized approach to quality control enables broader path selection while maintaining essential protection guarantees.

Inventive Principle:
Principle #3Local quality

2Reliability

If prefix-based LFA techniques are used, then protection coverage is improved, but performance impact increases

Engineering Contradiction:
Improveprotection coverageVSAvoidperformance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent extracts the essential requirement for LFA determination from the complex prefix-based approach: avoiding loops to edge devices. By taking out this critical element and making it the sole criterion for acceptable alternates, the patent achieves good protection coverage without the performance overhead of computing and maintaining per-prefix LFAs. This extraction simplifies the decision process to a binary check: does the path loop to an edge device?

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent changes the evaluation parameter from per-prefix destination analysis to a binary edge-device-loop classification. Instead of computing LFAs for each prefix separately, the patent uses a single parameter (whether the alternate path loops to an edge device) that applies to all traffic. This parameter change dramatically reduces computational complexity while maintaining adequate protection coverage.

Inventive Principle:
Principle #35Parameter changes

3Measurement precision

If manual configuration is used to identify edge and core devices, then accuracy is improved, but operational complexity increases

Engineering Contradiction:
Improvedevice classification accuracyVSAvoidconfiguration simplicity
Core Design Contradiction:
Measurement precisionVSEase of operation

Solution Approach 1:

The patent implements self-service by enabling network devices to automatically classify themselves as edge or core devices based on their local BGP configuration state. Devices with external BGP peers or route origination capabilities automatically identify as edge devices, while others identify as core devices. This self-service approach eliminates the need for manual configuration while maintaining accurate classification, as each device determines its own role based on its actual functional characteristics.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent uses feedback from the device's own BGP configuration state to determine its classification. The device queries its local configuration (external BGP peers, route origination) and uses this feedback to automatically set its edge/core status. This feedback mechanism ensures accurate classification without external intervention, as the classification is directly derived from the device's actual operational state.

Inventive Principle:
Principle #23Feedback

Data Source

PatentEP2036273B1A technique for efficiently determining acceptable link-based loop free alternatives in a computer network
Publication Date: 2015.03.04 CISCO TECHNOLOGY INC
  • EP2036273B1 patent drawingFigure 1
  • EP2036273B1 patent drawingFigure 2
  • EP2036273B1 patent drawingFigure 3

AI summary

A technique efficiently determines acceptable link-based loop free alternates (LFAs) in a computer network. According to the novel technique, a protecting network device configured to protect a link ("protected link") distinguishes other network devices (e.g., of the same domain as the protecting network device) as either network edge devices (i.e., an end point for external network traffic) or network core devices (i.e., not an end point for external network traffic). The protecting network device may then determine whether a neighboring network device loops toward a network edge device. If not, the protecting network device may determine that the neighboring network device is an acceptable LFA (e.g., for external network traffic). Notably, traffic directed to core devices may still loop, however, this traffic is generally internal (e.g., signaling) traffic, and may not be subject to the same operational constraints (e.g., protection) as external traffic.