Replicated Service Architecture for Multiprocessor Reliability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Multiprocessor systems face challenges in maintaining service availability when one or more nodes fail, as they typically rely on a master processor for request handling and lack redundancy in service execution.

Innovation Solution

A multiprocessor system architecture with replicated services across multiple nodes connected via mesh interconnects, allowing each node to communicate with every other node and operate independently, ensuring continued service availability even if individual nodes fail.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a multiprocessor system uses a master processor architecture for request handling, then the system structure is simplified and easier to control, but the system lacks redundancy and service availability when the master processor or any node fails

Engineering Contradiction:
Improveservice availabilityVSAvoidsystem architecture complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system divides the multiprocessor architecture into independent nodes, each capable of running replicated services autonomously. This segmentation eliminates the single master processor bottleneck and enables any node to handle service requests independently, thereby improving reliability without requiring a complex centralized control mechanism.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements replicated services across multiple nodes by creating copies of service instances on different processors. When one node fails, the replicated service copies on other nodes continue to operate, ensuring service availability. This copying approach provides redundancy without significantly increasing overall system complexity.

Inventive Principle:
Principle #26Copying

2Reliability

If the system implements replicated services across multiple nodes with mesh interconnects, then service redundancy and fault tolerance are improved, but the network routing complexity increases

Engineering Contradiction:
Improvefault toleranceVSAvoidnetwork routing complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

Each node in the mesh interconnect is designed with universal routing capabilities, allowing any node to route traffic to any other node directly. This multi-functional routing approach simplifies the overall network architecture by eliminating the need for specialized routing nodes or complex hierarchical routing logic, while still providing robust fault tolerance through multiple communication paths.

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

3Reliability

If the system operates without a master node using replicated services, then resilience against node failures is improved, but the ease of operation and system management becomes more difficult

Engineering Contradiction:
ImproveresilienceVSAvoidsystem management
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The replicated service architecture enables self-service operation where each node independently manages its own service instances and can autonomously handle service requests. Nodes can self-organize and self-manage without requiring a master node for coordination, simplifying operational management while maintaining high resilience through distributed autonomy.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS7783786B1Replicated service architecture
Publication Date: 2010.08.24 ORACLE AMERICAN INC
  • US7783786B1 patent drawing
  • US7783786B1 patent drawing
  • US7783786B1 patent drawing

AI summary

A system comprising a first node and a second node located in a single multiprocessor system, the first node including a first router and a first replicated service executing on a first operating system, the second node including a second router and a second replicated service executing on a second operating system, and a mesh interconnect connecting the first node to the second node using the first router and the second router.