Mobile Photo App Cloud Migration for Resource Optimization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Mobile applications designed for cloud computing platforms often require significant device resources, leading to inefficient use of processing power and storage, as they are typically executed locally on devices rather than on cloud servers, which have more powerful hardware.

Innovation Solution

A mechanism is introduced to migrate service components of mobile applications from devices to cloud servers, allowing the device to offload resource-intensive tasks while maintaining a seamless user interface experience by transferring background threads to the cloud for execution and receiving processed results, thus optimizing device resources and power management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If mobile applications are executed locally on computing devices, then user interface responsiveness is maintained, but device resources (processing power, memory, storage) are consumed inefficiently

Engineering Contradiction:
Improveapplication execution efficiencyVSAvoiddevice energy consumption
Core Design Contradiction:
ProductivityVSUse of energy by moving object

Solution Approach 1:

The application is divided into two separate components: a user interface component that remains on the mobile device and a service component that is migrated to the cloud server. This segmentation allows the device to maintain only the lightweight UI portion while offloading resource-intensive processing to the cloud, thereby improving execution efficiency without excessive energy consumption.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The service component is extracted from the mobile application and transferred to the cloud server for execution. This extraction removes the burden of resource-intensive tasks from the device, allowing it to conserve energy while the cloud server handles the computational workload.

Inventive Principle:
Principle #2Taking out (Extraction)

2Device complexity

If service components are migrated to cloud server, then device resources are freed up and power management improves, but network dependency increases

Engineering Contradiction:
Improvedevice resource utilizationVSAvoidapplication availability
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The user interface component acts as an intermediary between the user and the cloud-based service component. It maintains local caching mechanisms and handles UI rendering independently, providing a buffer that ensures continued functionality even when network connectivity is interrupted, thus maintaining reliability while benefiting from cloud migration.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Speed

If cloud server executes application components, then processing speed increases due to faster hardware, but data synchronization complexity increases

Engineering Contradiction:
Improveprocessing speedVSAvoiddata synchronization mechanism
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The system implements a feedback mechanism where the user interface component continuously monitors the state of the service component and synchronizes data bidirectionally. This automated feedback loop ensures that data remains consistent across the cloud server and device without requiring complex manual synchronization protocols.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20140136611A1Mobile photo application migration to cloud computing platform
Publication Date: 2014.05.15 RAZER ASIA PACIFIC
  • US20140136611A1 patent drawing
  • US20140136611A1 patent drawing
  • US20140136611A1 patent drawing

AI summary

Technology is disclosed herein for migrating execution of at least a portion of a photo application to a server. According to at least one embodiment, a computing device monitors the photo application executing at the mobile device to identify a background thread and a foreground thread of the photo application, determine a current workload of the mobile device, transmit a received photo and an instance of the background thread to the server when the determined current workload exceeds a predefined threshold, receive a processed photo from the server, and provide access to the processed photo through the mobile device using the user interface generated by the foreground thread of the photo application.