Application Call Restriction for Mobile Device Stability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The frequent calling of system services by applications can lead to high CPU load, power consumption, heating, lagging, and even restarts of mobile electronic terminals.

Innovation Solution

A method and apparatus for controlling an electronic device to identify and restrict abnormal call actions of applications by analyzing feature data, including current system state and running state data, using decision tree and Gaussian mixture clustering models, and adjusting suspension times through reinforcement learning.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If applications frequently call system services to achieve various functions, then application functionality and user experience are improved, but CPU load increases, power consumption rises, heating occurs, and system stability deteriorates

Engineering Contradiction:
Improveapplication functionalityVSAvoidsystem stability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs preliminary analysis of application behavior patterns and call frequency before problems occur. By monitoring and analyzing system service call patterns in advance, the system can identify applications that are likely to cause high CPU load or power consumption issues, and take preventive measures such as restricting their access to system services before the actual damage occurs.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediate management layer between applications and system services. This intermediary component monitors application behavior, analyzes call patterns, and selectively controls access to system services. It acts as a mediator that allows legitimate high-frequency calls while blocking or throttling abnormal calls that would cause CPU overload, power consumption issues, or system instability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If applications call system services with high frequency to achieve functions, then application performance is improved, but power consumption increases and battery life decreases

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

Solution Approach 1:

The system analyzes application call patterns and power consumption characteristics in advance to identify abnormal behavior. By detecting applications that excessively consume power through frequent system service calls before battery depletion occurs, the system can preemptively restrict their access and prevent severe power consumption issues.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

An intermediary monitoring mechanism is introduced between applications and system services to control power consumption. This intermediary analyzes call frequency and power usage patterns, allowing legitimate high-performance operations while blocking or throttling abnormal calls that would cause excessive power consumption and battery drain.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If applications call system services with high frequency, then application functionality is enhanced, but CPU load increases causing heating and lagging

Engineering Contradiction:
Improveapplication functionalityVSAvoiddevice heating
Core Design Contradiction:
Adaptability or versatilityVSTemperature

Solution Approach 1:

The system performs preliminary monitoring and analysis of system service call patterns to identify applications that will cause high CPU load. By detecting abnormal call frequency and patterns before CPU overload occurs, the system can preemptively restrict access to system services, preventing CPU-intensive operations that would lead to heating and lagging.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

An intermediary control mechanism is introduced between applications and system services to manage CPU load. This intermediary monitors call frequency and system state, allowing legitimate functionality while blocking or throttling abnormal calls that would cause CPU overload, subsequent heating, and user-visible lagging.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Adaptability or versatility

If applications call system services with high frequency, then application features are implemented, but system resource consumption increases and system stability decreases

Engineering Contradiction:
Improveapplication featuresVSAvoidsystem resource consumption
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The system performs preliminary analysis of application behavior and resource usage patterns to identify abnormal consumption. By monitoring system service call frequency and resource usage in advance, the system can detect applications that are consuming excessive system resources and take preventive measures before resource depletion or system instability occurs.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

An intermediary management layer is introduced between applications and system services to control resource consumption. This intermediary monitors and analyzes call patterns, allowing legitimate feature implementation while blocking or throttling abnormal calls that would cause excessive system resource consumption and potential system instability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20250036502A1Application running method, apparatus, electronic device and storage medium
Publication Date: 2025.01.30 SAMSUNG ELECTRONICS CO LTD
  • US20250036502A1 patent drawing
  • US20250036502A1 patent drawing
  • US20250036502A1 patent drawing

AI summary

A method of controlling an electronic apparatus for running at least one application is provided. The method includes obtaining feature data corresponding to a plurality of running applications, wherein the feature data comprises current system state data and running state data corresponding to the at least one application, identifying a target abnormal application based on the feature data corresponding to the plurality of the running applications, obtaining interactive data corresponding to a plurality of call actions of the target abnormal application within a preset duration, identifying a target abnormal call action based on the interactive data corresponding to the plurality of the call actions, and performing call restriction on the target abnormal call action based on monitoring the target abnormal call action.