CBUS Secondary Network for NoC Event Transfer

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current network-on-chip (NoC) systems face challenges in transferring configuration, management, debug information, and asynchronous events efficiently, particularly due to fixed topologies, high overhead, and lack of scalability, which limits their ability to dynamically adapt to changing network requirements.

Innovation Solution

A secondary network, referred to as the configuration bus network (CBUS), is introduced to facilitate the transfer of these events between NoC elements and external interfaces, utilizing a single-master topology with broadcast-based packet traversal, dynamic discovery and stubbing mechanisms, and encapsulation of wired events within data packets to reduce the need for physical wires and support scalability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional NOC systems use fixed topology and numerous physical wires for event transfer, then reliable communication is achieved, but device complexity and area overhead increase significantly

Engineering Contradiction:
Improvecommunication reliabilityVSAvoidwire complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent replaces physical wire-based event transfer mechanisms with a software-defined packet switching system. Event transfer information is encapsulated in packets that traverse the NOC using virtual channels, eliminating the need for dedicated physical wires for each event type between nodes. This substitution of mechanical/wire-based systems with information-based packet switching reduces device complexity while maintaining communication reliability through protocol-level guarantees.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The patent introduces event transfer information packets as intermediaries to carry event data between NOC nodes. Instead of direct wire connections, events are packaged into standardized packets that include event type, source node, destination node, and payload information. These packets traverse through the NOC fabric using existing routing infrastructure, acting as mediators that enable flexible event transfer without requiring dedicated physical paths.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Speed

If dedicated wires are used for event transfer between NOC elements, then real-time communication is achieved, but area overhead and scalability are limited

Engineering Contradiction:
Improveevent transfer speedVSAvoidwire area
Core Design Contradiction:
SpeedVSArea of stationary object

Solution Approach 1:

The patent enables the NOC fabric to serve multiple functions simultaneously: data packet routing and event transfer. The same physical infrastructure (switches, links, and routing logic) that handles regular data traffic is also used for event transfer packets. This multi-functionality eliminates the need for separate dedicated wire infrastructure for events, reducing area overhead while maintaining real-time transfer capabilities through priority handling and quality of service mechanisms.

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

Solution Approach 2:

The patent merges the event transfer function with the existing data communication infrastructure. Event transfer packets are combined with regular data traffic flows, sharing the same physical links and switching resources. This consolidation eliminates redundant wiring while preserving real-time performance through protocol features such as priority queuing and reserved bandwidth allocation for event packets.

Inventive Principle:
Principle #5Merging (Combining)

3Stability of the object's composition

If fixed parameters are used in NOC configuration, then system stability is maintained, but adaptability to changing network requirements is reduced

Engineering Contradiction:
Improvesystem stabilityVSAvoidnetwork adaptability
Core Design Contradiction:
Stability of the object's compositionVSAdaptability or versatility

Solution Approach 1:

The patent introduces dynamic configurability to the NOC system through software-defined parameters. Network topology, routing tables, quality of service policies, and resource allocation can be modified at runtime without hardware changes. Configuration parameters are stored in programmable memory and can be updated dynamically to adapt to changing network requirements, while the underlying physical infrastructure remains stable. This separation of stable hardware and flexible software configuration enables both stability and adaptability.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent enables dynamic modification of network parameters such as routing tables, bandwidth allocation, priority levels, and event transfer policies. These parameters can be adjusted in response to changing workload conditions, topology changes, or performance requirements. The system maintains stability by keeping the physical infrastructure fixed while achieving adaptability through software-controlled parameter changes that can be applied without hardware reconfiguration.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS12149407B2System and method for transferring configuration, management, debug information and asynchronous events between network-on-chip (NOC) and external interface
Publication Date: 2024.11.19 SKYECHIP BERHAD
  • US12149407B2 patent drawing
  • US12149407B2 patent drawing
  • US12149407B2 patent drawing

AI summary

The present invention relates to a system and method for transferring configuration, management, debug information and asynchronous events between network-on-chip (NOC) and external interface, wherein said system, referred to as secondary network (101), comprises of a plurality of configuration bus (CBUS) network elements such as a master network element (103) and a plurality of basic network elements (105); whereby said secondary network (101) is capable to convey events such as request, acknowledge assertions or de-assertions, saving the need for numerous wires connecting between main NOC elements such as nodes or routers.