Dynamic Namespace Configuration Protocol for Content-Centric Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Content-Centric Networks (CCNs) lack an automated mechanism for initial device configuration and namespace setup, relying on manual processes which are inefficient and inadequate for dynamic network environments.
Innovation Solution
The implementation of a Dynamic Namespace Configuration Protocol (DNCP) that allows devices to broadcast an interest message with a predetermined name prefix, triggering a response from a DNCP service that provides necessary configuration information for namespace setup, including forwarding information base entries and service namespaces, ensuring devices can operate correctly within the CCN network.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Manufacturing precision
If manual configuration processes are used for device initialization in CCN networks, then configuration accuracy can be maintained, but network setup time and operational complexity increase significantly
Solution Approach 1:
The system enables devices to automatically configure themselves by broadcasting interest messages and receiving namespace configuration information from DNCP services without requiring manual intervention. The device autonomously processes the received configuration data and applies it to its forwarding information base and service namespaces.
Solution Approach 2:
The DNCP service pre-prepares namespace configuration information including forwarding information base entries and service namespace definitions before devices need them. When a device broadcasts its interest message, the configuration is already available for immediate transmission, eliminating the need for manual configuration steps.
2Extent of automation
If manual configuration processes are used for device initialization in CCN networks, then configuration control can be maintained, but automation level and network efficiency decrease
Solution Approach 1:
The system enables devices to automatically configure themselves by broadcasting interest messages and receiving namespace configuration information from DNCP services without requiring manual intervention. The device autonomously processes the received configuration data and applies it to its forwarding information base and service namespaces.
3Productivity
If manual configuration processes are used for device initialization in CCN networks, then configuration reliability can be maintained, but operational efficiency and scalability are reduced
Solution Approach 1:
The system implements a feedback mechanism where devices broadcast interest messages to discover DNCP services and receive configuration information. The DNCP service responds to these broadcasts with appropriate namespace configuration data, creating a closed-loop feedback system that ensures reliable automatic configuration.
Solution Approach 2:
The DNCP service pre-prepares namespace configuration information including forwarding information base entries and service namespace definitions before devices need them. When a device broadcasts its interest message, the configuration is already available for immediate transmission, eliminating the need for manual configuration steps.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
One embodiment of the present invention provides a system for automatic configuration of a computing device in a content-centric network (CCN). During operation, the system sends, by the computing device on at least one of the computing device's faces, an interest in configuration information. The interest has a predetermined name prefix. The system then receives a content object in response to the interest. The content object includes at least a default name prefix, to which the computing device can send other interests. The system further configures the computing device based on the received content object.