L3 Cache Allocation for Faster Foreground Application Launch

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The launch time of foreground applications on electronic devices is prolonged due to contention for shared cache resources with background applications, leading to a poor user experience.

Innovation Solution

Allocate a fixed size of the shared cache to foreground applications of a specific type, determined using a white list or mapping relationship, to avoid contention and reduce launch time.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If background applications are allowed to run simultaneously, then application diversity and user functionality are improved, but foreground application launch time increases due to cache contention

Engineering Contradiction:
Improveapplication diversityVSAvoidlaunch time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The shared cache is segmented into dedicated portions for foreground applications and background applications. The memory management unit divides the cache space based on application priority and type, allowing foreground applications to access a dedicated cache region without interference from background applications, thus reducing launch time while maintaining background application functionality

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Different cache allocation strategies are applied to different application types. Foreground applications receive guaranteed cache space with higher priority, while background applications operate with lower priority or dynamic allocation. This local differentiation in cache quality and access rights resolves the contradiction between supporting diverse applications and maintaining fast launch times

Inventive Principle:
Principle #3Local quality

2Loss of time

If a fixed shared cache is allocated to a foreground application, then launch time is reduced by avoiding cache contention, but cache resource utilization efficiency decreases

Engineering Contradiction:
Improvelaunch timeVSAvoidcache resource utilization
Core Design Contradiction:
Loss of timeVSProductivity

Solution Approach 1:

The cache allocation system dynamically adjusts cache space distribution based on application characteristics, current system state, and workload demands. The memory management unit monitors cache usage patterns and reconfigures allocation in real-time, providing fixed cache guarantees for launch-critical applications while allowing flexible reallocation for other applications, thus balancing launch time improvement with overall resource utilization efficiency

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

Cache allocation parameters such as size, priority, and access rights are changed based on application type and system conditions. The system modifies cache configuration dynamically - allocating larger fixed portions to foreground applications needing fast launch while reducing or making dynamic the portions allocated to background applications, thereby optimizing both launch performance and overall resource utilization

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS20260037345A1Application launching method and electronic device
Publication Date: 2026.02.05 HONOR DEVICE CO LTD
  • US20260037345A1 patent drawing
  • US20260037345A1 patent drawing
  • US20260037345A1 patent drawing

AI summary

This application provides an application launching method. After receiving a launch operation performed by a user on a first application, an electronic device launches the first application in response to the launch operation. During launching of the first application, the electronic device may use a sensitivity curve corresponding to the first application to determine a target occupancy corresponding to the first application, where the sensitivity curve corresponding to the first application identifies a mapping relationship between an occupancy of an L3 cache attributable to the first application and an IPC of the first application, and the target occupancy represents a minimum occupancy of the L3 cache that corresponds to a highest IPC. The first application may allocate the L3 cache of a corresponding size to the first application based on the target occupancy to continue launching the first application based on the L3 cache allocated to the first application.