Web Proxy App Installation Without Session Interruption
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing application installation processes in communication devices are inefficient and disruptive, requiring user interaction and authentication during ongoing activities, leading to interruptions and delays in web app installations.
Innovation Solution
A friction-free download (FFD) system using an FFD proxy server and client application that authenticates and installs web apps silently in the background, allowing users to continue their activities without interruptions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional application installation processes are used, then user authentication and interaction are ensured for security, but user activities are interrupted and installation time is increased
Solution Approach 1:
The system performs preliminary authentication by obtaining device identification information and registering it with the proxy server before the actual installation process. This pre-registration enables subsequent installations to proceed without repeated authentication steps, reducing installation time while maintaining security through prior verification.
Solution Approach 2:
A proxy server is introduced as an intermediary between the content management server and the user communication device. The proxy server handles authentication and routing of installation requests, enabling seamless background installations without interrupting user activities while maintaining security through centralized credential verification.
2Reliability
If traditional application installation processes are used, then proper authentication is performed, but user activities are disrupted and installation efficiency is reduced
Solution Approach 1:
The system implements self-service installation where the FFD client application automatically handles installation requests in the background without requiring user interaction. The application silently downloads and installs web applications based on installation requests from web applications, maintaining authentication reliability through pre-obtained credentials while dramatically improving installation efficiency by eliminating manual user steps.
Solution Approach 2:
The installation process is designed to run continuously in the background without interrupting ongoing user activities. The proxy server and client application work together to perform installations during idle periods or in parallel with user tasks, ensuring that authentication remains reliable while productivity is maintained as users experience no disruption to their workflows.
3Reliability
If manual user interaction is required for installation, then security control is maintained, but installation process becomes complex and time-consuming
Solution Approach 1:
The proxy server acts as an intermediary that centralizes the management of installation requests and authentication. By handling credential verification, request routing, and installation coordination through the proxy server, the system maintains secure control over installations while simplifying the user experience to minimal interactions, reducing the perceived complexity of the installation process.
Data Source
AI summary
A system comprises a user communication device, a content management server, and a friction free download (FFD) proxy server. The user communication device is configured to send identification information of the user communication device; receive web content in a first web application; send an FFD installation request to the FFD proxy server; download the second web application; and install the second web application during an active session of the first web application. The content management server is configured to send the web content. The FFD proxy server is configured to register the content management server and the user communication device; receive the FFD installation request; authenticate the user communication device during the application session of the first web application; send the second proxy routing information; and send notification information indicating a status of the FFD installation of the second web application.


