Service-Based Loss Forwarding for Fast Network Fault Detection

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current network architectures face significant delays in converging redundant paths following a link failure in physically non-transparent networks, affecting communication redundancy and fault management efficiency.

Innovation Solution

The implementation of Service-based Loss Forwarding (SLF) mechanism in network nodes, which includes Maintenance End Points (MEPs) and databases to rapidly detect and manage client interface and service faults, enabling quick communication of errors and selective action on affected interfaces, mimicking the response time of physical point-to-point connections.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional routing protocols (OSPF) are used to detect and establish redundant paths in physically non-transparent networks, then routing tables are automatically updated, but the convergence time is substantial (minutes)

Engineering Contradiction:

Improveredundant path establishmentVSAvoidconvergence time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent pre-establishes backup paths and pre-configures fast re-route (FRR) mechanisms before failures occur. When a link failure is detected, the backup path is immediately activated without waiting for routing protocol recalculation, reducing convergence time from minutes to seconds

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary loss forwarding mechanism that detects link failures and triggers backup path activation independently of the traditional routing protocol. This intermediary system bridges the gap between physical layer failures and network layer recovery, enabling faster response

Inventive Principle:

Principle #24Intermediary (Mediator)

2Loss of time

If ECMP with Fast ReRoute (FRR) is used to reduce convergence time, then backup paths are pre-configured, but detection and propagation time remain (convergence time reduces to ~1 minute)

Engineering Contradiction:

Improveconvergence timeVSAvoidrouting table configuration

Core Design Contradiction:

Loss of timeVSDevice complexity

Solution Approach 1:

The patent pre-configures multiple routes in the routing table with different metrics, where backup routes are prepared in advance but not used during normal operation. Upon failure detection, the backup route is immediately activated without requiring routing table updates, eliminating SPF calculation time

Inventive Principle:

Principle #10Preliminary action

3Loss of time

If physical point-to-point connections are used to achieve fast failure detection, then convergence time is reduced to dual digit milliseconds, but direct physical connections are not possible in most applications

Engineering Contradiction:

Improvefailure detection timeVSAvoidnetwork topology flexibility

Core Design Contradiction:

Loss of timeVSAdaptability or versatility

Solution Approach 1:

The patent creates a logical copy of the direct physical connection experience by implementing loss forwarding mechanisms that simulate the fast failure detection characteristics of point-to-point links. The system monitors packet loss patterns to detect failures, replicating the rapid detection capability without requiring physical direct connections

Inventive Principle:

Principle #26Copying

4Loss of time

If layer 1 loss forwarding is used to propagate network errors, then fast error propagation is achieved, but not impacted services are also affected

Engineering Contradiction:

Improveerror propagation timeVSAvoidservice impact scope

Core Design Contradiction:

Loss of timeVSObject-affected harmful factors

Solution Approach 1:

The patent implements service-based loss forwarding that applies loss forwarding selectively to individual services rather than globally. When a failure is detected, only the affected service experiences loss forwarding, while other services continue normally. This is achieved by maintaining service-specific forwarding rules and monitoring

Inventive Principle:

Principle #3Local quality

Data Source

PatentUS11388041B2Service-based loss forwarding in communication networks

Publication Date: 2022.07.12 XIEON NETWORKS SARL

AI summary

A network node (3, 4) comprising at least one client interface port (40) and a database (46, 48) storing data allowing to retrieve for a given client interface, a service associated therewith, for a given service, a client interface associated therewith. A Maintenance End Point (MEP) (50, 52) is established on the network node and is associated with an end-to-end service between a client device (10, 12) connected with said client interface port and a remote client device connected to a remote network node (3, 4). Said MEP is configured to exchange connectivity messages with a corresponding MEP (50, 52) established on said remote network node and to detect a client interface fault and a service fault based on connectivity messages received from said corresponding MEP, or based on missing connectivity messages from said corresponding MEP. Said network node is configured to determine which service(s) is (are) related to said client interface and to inform the MEP related to this service about said client interface fault, and is configured to determine which client interface(s) is (are) associated with said service and to carry out a predetermined action associated with said client interface(s).