Mobile Device Performance Management via Application Threshold Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current mobile devices lack effective management of power and memory resources among competing applications, and there is a need to collect usage data from users without impacting device performance or privacy concerns.
Innovation Solution
A mobile monitoring application that collects and reports data on network usage while minimizing its impact on the device's performance, using a systems management application to prioritize applications based on power and memory usage, and a registration process to ensure user privacy through anonymous data collection.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If a monitoring application collects usage data from mobile devices, then service providers can obtain network and usage data for planning purposes, but device performance may be degraded and user privacy may be compromised
Solution Approach 1:
The monitoring application segments data collection by focusing only on specific metrics (network usage, app performance) rather than comprehensive monitoring. It separates monitoring functions into discrete modules that can be independently controlled, allowing selective data collection that minimizes performance impact while maintaining useful information for service provider planning.
Solution Approach 2:
The system implements partial monitoring by collecting only essential usage data rather than all possible device information. It monitors specific parameters (network connectivity, app launch times, battery consumption) that are sufficient for service provider planning without the excessive data collection that would cause performance degradation or privacy concerns.
2Productivity
If applications operate without awareness of memory needs of other apps, then each app can optimize its own performance, but overall device performance degrades when memory approaches threshold limits
Solution Approach 1:
The monitoring application provides feedback to the operating system about memory usage patterns across applications. It tracks which applications consume the most memory and when memory thresholds are approached, enabling the system to make informed decisions about memory allocation and process management that maintain overall device performance while allowing individual apps to operate efficiently.
Solution Approach 2:
The monitoring application serves multiple functions: it monitors memory usage, tracks application performance, collects usage data for service providers, and provides insights into device state. This multi-functionality allows one application to address multiple technical challenges simultaneously without requiring separate specialized monitoring systems.
3Adaptability or versatility
If users are monitored to provide usage data for service planning, then service providers can optimize network architecture, but users may object on privacy grounds and consent may be limited
Solution Approach 1:
The system extracts only the necessary usage data from comprehensive device information. Instead of monitoring all user activities and device states, it selectively collects specific metrics (network connectivity patterns, data usage volumes, app performance data) that are sufficient for network planning while leaving sensitive personal information unmonitored, thereby reducing privacy concerns.
Solution Approach 2:
The monitoring application changes the parameters of data collection from detailed, granular user behavior tracking to aggregated, anonymized usage metrics. By transforming individual user data into consolidated statistical information about network usage patterns, it maintains the ability to optimize network architecture while eliminating identifiable personal information that would trigger privacy objections.
Data Source
AI summary
A system and method for managing performance of a mobile device. A current runtime list and a measure of performance are determined. A request to execute a new application not on the current runtime list is received. A determination is made whether executing the new application will cause the performance measure to be equal to or less than a threshold level. When executing the new application will not cause the performance measure to be equal to or less than a threshold level, the request to execute the new application is granted. When executing the new application will cause the performance measure to be equal to or less than a threshold level, the request to execute the new application is declined.