Switch Group Software Version Synchronization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing switch systems face challenges in efficiently managing multiple software versions within a switch group, leading to inconsistencies and reduced operational capability due to the need for all switches to have the same software version, which prevents gradual software updates and increases complexity and cost.

Innovation Solution

A switch system that includes a switch group module, a persistent storage module, and a synchronization module, using a portable representation of configuration information to manage updates across switches with different software versions, allowing for type conversion and default value assignment to ensure interoperability and seamless software version updates.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If all switches in a switch group must have the same software version, then interoperability and consistency are ensured, but software updates cannot be performed gradually and system flexibility is reduced

Engineering Contradiction:
ImproveinteroperabilityVSAvoidsoftware update flexibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent segments the switch group into different software version groups, allowing switches with different software versions to coexist. The synchronization module identifies software versions and selectively synchronizes configuration information only to switches that can process it, enabling gradual updates without requiring uniform versions across all switches.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent changes the parameter of software version uniformity from a strict requirement to a flexible condition. By introducing version identification and selective synchronization based on software version capabilities, the system allows configuration updates to proceed dynamically across switches with varying software versions.

Inventive Principle:
Principle #35Parameter changes

2Ease of manufacture

If configuration information is stored in unstructured format in local storage, then storage simplicity is maintained, but management efficiency decreases and runtime structuring is required

Engineering Contradiction:
Improvestorage simplicityVSAvoidconfiguration management efficiency
Core Design Contradiction:
Ease of manufactureVSProductivity

Solution Approach 1:

The patent implements preliminary structuring of configuration information by storing it in a structured format in persistent storage before it is needed. The synchronization module retrieves this pre-structured information and adapts it to different software versions, eliminating the need for runtime structuring and improving management efficiency.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If switch size and capability are increased to meet bandwidth demands, then service capability is improved, but physical space, power consumption, and design complexity increase

Engineering Contradiction:
Improvebandwidth capabilityVSAvoidswitch design complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the switch system into multiple independent member switches that can be scaled individually. Instead of building one large complex switch, the system uses multiple simpler switches that can be added or removed based on bandwidth demands, reducing overall design complexity while maintaining scalability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates a universal switch interface and configuration system that allows different switch models and versions to work together in the same fabric. This multi-functionality enables flexible scaling without requiring specialized hardware for each function, reducing design complexity.

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

4Device complexity

If member switches use the same software version, then operation as a single switch is simplified, but per-port cost increases due to economies of scale

Engineering Contradiction:
Improveswitch operation simplicityVSAvoidper-port cost
Core Design Contradiction:
Device complexityVSEase of manufacture

Solution Approach 1:

The patent segments the software version requirement, allowing different switches to run different software versions while maintaining fabric switch operation. This enables purchasing decisions to be based on cost-effectiveness rather than version uniformity, potentially reducing per-port costs through better economies of scale.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The synchronization module acts as an intermediary that translates and adapts configuration information between different software versions. This mediator enables switches with different versions to operate together, allowing cost optimization without sacrificing operational simplicity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS9628407B2Multiple software versions in a switch group
Publication Date: 2017.04.18 AVAGO TECHNOLOGIES INTERNATIONAL SALES PTE LTD
  • US9628407B2 patent drawing
  • US9628407B2 patent drawing
  • US9628407B2 patent drawing

AI summary

One embodiment of the present invention provides a switch. The switch includes one or more ports, a switch group module, a persistent storage module, and a synchronization module. The switch group module maintains a membership in a switch group. The persistent storage module stores configuration information associated with the switch group in a data structure, which includes one or more columns for attribute values of the configuration information, in a local persistent storage. The synchronization module obtains update information, which includes a first set of attribute values, from a portable representation. The synchronization module identifies a software version of a second switch in the switch group and generates an update instruction to update the first data structure in a persistent storage in the second switch with target update information. The target update information comprises a second set of attribute values updated from the first set of attribute values.