Traffic Cleaning Equipment Network Loop Detection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Network loops caused by policy-based routing configuration errors in DDoS cleaning equipment lead to network unavailability, as traffic is repeatedly diverted between routers and cleaning equipment, resulting in IP address errors and disrupted network operations.

Innovation Solution

Implementing a method in traffic cleaning equipment to identify network loops by tracking Time To Live (TTL) reductions in data packets, determining destination IP addresses, and recording changes in TTL values to detect abnormal loop formations, thereby preventing further diversion and restoring network usability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If DDoS cleaning equipment is deployed in in-path mode, out-of-path mode, or diversion mode to clean attack traffic, then network security and traffic cleaning capability are improved, but policy-based routing configuration errors can cause IP address errors and network loops that make the network unusable

Engineering Contradiction:
Improvenetwork securityVSAvoidnetwork usability
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system performs preliminary detection of network loops by monitoring TTL values of data packets before they cause complete network failure. The loop detection mechanism proactively identifies abnormal TTL reduction patterns and prevents further traffic diversion, thereby maintaining network usability while preserving security cleaning capabilities

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements a feedback mechanism that continuously monitors TTL values of packets passing through cleaning equipment and routers. When abnormal TTL reduction is detected indicating a loop, the system provides feedback to stop further diversion of that destination's traffic, creating a self-correcting system that maintains network usability

Inventive Principle:
Principle #23Feedback

2Measurement precision

If traffic is repeatedly diverted between routers and cleaning equipment due to routing configuration errors, then loop detection capability is needed, but network operations are disrupted and IP address errors occur

Engineering Contradiction:
Improveloop detection capabilityVSAvoidnetwork operation continuity
Core Design Contradiction:
Measurement precisionVSReliability

Solution Approach 1:

The system replaces complex routing configuration debugging with a simpler TTL-based detection mechanism. By monitoring the Time To Live field in IP packets, the system can automatically detect loops without requiring manual routing analysis, thereby maintaining network operation continuity while providing precise loop detection

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

Solution Approach 2:

The loop detection system is self-service in that it automatically monitors TTL values, detects abnormal patterns indicating loops, and triggers corrective actions without requiring manual intervention. This automated self-diagnosis and self-correction maintains network reliability while providing continuous monitoring capability

Inventive Principle:
Principle #25Self-service

Data Source

PatentEP3353957B1Method and system for identifying network loops
Publication Date: 2022.07.06 ALIBABA GROUP HOLDING LTD
  • EP3353957B1 patent drawingFigure 1A
  • EP3353957B1 patent drawingFigure 1B
  • EP3353957B1 patent drawingFigure 2

AI summary

Identifying network loops is disclosed including determining a first data packet having a time to live (TTL) that at least meets a first condition, the first data packet having a destination internet protocol (IΡ) address; within a time period after the determining of the first data packet, identifying a plurality of second data packets that are to be transmitted to the destination IΡ address; and determining whether a network loop exists for the destination IP address based on TTLs of the plurality of second data packets.