Anonymous Identifier Routing for Stateless CCN
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Content Centric Networks (CCN) face challenges with large forwarding information bases (FIB) and pending interest tables (PIT) that lead to increased lookup times and vulnerability to Interest-flooding attacks, as they rely on location-based addressing and store per-Interest forwarding state, which is inefficient and insecure.
Innovation Solution
Implementing a gateway router that uses anonymous identifiers (AIDs) to establish name-independent unicast and multicast routes, allowing routers to forward Interests and Content Objects without storing per-Interest forwarding state, and using a data-answer routing table (DART) to manage AIDs, reducing the size of routing tables and enhancing security by masking client information.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If CCN nodes use traditional FIB and PIT to map name prefixes to neighbors, then content routing functionality is achieved, but the FIB becomes substantially large and lookup times increase
Solution Approach 1:
The patent segments the traditional monolithic FIB into a hierarchical structure with a global FIB at core routers and local FIBs at edge routers. The global FIB stores only aggregate routing information for content prefixes, while local FIBs store mappings for locally cached content. This segmentation reduces the size of FIBs at individual nodes and distributes the lookup burden across multiple levels, thereby improving lookup time while managing FIB size.
Solution Approach 2:
The patent introduces a new dimensional approach by adding a hierarchical level to the traditional flat FIB structure. Instead of a single-level mapping from content prefix to neighbor, the system creates a two-dimensional hierarchy: global FIB (content prefix to anchor router) and local FIB (content prefix to local neighbor). This dimensional change allows the system to manage large routing tables more efficiently and perform lookups faster by checking local FIB first before querying global FIB.
2Reliability
If CCN nodes store per-Interest forwarding state in PIT, then Interest forwarding is enabled, but the PIT size increases proportionally to pending Interests and nodes become vulnerable to Interest-flooding attacks
Solution Approach 1:
The patent extracts the per-Interest forwarding state from the traditional PIT and replaces it with a new Interest-waiting table (IWT) that stores only aggregate information about pending Interests grouped by content prefix. Instead of maintaining individual entries for each pending Interest in the PIT, the system extracts the essential forwarding information and stores it in a compact IWT structure, significantly reducing the state storage requirements and making the system more resistant to Interest-flooding attacks.
Solution Approach 2:
The patent applies local quality by making the IWT size dependent on the number of distinct content prefixes rather than the number of pending Interests. This means that even if there are many pending Interests for the same content prefix, the IWT stores only one aggregate entry per prefix. This local optimization at the prefix level reduces the overall table size and improves security against flooding attacks while maintaining the necessary forwarding functionality.
3Adaptability or versatility
If CCN uses location-based addressing like IP, then routing to specific organization servers is enabled, but content can only be received from addresses associated with physical locations
Solution Approach 1:
The patent implements universality by designing a content-centric addressing scheme where content identifiers (CIDs) serve multiple functions: they uniquely identify content regardless of location, enable routing to any node caching the content, and work across different network domains. The CID structure incorporates both content-specific identifiers and routing information, allowing a single addressing mechanism to handle both content identification and location-independent routing, thereby achieving location-independent content access without proportionally increasing complexity.
Data Source
AI summary
A gateway router can receive an Interest that includes a location-independent name for a data collection. If the Interest does not include an Anchor Identifier, the gateway router can perform a lookup operation in a name-prefix forwarding-information base (NP-FIB) to select an Anchor Identifier for a target anchor node, and to select an interface for forwarding the Interest toward the anchor. The router can update the Interest to include the Anchor Identifier prior to forwarding the Interest via the interface. An edge or core router that receives the Interest can perform a lookup in a routing table using the Interest's Anonymous Identifier (AID) to obtain an interface toward the anchor node and a second AID that is to be used by the next-hop neighbor to process the Interest. The router may then update the Interest to replace the Interest's AID with the second AID prior to forwarding the Interest.


