Application Streaming Client Segmentation for Local Execution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current application delivery methods are slow, lack effective piracy prevention, and inefficient in network utilization and power management, while also limiting performance consistency across devices.
Innovation Solution
Implementing an application streaming system where a first application streaming client obtains and executes application portions, providing a pixel-based streaming client with access to the executing application through a generated pixel stream, allowing for efficient delivery and execution without the need for local storage on the client device, and utilizing a network to shift resource-intensive tasks closer to the client.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If application is downloaded and installed locally, then performance consistency is improved, but download time and installation time increase significantly
Solution Approach 1:
The application is divided into multiple components: a small client-side component that remains on the user device, and a larger server-side component that runs on remote servers. This segmentation allows the application to be delivered and executed without requiring full local download and installation, significantly reducing download time while maintaining performance consistency through centralized execution.
Solution Approach 2:
A cloud-based application delivery platform acts as an intermediary between the application source and the user device. This intermediary handles the heavy lifting of application execution on remote servers while providing a lightweight client interface to users, eliminating the need for local installation and reducing download requirements.
2Quantity of substance
If application is delivered from remote source, then local storage requirements are reduced, but network dependency and latency increase
Solution Approach 1:
Application components are pre-configured and prepared on remote servers before user interaction. The server-side application is ready to execute immediately upon user authentication, eliminating startup delays associated with local installation and extraction. This preliminary preparation on the server side compensates for network latency by having the application ready to run.
Solution Approach 2:
The system dynamically adapts the delivery and execution model based on network conditions and user needs. The client device can operate in different modes: fully offline with cached components, partially online with selective synchronization, or fully online for resource-intensive tasks. This dynamic approach optimizes the balance between local storage and network dependency.
3Object-affected harmful factors
If standard download and install method is used, then piracy prevention is limited, but device capability requirements are reduced
Solution Approach 1:
The critical application logic and executable code are extracted from the client device and placed on secure remote servers. This extraction removes the need for complex local security measures against piracy, as the application runs in a controlled server environment where access can be managed through authentication and licensing mechanisms. The client device only holds non-sensitive interface components.
Data Source
AI summary
For various implementations, a first application streaming client can obtain portions of an application from a application streaming server, execute the application based on those portions obtained, and provide a second application streaming client (a pixel-based application streaming client) access to the executing application using a pixel stream generated based on output from the executing application. Depending on the implementation, the first application streaming client could execute the application, based on the portions obtained, on behalf of a user at the application streaming client, on behalf of the pixel-based application streaming client, or both. In various implementations, the first application streaming client and the second application streaming client can be communicatively coupled through a local network (e.g., LAN or local WiFi), while the first application streaming client and the application streaming server can be communicatively coupled through a wider area network (e.g., WAN or MAN).