Middleware Cache Redirect for Broadcast Unicast Switching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing technologies face challenges in seamlessly switching between broadcast/multicast and unicast media data transmission techniques based on geographical location, leading to inefficiencies in media data retrieval when the broadcast/multicast service becomes unavailable.
Innovation Solution
A middleware unit controls an HTTP proxy unit and a local server to determine if cached media data is available, redirecting requests from an external server to the local server when the broadcast/multicast service is no longer available, allowing for efficient use of cached data during the transition to unicast transmission.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the client device switches from broadcast/multicast to unicast when broadcast service becomes unavailable, then media data retrieval continuity is maintained, but network traffic and server load increase
Solution Approach 1:
The system performs preliminary actions by caching media data segments in the broadcast/multicast path before the service becomes unavailable. When switching to unicast, these pre-cached segments are utilized, reducing the need for immediate network retrieval and thereby decreasing network traffic and energy consumption during the transition.
Solution Approach 2:
The HTTP proxy acts as an intermediary between the client device and the network. It intercepts unicast requests, checks for available cached segments, and redirects requests for cached segments to the local cache, thereby mediating between unicast transmission and local resource utilization to reduce network traffic.
2Loss of energy
If the client device utilizes cached media data after switching from broadcast/multicast to unicast, then network traffic is reduced, but device complexity increases
Solution Approach 1:
The HTTP proxy is designed with multi-functionality, serving both as a standard HTTP proxy for unicast requests and as a cache manager for broadcast/multicast segments. By integrating these functions into a single component, the system reduces device complexity compared to having separate dedicated components for each function.
Solution Approach 2:
The system implements self-service through automatic detection and handling. The HTTP proxy automatically detects when broadcast service becomes unavailable, identifies cached segments that can satisfy unicast requests, and redirects requests without requiring complex manual configuration or intervention, thereby reducing the effective complexity of cache management.
3Productivity
If the HTTP proxy redirects requests to the local server for cached segments, then media retrieval efficiency is improved, but loss of information about external server availability occurs
Solution Approach 1:
The system implements feedback mechanisms where the HTTP proxy monitors and tracks the availability status of external servers. This feedback information is used to make intelligent routing decisions, redirecting requests to the local cache when appropriate while maintaining awareness of external server availability, thus preventing information loss.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
An example client device includes a middleware unit for receiving media data either via a broadcast service or a unicast service, depending on whether the broadcast service is available. The client device also includes a streaming client, such as a Dynamic Adaptive Streaming over HTTP (DASH) client. The DASH client sends requests to retrieve media data via the middleware unit. The middleware unit may cache media data received via the broadcast service, such that even when the broadcast service is not active, if the streaming client requests media data that was previously received via the broadcast service, the middleware unit may provide the media data to the streaming client from the cache, rather than requesting the media data from an external server device specified in the request from the streaming client.