Content Centric Network Routing Table Aggregation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Content Centric Networks (CCN) face challenges with scalability due to the sharp growth in routing table size and complexity of routing table lookup, leading to redundancy and inefficiencies in data routing.
Innovation Solution
The introduction of a routing device that accounts for the relevance between identifiers of different lengths, using mask types (prefix and postfix) to abstract content name values, thereby reducing the routing table size and improving data forwarding efficiency by determining covering relations between content name values and routing entries.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the CCN approach stores one routing entry for each received Interest packet and LSA, then the routing table can accurately forward packets, but the routing table size grows sharply leading to scalability issues
Solution Approach 1:
The patent merges multiple routing entries that share common prefixes into single aggregated entries. For example, instead of storing separate entries for '/parc.com/media/art', '/parc.com/media/music', '/parc.com/media/video', the system aggregates them into a single entry '/parc.com/media' with appropriate forwarding information, thereby reducing routing table size while maintaining accurate packet forwarding capability
Solution Approach 2:
The patent introduces a universal routing entry structure that can handle multiple specific content prefixes through wildcard matching and prefix aggregation. A single routing entry can serve multiple specific content types by using hierarchical prefix matching, making the routing table more universal and reducing the number of entries needed
2Measurement precision
If the routing table contains a large number of routing entries to handle diverse content, then content forwarding accuracy is maintained, but the complexity of routing table lookup increases
Solution Approach 1:
The patent segments the routing table into hierarchical levels based on content name prefixes. The lookup process is segmented into multiple stages: first matching the most significant prefix, then progressively matching subsequent components. This segmentation transforms a single complex lookup operation into multiple simpler staged lookups, reducing overall complexity while maintaining precise content matching
Solution Approach 2:
The patent introduces a hierarchical dimension to the routing table structure, organizing entries by prefix depth and level. Instead of a flat one-dimensional table, the routing information is structured in multiple dimensions (prefix level, wildcard position, face list), enabling more efficient organized search and reducing lookup complexity through dimensional optimization
Data Source
Figure 1~3
Figure 4
Figure 5
AI summary
Routing device (1) comprising a routing table (10), the routing table comprising a set of entries, each entry comprising: a content name attribute containing a content name value identifying a content, a faces attribute containing a faces value identifying a set of devices storing data related to the content name value, and, a mask type attribute containing a mask type value identifying a type of mask to be used for performing a routing table lookup, the routing device (1) being configured to perform a routing table (10) lookup, the routing table lookup comprising the use of the mask type value of an entry to determine a covering relation between the content name value of the said entry and a content name value to be searched, the routing device being further configured to update the routing table depending on the determined covering relation.