Client Server Deployment via Online Distribution Platform
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In platform-based systems like OpenScape Business, synchronizing mobile or desktop application versions with server-side updates is complex, especially when updates need to be installed manually on hardware components within customer premises, and there's no guarantee that all servers are on the latest compatible version with client software updates.
Innovation Solution
A method and system for client-to-server deployment via an online distribution platform, allowing simultaneous updates of client and server-side software through mechanisms like receiving updates from platforms like App Store or Google Play, verifying necessary updates, installing, and transferring packages to ensure all servers are updated efficiently.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If updates are delivered as a whole official release via total image, then system compatibility is ensured, but update complexity and deployment time increase
Solution Approach 1:
The patent segments the update delivery process into two independent parts: client software updates delivered through online distribution platforms and server-side updates delivered separately. This allows each component to be updated independently without requiring complete system re-imaging, reducing deployment complexity while maintaining compatibility through version synchronization mechanisms.
Solution Approach 2:
The patent implements preliminary version checking and synchronization mechanisms where the system determines the current server version before deploying updates, and prepares compatible client updates in advance. This preliminary action ensures compatibility is verified before deployment, reducing the need for complete total image deliveries.
2Reliability
If manual installation of server updates is required, then security control is improved, but deployment time and labor requirements increase
Solution Approach 1:
The patent implements a self-service update mechanism where clients automatically check for updates, determine their own update needs based on server version information, and initiate update downloads. This automated self-service approach maintains security through controlled update sources while significantly reducing manual intervention requirements and deployment time.
Solution Approach 2:
The patent establishes a feedback loop where clients query the server for version information, receive guidance on necessary updates, and automatically proceed with appropriate updates. This feedback mechanism enables automated deployment while maintaining security control through server-authoritative version information.
3Reliability
If server updates must wait for client updates, then version compatibility is ensured, but time to market for critical patches is delayed
Solution Approach 1:
The patent implements preliminary version checking where the system determines the current server version before initiating client update deployments. This preliminary action allows for targeted updates that maintain compatibility without requiring sequential waiting, as the compatibility requirements are established in advance.
Solution Approach 2:
The patent creates a dynamic update synchronization system where client and server updates can proceed in different sequences based on actual compatibility requirements rather than fixed waiting protocols. The system adapts the update timing and sequence dynamically based on version information and compatibility determinations.
Data Source
AI summary
An apparatus and a method for a client to server deployment via an online distribution platform can include a mechanism to update at least part of a system software or server-side software via a parallel client software update. Online distribution platforms such as mobile application stores can be utilized in embodiments of the apparatus and method to provide not only the client update, but also the system software update in the underlying system (e.g. server-side version).