VLAN Spanning Tree Reconfiguration Without New Regions

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing network configurations employing spanning trees face challenges in reconfiguration without forming new regions, leading to undesirable situations like endless communication loops and broadcast floods, and existing methods may require the formation of new regions during VLAN/instance table changes.

Innovation Solution

A method that allows network devices to receive and process reconfigurations of VLAN/spanning tree tables by generating new identifiers and lists of digests associated with network regions, enabling reconfiguration without creating new regions by using a data unit with an indication for network devices to determine the region based on information other than the primary identifier.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a reconfiguration is made to a VLAN/spanning tree table, then the network configuration can be updated, but new regions may be formed causing communication loops and broadcast floods

Engineering Contradiction:
Improvenetwork reconfiguration capabilityVSAvoidnetwork stability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent applies preliminary action by pre-calculating and storing multiple alternative spanning tree configurations (first spanning tree, second spanning tree, etc.) before any reconfiguration is needed. When a reconfiguration event occurs, the system can immediately switch to a pre-computed alternative configuration without forming new regions, thus maintaining network stability while enabling adaptability.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system prepares backup spanning tree configurations in advance as a cushion against potential reconfiguration needs. These pre-computed alternative configurations act as a safety buffer that prevents harmful effects (communication loops, broadcast floods) from occurring when network changes are necessary.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

2Ease of operation

If network devices use primary identifier to determine region, then region identification is straightforward, but reconfiguration cannot occur without forming new regions

Engineering Contradiction:
Improveregion determination simplicityVSAvoidreconfiguration flexibility
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent introduces an intermediary mechanism (alternative region identification methods) that mediates between the simplicity of primary identifier-based region determination and the flexibility needed for reconfiguration. Network devices can use the primary identifier for normal operations but switch to alternative identification methods (such as using alternative spanning tree configurations) when reconfiguration is needed, allowing both simplicity and flexibility to coexist.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system dynamically switches between different region determination approaches. During normal operation, devices use the primary identifier for simple region determination. When reconfiguration is required, the system dynamically transitions to using alternative spanning tree configurations for region identification, enabling flexible adaptation while maintaining operational simplicity when applicable.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS9178762B2Configuring networks including spanning trees
Publication Date: 2015.11.03 JUNIPER NETWORKS INC
  • US9178762B2 patent drawing
  • US9178762B2 patent drawing
  • US9178762B2 patent drawing

AI summary

A method may include receiving a reconfiguration to a first Virtual Local Area Network (VLAN)/spanning tree table, where the first VLAN/spanning tree table has a first identifier and is associated with a region of a network; updating the first VLAN/spanning tree table to generate a second VLAN/spanning tree table based on the reconfiguration; determining a second identifier of the second VLAN/spanning tree table; and generating a list of identifiers associated with the region of the network, the list including the first identifier and the second identifier.