Location Hints in Content Requests for CCN Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Content Centric Networking (CCN) faces challenges in efficiently locating and routing content due to the vast number of content pieces (approximately 10^15) and the dynamic nature of content locations, leading to high overhead in updating routing tables and lack of reliable debugging tools, especially in mobile environments where connections can be disrupted.
Innovation Solution
Implementing a method where end devices actively assist in content location determination by inserting location hints in requests, using probe flags to test routes, and extending publish and subscribe primitives with content location messages, enabling efficient content retrieval and debugging through modes like location hint, probe only, and listed location modes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If content is cached in multiple network locations to reduce retrieval delay and publisher workload, then content accessibility and network efficiency are improved, but the complexity of locating and routing to the nearest content copy increases
Solution Approach 1:
The patent applies preliminary action by having end devices proactively insert location hints into content requests before the actual content retrieval occurs. This allows the network to pre-know potential content locations through caching information, avoiding the need for complex real-time routing table updates. The location hint mechanism prepares routing information in advance, resolving the contradiction between fast content retrieval and routing complexity.
2Productivity
If routing tables are updated to direct requests to the nearest content copy, then content retrieval efficiency is improved, but the overhead of maintaining routing information for vast content scales becomes prohibitive
Solution Approach 1:
The patent extracts the location information from the traditional routing table structure and places it directly in the content request packets as location hints. This removes the burden of maintaining large routing tables at network nodes, as each node only needs to process the location hint information carried in individual requests rather than maintaining comprehensive routing information for all content.
Solution Approach 2:
The location hint acts as an intermediary that carries content location information between the end device and network nodes. Instead of requiring network nodes to store and manage routing tables for all content, the location hint mediates the routing process by providing necessary location information on-demand, reducing the quantity of routing data needed in the network.
3Adaptability or versatility
If content location information is aggregated by name prefixes to enable routing, then routing scalability is improved, but the ability to route to specific cached copies is lost
Solution Approach 1:
The patent merges the benefits of prefix-based aggregation with specific content copy locationing by combining location hints with content name requests. The location hint carries specific cached copy information while maintaining compatibility with prefix-based routing structures, allowing both aggregation scalability and precise copy locationing to coexist in the routing process.
Data Source
AI summary
A method implemented by a network node coupled to a network, the method comprising inserting a location hint in a request for a content, wherein the location hint specifies one or more network locations that are known by the network node to hold at least part of the content, sending the request to the network, wherein the request comprises a content name that describes the content, and receiving a data message corresponding to the request from the network, wherein the data message comprises at least a portion of the content.