Adaptive Content Balancing for Web Clients

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing content delivery systems struggle to adapt to varying host device performance and network conditions, leading to inconsistent user experiences due to the static delivery of content, which can result in either suboptimal rendering on capable devices or wasteful resource usage.

Innovation Solution

Implement a method and system for adaptive content balancing that monitors and measures content processing performance across different client devices, matching resource groupings based on performance profiles to deliver content tailored to the device's capabilities, ensuring optimal rendering speed and quality.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If content is statically delivered based on host device physical characteristics, then content rendering compatibility is improved, but content quality and user experience deteriorate on capable devices

Engineering Contradiction:
Improvecontent rendering compatibilityVSAvoidcontent quality
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system dynamically adjusts content delivery based on real-time performance feedback rather than static device characteristics. The content server continuously monitors processing performance metrics from client devices and adapts content resource groupings accordingly, enabling the system to respond to changing conditions and maximize content quality while maintaining compatibility.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes the parameters of content delivery by varying resource groupings based on measured performance metrics. Instead of delivering the same content format to all devices, the server adjusts content parameters (resource complexity, detail level, etc.) according to the specific performance capabilities of each client device, thereby optimizing both compatibility and quality.

Inventive Principle:
Principle #35Parameter changes

2Productivity

If complex content is delivered to highly capable host devices, then content quality is improved, but network resource wastage and server load increase

Engineering Contradiction:
Improvecontent qualityVSAvoidnetwork resource wastage
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

The system implements a feedback mechanism where client devices report their content processing performance metrics back to the content server. The server uses this feedback to intelligently determine appropriate resource groupings for content delivery, ensuring that complex content is only delivered when the client device can effectively utilize it, thereby avoiding network resource wastage.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system delivers content with appropriate complexity rather than maximum complexity to all capable devices. By delivering only the necessary level of content complexity based on measured performance, the system avoids the excessive action of delivering unnecessarily complex content that would waste network resources and server capacity.

Inventive Principle:
Principle #16Partial or excessive action

3Reliability

If simplified content is delivered to accommodate slower rendering devices, then rendering compatibility is improved, but user experience deteriorates on capable devices

Engineering Contradiction:
Improverendering compatibilityVSAvoiduser experience
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system dynamically determines content complexity based on real-time performance measurements from each client device. Rather than using a static simplification rule for all devices, the server adapts content delivery to match each device's actual capabilities, ensuring that capable devices receive rich, high-quality content while less capable devices receive appropriately simplified content.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system applies different content quality levels to different client devices based on their individual performance characteristics. Each device receives content tailored to its specific capabilities, with capable devices receiving high-quality complex content and less capable devices receiving simplified content, thereby optimizing user experience for each local context.

Inventive Principle:
Principle #3Local quality

4Ease of manufacture

If content delivery is statically determined by device type, then server implementation simplicity is improved, but adaptability to varying performance conditions deteriorates

Engineering Contradiction:
Improveserver implementation simplicityVSAvoidadaptability to performance conditions
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The system transitions from static content delivery based on device type to dynamic content delivery based on measured performance metrics. The server continuously monitors and adapts to varying performance conditions of client devices, enabling flexible and versatile content delivery that responds to actual device capabilities rather than predetermined device categories.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS10007591B2Adaptive content balancing in a web application environment
Publication Date: 2018.06.26 SUGARCRM INC
  • US10007591B2 patent drawing
  • US10007591B2 patent drawing
  • US10007591B2 patent drawing

AI summary

A method for adaptive content balancing for Web clients includes monitoring content processing performance in different client computing devices communicatively coupled over a network to a content server, measuring the content processing performance for each of the different devices and storing the measured performance for each of the different devices in connection with different resource groupings of the requested content type. Thereafter, a request for content is received in the content server from one of the devices, and the stored performance is retrieved. As such, the retrieved metrics of the computing device are matched to the retrieved metrics of one of a multiplicity of groupings of one or more different resources associated with the requested content and the resources of the one of the multiplicity of the groupings is included in the requested content. Finally, the requested content is transmitted to the one of the client computing devices.