Network Change Management via Segmented Validation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network change management approaches are inefficient and prone to failures, especially in complex networks, as they often require rolling back updates and can disrupt service level agreements (SLAs), and lack consistency in implementation across different administrators.
Innovation Solution
A systematic approach using a change management server that generates and validates network changes operation-by-operation, incorporating feedback to ensure consistency and minimize disruptions, by using common scripts and pre-checks to verify hardware and software configurations before implementing changes, and monitoring performance to roll back if necessary.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If group deployment strategy is used to make network changes, then implementation speed is improved, but reliability deteriorates due to all-or-nothing failure mode requiring rollback
Solution Approach 1:
The patent segments network changes into individual operable units that can be independently deployed and validated. Each operable unit represents a discrete change that can be applied to specific network devices without requiring simultaneous changes across the entire network. This segmentation enables partial deployment and validation, eliminating the all-or-nothing failure mode of group deployment while maintaining implementation efficiency.
2Adaptability or versatility
If manual evaluation of network changes is performed, then adaptability is improved, but consistency deteriorates across different administrators
Solution Approach 1:
The patent creates a universal change management system that standardizes the network change process through predefined operable units, validation rules, and automated workflows. This universal framework ensures consistent implementation across different administrators and networks while maintaining adaptability through configurable parameters and customizable change templates that can be adapted to specific network requirements.
Solution Approach 2:
The patent implements automated validation and feedback mechanisms that evaluate network changes before and after deployment. The system validates operable units against predefined criteria, monitors deployment outcomes, and provides feedback to ensure consistent implementation. This automated feedback loop eliminates variability introduced by manual evaluation while preserving adaptability through configurable validation rules.
3Productivity
If network changes are implemented without pre-validation, then productivity is improved, but harmful factors increase due to SLA disruptions
Solution Approach 1:
The patent performs preliminary validation of operable units before deployment by checking against predefined validation rules, hardware configurations, and software requirements. This preliminary action identifies potential issues before they affect the network, preventing SLA disruptions while maintaining deployment efficiency. The validation process occurs automatically as part of the change management workflow without requiring manual intervention.
Data Source
AI summary
Systems and methods for implementing network changes are described herein. In one aspect, a network change procedure may be comprised of a plurality of scripts that may implement a change in the network. In one embodiment, the deployment may be paused after the script has been executed. During the pause, a change management server may determine the impact of the change on the network. If the change had a positive effect, the change management server may execute another script to make another network change. However, if the change had a negative effect, the change management server may initiate one or more remedial actions.