Fault Zone Definition for Interconnect Fabric Reliability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current System Area Networks face challenges in reliability and availability due to shared components and dependencies, which can lead to single points of failure, increasing complexity, size, and cost without fully addressing redundancy issues.

Innovation Solution

A fault zone definition mechanism is implemented to identify and group components with common dependencies, creating independent paths by analyzing component dependencies and managing resource interdependencies, allowing for increased reliability and availability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If redundancy is included in the system area network to improve reliability, then system availability is improved, but device complexity and cost increase

Engineering Contradiction:
Improvesystem availabilityVSAvoidcomponent count
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system is segmented into fault zones based on shared dependencies. By dividing the network into independent fault zones, the patent enables targeted redundancy management where each zone can be independently protected, reducing the overall complexity compared to universal redundancy while maintaining reliability through zone-specific fault isolation.

Inventive Principle:
Principle #1Segmentation

2Device complexity

If components are shared between paths to reduce complexity, then device complexity is reduced, but reliability deteriorates due to single points of failure

Engineering Contradiction:
Improvecomponent countVSAvoidpath independence
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The fault zone definition mechanism acts as an intermediary layer between physical components and path routing. It introduces fault zone identifiers that mediate the relationship between shared components and communication paths, enabling the system to track and manage dependencies without increasing physical component count, thus maintaining reliability while controlling complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If component dependencies are analyzed and grouped into fault zones, then reliability is improved through independent paths, but measurement precision requirements increase

Engineering Contradiction:
Improvepath independenceVSAvoiddependency analysis accuracy
Core Design Contradiction:
ReliabilityVSMeasurement precision

Solution Approach 1:

The system performs preliminary action by defining fault zones and assigning identifiers before actual communication paths are established. This advance categorization of components based on their dependency relationships simplifies subsequent path analysis and reduces the precision requirements for real-time dependency measurement, as the heavy lifting of dependency analysis is completed in advance.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS7774642B1Fault zones for interconnect fabrics
Publication Date: 2010.08.10 ORACLE AMERICAN INC
  • US7774642B1 patent drawing
  • US7774642B1 patent drawing
  • US7774642B1 patent drawing

AI summary

A fault zone definition mechanism groups components of an interconnect environment having a common point of dependence into a logical group defining a fault zone for the interconnect environment. The fault zone definition mechanism may be implemented in software, firmware or hardware, or a combination of two or more of software, firmware and hardware. A method for defining a fault zone is also disclosed.