Network Management Data Subtree Distribution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional SNMP discovery and polling processes are time-consuming and resource-intensive due to the need for serial communication and maintenance of lexicographical ordering in management data, limiting the efficient distribution of management data to Network Management Stations (NMSes).
Innovation Solution
Storing management data as a set of subtrees in a database, allowing a processing unit to identify and retrieve all relevant data within a subtree in response to a single request from an NMS, eliminating the need for additional requests and lexicographical ordering.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If traditional discovery operations are performed to enumerate management data objects, then the NMS can identify all objects in the management data, but the process becomes time-consuming and resource-intensive due to serial communication requirements
Solution Approach 1:
The patent segments the management data into hierarchical subtrees (e.g., iso, org, dod, int, private branches) that can be independently identified and retrieved. Instead of enumerating every object individually through serial discovery operations, the system divides the data structure into manageable subtree units that can be fetched in parallel or fewer sequential operations, reducing the overall discovery time while maintaining complete object enumeration capability.
2Ease of operation
If traditional polling processes request individual objects using OIDs, then the NMS can retrieve specific management data, but additional requests are needed for other portions of the data
Solution Approach 1:
The patent merges multiple individual object requests into a single subtree retrieval operation. When the NMS requests a subtree by its root OID, all objects within that subtree are returned in a single response, combining what would otherwise require multiple separate polling requests. This maintains the flexibility to target specific data portions while dramatically improving efficiency by eliminating redundant request-response cycles.
3Stability of the object's composition
If the network device maintains management data in lexicographical order, then the data can be reported systematically during discovery, but significant resources are invested to preserve ordering when data is dynamically added or removed
Solution Approach 1:
The patent transitions from maintaining flat lexicographical ordering to a hierarchical tree structure organized by standardized OID branches (iso.3, org, dod, int, private). This dimensional reorganization allows data to be naturally ordered by the hierarchical path rather than requiring continuous re-sorting. When objects are added or removed, the tree structure maintains its organizational integrity without requiring resource-intensive re-aggregation or re-assembly operations, as the hierarchical relationships remain stable.
4Reliability
If the NMS performs discovery operations regularly to account for dynamic changes in management data, then the NMS can maintain up-to-date object information, but the processing burden on both NMS and network device increases
Solution Approach 1:
The patent implements preliminary action by pre-organizing management data into subtree structures with clearly defined root OIDs and hierarchical relationships before discovery operations begin. This pre-structuring allows the NMS to efficiently identify and retrieve only the specific subtrees it needs without performing exhaustive discovery operations. When data changes occur, the pre-established tree structure enables targeted updates rather than full re-discovery, reducing processing resource consumption while maintaining data currency accuracy.
Data Source
AI summary
The disclosed apparatus may include (1) a database that stores management data as a set of subtrees and (2) a processing unit having access to the database, wherein the processing unit (A) receives, from an NMS included in a network, a request for at least a portion of the management data, (B) identifies, based at least in part on the request, a subtree within the set of subtrees of management data stored in the database, (C) retrieves all of the management data included in the identified subtree from the database, and then (D) provides all of the management data included in the identified subtree to the NMS that initiated the request for the portion of management data without necessitating another request for any other portion of the management data included in the identified subtree. Various other apparatuses, systems, and methods are also disclosed.