Content Centric Network Routing via Persistent Names
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Internet architecture relies on location-based addressing, which is inadequate for meeting evolving network demands, particularly in facilitating access to content anywhere, anytime, and lacks dynamism and human-readable naming schemes, leading to inefficiencies and security concerns.
Innovation Solution
A content-centric network (CCN) system that routes content based on unique, persistent, and structured names, enabling authentication and caching, with dynamic routing and flow control, allowing content to be accessed independently of its location or publisher.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If location-based addressing (IP address) is used, then network communication can be established, but content accessibility becomes tied to physical location and device, reducing flexibility and adaptability
Solution Approach 1:
The patent segments the addressing function by separating content identification (name) from location identification (IP address). Content is addressed by its name rather than its location, allowing the same content to be accessed from multiple locations. This segmentation enables content to be routed independently of the consumer's physical location or device.
Solution Approach 2:
The patent introduces content names as an intermediary between the consumer and the content location. Instead of directly addressing content by IP address, consumers use human-readable names as intermediaries to request content. The network then resolves these names to appropriate content locations, providing flexibility and location independence.
2Adaptability or versatility
If DNS is used to translate hostnames to IP addresses, then human-readable addressing is enabled, but the mapping is rigid and cannot accommodate content movement or changes
Solution Approach 1:
The patent implements dynamic name-to-content mapping where content names can be associated with multiple locations and the mapping can change over time. Unlike static DNS records, content names can be dynamically reassigned to different content sources or locations, allowing the system to adapt to content movement, updates, and redistribution without requiring complex reconfiguration.
Solution Approach 2:
The patent makes content names universal by allowing a single name to map to multiple content locations and sources. This multi-functionality enables the same content name to be served from different servers, locations, or content sources depending on availability, preference, or network conditions, providing flexibility that rigid DNS cannot achieve.
3Ease of operation
If DHT systems use opaque binary names, then content location can be determined, but human readability and authentication capabilities are lost
Solution Approach 1:
The patent applies local quality by making different parts of the content name serve different functions. The name can have human-readable portions for identification and authentication, while maintaining structural components for routing and location determination. This allows the name to be both readable and functional without requiring opaque binary encoding.
Solution Approach 2:
The patent uses cryptographic hashes or digests as copies of content identifiers that can be verified for authenticity. Instead of using opaque binary names directly, the system uses readable names that can be verified through cryptographic copying, allowing users to read and verify content authenticity without relying on unreadable binary identifiers.
4Adaptability or versatility
If DHT systems assume fully connected network, then content can be located, but network topology changes and dynamic reconfiguration become difficult
Solution Approach 1:
The patent implements dynamic network mapping where content names can be associated with multiple locations and the mapping can change as network conditions change. The system can dynamically update content location information without requiring complex reconfiguration of the entire network mapping, allowing flexible adaptation to network topology changes.
Solution Approach 2:
The patent enables the system to discard outdated content location mappings and recover or establish new mappings as needed. When content moves or network conditions change, the system can abandon old location associations and create new ones, providing flexibility without requiring complex persistent mapping maintenance.
5Productivity
If content is delivered without flow control, then content can be transmitted, but network load increases and fair sharing becomes difficult
Solution Approach 1:
The patent implements flow control through feedback mechanisms where the network monitors content delivery and adjusts transmission based on consumer interest and network conditions. The system uses feedback about content consumption patterns to regulate delivery, preventing excessive bandwidth usage while maintaining efficient content transmission to interested consumers.
Solution Approach 2:
The patent applies partial action by delivering only the portions of content that are actually requested or needed, rather than transmitting complete content streams. The system can selectively deliver content based on consumer interests, usage patterns, and network conditions, reducing unnecessary bandwidth consumption while maintaining productivity for actual content needs.
Data Source
AI summary
One embodiment of the present invention provides a system for facilitating communication in a content centric network (CCN). During operation, the system receives at a first node from an interest owner an interest in a piece of content. The interest indicates a structured name for the content. Furthermore, the name is unique and persistent with respect to the content, and where the name includes authentication information for the content. Next, the system determines whether content available at the first node satisfies the interest. If so, the system sends the content to the interest owner. Otherwise, the system marks the interest as pending, and forwards the interest to a second node in the network based on the interest. After receiving content from the second node in response to the forwarded interest, the system un-marks the interest as pending and sends the content to the interest owner.