Multi-Channel Interconnect Fabric for SoC IP Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The integration of diverse intellectual property (IP) blocks into a single system-on-chip (SoC) is hindered by the complexity of accommodating different interface and signaling requirements, leading to slow design emergence and limited reuse of IP blocks due to the lack of standardized interconnect protocols that support multiple channels and attributes for channel mapping.

Innovation Solution

The implementation of a standardized interconnect protocol, such as the Integrated On-Chip System Fabric (IOSF) specification, which provides multiple channels with dedicated resources, allowing for flexible channel mapping based on transaction attributes like traffic class, requester ID, and tags, enabling efficient reuse of IP agents across various systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If IP blocks are integrated into a single SoC to combine multiple functionalities, then the device functionality and integration level are improved, but the design complexity increases due to varying interface and signaling requirements of different IP blocks

Engineering Contradiction:
Improvedevice functionalityVSAvoiddesign complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The interface is segmented into multiple independent channels, each capable of handling different types of transactions. This allows different IP blocks to communicate through standardized channel interfaces rather than requiring custom point-to-point connections, reducing the complexity of integrating diverse IP blocks into an SoC.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A universal interconnect fabric is implemented that can handle multiple types of transactions (memory reads, memory writes, I/O operations, configuration cycles) through a single standardized interface. This universal interface accommodates various IP blocks with different requirements without requiring separate dedicated interfaces for each block type.

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

2Adaptability or versatility

If IP blocks are re-designed to accommodate specific interface requirements of each SoC, then the interface compatibility is improved, but the design reuse and development time are worsened

Engineering Contradiction:
Improveinterface compatibilityVSAvoiddesign reuse
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent implements a universal interface standard that allows IP blocks to maintain their original design characteristics while communicating through a common fabric. IP blocks can be designed once with standardized channel interfaces and reused across multiple SoC designs without re-design, improving both interface compatibility and design reuse.

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

Solution Approach 2:

The interface supports configurable parameters such as channel width, timing characteristics, and transaction types that can be adjusted to match different IP block requirements. This parameter configurability allows a single IP block design to interface with various SoC configurations without modification.

Inventive Principle:
Principle #35Parameter changes

3Adaptability or versatility

If a single interface supports multiple channels with independent data flows, then the data flow independence and quality of service are improved, but the interface complexity increases

Engineering Contradiction:
Improvedata flow independenceVSAvoidinterface complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The interface is divided into multiple independent channels, each with its own data path and control logic. This segmentation allows different channels to handle different types of traffic independently, providing data flow independence and quality of service guarantees while maintaining a relatively simple overall interface structure through modular design.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS9489329B2Supporting multiple channels of a single interface
Publication Date: 2016.11.08 INTEL CORP
  • US9489329B2 patent drawing
  • US9489329B2 patent drawing
  • US9489329B2 patent drawing

AI summary

In one embodiment, the present invention includes a method for receiving a request for a transaction from a first agent in a fabric and obtaining an address, a requester identifier, a tag, and a traffic class of the transaction, and determining a channel of a target agent to receive the transaction based on at least two of the address, the requester identifier, the tag, and the traffic class. Based on this channel determination, the transaction can be sent to the channel of the target agent. Other embodiments are described and claimed.