Mobile Application Launch via Server-Local Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing mobile device systems face challenges in reducing data transmission and minimizing delay when accessing and executing applications, especially in scenarios with limited bandwidth or high data traffic, as they rely on remote server execution rather than local processing.
Innovation Solution
A method and system that enables a mobile device to launch applications by establishing a communicative link with a remote computing device, receiving minimal data to create a user interface, and synchronizing data with the remote device, allowing for local execution and minimizing data transmission while maintaining offline capabilities.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If application execution is performed on a remote server, then device complexity and software requirements are reduced, but data transmission volume and interaction delay increase
Solution Approach 1:
The patent segments the application execution process into two parts: core application logic runs on the remote server, while localized UI rendering and user interaction handling are performed locally on the mobile device. This segmentation allows the device to maintain simplicity while reducing the need to transmit all application data and instructions, thereby decreasing overall data transmission volume.
Solution Approach 2:
The patent introduces an intermediary component that caches application data and state information locally on the mobile device. This intermediary layer enables the device to retrieve frequently accessed data locally rather than transmitting requests and responses with the remote server for every interaction, thus reducing data transmission volume while maintaining device simplicity.
2Speed
If data is transmitted to handle localized user actions, then user interaction responsiveness improves, but data transmission volume increases
Solution Approach 1:
The patent implements preliminary action by pre-loading and caching application data, user interface elements, and state information locally on the mobile device before they are needed. This allows the device to immediately respond to user interactions using locally cached data without waiting for server responses, thereby improving interaction responsiveness while minimizing the volume of data that needs to be transmitted during actual user interactions.
3Loss of substance
If minimal data is received to create user interface locally, then data transmission and memory usage are reduced, but application launch speed must be maintained
Solution Approach 1:
The patent employs copying by creating a local replica or representation of the application's user interface and essential data structures on the mobile device. Instead of transmitting the entire application, only minimal data needed to construct the user interface is received and copied locally. This approach reduces data transmission volume while enabling fast local rendering and application launch, as the device can immediately render the copied interface without waiting for additional data from the server.
Data Source
AI summary
In an aspect of the disclosure, a method and system for launching a mobile device application is disclosed including launching an application on a mobile device and transmitting a request to a remote computing device for receiving data to create a user interface for the application. The method and system further includes receiving the requested data at the mobile device and creating the user interface on the mobile device using the requested data. Also disclosed is a method of data synchronization in which data is synchronized from an application on a mobile device to an identical application on a remote computing device. The method includes establishing a communicative link between the mobile device and the remote computing device, synchronizing an application through the communicative link allowing the application to be used on the mobile device when the communicative link is discontinued and synchronizing the application upon reestablishing the communicative link.