Unified Data Bus Adapters for Heterogeneous Core Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Multi-core processor systems face design inflexibility, scalability issues, and compatibility problems due to the use of different core technologies, leading to inefficiencies and errors in data bus design, which limits performance gain and requires custom designs for each system.

Innovation Solution

A computationally-networked unified data bus architecture that uses data bus adapters to encapsulate, translate, and interpret data between processing domains, allowing for integration of heterogeneous and hybrid cores, and enabling real-time reconfiguration and virtualization, thereby facilitating flexible and efficient data communication across multiple processing domains.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If conventional custom data bus design is used for each multi-core system, then design flexibility is improved, but design time and error rate increase

Engineering Contradiction:
Improvedesign flexibilityVSAvoiddesign time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent introduces a unified data bus as an intermediary component that standardizes communication between heterogeneous processing domains. This mediator handles the complexity of interfacing different core technologies, allowing custom design flexibility while reducing actual design time through standardized protocols and automated integration processes.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The unified data bus provides universal communication capabilities that work across multiple heterogeneous processing domains simultaneously. This multi-functional approach allows a single standardized interface to serve diverse core technologies, eliminating the need for separate custom designs for each system while maintaining adaptability.

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

2Adaptability or versatility

If heterogeneous cores are integrated in multi-core systems, then functional versatility is improved, but compatibility and efficiency problems worsen

Engineering Contradiction:
Improvefunctional versatilityVSAvoidcompatibility
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The unified data bus acts as a mediator that translates and adapts communication protocols between heterogeneous cores. This intermediary layer handles compatibility issues automatically, allowing diverse functional capabilities to coexist reliably through standardized interfacing and protocol conversion.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of manufacture

If conventional direct-computation mode is used for core collaboration, then implementation simplicity is improved, but performance gain is reduced

Engineering Contradiction:
Improveimplementation simplicityVSAvoidperformance gain
Core Design Contradiction:
Ease of manufactureVSProductivity

Solution Approach 1:

The unified data bus enables dynamic collaboration modes that go beyond conventional direct-computation approaches. It supports adaptive communication patterns, data sharing, and coordinated operations that can dynamically adjust to workload requirements, thereby improving performance while maintaining implementation simplicity through standardized interfaces.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS8751720B2Computationally-networked unified data bus
Publication Date: 2014.06.10 SDEP CORP
  • US8751720B2 patent drawing
  • US8751720B2 patent drawing
  • US8751720B2 patent drawing

AI summary

Embodiments of the present invention provide a computationally-networked unified data bus for a multi-processing domain architecture. Specifically, in a typical embodiment, a unified data bus is provided. A first data bus adapter (e.g., a node) is coupled to the unified data bus (e.g., a link), and a first processing domain is coupled to the first data bus adapter. In general, the first data bus adapter encapsulates, translates, and interprets data communicated between the unified data bus and the first processing domain. In addition, a second data bus adapter (e.g., a node) is coupled to the unified data bus and a second processing domain is coupled to the second data bus adapter. Similar to the first data bus adapter, the second data bus adapter encapsulates, translates, and interprets data communicated between the unified data bus and the second processing domain. Under these embodiments, the first processing domain and the second processing domain can each comprise at least one element selected from a group consisting of: memory input/outputs (I/Os), cache, heterogeneous data buses, and processors. Moreover, the first processing domain and the second processing domain can be selected from a group consisting of a heterogeneous processing domain and a hybrid processing domain.