# US 12,184,499 B2 · System and method for editing a network-on-chip (NOC)

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

- Number: US 12,184,499 B2
- Document ID: US12184499B2
- Status: Granted
- Kind: B2
- Application number: 17/942,180
- Filed: 2022-09-12
- Published: 2023-03-30
- Granted: 2024-12-31
- Earliest claimed: 2021-09-29
- Assignees: Arteris, Inc.
- Applicants: Arteris, Inc.
- Inventors: Benoit de Lescure
- Web page: https://patentgrep.com/patent/US12184499B2

## CPC

- G06F 30/337: Design optimisation
- H04L 41/12: Discovery or management of network topologies
- G06F 30/327: Logic synthesis; Behaviour synthesis, e.g. mapping logic, HDL to netlist, high-level language to RTL or netlist
- G06F 30/394: Routing (G06F30/396 takes precedence)
- H04L 41/06: Management of faults, events, alarms or notifications
- H04L 41/22: comprising specially adapted graphical user interfaces [GUI]
- H04L 49/109: Integrated on microchip, e.g. switch-on-chip
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A system and method implemented by tool is disclosed. The tool receives input of a network-on-chip (NoC) and the NoC's desired connectivity and efficiently guides the designer through interactive NoC topology editing sessions to ensure the obtained network is both complete and correct during topology creation or modification.

## Claims

### Claim 1

A method comprising:
receiving a description of a network-on-chip (NoC) connectivity, including:
receiving a list of sources of traffic; and
receiving a list of destinations of traffic;
creating an initial NoC topology chart showing routes for traffic between each source and each of the source's respective destinations;
receiving user input for changes to at least one route;
determining an insertion point for a NoC element;
inserting the NoC element at the insertion point;
updating the initial NoC topology to generate a new NoC topology that includes the NoC element at the insertion point;
analyzing the new NoC topology for rule violations; and
reporting the rule violation to a user.

### Claim 2 (depends on 1)

The method of claim 1, wherein the description used to create an initial NoC topology includes a plurality of network interface units needed by each source and destination of traffic.

### Claim 3 (depends on 2)

The method of claim 2, wherein the NoC topology includes required direct connections as part of the routes.

### Claim 4 (depends on 1)

The method of claim 1, further comprising generating a netlist for the new NoC topology.

### Claim 5 (depends on 1)

The method of claim 1, wherein the user input includes electing one or more routes to modify.

### Claim 6 (depends on 1)

The method of claim 1, wherein the user input includes selecting a plurality of routes for editing such that all of the selected plurality of routes for editing have at least one element in common.

### Claim 7 (depends on 1)

The method of claim 1 further comprising:
receiving, as input from the user, a route to modify;
identifying at least one common element in a route to modify;
selecting the insertion point along the route.

### Claim 8 (depends on 1)

The method of claim 1, further comprising performing an editing operation on a set of selected routes and the insertion point, wherein the editing operation includes at least one of:
inserting a new element after the insertion point;
inserting a new element before the insertion point;
replacing the insertion point by another NoC element; and
deleting the insertion point.

### Claim 9 (depends on 1)

The method of claim 1 further comprising automatically inferring, from a set of routes selected for editing, the changes required to the initial NoC topology including at least one of:
removing elements no longer on any routes;
adding new elements; and
rewiring interconnections between elements to implement the required physical connectivity between NoC elements.

### Claim 10 (depends on 9)

The method of claim 9 further comprising generating a netlist.

### Claim 11

A system comprising:
memory for storing code;
a display; and
a processor in communication with the memory and the display, wherein the processor executes the code to cause the system to:
receive connectivity information for a network-on-chip (NoC) including sources and destinations;
create an initial NoC topology chart for traffic between each source and each of the source's respective destinations;
receive at least one user input identifying at least one change to the initial NoC topology;
determine an insertion point for a NoC element based on the at least one change;
inserts the NoC element at the insertion point;
generate a new NoC topology by updating the initial NoC topology having the NoC element at the insertion point;
analyzing the new NoC topology for rule violations; and
reporting the rule violation to a user.

### Claim 12 (depends on 11)

The system of claim 11, wherein the processor executes the code to further cause the system to generate a netlist for the new NoC topology.