Modular Service Delivery System for Automated Software Update Scheduling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Large enterprises face challenges in managing the deployment and updating of software services across diverse computing environments due to the complexity of maintaining multiple independent software systems running on different operating systems, which leads to increased IT support costs and difficulties in timely deployment of updates across globally distributed servers.
Innovation Solution
A technology-agnostic and protocol-agnostic modular-based system that provides centralized management for service delivery, including automated scheduling of service deployment, version updates, and rollbacks, with features like side-loading of updates to allow simultaneous execution of current and new versions, and denial of non-permitted service versions to ensure efficient and unified service management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple independent software systems are deployed across diverse computing environments, then service functionality and versatility are improved, but system complexity and IT maintenance costs increase
Solution Approach 1:
The patent segments the software delivery system into independent modules that can be deployed across diverse computing environments. Each module is self-contained and can be managed independently, allowing the system to maintain multiple software systems without proportionally increasing overall complexity. The segmentation enables granular control and simplified maintenance of each component.
Solution Approach 2:
The patent implements a universal service delivery framework that can manage multiple independent software systems across diverse operating systems and computing environments. This multi-functional platform provides common capabilities for deployment, updates, and lifecycle management across heterogeneous systems, reducing the need for environment-specific management approaches.
2Adaptability or versatility
If independent software systems with distinct tracking controls are deployed, then system independence and flexibility are improved, but maintenance costs and governance complexity increase
Solution Approach 1:
The patent merges the tracking and governance controls of multiple independent software systems into a unified service delivery management platform. This consolidation maintains the independence of individual software systems while providing centralized oversight, reducing governance complexity and maintenance costs through shared management infrastructure.
3Reliability
If software updates are deployed across globally distributed servers, then service coverage and availability are improved, but deployment timing and update synchronization become problematic
Solution Approach 1:
The patent implements preliminary actions in the software update process by first deploying updates to test environments and staging servers before production deployment. The system performs validation, testing, and approval workflows in advance, ensuring that updates are ready for synchronized deployment across globally distributed servers, thereby maintaining service availability while managing deployment timing.
Solution Approach 2:
The patent employs feedback mechanisms to monitor the deployment status and performance of software updates across distributed servers. The system collects data from various environments and uses this feedback to adjust deployment schedules, synchronize updates, and ensure timely rollouts while maintaining service availability. Feedback loops enable real-time tracking and coordination of updates across global infrastructure.
Data Source
AI summary
A technology/operating system-agnostic and protocol-agnostic modular-based service delivery system that includes a management of enterprise-wide deployment of services and updates to services delivered by the modules of the system. Management includes determination and automatic implementation of an optimal schedule for service deployment, service version updates and service version roll-backs based on (i) predetermined lifecycle levels assigned to networked devices in the enterprise executing the service delivery application, and/or (ii) segments within the enterprise.