Background Application Permission Management via Threshold Allocation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current computing devices face challenges in managing background applications, leading to battery life and processing performance issues due to the lack of effective permission management, with either overly restrictive or permissive approaches, and existing solutions lack objective criteria for allowing real-time communication applications to run in the background.

Innovation Solution

Implementing a user interface that allows users to manage application permissions through a predetermined threshold, enabling users to allocate and reassess permissions for background applications, with a background application manager that determines availability and enforces limits to prevent excessive resource usage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If administrators manually test and decide which applications are allowed to run in the background, then application selection precision is improved, but device complexity and user control are worsened

Engineering Contradiction:
Improveapplication selection precisionVSAvoidpermission management complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The system automatically manages background application permissions by having applications self-evaluate and self-select based on predefined objective criteria. Applications automatically determine their own eligibility for background execution based on their functionality and requirements, eliminating the need for manual administrator testing and decision-making while maintaining precise selection.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system changes the state of permission management from static manual configuration to dynamic automated evaluation. By implementing objective criteria that automatically assess application requirements and adjust permissions accordingly, the system transforms the permission allocation process from a complex manual procedure to a streamlined automated parameter-based system.

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If the system allows applications to run in the background without restrictions, then application functionality is improved, but battery life and processing performance are worsened

Engineering Contradiction:
Improveapplication functionalityVSAvoidbattery consumption
Core Design Contradiction:
Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

The system applies different permission levels to different applications based on their specific needs and the objective criteria they meet. Instead of a blanket restriction or permission for all applications, each application receives localized permission treatment - those that meet the criteria for real-time communication or essential functionality receive background execution permission, while others are restricted, optimizing battery usage while maintaining necessary functionality.

Inventive Principle:
Principle #3Local quality

3Device complexity

If push notifications are used for delivering messages to clients, then system simplicity is improved, but delivery reliability and security are worsened

Engineering Contradiction:
Improvenotification system complexityVSAvoidnotification delivery guarantee
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The system segments the notification delivery mechanism into two distinct pathways: push notifications for non-critical updates and direct background connections for critical real-time communications. This segmentation allows push notifications to handle general updates with simple infrastructure, while time-sensitive and security-critical communications use dedicated background channels that guarantee delivery and maintain encryption, resolving the contradiction between simplicity and reliability.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS8813177B2Background application management
Publication Date: 2014.08.19 MICROSOFT TECHNOLOGY LICENSING LLC
  • US8813177B2 patent drawing
  • US8813177B2 patent drawing
  • US8813177B2 patent drawing

AI summary

The techniques and systems disclosed herein generally pertain to managing permissions for applications to allow the applications to run in a background state by an operating system. In some embodiments, user interfaces may be used to allow users to manage application permissions without requiring the user to understand specifics of background applications, but rather by providing a predetermined threshold number of permissions that the user can assign to applications. When the predetermined threshold number of permissions has been allocated and a subsequent application requests a permission, the user may replace or swap out an application that currently has a permission by giving the permission to the requesting application.