Publisher ID Scoping for Hash Collision Reduction in CCN
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In Content Centric Networks (CCNs), the current system faces challenges in reducing collision probabilities of nameless Content Objects, particularly when multiple publishers replicate their content across various host servers, leading to burdensome forwarding table updates and potential failures in forwarding Interests to all available Content Objects.
Innovation Solution
The introduction of a Publisher ID in Interests allows CCN nodes to match and forward nameless Content Objects based on their hash values, reducing collisions by scoping Content Object Hash values to the publisher, thereby eliminating the need for explicit name prefix advertisement and reducing the burden on forwarding tables.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If host servers store Content Objects for a large number of publishers, then content availability increases, but forwarding table update burden increases
Solution Approach 1:
The patent extracts the publisher identification function from the content name prefix and places it in a separate Publisher ID field. This allows forwarding tables to only store content name prefixes without needing to track which publisher each content belongs to, reducing the forwarding table update burden while maintaining content availability across multiple publishers.
Solution Approach 2:
The patent segments the interest message into distinct components: content name prefix, Publisher ID, and Content Object Hash. This segmentation allows CCN routers to process only the content name prefix for forwarding decisions, while the Publisher ID is used by replica services for content verification, thereby reducing forwarding table complexity.
2Reliability
If CCN routers implement large forwarding tables to forward all Content Objects, then forwarding completeness improves, but device complexity and resource consumption increase
Solution Approach 1:
The patent extracts publisher-specific information from the forwarding decision process. By placing Publisher ID in a separate field not used by CCN routers for forwarding, the system allows routers to maintain smaller forwarding tables that only handle content name prefixes, while publisher identification is handled separately by replica services.
3Ease of manufacture
If nameless Content Objects use only hash values for identification, then object creation simplifies, but collision probability increases
Solution Approach 1:
The patent segments the content identification process into two independent parts: Content Object Hash for object creation and verification, and Publisher ID for object source identification. This segmentation maintains the simplicity of creating nameless content objects while reducing collision probability by adding the Publisher ID as an additional distinguishing factor.
Solution Approach 2:
The Publisher ID acts as an intermediary element that mediates between the simplicity of hash-based identification and the need to reduce collisions. It provides an additional layer of differentiation without complicating the fundamental hash-based object creation process.
Data Source
AI summary
A replica service of a Content Centric Network can host content published by various publishers, without having to explicitly advertise a name prefix associated with these various publishers. Consumers across CCN can generate an Interest that includes a location-independent name associated with a replica service that hosts content for a given publisher, and includes a hash of the desired Content Object. CCN nodes can forward the Interest to the corresponding replica service based on the Interest's name, and the replica service can return a nameless Content Object whose hash matches the Interest's hash value. It may be possible for nameless Content Objects from various publishers to have matching hash values from time to time. CCN nodes can reduce collisions of nameless Content Objects by using a Publisher ID specified in an Interest to find a matching Content Object that was published by a desired publisher.