Mobile Application Segmentation for Reduced Transmission Time

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional methods for providing mobile applications are limited by the resources of mobile communication terminals and bandwidth, resulting in large transmission and loading times, and a restriction on the size and number of applications, which hinders the provision of complex and personalized applications.

Innovation Solution

A method that divides the mobile application into multiple execution data sets, including executable code, display data, and resource data, and transmits only the required data based on device and user information, using control profiles to manage and extract the necessary data for scene-by-scene loading and execution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If the entire mobile application is transmitted through the mobile communication network, then the application can be executed, but the transmission time and loading time become excessively long

Engineering Contradiction:
Improvetransmission time and loading timeVSAvoidapplication execution efficiency
Core Design Contradiction:
Loss of timeVSProductivity

Solution Approach 1:

The mobile application is divided into multiple execution data sets corresponding to different scenes or functional modules. Only the required execution data for the current scene is transmitted and loaded, rather than the entire application. This segmentation reduces transmission time and memory usage while maintaining full application functionality through on-demand loading.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The mobile application providing server pre-processes and stores the application as divided execution data sets before transmission. When a user accesses a specific scene, the server has already prepared the corresponding execution data for immediate transmission, eliminating the need to load and process the entire application beforehand.

Inventive Principle:
Principle #10Preliminary action

2Loss of time

If the mobile application is optimized for limited bandwidth by minimizing screen configuration and image configuration, then transmission time is reduced, but the application becomes simple and cannot provide various functions

Engineering Contradiction:
Improvetransmission timeVSAvoidapplication functionality
Core Design Contradiction:
Loss of timeVSAdaptability or versatility

Solution Approach 1:

The application is segmented into execution data sets where complex functional elements (images, screen configurations) are separated from control logic. Only essential execution data is transmitted initially, while complex resources can be loaded on-demand when bandwidth allows, maintaining both speed and functionality.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The application configuration becomes dynamic based on available bandwidth and user needs. Execution data can be selectively loaded with varying levels of detail or quality, allowing the application to adapt its resource consumption to current network conditions while maintaining full functional capability.

Inventive Principle:
Principle #15Dynamics

3Loss of time

If the mobile application is optimized for limited bandwidth by minimizing screen configuration and image configuration, then transmission time is reduced, but the provision of mobile applications for processing various functions is suppressed

Engineering Contradiction:
Improvetransmission timeVSAvoidapplication functional capability
Core Design Contradiction:
Loss of timeVSProductivity

Solution Approach 1:

Functional capabilities are segmented into separate execution data sets that can be independently loaded. This allows the application to provide various functions by loading only the necessary functional modules rather than requiring a complete pre-optimized package, maintaining both transmission efficiency and functional versatility.

Inventive Principle:
Principle #1Segmentation

4Adaptability or versatility

If the mobile communication terminal stores and processes large size mobile applications, then more complex applications can be provided, but the limited resources of the terminal are exceeded

Engineering Contradiction:
Improveapplication complexityVSAvoidterminal resource capacity
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The application is divided into execution data sets that are loaded on-demand rather than stored entirely in the terminal. This reduces the memory and storage requirements of the terminal while maintaining the capability to execute complex applications, as only the currently needed portions reside in device memory.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The mobile application providing server acts as an intermediary between the user and the application resources. Instead of requiring all application data to be stored locally in the terminal, the server maintains the complete application and streams only necessary execution data to the terminal, reducing device resource requirements.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS8374593B2Method of providing mobile application
Publication Date: 2013.02.12 SK PLANET CO LTD
  • US8374593B2 patent drawing
  • US8374593B2 patent drawing
  • US8374593B2 patent drawing

AI summary

A method of providing a mobile application is disclosed. In accordance with the method of the present invention, a transmission time and a loading time of the mobile application, and a limitation on a number and a size of the mobile application are minimized, and providing the personalized mobile application is possible.