Mixed Mode Content Delivery for Mobile Devices
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current dynamic content delivery models, either push-based or pull-based, face inefficiencies such as wasteful bandwidth usage, complex infrastructure requirements, and scalability issues, leading to poor user experience and increased costs.
Innovation Solution
A mixed mode delivery model that combines subscription-based delivery with client-driven pull models, allowing content delivery to be triggered when content is consumed or expires, using either push or pull bearers, and leveraging a content delivery server for processing and caching to optimize content management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If pull-based delivery is used, then the client application can request content on demand, but the client application must periodically pull content wasting wireless bandwidth and increasing customer costs
Solution Approach 1:
The patent implements a hybrid model where the content provider periodically pushes content availability information to the client application, but the actual content transfer only occurs when the client explicitly requests it. This periodic notification mechanism reduces unnecessary bandwidth consumption compared to continuous polling, while still allowing on-demand content retrieval.
Solution Approach 2:
The system uses feedback mechanisms where the client application notifies the content provider when it has consumed or expired its content buffer, triggering the next content delivery. This feedback loop ensures content is delivered only when needed, optimizing bandwidth usage while maintaining content freshness.
2Productivity
If push mode delivery is used, then content can be delivered to mobile device, but requires complex content delivery infrastructure including subscription and content management
Solution Approach 1:
The patent extracts the complex subscription management and content filtering logic from the content provider and relocates it to the client application. The client application now handles subscription filters locally, requesting only the content it needs, which simplifies the content provider's infrastructure while maintaining efficient content delivery.
Solution Approach 2:
The client application performs self-service by autonomously managing its own content subscriptions, filters, and requests. It independently determines what content it needs based on local filter criteria and consumes content from the provider without requiring complex centralized management, thereby reducing infrastructure complexity.
3Reliability
If frequent pull attempts are made, then content freshness is maintained, but network resources are affected and customer bill increases
Solution Approach 1:
The system maintains continuous content availability through a hybrid approach: the content provider continuously prepares and holds content ready for delivery, while the client application continuously monitors its content buffer status. This ensures content freshness is maintained without requiring frequent active pull attempts, as content can be pushed immediately when the client indicates readiness.
4Loss of energy
If infrequent pull attempts are made, then network resources are saved, but content becomes outdated
Solution Approach 1:
The content provider performs preliminary actions by pre-processing and preparing content in advance, holding it ready in a buffered state. When the client application indicates it has consumed its content or is ready for more, the prepared content is immediately delivered, ensuring freshness without requiring frequent pull attempts from the client.
Data Source
AI summary
A method, system and apparatus for mixed mode delivery of content to a mobile device, the method having the steps of: receiving a subscription message including a filter; storing the filter; sending a subscription identifier; applying the filter to content available on the content provider, thereby producing a content subset; waiting for receipt of a content request; and forwarding the content subset upon receipt of the content request.