Service Plane Fast Reroute for Network Failure Detection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional link state protocols in computer networks take a long time to adapt to failures, leading to traffic loss and performance issues in applications like VoIP and multimedia, as they require updating forwarding tables and recalculating paths, which can take up to several seconds.

Innovation Solution

Implementing a monitor component at the service layer to detect failures or degradation of service enabling technology functions, which triggers a fault detection network protocol to reroute traffic through a backup path using Bidirectional Forwarding Detection (BFD) and Fast Reroute mechanisms, allowing for automatic rerouting without operator intervention.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional link state protocols (OSPF/IS-IS) are used to detect and adapt to node/link failures, then the network can maintain routing consistency, but the convergence time is long (500 milliseconds to several seconds) causing traffic loss

Engineering Contradiction:
Improverouting consistencyVSAvoidconvergence time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent establishes Fast Reroute (FRR) backup paths in advance before failures occur. When a service function fails, the ingress router can immediately switch traffic to the pre-computed backup path without waiting for traditional link-state protocol convergence, thus resolving the contradiction between routing consistency and convergence time

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements a monitoring mechanism that continuously tracks the operational status of service functions. When a failure is detected, the system provides feedback to trigger Fast Reroute, enabling rapid response to failures without waiting for periodic link-state protocol updates, thereby reducing convergence time while maintaining routing consistency

Inventive Principle:
Principle #23Feedback

2Reliability

If Fast Reroute is implemented to reduce convergence time and prevent traffic loss, then service continuity is improved, but the system complexity increases due to additional monitoring components and backup path management

Engineering Contradiction:
Improveservice continuityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a dedicated monitoring component as an intermediary between the service function and the Fast Reroute mechanism. This intermediary handles the complexity of service status detection and failure notification, allowing the core Fast Reroute system to remain relatively simple while still achieving improved service continuity

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The monitoring component autonomously detects service function failures and triggers Fast Reroute without requiring manual intervention or complex centralized control. This self-service approach reduces the operational complexity of managing FRR systems while maintaining high service continuity

Inventive Principle:
Principle #25Self-service

3Reliability

If service function performance degradation is monitored and Fast Reroute is triggered, then service level agreements are maintained, but false positives may cause unnecessary traffic rerouting and network disruption

Engineering Contradiction:
Improveservice level agreement complianceVSAvoidfalse positive rerouting
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent implements threshold-based monitoring that compares service function performance against predefined thresholds before triggering Fast Reroute. This preliminary check prevents false positives by ensuring that only significant performance degradations trigger rerouting, while minor fluctuations are ignored, thus maintaining SLA compliance without causing unnecessary disruptions

Inventive Principle:
Principle #9Preliminary anti-action

Data Source

PatentEP2680510B1Service plane triggered fast reroute protection
Publication Date: 2015.09.09 JUNIPER NETWORKS INC
  • EP2680510B1 patent drawingFigure 1
  • EP2680510B1 patent drawingFigure 2
  • EP2680510B1 patent drawingFigure 3

AI summary

Techniques are described for detecting failure or degradation of a service enabling technology function independent from an operational state of a service node hosting the service enabling technology function. For example, a service node may provide one or more service enabling technology functions, and service engineered paths may be traffic-engineered through a network to service node network devices that host a service enabling technology function. A monitor component at the service layer of the service node can detect failure or degradation of one or more service enabling technology functions provided by the service node. The monitor component reports detection of failure or degradation to a fault detection network protocol in a forwarding plane of the service node. The fault detection network protocol communicates with an ingress router of a service engineered path to trigger fast reroute by the ingress of traffic flows to bypass the affected service enabling technology function.