Cache Subscription Server for Wireless Mobile Content Delivery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing Content Delivery Networks (CDNs) may not cache Internet content that is not popular or important, leading to missed opportunities for users who prefer specific content that does not meet the CDN's caching rules.
Innovation Solution
A Cache Subscription Server (CSS) allows users to subscribe to caching services, determining and storing desirable content based on user preferences and access patterns, enabling faster delivery of preferred content to mobile devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If CDN caches content based on popularity and importance rules, then delivery speed of popular content is improved, but user-specific preferred content may not be cached
Solution Approach 1:
The system segments the caching function into two parts: CDN handles popular content caching based on global rules, while CSS handles user-specific content caching based on individual preferences. This segmentation allows each component to specialize, resolving the contradiction between optimizing for popular content delivery speed and adapting to user-specific content needs.
Solution Approach 2:
Cache Subscription Server acts as an intermediary between users and CDN, receiving user preferences, identifying relevant content, and requesting caching from CDN. This intermediary enables user-specific content to be cached without requiring CDN to change its global popularity-based caching strategy, thus maintaining both popular content optimization and user-specific adaptability.
2Productivity
If CDN stores only popular content, then caching resource utilization is improved, but user-specific content access performance deteriorates
Solution Approach 1:
Users actively subscribe to their preferred content through CSS, which then automatically requests caching from CDN. This self-service approach ensures that user-specific content is cached without consuming CDN resources that would be better spent on popular content, maintaining caching efficiency while improving user-specific content availability.
Solution Approach 2:
CSS identifies and requests caching of user-preferred content in advance based on user profiles and access patterns. This preliminary action ensures that when users access their preferred content, it is already cached and ready for fast delivery, improving reliability without requiring CDN to pre-cache all possible user-specific content.
3Device complexity
If CDN uses general caching rules, then system complexity is reduced, but user preference customization capability is limited
Solution Approach 1:
The caching system is segmented into CDN with simple popularity-based rules and CSS with user preference management. This segmentation allows CDN to maintain low complexity while CSS handles the complexity of user preference customization, enabling both simple operation and high adaptability.
Solution Approach 2:
CSS serves as an intermediary that manages user preferences and translates them into CDN caching requests. This intermediary shields users from CDN complexity while enabling sophisticated preference-based caching, resolving the contradiction between system simplicity and customization capability.
Data Source
AI summary
A server device may receive an indication that a mobile device has enrolled in a cache subscription service. The server device may receive cache parameters associated with the cache subscription service, where the cache parameters are specific to the mobile device. Content may be retrieved from a network and stored, in a memory associated with the one or more server devices, based on the received cache parameters. The server device may receive, from the mobile device, a request for particular content, determine whether the request for particular content corresponds to content that is stored in the memory, and provide, when determining that the requested particular content corresponds to content that is stored in the memory, the corresponding stored content to the mobile device.