Network Resource Locking via Centralized Agent
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network management systems lack a comprehensive mechanism to prevent simultaneous modifications to resources by multiple network management stations, leading to unpredictability and potential integrity issues during configuration changes.
Innovation Solution
An agent on a network device implements explicit resource locking using a Management Information Base (MIB) and keep-alive messages to ensure exclusive access and scheduled lock requests, preventing conflicts and ensuring reliable resource modifications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a NMS maintains an internal table indicating locked external resources and denies access to other applications in the same NMS, then exclusive access is provided to the requesting application, but applications in other NMSs can still access and modify the same resource simultaneously
Solution Approach 1:
The patent introduces a centralized locking server as an intermediary component that manages lock requests between multiple NMSs and network devices. This server receives lock requests from any NMS, maintains a centralized lock table, and coordinates access rights, thereby enabling true multi-NMS exclusive access without requiring complex distributed locking logic in each NMS.
Solution Approach 2:
The patent extends the locking mechanism from a single-NMS internal table approach to a network-wide distributed locking system. By adding the dimension of network-wide coordination through a centralized locking server, the system achieves exclusive access control across multiple NMSs that were previously unmanageable in the original two-dimensional (single-NMS) approach.
2Adaptability or versatility
If multiple NMSs can access and modify the same resource simultaneously, then system flexibility and concurrent operations are enabled, but predictability of modification results and configuration integrity are lost
Solution Approach 1:
The patent implements a feedback mechanism where the centralized locking server continuously monitors lock request status and notifies NMSs of lock acquisition or conflict conditions. This feedback loop enables NMSs to understand the current lock state and adjust their operations accordingly, maintaining both concurrent access capability and configuration integrity through informed decision-making.
Solution Approach 2:
The patent requires NMSs to submit lock requests in advance before modifying resources. The centralized locking server processes these preliminary lock requests, assigns exclusive access rights, and only permits modifications after lock acquisition is confirmed. This preliminary locking action prevents conflicting modifications and ensures predictable, integrity-preserving operations.
3Reliability
If an application requests a lock on a resource, then exclusive access is granted to prevent other applications in the same NMS from accessing the resource, but the lock indication does not prevent applications in other NMSs from accessing and modifying the same resource
Solution Approach 1:
The centralized locking server acts as an intermediary that simplifies lock management across multiple NMSs. Instead of each NMS implementing complex distributed locking logic, the server handles all lock coordination centrally, making the system easier to operate while maintaining reliable exclusive access control through standardized lock request and release protocols.
Data Source
AI summary
An agent locking a resource in a device in response to receiving an explicit request to lock the resource. Once in a locked state, access to entities (applications, devices, etc.) other than a owner of the lock may be restricted (e.g., no access, only read access, etc.). The agent unlocks the resource in response to an unlock request or if keep-alive messages are not received for a long duration.