Mobile Device Application Execution via Remote Computing Resources

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Mobile devices with low-end computing resources, such as smartphones and tablets, are unable to execute applications that require high-end resources, leading to performance issues and incomplete execution of applications like graphics editing or numerical computing.

Innovation Solution

A method where a mobile device communicates with a computing device over a wireless link to execute resource-intensive applications, using a front-end manager to control user interaction and a back-end manager to handle the application execution, allowing the mobile device to utilize the computing device's resources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If applications are executed locally on mobile devices, then user interaction responsiveness is improved, but device resource requirements increase beyond what low-end devices can provide

Engineering Contradiction:
Improveuser interaction responsivenessVSAvoidcomputing resources
Core Design Contradiction:
SpeedVSQuantity of substance

Solution Approach 1:

The system divides the application execution into two segments: the front-end runs on the mobile device to handle user interactions, while the back-end executes on a remote computing device to perform resource-intensive operations. This segmentation allows each component to run on appropriate hardware, maintaining responsiveness while reducing local resource requirements.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A communication interface acts as an intermediary between the mobile device and the remote computing device, transmitting user inputs and application outputs. This mediator enables the mobile device to interact with applications running remotely, providing the experience of local execution without the associated resource demands.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If resource-intensive applications are executed on mobile devices, then application functionality is improved, but device performance deteriorates due to insufficient resources

Engineering Contradiction:
Improveapplication functionalityVSAvoiddevice performance
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The system extracts the resource-intensive back-end execution from the mobile device and relocates it to a remote computing device with sufficient resources. This extraction allows mobile devices to run sophisticated applications that would otherwise be impossible, while the actual heavy processing occurs on powerful remote hardware.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system transitions from a single-device execution model to a distributed execution model across multiple devices. By adding the spatial dimension of remote computing resources, the system enables mobile devices to access computational power beyond their physical constraints, running complex applications without local performance degradation.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

3Quantity of substance

If applications are offloaded to remote computing devices, then mobile device resource requirements are reduced, but system complexity increases due to communication and coordination overhead

Engineering Contradiction:
Improvemobile device resourcesVSAvoidsystem complexity
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

The execution manager implements a universal interface that can handle multiple application types and communication scenarios through a single unified mechanism. This multi-functional approach manages the complexity of remote execution, input handling, and output transmission through a standardized system that works across different application contexts.

Inventive Principle:
Principle #6Universality (Multi-functionality)

4Duration of action of stationary object

If continuous application execution is maintained across device connections, then user experience is improved, but connection management complexity increases

Engineering Contradiction:
Improveapplication execution continuityVSAvoidconnection management complexity
Core Design Contradiction:
Duration of action of stationary objectVSDevice complexity

Solution Approach 1:

The execution manager performs preliminary actions by maintaining application state and configuration data in advance, allowing the application to resume execution quickly after connection restoration. This pre-prepared state management reduces the complexity of re-establishing connections and ensures continuous user experience without requiring complex real-time synchronization protocols.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9509827B2Apparatus, system and method of managing at a mobile device execution of an application by a computing device
Publication Date: 2016.11.29 INTEL CORP
  • US9509827B2 patent drawing
  • US9509827B2 patent drawing
  • US9509827B2 patent drawing

AI summary

Some demonstrative embodiments include apparatuses, systems and/or methods of managing at a mobile device execution of an application on a computing device. For example, an apparatus may include an execution manager to manage at a mobile device execution of an application by a computing device, the execution manager to communicate with the computing device over a wireless communication link between the mobile device and the computing device, and to execute at the mobile device a front-end to control interaction between a user of the mobile device and the application according to a configuration of the mobile device.