CCN Service Discovery Using Exact Name Manifest Synchronization

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current Content-Centric Network (CCN) synchronization protocols rely on longest-prefix matching, which is inadequate for service discovery and synchronization using exact name matches, limiting their effectiveness in evolving network architectures.

Innovation Solution

A system that facilitates synchronization of manifests between nodes in a CCN using exact match names, where each node maintains a manifest with a unique root hash value, allowing for precise identification and synchronization of content objects across the network, and enables service discovery by advertising and retrieving manifests based on exact name matches.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If longest-prefix match method is used for content identification, then routing flexibility and content aggregation are improved, but service discovery precision and exact name matching capability deteriorate

Engineering Contradiction:

Improverouting flexibilityVSAvoidservice discovery precision

Core Design Contradiction:

Adaptability or versatilityVSMeasurement precision

Solution Approach 1:

The patent segments the content identification process into two distinct phases: routing phase using prefix matching for flexibility, and service discovery phase using exact name matching for precision. This segmentation allows each phase to use the most appropriate matching method for its specific requirements, resolving the contradiction between routing flexibility and service discovery precision.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent applies different matching quality requirements to different network functions: prefix matching (lower precision) for routing decisions and exact name matching (high precision) for service discovery. This local quality approach allows the system to optimize each function independently, achieving both routing flexibility and service discovery precision simultaneously.

Inventive Principle:

Principle #3Local quality

2Adaptability or versatility

If longest-prefix match synchronization protocol is used, then network compatibility and content aggregation are improved, but service discovery effectiveness and exact name matching capability deteriorate

Engineering Contradiction:

Improvenetwork compatibilityVSAvoidservice discovery effectiveness

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements a dynamic synchronization protocol that adapts its matching behavior based on the synchronization context. For general content synchronization, it uses longest-prefix match to maintain compatibility, while for service discovery synchronization, it switches to exact name matching to ensure effectiveness. This dynamic adaptation resolves the contradiction between network compatibility and service discovery effectiveness.

Inventive Principle:

Principle #15Dynamics

3Measurement precision

If exact name match is used for service discovery, then service discovery precision and data consistency are improved, but routing flexibility and content aggregation capability deteriorate

Engineering Contradiction:

Improveservice discovery precisionVSAvoidrouting flexibility

Core Design Contradiction:

Measurement precisionVSAdaptability or versatility

Solution Approach 1:

The patent segments the network functionality into routing operations (using prefix matching) and service discovery operations (using exact name matching). This segmentation allows exact name matching to be applied only where precision is critical, while prefix matching handles routing flexibility, thus resolving the contradiction between service discovery precision and routing flexibility.

Inventive Principle:

Principle #1Segmentation

4Productivity

If current CCN synchronization protocol is used, then content synchronization is achieved, but service discovery functionality and exact name matching capability deteriorate

Engineering Contradiction:

Improvecontent synchronization efficiencyVSAvoidservice discovery functionality

Core Design Contradiction:

ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent enhances the synchronization protocol to be multi-functional: it can operate in prefix-matching mode for general content synchronization and in exact name-matching mode for service discovery. This universality allows a single protocol to handle both content synchronization and service discovery effectively, resolving the contradiction between synchronization efficiency and service discovery functionality.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentEP2930912B1Service discovery using collection synchronization with exact names

Publication Date: 2021.01.27 CISCO TECHNOLOGY INC

Figure 1
Figure 2
Figure 3

AI summary

One embodiment provides a system that facilitates service discovery based on the synchronization of manifests between devices in a content centric network by using a synchronization protocol based on exact match names. During operation, a local device receives an advertisement corresponding to a remote manifest of a remote device. A manifest represents a collection of service records, and the advertisement includes a service record corresponding to the remote device. The local device updates its local manifest, in response to determining that the local manifest and the remote manifest correspond to a same namespace, by inserting the advertised service record into the local manifest.