Context-Specific Data Plans via Zero-Rated Proxy Servers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Users face challenges with unpredictable and costly data access on cellular networks, as data-intensive applications often deplete allocated data limits, leading to additional purchases and disrupted service for other applications.
Innovation Solution
Implementing context-specific data plans that utilize zero-rated proxy servers to authorize network requests, allowing users to purchase application-specific or resource-specific data plans that provide unlimited data access for a set period, avoiding metered network fees for designated applications or resources.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If users access data-intensive applications on metered cellular networks, then data usage increases and applications can run without restriction, but the user allocation is depleted quickly leading to additional purchases and service disruption
Solution Approach 1:
The patent segments data access by introducing context-specific data plans that separate different types of network traffic. Applications are categorized into different contexts (e.g., background vs. foreground, specific app types) and each context has its own data plan with different billing rules. This allows data-intensive applications to run without depleting the user's general data allocation, as they are billed under their specific context plan.
Solution Approach 2:
The patent changes the billing parameters from a flat metered rate to a contextualized pricing model. Instead of charging uniformly for all data usage, the system implements context-specific data plans with different parameters (zero-rating for certain contexts, different rates for others). This allows data-intensive applications to operate with predictable costs without depleting the user's general data allocation.
2Reliability
If cellular providers implement context-specific data plans with zero-rated proxy servers, then users gain predictable billing and transparency, but the device complexity increases due to local gateway utility and proxy server integration
Solution Approach 1:
The patent implements preliminary action by pre-configuring context-specific data plans and establishing proxy server relationships before data usage occurs. The local gateway utility is pre-installed and pre-configured with the provider's proxy server addresses and authentication credentials. When an application requests data access, the gateway utility automatically routes traffic through the appropriate proxy server based on the context, eliminating the need for real-time complex decision-making and reducing runtime device complexity.
3Productivity
If users purchase application-specific data plans for unlimited access, then data-intensive applications can run without depleting general allocation, but the overall device complexity increases due to multiple data plan management
Solution Approach 1:
The patent implements self-service by enabling the local gateway utility to automatically manage context-specific data plans without requiring user intervention. The gateway utility autonomously monitors application activity, identifies which context-specific plan applies to each application, and routes traffic accordingly. This automation eliminates the complexity of manual data plan management for users while maintaining the benefits of application-specific unlimited access.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Techniques for contextual mobile data access are described. In one embodiment, an apparatus may comprise a mobile device with a local gateway utility. The local gateway utility may be operative to receive a network request on a device, determine that the network request corresponds to a context-specific data plan for the device, the context-specific data plan authorizing performance of the network request through a zero-rated proxy server, and perform the network request for the application using the zero-rated proxy server as an intermediary. Other embodiments are described and claimed.