Adaptive Content Delivery via Device-Specific Resource Locators
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Content delivery systems face complexity and network latency due to the need to provide content in various formats for different devices, requiring multiple codecs and hardware components for format conversion, which diminishes the consumer experience.
Innovation Solution
A server complex redirects content requests from a generic resource locator to a device-specific resource locator, caching content in formats suitable for each device type, eliminating the need for on-the-fly conversion and simplifying system architecture.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If content is delivered in different formats for different devices using multiple codecs and hardware components for format conversion, then content compatibility across diverse devices is improved, but system complexity increases and network latency occurs
Solution Approach 1:
The patent segments the content delivery system into device-specific resource locators, where each locator is dedicated to a particular device type (e.g., smartphone, tablet, TV). This segmentation eliminates the need for complex format conversion by directing each device type to its optimized content format from the start, thereby reducing system complexity while maintaining content compatibility across diverse devices.
Solution Approach 2:
The patent implements preliminary action by pre-configuring device-specific resource locators with content in the appropriate formats for each device type. Instead of converting formats on-demand, the system prepares and stores content in multiple formats in advance, associated with specific device identifiers. When a request arrives, the system simply redirects to the pre-prepared format, eliminating real-time conversion complexity and latency.
2Adaptability or versatility
If content is converted from one format to another using numerous codecs and hardware components, then content compatibility across different devices is improved, but network latency increases
Solution Approach 1:
The patent applies preliminary action by pre-converting and storing content in multiple device-specific formats in advance. Content is converted to various formats (e.g., mobile, tablet, TV optimizations) before being stored in the CDN, with each format associated with a specific device type identifier. When a content request arrives, the system performs a rapid redirect to the pre-converted format matching the device type, eliminating real-time conversion latency and delivering content immediately.
3Device complexity
If a generic resource locator is used for all devices, then system architecture is simplified, but content delivery in device-specific formats is not achieved
Solution Approach 1:
The patent implements universality by creating a unified CDN architecture that handles multiple device types through a single redirect mechanism. The system maintains a universal resource locator structure that automatically detects device type from the request and redirects to the appropriate device-specific locator. This universal approach simplifies the overall architecture compared to maintaining separate CDN infrastructures for each device type, while still achieving device-specific content delivery through intelligent redirection.
Data Source
AI summary
A server complex (102) includes an interface portal (116). The server complex exposes (401) a generic resource locator (402) pointing to the media content in a generic format at the interface portal. The server complex receives requests for media content (101) from at least a first client device (601) to receive the media content in a first format (603) and at least a second client device (602) to receive the media content in a second format (604). The server complex determines (405), from a header (407) of the request, whether the request is from the first client device or the second client device, generates (409) a response message (108) comprising a manifest file (109) comprising a device specific resource locator (410) pointing to the media content cached (412) in one of the first format or the second format, and transmits (411) the response message to the requesting client.