Pluggable Service Architecture for Downtime-Free Communication Upgrades
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current communication systems require operational downtime for software upgrades and do not allow for convenient or user-specific upgrades of call treatment features, impacting all users even if only a subset benefits from the changes.
Innovation Solution
Implementing a communication system that enables administrators to download and deploy new services or service versions independently, allowing specific users or groups to access different services or service versions, with the ability to test and roll out upgrades without downtime, using a pluggable service architecture that includes call processing, user interface, and management components, and allowing dynamic customization and licensing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If a new service version is deployed system-wide, then all users benefit from the upgrade, but operational downtime occurs and bugs may affect all users
Solution Approach 1:
The patent segments the user base into different groups that can receive different service versions simultaneously. The service deployment is divided into manageable portions where each user group can be upgraded independently, allowing the system to roll out new versions to subsets of users without forcing a complete system-wide deployment at once. This segmentation enables controlled testing and reduces the risk of system-wide failures.
Solution Approach 2:
The patent implements dynamic service version assignment where users can be moved between different service versions at runtime without requiring system downtime. The system dynamically adjusts which service version each user experiences, allowing seamless transitions and enabling the deployment of new versions while maintaining system stability for users on older versions.
2Device complexity
If a monolithic feature server is used, then system management is simplified, but upgrading any feature requires upgrading the entire server causing downtime
Solution Approach 1:
The patent segments the monolithic feature server into independent service modules that can be upgraded separately. Each service can be developed, deployed, and upgraded independently while the rest of the system continues to operate. This modular architecture maintains relative simplicity in management while eliminating the requirement to upgrade the entire server simultaneously.
Solution Approach 2:
The patent allows service upgrades to be prepared and staged in advance without interrupting service to users. New service versions can be pre-configured and validated before being activated for any user group, ensuring that upgrade activities do not cause operational downtime while maintaining straightforward system management.
3Reliability
If service upgrades are tested system-wide, then comprehensive testing is achieved, but the impact of bugs affects all users
Solution Approach 1:
The patent applies local quality by allowing different user groups to experience different service versions simultaneously. Bug testing can be performed on localized user subsets where any issues will only affect that specific group rather than the entire user base. This enables thorough testing while containing the potential harmful impact of bugs to a minimal scope.
Solution Approach 2:
The patent implements partial testing action by allowing service versions to be tested on selected user groups rather than requiring complete system-wide deployment for testing. This partial deployment approach provides sufficient testing coverage to identify bugs while limiting their impact scope, and allows iterative refinement before broader deployment.
4Ease of operation
If a single service version is provided to all users, then system management is easier, but user-specific customization and gradual rollouts are not possible
Solution Approach 1:
The patent implements a universal service framework that can simultaneously provide multiple service versions to different user groups. The system maintains a unified management interface while supporting diverse service configurations for different users. This multi-functional approach allows administrators to manage services centrally while enabling user-specific customization and gradual rollouts without sacrificing operational simplicity.
Data Source
AI summary
Downloadable pluggable services and methods of distributing the same are described. The downloadable pluggable services may correspond to communication services that can be downloaded to upgrade a communication system. The downloadable pluggable services may include a number of component parts that can be distributed among various servers in the communication system being upgraded along with instructions that enable the component parts to instruct each server in the communication system to operate in a coordinated fashion so as to provide the downloaded service.