Remote Bytecode Compilation for Mobile Application Execution

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Mobile device platforms have diverse requirements for application software, leading to the need for multiple iterations of applications, and their limited processing power results in slow loading and performance, especially when updating applications requires reinstallation and recompilation.

Innovation Solution

A computer-implemented method where source code is compiled into bytecode on a remote server, sent to mobile devices with corresponding runtime engines, allowing for execution without the need for user intervention, and enabling seamless updates without reinstallation, using a remote server to handle compilation and distribution efficiently.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If application is compiled on mobile device, then application can be executed, but processing power is consumed and loading is slow

Engineering Contradiction:

Improveapplication execution capabilityVSAvoidprocessing power consumption

Core Design Contradiction:

ReliabilityVSPower

Solution Approach 1:

A remote server acts as an intermediary between the application source code and the mobile device. The server compiles the source code into bytecode and sends it to the mobile device, where a runtime engine executes it. This intermediary approach allows the mobile device to avoid the computationally intensive compilation process while still achieving application execution.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The compilation process is segmented from the execution process. Compilation occurs on the remote server while execution occurs on the mobile device via a runtime engine. This segmentation allows the mobile device to focus only on execution without bearing the computational burden of compilation.

Inventive Principle:

Principle #1Segmentation

2Reliability

If entire application is reinstalled for updating, then application can be updated, but time and complexity increase

Engineering Contradiction:

Improveapplication update capabilityVSAvoidupdate time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The update mechanism extracts only the necessary bytecode components that need to be updated, rather than redistributing the entire application. The runtime engine on the mobile device receives and applies only the updated bytecode portions, significantly reducing update time and complexity.

Inventive Principle:

Principle #2Taking out (Extraction)

3Adaptability or versatility

If multiple iterations of application are written for different platforms, then application can run on various operating systems, but development complexity increases

Engineering Contradiction:

Improvecross-platform compatibilityVSAvoiddevelopment complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

A universal bytecode format is created that can be executed by runtime engines across different mobile operating systems. The compilation process generates this platform-independent bytecode from a single source code, allowing the same application to run on multiple platforms without requiring separate iterations for each operating system.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS9146732B2Systems and methods for executing an application on a mobile device

Publication Date: 2015.09.29 FIDELITY INFORMATION SERVICES LLC

AI summary

The invention provides a method and system to execute applications on a mobile device. The applications may be compiled on a remote server and sent to the mobile device before execution. The applications may be updated by the remote server without interaction by the mobile device user.