LLDP Topology Propagation via TLV Fields

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Network management devices face impracticalities in obtaining network topology information from intermediate devices, especially as the number of intermediate devices increases, leading to delays in updating connections and visualization, as they need to be directly connected to each device.

Innovation Solution

Implementing a communications protocol that uses mandatory and configurable Type-Length-Value (TLV) fields in LLDP messages to propagate network topology information, allowing devices to store and transmit information without requiring direct connections to all intermediate devices, using optional TLV fields for additional topology data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If network management devices directly connect to each intermediate device to obtain topology information, then the reliability of topology data is improved, but the device complexity and scalability deteriorate as the number of intermediate devices increases

Engineering Contradiction:

Improvetopology information accuracyVSAvoidconnection requirements

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces LLDP protocol messages as an intermediary mechanism that carries topology information through the network. Instead of direct connections, intermediate devices forward LLDP messages containing topology data, allowing the network management device to obtain accurate topology information without direct physical connections to all intermediate devices.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The LLDP protocol serves multiple functions: it enables topology discovery, device identification, and connection mapping simultaneously. The protocol messages contain standardized fields that can be universally processed by any LLDP-compliant device, eliminating the need for device-specific connection requirements.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Loss of information

If network management devices directly connect to all intermediate devices, then complete topology information is obtained, but the loss of time increases due to delays in updating connections

Engineering Contradiction:

Improvetopology information completenessVSAvoidtopology update delay

Core Design Contradiction:

Loss of informationVSLoss of time

Solution Approach 1:

The LLDP protocol performs preliminary topology discovery by having intermediate devices pre-populate their LLDP message buffers with topology information before queries are made. This preliminary action allows the network management device to receive complete topology data without experiencing delays from real-time connection establishment.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent implements continuous LLDP message transmission and forwarding, where topology information flows continuously through the network rather than being requested intermittently. This continuous action ensures that the network management device receives up-to-date topology information without delays, maintaining both completeness and timeliness.

Inventive Principle:

Principle #20Continuity of useful action

3Reliability

If mandatory TLV fields are used for topology information, then the reliability of core topology data is improved, but the adaptability deteriorates when additional topology details are needed

Engineering Contradiction:

Improvetopology data consistencyVSAvoidtopology information flexibility

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent segments topology information into mandatory TLV fields for core required data and optional TLV fields for additional details. This segmentation allows the protocol to maintain reliable transmission of essential topology information while providing flexibility to include supplementary data when needed, resolving the contradiction between consistency and adaptability.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The LLDP message structure dynamically adapts its content based on network needs. While mandatory fields ensure consistent core information, optional fields can be dynamically included or excluded depending on the specific topology discovery requirements, providing both reliability and versatility.

Inventive Principle:

Principle #15Dynamics

Data Source

PatentUS10567230B1Topology information for networks

Publication Date: 2020.02.18 JUNIPER NETWORKS INC

AI summary

A device may receive a first network topology message from a network device. The first network topology message may include first network topology information associated with the network device in a first set of fields of the first network topology message. The device may generate a second network topology message. The second network topology message may include second network topology information associated with the device in a first set of fields of the second network topology message. The first set of fields of the second network topology message may correspond to the first set of fields of the first network topology message. The second network topology message may include the first network topology information associated with the network device in a second set of fields of the second network topology message. The device may provide the second network topology message.