Interest Packet Payload Configuration for NDN Nodes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In information-centric networks, such as Content-Centric Networking (CCN) or Named-Data Networking (NDN), there is a limitation in the amount of information that can be attached to an Interest packet's name, leading to issues like router dropping or mismatched entries in forwarding tables, which complicates content retrieval and network configuration.

Innovation Solution

An Interest-processing network device that includes a payload within the Interest packet, allowing for hierarchical or flat names, and carrying instructions to manipulate resources at network devices, enabling caching, forwarding, and configuration of network nodes, including routers and cache servers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If additional information is attached to an Interest packet's name to provide configuration data to network devices, then the amount of information available for network configuration increases, but the name becomes too large causing routers to drop the Interest packet or fail to match entries in forwarding tables

Engineering Contradiction:
Improveamount of informationVSAvoidpacket delivery reliability
Core Design Contradiction:
Quantity of substanceVSReliability

Solution Approach 1:

The patent segments the Interest packet into two distinct parts: a compact name field that maintains compatibility with existing router PIT and FIB structures, and a separate payload field that carries the additional configuration information. This segmentation allows the name to remain within size limits while the payload provides the necessary configuration data without causing packet drops.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a payload as an intermediary carrier for configuration information. Instead of embedding configuration data directly in the name (which causes size issues), the payload acts as a mediator that transports the configuration data alongside the Interest packet, allowing routers to process both the name for routing purposes and the payload for configuration purposes.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If the Interest packet name is kept at a fixed size to ensure router compatibility, then routing efficiency is maintained, but the ability to carry configuration information is limited

Engineering Contradiction:
Improverouting efficiencyVSAvoidconfiguration capability
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent divides the information-carrying function into two segments: the name segment maintains fixed size for efficient routing and table lookups, while the payload segment provides variable-size configuration data. This segmentation enables both routing efficiency and configuration versatility to coexist without compromising either.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent adds a new dimension (the payload field) to the Interest packet structure. Instead of expanding the name field in one dimension (which causes size problems), the configuration information is placed in a separate payload dimension, allowing the name to remain compact while the system gains enhanced configuration capabilities.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

3Adaptability or versatility

If the Interest packet includes a payload with configuration instructions, then network node configuration capability is enhanced, but the device complexity increases

Engineering Contradiction:
Improveconfiguration capabilityVSAvoidpacket processing complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements self-service by allowing network devices to autonomously process the payload based on their own capabilities and the information contained in the Interest name. Each router or network device independently evaluates whether it should process the configuration payload, reducing the need for complex centralized control and simplifying overall system architecture.

Inventive Principle:
Principle #25Self-service

Data Source

PatentEP2869537B1Using interest messages with payload to configure network nodes in named data networks
Publication Date: 2016.05.04 PALO ALTO RESEARCH CENTER INC
  • EP2869537B1 patent drawingFigure 1
  • EP2869537B1 patent drawingFigure 2A
  • EP2869537B1 patent drawingFigure 3

AI summary

A network device can process a payload in an Interest packet. During operation, the network device can receive an Interest packet that includes a name or a name prefix associated with one or more target entities for the Interest. If the network device determines that the Interest packet includes a payload, the network node can analyze the Interest's name and/or payload to determine an operation to perform for processing the payload. The network device then proceeds to process the payload by performing the determined operation.