Limited Functionality Link State Protocol Node for IS-IS Routing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current communications networks face challenges in efficiently managing link state protocol data units (LSPs) within Intermediate System to Intermediate System (IS-IS) routing protocols, particularly in networks requiring reduced processing and maintenance of extensive link state databases, where full functionality nodes maintain all network information, while limited functionality nodes only maintain their own data.

Innovation Solution

A partially-participating link state protocol node is introduced, which stores a local link state database and processes LSPs by sending them without updating the database when received, and sends acknowledgments as necessary, allowing for reduced processing and maintenance, specifically in IEEE 802.1aq Shortest Path Bridging (SPB) networks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If full functionality nodes maintain all network link state information, then complete network visibility and routing accuracy are achieved, but device complexity and processing overhead increase significantly

Engineering Contradiction:
Improverouting accuracyVSAvoidlink state database maintenance
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments network nodes into full functionality nodes that maintain complete link state databases and limited functionality nodes that maintain only their own link state information. This segmentation allows routing accuracy to be maintained through full functionality nodes while reducing device complexity for limited functionality nodes that only store and forward their own LSPs without processing entire network databases.

Inventive Principle:
Principle #1Segmentation

2Loss of information

If limited functionality nodes process and update all received LSPs, then complete link state information is maintained, but processing operations and memory requirements increase

Engineering Contradiction:
Improvelink state information completenessVSAvoidprocessing efficiency
Core Design Contradiction:
Loss of informationVSProductivity

Solution Approach 1:

The patent extracts the link state information maintenance function from limited functionality nodes, requiring them to only store and forward their own LSPs while full functionality nodes extract and maintain the complete network link state database. This extraction allows limited functionality nodes to operate with minimal processing while full functionality nodes handle the information completeness requirement.

Inventive Principle:
Principle #2Taking out (Extraction)

3Device complexity

If limited functionality nodes maintain minimal link state data, then device complexity and processing are reduced, but ability to perform full routing calculations is impaired

Engineering Contradiction:
Improvelink state database sizeVSAvoidrouting protocol functionality
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The patent implements multi-functionality where full functionality nodes serve dual roles as both limited functionality nodes (maintaining their own LSPs) and network-wide information maintainers (maintaining complete link state databases). This universality allows the network to support both simplified nodes with minimal data and comprehensive routing capabilities through the full functionality nodes, resolving the contradiction between reduced complexity and maintained adaptability.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS9372821B2Limited functionality link state protocol node
Publication Date: 2016.06.21 CISCO TECHNOLOGY INC
  • US9372821B2 patent drawing
  • US9372821B2 patent drawing
  • US9372821B2 patent drawing

AI summary

In one embodiment a limited functionality link state protocol node has one or two interfaces configured to send and receive link state protocol packets. In response to receiving, by the partially-participating link state protocol node on a first interface, a particular link state protocol data unit (LSP): sending the particular LSP from a second interface of the partially-participating link state protocol node without updating the local link state database when the second interface is currently participating in the link state protocol distribution; and sending an acknowledgment of the particular LSP from the first interface when the second interface is not currently participating in the link state protocol distribution.