Network Link Failure Detection via Continuous Packet Monitoring
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current techniques for detecting link failures in computer networks are inefficient, often consuming significant resources or taking too long to detect failures, which can reduce the effectiveness of Rapid Spanning Tree Protocol (RSTP) recovery processes.
Innovation Solution
A system and method that includes a failure detection engine in network devices, which generates and exchanges failure detection packets to continuously monitor links, allowing for rapid detection of interruptions and immediate shutdown of failed links, with the ability to re-establish connections once the failure is resolved.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional link failure detection methods are used, then network reliability is maintained, but detection time is too long and resources are consumed significantly
Solution Approach 1:
The patent implements preliminary action by continuously transmitting detection packets before actual failures occur. The system proactively sends packets at regular intervals to monitor link status, so when a failure happens, the detection is already in progress and can immediately detect the interruption, eliminating waiting time for failure detection.
Solution Approach 2:
The patent applies periodic action by transmitting failure detection packets at predetermined time intervals. This continuous periodic monitoring ensures that link status is constantly checked without requiring significant resources, achieving both fast detection and efficient resource utilization through rhythmic, predictable packet transmission.
2Speed
If continuous monitoring packets are transmitted, then detection speed is improved, but network bandwidth is consumed
Solution Approach 1:
The patent uses partial action by transmitting detection packets only when necessary for failure detection, rather than continuously flooding the network with data. The system sends packets at optimized intervals just sufficient to detect failures quickly, avoiding excessive bandwidth consumption while maintaining adequate detection speed.
Solution Approach 2:
The patent applies parameter changes by dynamically adjusting the transmission interval of detection packets based on network conditions and requirements. By modifying the time parameter between packets, the system optimizes the balance between detection speed and bandwidth consumption, transmitting more frequently when needed and less frequently when stable.
3Loss of time
If rapid failure detection is implemented, then network recovery time is reduced, but device complexity increases
Solution Approach 1:
The patent implements feedback by having receiving devices respond to detection packets with acknowledgment packets. This feedback mechanism allows the sending device to determine link status based on the presence or absence of responses, enabling rapid failure detection through a relatively simple mechanism that doesn't require complex analysis or processing.
Solution Approach 2:
The patent applies self-service by enabling network devices to autonomously monitor their own link status through the detection packet mechanism. Each device independently sends and receives detection packets, automatically detecting failures without requiring external monitoring systems or complex centralized control, thus reducing overall system complexity.
Data Source
AI summary
A system and method monitors links in a computer network and rapidly detects failures of such links. Network entities disposed at opposite ends of a link are provided with failure detection engines that signal their presence to each other. Thereafter, each failure detection engine ensures that its entity transmits a continuous stream to the other entity by sending either data frames or newly defined failure detection packets. If an interruption in this continuous stream is detected, then the failure detection engine concludes that the link has failed. In response, the failure detection engine preferably notifies other applications or protocols of the failure, and causes the link to be shut-down.