Adaptive Software Load Delivery for Network Elements
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The increasing size of software releases poses challenges in accommodating and delivering them to network elements with limited file system space, leading to cumbersome and error-prone manual processes, especially when upgrading from one software release to another, requiring different delivery approaches based on the type of network element, its modules, and controller capabilities.
Innovation Solution
The system automatically determines a software delivery approach based on factors such as the 'to' and 'from' software releases, catalog information, network element type, and modules present, offering full, minimal, or hybrid delivery options, including service bundles, to ensure deterministic, stable, and error-proof software delivery.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If software release size increases to include more features and functionality, then software capabilities improve, but file system space requirements increase making delivery to legacy network elements difficult
Solution Approach 1:
The software release is segmented into multiple load types (full load, minimal load, hybrid load) based on network element capabilities. The full load contains all files for complete functionality, while the minimal load contains only essential files for basic operation. This segmentation allows legacy network elements with limited file system space to receive and operate with essential functionality, while newer elements can receive the complete full load for enhanced capabilities.
Solution Approach 2:
Different delivery approaches are applied to different network elements based on their specific characteristics. Network elements are categorized by controller type, file system size, and module presence. Elements with sufficient space receive full loads, while legacy elements receive minimal or hybrid loads. This local quality approach ensures each element receives appropriately sized software loads matched to its capabilities.
2Adaptability or versatility
If manual software delivery processes are used to accommodate different network element configurations, then delivery flexibility improves, but operational complexity and error rates increase
Solution Approach 1:
The software delivery system automatically determines the appropriate load type and delivers software without requiring manual intervention. The system self-evaluates network element characteristics (controller type, file system size, modules present) and autonomously selects the delivery approach (full, minimal, or hybrid load). This automation maintains delivery flexibility while eliminating manual complexity and reducing human error.
Solution Approach 2:
The system dynamically changes delivery parameters based on network element characteristics. By evaluating parameters such as file system size, controller capabilities, and module presence, the system automatically adjusts the software load composition and delivery method. This parameter-driven approach provides flexibility for different configurations while maintaining automated, consistent processes.
3Reliability
If full software loads are delivered to all network elements to ensure complete functionality, then software completeness improves, but delivery time and file system space requirements increase
Solution Approach 1:
Instead of delivering complete full loads to all network elements, the system applies partial action by delivering minimal loads containing only essential files needed for basic operation. For legacy network elements with limited space, this partial delivery ensures critical functionality is maintained while significantly reducing delivery time and space requirements. Newer elements with sufficient capacity receive complete loads for full functionality.
Data Source
AI summary
Systems and methods include obtaining a catalog for a “to” software release and details of a controller of a network element operating a “from” software release, wherein the software releases are associated with the network element, and wherein the controller has a file system associated therewith; determining a delivery technique for a software load of the “to” software release based on the catalog and the details of the controller; and causing delivery of the software load to the file system based on the determined delivery technique, wherein the causing is one of automatic and subsequent to a user command. The delivery technique can be one of i) a full delivery, including all files in the catalog, ii) a minimal delivery, including only files in the catalog needed based on modules present in the network element, and iii) a hybrid delivery, between the full and minimal delivery.