# US 2015/0103822 A1 · Noc interface protocol adaptive to varied host interface protocols

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2015/0103822 A1
- Document ID: US20150103822A1
- Status: Published application
- Kind: A1
- Application number: 14/054,667
- Filed: 2013-10-15
- Published: 2015-04-16
- Earliest claimed: 2013-10-15
- Assignees: NetSpeed Systems
- Applicants: Netspeed Systems
- Inventors: Jaya GIANCHANDANI; Sailesh KUMAR; Eric NORIGE; Joe ROWLANDS; Rajesh CHOPRA
- Web page: https://patentgrep.com/patent/US20150103822A1

## CPC

- H04L 69/08: Protocols for interworking; Protocol conversion
- G06F 15/7825: {Globally asynchronous, locally synchronous, e.g. network on chip}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Systems and methods described herein are directed to solutions for Network on Chip (NoC) interconnects that support a variety of different component protocols each having different sets of data and/or metadata even after the NoC is designed and finalized. Example implementations include, automatically changing format of packets received from an originating SoC component by an originating bridge based on a NoC interface protocol and then transmitting the packet across the NoC interconnect to a destination bridge. The format may again be changed based on the protocol of the destination SoC component. The proposed protocol can be configured to map various transactions presented to it, be they packets belonging to the physical, data link layer, network layer or transport layer. As part of the mapping process, virtual channels for latency or deadlock avoidance may be created and may be maintained for the entire life of the packet within the NoC.

## Claims

### Claim 1

A method for communicating data between System on Chip (SoC) component through an Network on Chip (NoC) interconnect, the method comprising:
converting a format of the data from a source SoC interface protocol format to a NoC interface protocol format;
converting the format of the data from the NoC interface protocol format to a destination SoC interface protocol format;
sending the data in the destination SoC interface protocol format to the SoC component.

### Claim 2 (depends on 1)

The method of claim 1, wherein the converting the format of the data from the source SoC interface protocol format to the NoC interface protocol format is conducted by an originating bridge.

### Claim 3 (depends on 2)

The method of claim 2, wherein the data comprises one or more flits and the originating bridge incorporates one or more of a start of packet (SOP), an end of packet (EOP), and a valid packet field in the one or more flits.

### Claim 4 (depends on 2)

The method of claim 2, wherein the data has one or more flits and the originating bridge incorporates one or more of a destination node identifier, a destination interface identifier, and a virtual channel identifier in at least one flit of the data.

### Claim 5 (depends on 4)

The method of claim 4, wherein the at least one flit is a first flit of the data.

### Claim 6 (depends on 1)

The method of claim 1, wherein the converting the data from the NoC interface protocol format to the destination SoC interface protocol format is conducted by a destination bridge.

### Claim 7 (depends on 6)

The method of claim 6, further comprising removing one or more of a destination node identifier, a destination interface identifier, and a virtual channel from the data before sending the data to the destination SoC component.

### Claim 8 (depends on 1)

The method of claim 1, wherein the data is unpacketized, and wherein the unpacketized data is packetized based on the NoC interface protocol format before conversion to the destination SoC interface protocol format.

### Claim 9 (depends on 1)

The method of claim 1, wherein the source SoC interface protocol format and the destination SoC interface protocol format have different parameters comprising at least one of size, width, sequence, and length.

### Claim 10

A computer readable storage medium storing instructions for communicating data between System on Chip (SoC) component through an Network on Chip (NoC) interconnect, the instructions comprising:
converting a format of the data from a source SoC interface protocol format to a NoC interface protocol format;
converting the format of the data from the NoC interface protocol format to a destination SoC interface protocol format; and
sending the data in the destination SoC interface protocol format to the SoC component.

### Claim 11 (depends on 10)

The computer readable storage medium of claim 10, wherein the instructions further comprise utilizing an originating bridge for converting the format of the data from the source SoC interface protocol format to the NoC interface protocol format.

### Claim 12 (depends on 11)

The computer readable storage medium of claim 11, wherein the data comprises one or more flits and wherein the utilizing the originating bridge comprises incorporating one or more of a start of packet (SOP), an end of packet (EOP), and a valid packet field in the one or more flits.

### Claim 13 (depends on 11)

The computer readable storage medium of claim 11, wherein the data has one or more flits and wherein the utilizing the originating bridge comprises incorporating one or more of a destination node identifier, a destination interface identifier, and a virtual channel identifier in at least one flit of the data.

### Claim 14 (depends on 13)

The computer readable storage medium of claim 13, wherein the at least one flit is a first flit of the data.

### Claim 15 (depends on 10)

The computer readable storage medium of claim 10, wherein the instructions further comprise utilizing a destination bridge for converting the data from the NoC interface protocol format to the destination SoC interface protocol format.

### Claim 16 (depends on 15)

The computer readable storage medium of claim 15, wherein the instructions further comprise removing one or more of a destination node identifier, a destination interface identifier, and a virtual channel from the data before sending the data to the destination SoC component.

### Claim 17 (depends on 10)

The computer readable storage medium of claim 10, wherein the data is unpacketized, and wherein the instructions further comprise packetizing the unpacketized data based on the NoC interface protocol format before conversion to the destination SoC interface protocol format.

### Claim 18 (depends on 10)

The computer readable storage medium of claim 10, wherein the source SoC interface protocol format and the destination SoC interface protocol format have different parameters comprising at least one of size, width, sequence, and length.
