CCN Node Storage Integration for Direct Content Retrieval
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Internet protocols, such as IP and Ethernet, rely on location-based addressing, which becomes inadequate for meeting the evolving demands of network traffic, especially in content-centric networks where content is requested by unique names rather than physical locations, leading to inefficiencies in content delivery and storage access.
Innovation Solution
A system and method for caching content data in a content-centric network (CCN) that involves forwarding content packets to an incoming port, caching them in attached storage, assembling queries for storage blocks, and storing these queries in a cache table for direct access, using advanced storage technologies like ATA over Ethernet or Fibre Channel over Ethernet, and performing longest-prefix-match lookups for efficient retrieval.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If content is cached in attached storage devices in a CCN, then content retrieval speed is improved, but system complexity increases due to integration of storage devices with network nodes
Solution Approach 1:
The patent combines network node functions with storage device functions by integrating attached storage devices directly into CCN nodes. The network node simultaneously performs packet forwarding, content caching, and storage management, eliminating the need for separate storage infrastructure and reducing overall system complexity despite adding storage capabilities.
Solution Approach 2:
The network node is designed to perform multiple functions: it acts as a router for packet forwarding, a cache for popular content, and a storage device for persistent content retention. This multi-functionality allows a single component to handle diverse operations, improving content retrieval speed while managing system complexity through functional consolidation.
2Productivity
If direct access to storage blocks is implemented, then content delivery efficiency is improved, but query assembly and cache table management increase processing overhead
Solution Approach 1:
The system pre-assembles queries for storage blocks when content is initially cached, and stores these pre-assembled queries in a cache table. When content needs to be retrieved, the pre-assembled queries are already available, eliminating the need for complex query assembly operations at retrieval time and reducing processing overhead.
Solution Approach 2:
The system creates and stores copies of query structures in the cache table alongside cached content. These query copies are prepared in advance and stored with the content, allowing direct retrieval without regenerating queries. This copying approach transfers the processing overhead to the initial caching phase rather than every retrieval operation.
3Loss of energy
If content packets are cached in attached storage, then network load is reduced, but storage device integration requires additional protocols like ATA over Ethernet or Fibre Channel over Ethernet
Solution Approach 1:
The network node acts as an intermediary between the CCN and attached storage devices, translating CCN content packets into storage device protocols (ATA over Ethernet, Fibre Channel over Ethernet, or iSCSI). This intermediary function allows the use of standardized storage protocols while maintaining content-centric network operations, reducing network load by handling storage translations locally at the node.
Data Source
AI summary
One embodiment of the present invention provides a system for caching content data to a storage device attached to a node in a content-centric network (CCN). During operation, the system receives a content packet; forwards the content packet to an incoming port of an interest in the content packet; caches a copy of the content packet in the attached storage device, assembles a query; which includes at least a network header and an address associated with storage blocks at which the cached copy of the content packet is located, corresponding to the content packet; and stores the query in a cache table, thereby facilitating a subsequent direct access to the storage blocks using the assembled query to retrieve the copy of the content packet.