Pattern-Based OID Matching for RMM Device Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The rigid structure of Management Information Bases (MIBs) used in network device management leads to duplication and near-duplication issues, making it challenging to update and maintain device definitions, and RMM software is prone to errors due to imperfections in MIBs, which can prevent proper device monitoring and management.
Innovation Solution
The system employs search patterns to match object identifiers and values, allowing RMM software to tolerate imperfections in MIBs and use existing definitions for new products, reducing the need for rigid OID naming schemes and minimizing the number of definitions required, thereby facilitating the management of devices even if specific MIBs are not available.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Stability of the object's composition
If a rigid MIB structure with standardized OID naming schemes is used, then device management follows a consistent format, but it leads to duplication and near-duplication issues making updates and maintenance challenging
Solution Approach 1:
The patent changes the parameter of OID matching from exact matching to pattern-based matching. This allows the system to accommodate variations in OID naming schemes across different vendors and device versions while maintaining a consistent management approach. The pattern matching mechanism transforms the rigid parameter requirement into a flexible one, resolving the contradiction between structural consistency and maintenance complexity.
Solution Approach 2:
The patent creates a universal device management system that can handle multiple OID naming schemes through pattern matching. Instead of requiring separate MIB definitions for each vendor or device version, the system uses universal patterns that can match various OID formats. This multi-functional approach allows a single management framework to work across diverse devices, reducing duplication and simplifying updates.
2Reliability
If extensive testing is performed to verify MIB correctness, then device management reliability improves, but the testing process becomes extensive and costly
Solution Approach 1:
The patent applies partial action by implementing pattern matching that partially verifies MIB correctness without requiring exhaustive testing. Instead of testing every possible OID and device configuration, the system uses patterns to validate the essential structure and semantics. This partial verification approach maintains reliability while significantly reducing testing time and costs.
Solution Approach 2:
The patent performs preliminary validation by checking OIDs against predefined patterns before full device management operations. This preliminary action catches obvious errors early in the process, preventing more extensive testing from being necessary. The pattern matching serves as a preliminary filter that ensures basic correctness without requiring comprehensive testing of all device functions.
3Measurement precision
If RMM software requires exact MIB matches for device management, then precise device control is achieved, but the software becomes prone to errors due to imperfections in MIBs
Solution Approach 1:
The patent changes the matching parameter from exact equality to pattern-based similarity. This allows the system to identify devices accurately even when their OIDs deviate slightly from expected formats. The pattern matching parameter transformation maintains identification precision while increasing robustness against MIB imperfections and vendor-specific variations.
Solution Approach 2:
The patent introduces pattern matching as an intermediary layer between the RMM software and the actual device OIDs. This intermediary translates various OID formats into a common management framework, preventing errors from propagating. The pattern acts as a mediator that reconciles differences between expected and actual OID formats, ensuring reliable device management despite MIB imperfections.
4Adaptability or versatility
If complete MIB definitions are maintained for all device versions, then comprehensive device management is possible, but tracking changes and propagating updates becomes a significant version control challenge
Solution Approach 1:
The patent changes the version control parameter from tracking every MIB definition to tracking pattern evolution. Instead of maintaining separate MIB files for each device version and tracking their differences, the system uses patterns that can accommodate variations across versions. This parameter change transforms version control from a complex file-diff problem into a simpler pattern-maintenance task, reducing complexity while maintaining adaptability.
Solution Approach 2:
The patent creates a universal pattern framework that serves multiple device versions simultaneously. Instead of requiring separate MIB definitions for each version, the universal patterns can match OIDs across multiple versions and vendors. This multi-functional approach consolidates version control, allowing a single pattern set to manage diverse device versions without requiring complex tracking and propagation mechanisms.
Data Source
AI summary
The present disclosure is directed to systems and methods of managing remote devices. The system can include a server with memory, a detection module, and a collection module. The memory can store a management information base (MIB) having a hierarchical tree of object identifiers and corresponding object values. The detection module can query devices and receive a first object identifier and its first object value, which can vary from those in the MIB; and use patterns to match the first object identifier and object value; and generate an identification of the device from the matches. The collection module can use the identification to select a collection template, which can indicate a subtree of the MIB and a collection pattern; traverse the subtree and identify a second object identifier that matches the collection pattern, and its second object value; and associate the second object value with the first object value.