Network Node Content Size Pre-Sending for Client Resource Constraints
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data communication methods, particularly in mobile client environments, are inefficient due to the lack of pre-sent content size information, leading to resource constraints and excessive usage of device and network resources when attempting to display web pages with linked objects that exceed client device capabilities.
Innovation Solution
A method where a network node or client device receives content size information to determine whether to request or send objects based on the size and capabilities of the client device, modifying the content message by removing object references if the aggregate size exceeds the supported content size, thereby optimizing resource usage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If the client device requests and receives all linked objects referenced in the HTML page, then the complete web page content is available for display, but the client device exceeds its memory and processor capabilities leading to resource constraints
Solution Approach 1:
The server performs preliminary actions by calculating and including content size information for all linked objects within the HTML page response. This allows the client device to预先 know the total content size before actually downloading all objects, enabling it to make informed decisions about whether to request additional objects based on its resource constraints.
Solution Approach 2:
The client device can choose to perform partial action by requesting only a subset of linked objects based on the content size information provided in the HTML page, rather than excessively requesting all objects. This allows the device to balance between obtaining complete content and staying within its memory and processor capabilities.
2Loss of information
If the client device sends additional content requests to obtain all linked objects, then complete page content is obtained, but significant device resources, RF and network resources are consumed
Solution Approach 1:
The HTML page includes feedback information in the form of content size data for all linked objects. This feedback allows the client device to determine in advance whether requesting additional objects would be worthwhile given its resource constraints, thereby avoiding unnecessary energy consumption from requesting and processing content that cannot be properly displayed.
Solution Approach 2:
The server performs preliminary calculation and inclusion of content size information for all linked objects in the HTML response. This preliminary action eliminates the need for the client device to make multiple separate requests to discover content sizes, reducing both the number of requests (network resources) and the processing overhead (device resources).
3Productivity
If the client device attempts to process the page without knowing object sizes, then the device uses resources trying to display the page, but the page may not be fully renderable due to memory or processor constraints
Solution Approach 1:
The server performs preliminary calculation and inclusion of content size information for all linked objects in the HTML response. This preliminary action allows the client device to assess whether the page can be successfully rendered before committing significant resources to downloading and processing all objects, thereby improving both productivity and reliability.
Solution Approach 2:
The client device can adjust its action level by requesting only a subset of objects that fit within its resource constraints, as determined by the content size information provided in the HTML page. This prevents the device from attempting to process content that would exceed its capabilities and result in failed rendering.
Data Source
AI summary
A method is disclosed for pre-sending content size information so that content objects that might exceed the client device's resources are not sent in subsequent content transmissions. For example, a network node may receive from a content server a content message directed to a client device, wherein the content message includes a plurality of object references, each referencing respectively an object that is not contained in the content message. The network node may determine an object size of at least one of the objects and a supported content size for the client device. Based upon the determined object size and the determined supported content size of the client device, the network node may modify the content message by removing the object reference referencing the at least one object and then send the modified content message to the client device.