Intermediary Server for Monitoring Mobile App Data Usage
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Users lack control over data consumption by applications on their mobile devices, as system processes and background applications can use data without user knowledge, leading to unexpected data usage beyond allocated limits, and there is a need for methods to monitor and limit data usage by specific applications.
Innovation Solution
A system that intercepts requests from applications on a client computer, determines if they should be monitored, and redirects them to an intermediary server that tracks and limits data consumption by applications, ensuring that data usage does not exceed predefined thresholds, allowing users to manage data allocation per application and network.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If applications are allowed to access the network freely, then application functionality is maintained, but data consumption cannot be controlled or monitored
Solution Approach 1:
The patent introduces a data monitor component that acts as an intermediary between applications and the network connection. This monitor intercepts network requests from applications, tracks data consumption, and enforces data limits without preventing applications from functioning. The intermediary approach allows the system to maintain application functionality while gaining control over data usage through monitoring and limiting mechanisms.
2Loss of energy
If data consumption is monitored and limited, then data usage is controlled, but application performance may be affected
Solution Approach 1:
The data monitoring system implements dynamic behavior by adjusting its intervention level based on current data consumption status. When applications are within their allocated data limits, the monitor allows normal network access without interference. When limits are approached or exceeded, the monitor dynamically blocks additional data requests. This dynamic approach ensures application performance remains unaffected during normal operation while enabling effective data control when limits are reached.
Solution Approach 2:
The system performs preliminary actions by pre-defining data limits and allocation rules before data consumption occurs. Applications are assigned predetermined data quotas and the monitor is configured with blocking rules in advance. This preliminary configuration allows the system to automatically enforce data limits without real-time complex decision-making, thereby maintaining application performance while achieving data control objectives.
3Productivity
If background processes are allowed to use data, then system functionality is maintained, but user awareness and control of data usage is lost
Solution Approach 1:
The patent implements feedback mechanisms that provide users with information about data consumption by different applications and background processes. The data monitor tracks and reports data usage, enabling users to see which processes are consuming data and how much. This feedback loop restores user awareness and control by making previously invisible background data usage visible and measurable, allowing users to make informed decisions about their data consumption patterns.
Data Source
AI summary
Computer systems and methods for managing network data consumption between a client computer and one or more server computers. A computer system comprising: a memory persistently storing a set of instructions; one or more processors coupled to the memory, wherein the one or more processors execute the set of instructions, which causes the one or more processors to: intercept, at a client computer, a first request to a first server computer from a first application being executed on the client computer before the client computer sends the first request to the first server computer; determine whether the first request should be monitored based on data associated with the first application; in response to determining that the first request should be monitored, redirect the first request to a second server computer that is different than the first server computer, and include one or more parameters that identify the first application and the first server computer.