Device Context-Aware Content Delivery for Adaptive User Experience
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing web pages and content are often not optimized for various devices, leading to suboptimal user experiences due to differences in screen sizes and device capabilities, and there is a lack of integration between devices and applications with servers.
Innovation Solution
Devices provide device context information, such as battery level and network settings, to content providers, allowing them to select the most appropriate version of content for display, which can be configured to conserve resources like power, by using mode settings based on processor load, memory, and other metrics.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If a one-size-fits-all web page is provided to all devices, then the content provider can maintain a single version of content, but the user experience deteriorates because the page is not suitable for certain devices with different screen sizes and capabilities
Solution Approach 1:
The patent segments content into multiple versions tailored for different device types and screen sizes. The system divides the single content source into device-specific variations, allowing each device to receive appropriately formatted content rather than a generic one-size-fits-all page.
Solution Approach 2:
The patent implements dynamic content selection based on device characteristics. The system automatically adjusts which content version is delivered by detecting device properties such as screen size, device type, and capabilities, making the content delivery adaptive rather than static.
2Ease of operation
If multiple versions of content are created for different devices, then user experience improves, but the complexity of content management increases
Solution Approach 1:
The patent prepares multiple content versions in advance and stores them on the server. By pre-segmenting content into device-specific versions before delivery, the system avoids the complexity of real-time content transformation, simplifying the content management process while still providing customized content.
Solution Approach 2:
The patent introduces an intermediary mechanism (device detection and content selection system) that automatically matches devices with appropriate content versions. This intermediary handles the complexity of content management by automating the selection process based on device characteristics, reducing manual intervention.
3Device complexity
If standard content is delivered without considering device context, then network transmission is simplified, but power consumption increases because content is not optimized for device capabilities
Solution Approach 1:
The patent applies local quality optimization by delivering content with characteristics matched to specific device properties. Content is customized locally for each device type, optimizing elements such as image resolution, video quality, and text formatting to match the receiving device's capabilities, thereby reducing unnecessary data transmission and power consumption.
4Manufacturing precision
If device context information is collected and processed, then content optimization improves, but the system complexity increases
Solution Approach 1:
The patent implements a feedback mechanism where device context information (such as device type, screen size, and capabilities) is collected and used to automatically select and deliver the appropriate content version. This feedback loop enables precise content optimization without requiring complex manual configuration, as the system self-adjusts based on received device information.
Data Source
AI summary
According to some aspects of the disclosure, when a computing device sends a request for content, such as an Internet page, the computing device can include with the request one or more device context parameters, such as the computing device's power preferences (e.g., current battery level), wireless settings, network connection, etc. The content provider may then use this device context information to select the most appropriate version of the requested content. One example of device context information may be a low-power power save mode setting, or other mode setting.