Incremental NIS Map Updates via Directory Monitoring
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional Network Information Service (NIS) systems require complete regeneration of NIS maps for every change in network entities, which is resource-intensive and inefficient, especially in large networks with frequent modifications.
Innovation Solution
Implementing a system that uses a directory database like LDAP to monitor and incrementally update NIS maps in response to changes, eliminating the need for full map regeneration by tracking record additions, deletions, and modifications within the database.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If complete NIS map regeneration is performed for every change in network entities, then NIS maps are kept up-to-date, but computational resources and time are excessively consumed
Solution Approach 1:
The patent divides the NIS map update process into incremental segments. Instead of regenerating entire maps, only specific portions corresponding to changed network entities are updated. The NIS server identifies and processes only the affected map sections, thereby maintaining data currency while minimizing computational overhead and update time.
Solution Approach 2:
The system transitions from static periodic full-regeneration updates to dynamic incremental updates. The NIS server continuously monitors for changes in network entities and automatically triggers selective map updates only when changes are detected, making the update process adaptive and responsive to actual data changes rather than following a fixed schedule.
2Reliability
If complete NIS map regeneration is performed for every change in network entities, then NIS maps are kept up-to-date, but computational resources are excessively consumed
Solution Approach 1:
The update process is segmented to process only the specific NIS map portions affected by changes in network entities. The server identifies changed entities and generates updates solely for the relevant map sections, dramatically reducing computational resource consumption compared to regenerating entire maps while ensuring affected data remains current.
Solution Approach 2:
The system applies partial action by performing only the necessary portion of the update task. Instead of executing complete map regeneration (excessive action), the NIS server performs selective incremental updates on only the affected map sections (partial action), optimizing resource utilization while maintaining data accuracy.
3Device complexity
If traditional NIS map update process is used, then simplicity is maintained, but efficiency deteriorates in large networks with frequent modifications
Solution Approach 1:
The system implements dynamic incremental updates that automatically adapt to network conditions. The NIS server continuously monitors for changes and selectively updates only affected map portions, making the process efficient for large networks with frequent modifications while maintaining operational simplicity through automated change detection and selective processing.
Solution Approach 2:
The NIS server performs self-service by automatically detecting changes in network entities and triggering incremental map updates without external intervention. This self-monitoring and self-updating mechanism maintains simplicity in operation while dramatically improving efficiency, as the system autonomously optimizes its update process based on actual data changes.
Data Source
AI summary
A method of maintaining Network Information Service (NIS) maps where modifying information about any of the network entities described by the NIS maps requires only incremental update of the NIS maps instead of full NIS map regeneration. A further method of detecting when network entity records on a network directory server change so that NIS map updates are necessary.