Application Loading via Functional Component Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The complexity of application code leads to slow and error-prone loading processes, occupying significant storage space, which negatively impacts user experience in Internet services.

Innovation Solution

A method and device for loading applications in user terminals that match and load independent functional components in response to function enabling instructions, reducing unnecessary storage usage by loading only the required executable files, allowing for quicker and more flexible application loading.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If the entire application is loaded into memory at startup, then all functions are immediately available, but storage space is occupied unnecessarily and loading time increases

Engineering Contradiction:
Improveapplication loading speedVSAvoidstorage space occupied
Core Design Contradiction:
ProductivityVSQuantity of substance

Solution Approach 1:

The application is divided into multiple independent functional components (first functional component, second functional component, etc.), each implementing a specific function. Only the required functional component is loaded into memory when a function is invoked, rather than loading the entire application. This segmentation allows the system to load only necessary portions of the application, reducing storage occupancy and improving loading speed.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The required functional component is extracted from the packaged application file at the time of function invocation. The extraction process obtains only the specific executable code needed for the current function, leaving the rest of the application packaged and not occupying memory space. This extraction approach directly addresses the contradiction by taking out only what is needed.

Inventive Principle:
Principle #2Taking out (Extraction)

2Adaptability or versatility

If the entire application code is loaded, then all functions are available, but the loading process becomes slow and error-prone

Engineering Contradiction:
Improvefunction availabilityVSAvoidapplication loading time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

By segmenting the application into independent functional components, the system loads only the specific component needed for the current function. This reduces the amount of data that needs to be processed during loading, thereby reducing loading time and making the process less error-prone, while still maintaining full functional availability when needed.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The application is packaged in advance with multiple functional components separated and organized. This preliminary organization allows the system to quickly locate and load only the required component without processing the entire application code, thus reducing loading time while ensuring all functions remain available.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If complex application code is loaded completely, then all features are accessible, but storage space is occupied for extended periods

Engineering Contradiction:
Improveapplication functionalityVSAvoidstorage space occupancy duration
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The application functionality is segmented into independent functional components. Each component can be loaded only when its corresponding function is needed, and unloaded or kept packaged when not needed. This segmentation enables the system to maintain full application functionality while significantly reducing the duration and amount of storage space occupied by application code.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

After a functional component has been executed, it can be discarded from memory or kept in packaged form, and recovered later when the same function is needed again. This approach reduces storage occupancy duration while maintaining functionality availability, as the packaged application serves as a recovery source for future use.

Inventive Principle:
Principle #34Discarding and recovering

Data Source

PatentUS10860337B2Method, device and user terminal for loading application
Publication Date: 2020.12.08 ALIBABA GROUP HOLDING LTD
  • US10860337B2 patent drawing
  • US10860337B2 patent drawing
  • US10860337B2 patent drawing

AI summary

Provided are a method, a device and a user terminal for loading an application, and relates to the field of Internet technology. The method for loading an application is applied to a user terminal, and the method includes: in response to a function enabling instruction, matching independent functional components of a corresponding application program, where the application program is packaged in advance according to the implemented functions to include multiple functional components, and the functional components include an independent functional component; obtaining an executable file corresponding to the independent functional component; and loading the executable file corresponding to the independent functional component. According to the present invention, a corresponding executable file is loaded according to a user's needs, such that the application is loaded in a way more flexible and quicker, the storage space occupied by the application for a long period of time is reduced.