Exact Name Matching for CCN Data Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Content-Centric Network (CCN) synchronization protocols rely on longest-prefix matching, which is inadequate for exact name matching, leading to inefficiencies in synchronizing collections of data between peers on a network.
Innovation Solution
A system that uses exact match names for synchronizing collections by comparing root hash values of manifests to identify differences and updates content objects based on modified times and sequence numbers, facilitating precise synchronization between local and remote nodes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If longest-prefix match method is used for synchronization, then broader content matching is achieved, but exact name matching precision is lost
Solution Approach 1:
The system dynamically adapts the matching strategy based on the synchronization context. During collection synchronization, exact name matching is applied to ensure precision, while the protocol maintains flexibility to handle different synchronization scenarios. The synchronization protocol switches between exact match and prefix match modes depending on whether collections need to be synchronized or new collections discovered.
Solution Approach 2:
The matching parameter is changed from prefix-based to exact match-based for the specific function of collection synchronization. The patent modifies the traditional CCN longest-prefix match behavior by implementing exact name matching for manifest comparisons, while maintaining prefix matching for other CCN operations, thus changing the matching parameter according to the specific task requirements.
2Measurement precision
If exact name matching is implemented for synchronization, then synchronization precision is improved, but protocol compatibility with existing CCN architectures is reduced
Solution Approach 1:
The manifest acts as an intermediary structure that enables exact name matching for synchronization while maintaining compatibility with the broader CCN architecture. The manifest contains hash values and metadata that allow precise comparison of collections without requiring changes to the underlying CCN prefix-matching infrastructure. This intermediary layer resolves the conflict between exact matching requirements and architecture compatibility.
Solution Approach 2:
The synchronization protocol is segmented into distinct phases: manifest advertisement phase using exact name matching, and content object retrieval phase using traditional CCN mechanisms. This segmentation allows exact matching to be applied only where necessary (during synchronization setup) while maintaining compatibility with existing CCN operations for actual content transfer.
3Reliability
If all content objects are synchronized regardless of differences, then completeness is achieved, but network bandwidth and time are wasted
Solution Approach 1:
The protocol applies partial action by comparing only the hash values of content objects in manifests to identify differences, rather than transferring all content objects. Only the minimal necessary content objects that differ between collections are synchronized, avoiding excessive transmission of duplicate data while ensuring completeness of necessary updates.
Solution Approach 2:
The synchronization protocol uses feedback mechanisms where the local node compares its manifest hash with the remote manifest hash, identifies specific differences, and requests only those particular content objects. This feedback-driven approach ensures synchronization completeness while minimizing bandwidth consumption by transmitting only what is actually different.
4Measurement precision
If version information is tracked for all content objects, then update accuracy is improved, but manifest size and processing complexity increase
Solution Approach 1:
The protocol extracts only the essential version identification information (hash values) from content objects and stores them in manifests, rather than tracking complete version histories. This extraction of critical identifying features enables accurate version comparison while keeping manifest structures compact and processing straightforward, avoiding the complexity of full version control systems.
Data Source
AI summary
One embodiment provides a system that facilitates synchronization collections of data between a local and a remote node by using exact match names. During operation, a local node receives an advertisement corresponding to a remote manifest at a remote node. A manifest represents a collection of content objects at a node. In some embodiments, a manifest corresponds to a root hash value that identifies the content objects of the collection. The local node determines that the local manifest and the remote manifest both indicate the same collection of content objects. The local node then determines if the content of the collections are different by comparing the root hash value of the local manifest with the root hash value of the remote manifest. Responsive to determining that the root hash values of the manifests are different, the local node retrieves the remote manifest by sending a request for the remote manifest. The local node determines which content objects identified in the remote manifest are different from the content objects identified in the local manifest. The local node transmits a set of interests for the content objects that are different and receives the requested set of content objects, thereby facilitating synchronization of content objects associated with the manifests at both the local and remote node.