Content Stream Aggregation for Content-Centric Network Latency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Content-centric networks (CCNs) face significant download latency due to the need for multiple round-trip times to obtain and download embedded objects within a content collection, as existing protocols like HTTP are inefficient for transferring large numbers of small files, and there are no 'zero round-trip time' solutions available in CCN settings.
Innovation Solution
A system that aggregates all necessary content into a single named stream, known as an all-in-one stream, which includes a specially constructed manifest followed by constituent objects, allowing for the download of a content collection without incurring a round-trip time for the content manifest, by packaging the manifest and content components under the same namespace and using sequence numbers and hash values to facilitate efficient content retrieval.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If multiple separate requests are used to download individual content components, then each component can be retrieved independently, but the overall download latency increases due to multiple round-trip times
Solution Approach 1:
The patent combines multiple separate content component requests into a single aggregate request that retrieves all content components in one round-trip time. The requestor sends one request for the entire content collection, and the responder returns all content components packaged together, eliminating the need for multiple sequential requests and significantly reducing download latency.
Solution Approach 2:
The responder performs preliminary packaging of all content components into a single response before transmission. The manifest describing the content collection is prepared in advance, allowing the requestor to receive all necessary content components in one go without needing to make subsequent requests for individual components.
2Productivity
If HTTP protocol is used to transfer multiple small files, then individual files can be transferred reliably, but the throughput decreases due to overhead of separate TCP sessions for each file
Solution Approach 1:
The patent merges multiple small file transfers into a single aggregated transfer operation. Instead of establishing separate TCP sessions for each content component, the system packages all content components into one large response, reducing protocol overhead and improving throughput when transferring large numbers of small files.
Solution Approach 2:
The single request mechanism serves multiple functions simultaneously: it requests the manifest, retrieves all content components, and obtains metadata about the entire content collection in one operation, eliminating the need for separate requests for each component.
3Loss of time
If content components are downloaded sequentially after parsing the markup document, then the requestor can process content as it arrives, but the total download time increases due to sequential processing
Solution Approach 1:
The system performs preliminary packaging of all content components into a single response, allowing the requestor to receive the complete content collection in one operation. The manifest is included in the initial response, enabling the requestor to immediately begin processing content without waiting for subsequent requests or parsing intermediate markup documents.
Data Source
Figure 1
Figure 2
Figure 3A~3B
AI summary
One embodiment of the present invention provides a system for assembling a single content stream that enables downloading of a content collection using the single content stream over a network. During operation, the system obtains the content collection that includes a plurality of content components, and generates a manifest for the content collection. A respective entry in the manifest corresponds to a content component. The system assembles the single content stream by including the manifest followed by the plurality of content components. The manifest and the content components are packaged into objects under a same namespace, thereby facilitating a requester requesting one or more content components within the content collection using interests under the same namespace.