Device Matching System for Component Discovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current device management systems are inefficient in accurately tracking and managing components within computer networks, leading to duplicate records, erroneous updates, and increased systemic risk due to their overly-sweeping discovery processes.
Innovation Solution
A device management system that utilizes auto-discovery to identify and match newly added components with existing ones based on attributes, calculating a match score and comparing it to an aggressiveness level to determine if a match exists, thereby reducing duplicate records and enhancing system transparency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If current device management systems use overly-sweeping discovery processes, then they can discover all components on the network, but they create duplicate records and erroneous updates
Solution Approach 1:
The system changes parameters by implementing a multi-attribute matching system that evaluates multiple attributes (device name, IP address, MAC address, serial number, hostname) with different weights. This transforms the discovery process from a single-criteria sweep to a multi-parameter verification system, resolving the contradiction between comprehensive discovery and accurate identification.
Solution Approach 2:
The patent replaces the mechanical sweeping discovery approach with an information-based matching system. Instead of relying on broad network scanning that creates duplicates, the system uses attribute comparison algorithms and scoring mechanisms to precisely identify components, substituting brute-force discovery with intelligent matching.
2Reliability
If device management systems create duplicate component records, then they ensure comprehensive tracking, but they cause mismanagement of computing power and resources
Solution Approach 1:
The system performs preliminary matching verification before creating new component records. By pre-evaluating multiple attributes and calculating match scores against existing records, the system prevents duplicate record creation in advance, ensuring tracking completeness while avoiding the computational waste of storing and processing duplicate data.
Solution Approach 2:
The matching system implements feedback mechanisms where discovery results are continuously compared against the existing component database. The scoring system provides feedback on match confidence levels, allowing the system to adjust its behavior and prevent duplicate recordings, thereby optimizing resource utilization while maintaining reliable tracking.
3Productivity
If device management systems use broad discovery processes, then they discover all network components, but they increase systemic risk by not allowing proper tracking
Solution Approach 1:
The system transforms broad network discovery into precise component identification by implementing multi-attribute parameter matching. This ensures that each discovered component is accurately verified against existing records using multiple identification parameters, maintaining comprehensive network coverage while enabling reliable tracking for security purposes.
4Loss of information
If device management systems update CMDB records frequently, then they maintain current system information, but they cause erroneous updates and increased processing overhead
Solution Approach 1:
Before updating CMDB records, the system performs preliminary verification by calculating match scores and verifying multiple attributes. This preliminary action filters out erroneous updates before they occur, maintaining current system information while reducing update management complexity by preventing invalid changes.
Data Source
AI summary
Disclosed is a device management system for discovery and management of components added to computer systems and sub-systems. The device management system provides for recognizing a newly added component, and determining if the newly added component is already a part of the system inventory. The newly added component is matched with a component currently on the system, based on at least one matching attribute. A point total is calculated for each match level and a final match score is provided. The match score is compared with an aggressiveness level to determine if a match does indeed exist.


