Push-Pull Information Distribution Protocol for Network Configuration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The complexity of modern computer networks leads to increased operational expenditures due to inefficient configuration and information distribution methods, such as flooding and gossip protocols, which result in wastefulness and delays.

Innovation Solution

A push/pull distribution protocol that separates the notification of new revisions from the content itself, allowing only requesting nodes to receive and transmit the content once, providing a decentralized, resource-efficient, and resilient method for distributing intent information across the network.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If flooding mechanism is used to distribute information to multiple nodes, then information dissemination coverage is improved, but bandwidth usage increases and redundancy occurs

Engineering Contradiction:
Improveinformation dissemination coverageVSAvoidbandwidth usage
Core Design Contradiction:
Loss of informationVSLoss of energy

Solution Approach 1:

Nodes autonomously request information only when they need it, rather than receiving unsolicited broadcasts. Each node serves itself by initiating requests to neighbors that have the information, eliminating redundant receptions and reducing overall bandwidth consumption while ensuring all nodes receive necessary information.

Inventive Principle:
Principle #25Self-service

2Loss of energy

If gossip protocols are used to distribute information, then bandwidth usage is reduced, but transmission delays increase

Engineering Contradiction:
Improvebandwidth usageVSAvoidtransmission delays
Core Design Contradiction:
Loss of energyVSLoss of time

Solution Approach 1:

Nodes pre-establish adjacency lists and identify potential information sources in advance. When information is needed, nodes can immediately query prepared neighbors without delay, combining the efficiency of selective transmission with rapid access times.

Inventive Principle:
Principle #10Preliminary action

3Ease of operation

If centralized server configuration is used, then configuration control is improved, but device complexity and operational expenditure increase

Engineering Contradiction:
Improveconfiguration controlVSAvoidnetwork management complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

Network nodes autonomously configure themselves by requesting information from neighbors and automatically processing the received data. This eliminates the need for centralized configuration servers and complex manual management, while nodes maintain proper configuration through self-directed information gathering and processing.

Inventive Principle:
Principle #25Self-service

4Speed

If push model is used for information distribution, then information delivery speed is improved, but redundant transmissions occur

Engineering Contradiction:
Improveinformation delivery speedVSAvoidtransmission redundancy
Core Design Contradiction:
SpeedVSLoss of energy

Solution Approach 1:

Version number metadata acts as an intermediary mechanism that enables nodes to quickly determine whether they need to receive information. By comparing version numbers before full information transfer, nodes avoid redundant receptions while maintaining fast delivery speeds for necessary updates.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS9819548B2Shared information distribution in a computer network
Publication Date: 2017.11.14 CISCO TECHNOLOGY INC
  • US9819548B2 patent drawing
  • US9819548B2 patent drawing
  • US9819548B2 patent drawing

AI summary

In one implementation, a protocol for dissemination of information, such as configuration information, in a computer network is provided. The dissemination of the payload or content is separated from the dissemination of the fact that a new revision of that payload or content exists. The availability of a new revision of the payload or content is signaled prior to the transfer. Only nodes receiving the notice of existence of the new revision and requesting the new revision receive the payload or content. While the payload or content revision notifications potentially arrive at a receiving node from many different neighbors, the payload or content is only requested once by the receiving node and transmitted once over links between neighbors. This scheme may result in low end-to-end delays and in resiliency.