Network Topology Discovery Resolving Loops in Uplink Metadata
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network monitoring and management systems fail to provide accurate and real-time network topology discovery, especially in environments with both compliant and non-compliant networking devices, leading to outdated topology maps and unresolved loops in uplink metadata.
Innovation Solution
The implementation of systems and methods that determine the existence of loops in uplink metadata by identifying compliant devices, resolving these loops by adding non-compliant devices to the topology-link map data, and tracing paths to connect disconnected partial trees and determine non-external facing port connections using uplink metadata.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If network monitoring systems use traditional topology discovery methods, then the system complexity is reduced, but the topology map becomes outdated and inaccurate due to non-compliant devices
Solution Approach 1:
The patent introduces an intermediary processing layer that receives uplink metadata from compliant devices, processes it to identify loops and non-compliant devices, and generates corrected topology maps. This intermediary function separates the complexity of handling non-compliant devices from the core topology discovery process, allowing accurate topology mapping without requiring all devices to be compliant.
Solution Approach 2:
The system implements feedback mechanisms by continuously monitoring uplink metadata, detecting loops and non-compliant device behavior, and using this information to correct and update topology maps in real-time. This feedback loop ensures the topology map remains accurate despite the presence of non-compliant devices that would otherwise cause it to become outdated.
2Measurement precision
If the system processes uplink metadata from all devices, then topology discovery accuracy improves, but processing time increases due to loop detection and resolution
Solution Approach 1:
The patent segments the topology discovery process into distinct phases: collecting uplink metadata, detecting loops, resolving loops by identifying non-compliant devices, and generating corrected topology maps. This segmentation allows the system to process data in manageable stages rather than attempting to analyze everything simultaneously, reducing overall processing time while maintaining accuracy.
Solution Approach 2:
The system extracts and isolates problematic elements (loops and non-compliant devices) from the overall topology data set. By identifying and separating these problematic elements, the system can process the remaining valid topology information more efficiently while still accounting for the exceptions, thus reducing processing time compared to analyzing every detail equally.
3Reliability
If the system resolves loops by adding non-compliant devices, then topology map reliability improves, but the number of entries in topology-link map data increases
Solution Approach 1:
The patent applies local quality by adding non-compliant devices only where necessary to resolve specific loops, rather than uniformly adding entries throughout the entire topology map. This targeted approach ensures reliability is improved only in the specific areas where loops were detected, minimizing the overall increase in data volume while maintaining accuracy where it matters most.
Data Source
AI summary
Previously available network management systems fail to adequately enable discovery of a network topology that includes both compliant and non-compliant networking devices. By contrast, and to that end, various implementations disclosed herein include systems, methods and apparatuses that determine whether or not a loop exists within uplink metadata associated with first and second compliant devices, wherein the loop in the uplink metadata is characterized by pointers provided to indicate that the first and second compliant devices operate to send externally addressed traffic to one another contrary to the operation of the first and second compliant devices within a network; and resolve the loop by adding a non-compliant device to topology-link map data associated with the first and second compliant devices in response to determining the existence of the loop, wherein the topology-link map data archives accessible information about the topology of the network based at least on the uplink metadata.