Network Topology Change Detection Using Checksum-Based Polling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for managing network topology changes are resource-intensive and inefficient, often leading to unnecessary updates and data losses, as they rely on time-based polling and cannot accurately identify changes made by external configuration tools or proprietary protocols, and update the entire network regardless of specific changes.
Innovation Solution
A method that involves calculating and comparing checksum values for sensitive network elements during primary and secondary pollings, updating only the affected elements in the topology database, thereby reducing unnecessary updates and optimizing polling processes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If total discovery of network infrastructure is performed in a scheduled manner to update topology database, then network topology management is achieved, but excessive quantity of resources and time are occupied
Solution Approach 1:
The patent segments the network elements into two categories: sensitive elements (those with configuration changes to track) and non-sensitive elements. This segmentation allows the system to apply different polling strategies to different segments, performing detailed checksum verification only on sensitive elements while using simpler presence detection for non-sensitive elements, thereby reducing overall resource consumption while maintaining reliable topology management.
Solution Approach 2:
The patent applies partial action by performing complete checksum verification only on sensitive network elements rather than all network elements. The system calculates checksums only for elements where configuration changes are expected or relevant, avoiding the excessive resource consumption of verifying every element in the network while still achieving reliable topology management for the critical subset.
2Productivity
If time-recording meters are used to track user connections and configuration changes, then change tracking is achieved, but unnecessary updates are authorized and data losses occur
Solution Approach 1:
The patent replaces the mechanical time-recording meter approach with a cryptographic checksum verification system. Instead of relying on time-based presence indicators that can trigger false updates, the system uses checksum algorithms to mathematically verify whether actual configuration changes have occurred. This substitution eliminates false positives and information loss by providing accurate binary detection of real changes versus mere time-based events.
Solution Approach 2:
The patent implements feedback through checksum verification where the system continuously monitors sensitive network elements, calculates their checksums, and compares them against previous values. This feedback mechanism provides accurate information about actual configuration changes, enabling the system to distinguish between genuine changes requiring updates and unchanged elements, thereby preventing unnecessary updates and information loss.
3Adaptability or versatility
If configuration changes are tracked using external configuration tools with proprietary protocols or SNMP sets, then configuration monitoring is achieved, but changes made by these tools are not identified
Solution Approach 1:
The patent uses copying by retrieving configuration data from multiple sources including external configuration tools, SNMP agents, and direct device queries. By obtaining copies of the configuration data through various protocols and methods, the system can compute checksums from these copies and compare them against stored values, enabling detection of changes regardless of which tool or protocol made the modification.
Solution Approach 2:
The patent implements universality by designing a checksum-based detection mechanism that works across multiple configuration sources and protocols. The system can monitor configurations from proprietary tools, SNMP sets, and other sources using the same checksum verification approach, making the detection mechanism universally applicable to different configuration management scenarios while maintaining precise change detection.
4Speed
If primary and secondary pollings are performed regularly to detect topology changes, then change detection is achieved, but polling stress is applied to network equipment
Solution Approach 1:
The patent applies local quality by differentiating the polling intensity applied to different network elements. Sensitive elements undergo frequent secondary pollings with checksum verification, while non-sensitive elements receive less frequent primary pollings with simpler presence detection. This localized approach enables rapid change detection for critical elements while minimizing polling stress on the overall network equipment.
Solution Approach 2:
The patent uses preliminary action by first performing a primary polling to identify sensitive elements that require monitoring, then conducting secondary pollings only on those identified elements. This preliminary identification step prevents unnecessary polling of all network elements, reducing overall polling stress while maintaining fast change detection capability for the sensitive subset that actually requires monitoring.
Data Source
AI summary
A method for detecting topology changes of a computer network, includes the following steps of acquisition of the raw data from the configuration tables of the network elements during successive primary pollings, the following steps being carried out between two successive primary pollings: calculation and storage of a checksum value for each network element having raw data which are considered to be sensitive, at least one secondary polling, allowing the sensitive data to be retrieved again from each corresponding element, comparison of the previously-stored checksum value, at each secondary polling and for each element termed sensitive, with a new checksum value calculated with the new sensitive data, for each sensitive element, when the two checksum values differ, updating in a topology database only the topology data relative to the corresponding element.