Dynamic Spanning Tree Protocol for Traffic Adaptation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current spanning tree protocols, such as STP, RSTP, MSTP, and AMSTP, face challenges in dynamically adjusting network topology in response to changes in network hardware, traffic patterns, and resource availability without link failures, leading to suboptimal traffic paths and inefficient bandwidth utilization.

Innovation Solution

The implementation of a dynamic spanning tree protocol that allows for real-time reconfiguration based on events such as changes in traffic patterns, hardware capabilities, and resource availability, using mechanisms like Layer 2 realignment and dynamic traffic mapping to select optimal spanning tree instances and root bridges, facilitated by protocols like Generic Instance Registration Protocol (GIRP) for efficient communication and reconfiguration.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional spanning tree protocols (STP, RSTP, MSTP, AMSTP) are used, then network topology stability is maintained, but the network cannot dynamically adapt to traffic pattern changes and hardware capability variations, resulting in suboptimal traffic paths

Engineering Contradiction:
Improvedynamic adaptation to traffic patternsVSAvoidprotocol complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements dynamic spanning tree instances that can be created, modified, and deleted based on real-time traffic patterns and network conditions. Unlike traditional static spanning tree configurations, the system continuously monitors traffic characteristics and automatically adjusts the spanning tree topology to optimize traffic flow, enabling the network to adapt dynamically without manual intervention

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes spanning tree parameters (such as root bridge selection, path costs, and instance configurations) based on monitored traffic patterns and network conditions. By dynamically modifying these parameters in response to changing network states, the system achieves adaptability while maintaining protocol compatibility with existing spanning tree implementations

Inventive Principle:
Principle #35Parameter changes

2Productivity

If static spanning tree configurations are used, then network stability is maintained, but bandwidth utilization is inefficient due to unused paths

Engineering Contradiction:
Improvebandwidth utilizationVSAvoidnetwork stability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent segments the network into multiple dynamic spanning tree instances, each optimized for specific traffic patterns or network conditions. This segmentation allows different portions of the network to utilize different paths simultaneously, increasing overall bandwidth utilization while maintaining stability through controlled instance management and failure isolation

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system dynamically creates and activates additional spanning tree instances when traffic patterns indicate underutilized paths. By continuously monitoring network usage and automatically provisioning new instances as needed, the system maximizes bandwidth utilization while maintaining network stability through controlled dynamic adjustment

Inventive Principle:
Principle #15Dynamics

3Productivity

If multiple spanning tree instances are configured manually, then load balancing can be achieved, but configuration complexity and administrative overhead increase significantly

Engineering Contradiction:
Improveload balancing efficiencyVSAvoidconfiguration simplicity
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The patent implements self-service spanning tree management where the system automatically monitors traffic patterns, identifies load balancing opportunities, creates appropriate spanning tree instances, and configures them without manual intervention. The system serves itself by continuously optimizing the spanning tree topology based on observed network conditions, eliminating the need for manual configuration while maintaining effective load balancing

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system employs feedback mechanisms where traffic monitoring data is continuously collected and used to automatically adjust spanning tree configurations. By implementing closed-loop control where the system responds to observed traffic patterns by dynamically creating and modifying spanning tree instances, the system achieves automated load balancing that adapts to changing conditions without administrative overhead

Inventive Principle:
Principle #23Feedback

4Loss of time

If rapid spanning tree convergence is implemented, then recovery time after link failure is reduced, but network stability during convergence may be compromised

Engineering Contradiction:
Improveconvergence timeVSAvoidnetwork topology stability
Core Design Contradiction:
Loss of timeVSStability of the object's composition

Solution Approach 1:

The patent implements preliminary action by pre-establishing multiple spanning tree instances with different topologies before failures occur. When a link failure is detected, the system can immediately switch to a pre-configured alternative instance without requiring time-consuming recalculation, thus achieving rapid convergence while maintaining topology stability through pre-planned failure paths

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS7760668B1Self-reconfiguring spanning tree
Publication Date: 2010.07.20 DELL MARKETING CORP
  • US7760668B1 patent drawing
  • US7760668B1 patent drawing
  • US7760668B1 patent drawing

AI summary

A dynamic multiple spanning tree protocol is described. In at least one embodiment, this protocol allows for the dynamic creation and destruction of mappings between traffic attributes and spanning tree instances with the spanning tree region. These mappings are determined based on the observation of events in the spanning tree, such as the appearance of a significant traffic stream, not mapped to any spanning tree instance, at an edge port of the region. Other embodiments are also described and claimed.