Common Interface Container for Sub-Application Resource Preloading

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current application page processing methods are inefficient as they require full resource loading for each sub-application page, leading to increased installation time and resource consumption.

Innovation Solution

A method and apparatus that utilize a common page container to preload common resources across multiple sub-application pages, with independent resources loaded only when a specific sub-application page is launched, allowing for efficient generation and display of sub-application pages.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If full resource loading is performed for each sub-application page, then complete functionality is ensured, but installation time and resource consumption increase

Engineering Contradiction:

Improvefunctionality completenessVSAvoidinstallation time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent segments application resources into two distinct categories: common resources (shared across multiple sub-application pages) and independent resources (specific to individual sub-application pages). This segmentation allows the system to load only the necessary common resources initially, rather than loading all resources for all possible sub-application pages, thereby reducing installation time while ensuring functionality completeness when needed.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent performs preliminary loading of common resources that are shared across multiple sub-application pages. By pre-loading these common resources into memory before the user actually needs them, the system reduces the perceived installation time and improves subsequent page loading speeds, while maintaining the ability to load independent resources on-demand when specific pages are accessed.

Inventive Principle:

Principle #10Preliminary action

2Reliability

If full resource loading is performed for each sub-application page, then complete functionality is ensured, but resource consumption increases

Engineering Contradiction:

Improvefunctionality completenessVSAvoidresource consumption

Core Design Contradiction:

ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent segments application resources into common resources and independent resources, allowing the system to load and maintain in memory only the common resources that are frequently accessed across multiple sub-application pages. Independent resources are loaded on-demand only when their specific sub-application page is accessed, thereby significantly reducing overall resource consumption while ensuring that complete functionality is available when needed.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent creates a common resource container that serves multiple sub-application pages simultaneously. This universal container holds shared resources that can be reused across different pages, eliminating the need to load duplicate copies of the same resources for each page. This multi-functional approach reduces resource consumption by ensuring that common resources are loaded once and shared, rather than being loaded repeatedly for each sub-application page.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Use of energy by moving object

If common resources are preloaded for multiple sub-application pages, then resource consumption is reduced, but memory management complexity increases

Engineering Contradiction:

Improveresource consumptionVSAvoidmemory management complexity

Core Design Contradiction:

Use of energy by moving objectVSDevice complexity

Solution Approach 1:

The patent introduces a common resource container as an intermediary structure between the resource management system and the sub-application pages. This container acts as a centralized repository that manages shared resources, providing a standardized interface for loading, storing, and accessing common resources. By using this intermediary, the system simplifies memory management complexity, as the container handles resource allocation and retrieval operations, rather than requiring each sub-application page to manage its own resources independently.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS11119812B2Method and device for processing application program page according to a common interface container

Publication Date: 2021.09.14 TENCENT TECHNOLOGY (SHENZHEN) CO LTD

AI summary

This application relates to an application interface processing method performed at a terminal. After running a parent application on an operating system, the terminal generates, by the parent application, a common interface container by using a common resource of a plurality of child application interfaces. In response to an event of launching a first child application interface, the terminal loads an independent resource of the first child application interface in the common interface container, the independent resource including data in the child application interface other than the common resource. Finally, the terminal generates and displays the first child application interface according to the common interface container.