# US 2026/0230434 A1 · Hierarchical Network Sub-Partitioning

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

- Number: US 2026/0230434 A1
- Document ID: US20260230434A1
- Status: Published application
- Kind: A1
- Application number: 19/043,475
- Filed: 2025-02-02
- Published: 2026-08-06
- Earliest claimed: 2025-02-02
- Assignees: Mellanox Technologies, Ltd.
- Applicants: Mellanox Technologies, Ltd.
- Inventors: Rafi Ram; Ortal Bashan; Alex Netes; Ayal Lior
- Web page: https://patentgrep.com/patent/US20260230434A1

## CPC

- H04L 47/2483: involving identification of individual flows
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A Network Management System (NMS) includes one or more network interfaces and one or more processors. The one or more network interfaces are to communicate with a communication network including multiple network devices, the network devices being connected (i) to one another via inter-device ports and (ii) to network endpoints via endpoint-facing ports. The one or more processors are to define a plurality of traffic domains arranged in a hierarchy having two or more levels, to associate the endpoint-facing ports of the network devices with respective ones of the traffic domains, and to configure the network devices (i) to assign incoming packets to the respective traffic domains that are associated with the endpoint-facing ports via which the incoming packets enter the communication network, and (ii) to permit forwarding of packets only within each of the traffic domains.

## Claims

### Claim 1

A Network Management System (NMS), comprising:
one or more network interfaces, to communicate with a communication network comprising multiple network devices, the network devices being connected (i) to one another via inter-device ports and (ii) to network endpoints via endpoint-facing ports; and
one or more processors, to:
define a plurality of traffic domains arranged in a hierarchy having two or more levels;
associate the endpoint-facing ports of the network devices with respective ones of the traffic domains; and
configure the network devices (i) to assign incoming packets to the respective traffic domains that are associated with the endpoint-facing ports via which the incoming packets enter the communication network, and (ii) to permit forwarding of packets only within each of the traffic domains.

### Claim 2 (depends on 1)

The NMS according to claim 1, wherein the one or more processors are to configure the network devices to mark an incoming packet with a domain identifier that is (i) indicative of a traffic domain assigned to the incoming packet, but (ii) not indicative of the hierarchy.

### Claim 3 (depends on 1)

The NMS according to claim 1, wherein, in response to adding a traffic domain to the plurality, the one or more processors are to (i) define a location of the traffic domain in the hierarchy, (ii) define a domain identifier for the traffic domain, (iii) update association of the endpoint-facing ports to account for the traffic domain, and (iv) reconfigure the network devices to account for the traffic domain.

### Claim 4 (depends on 1)

The NMS according to claim 1, wherein, in response to terminating a traffic domain in the plurality, the one or more processors are to (i) remove the traffic domain from the hierarchy, (ii) release a domain identifier that was assigned to the traffic domain, and (iii) reconfigure the network devices to account for removal of the traffic domain.

### Claim 5

A network device, comprising:
multiple ports for sending and receiving packets to and from a communication network, one or more of the ports serving as endpoint-facing ports for connecting to endpoints of the communication network;
forwarding circuitry, to forward the packets between the ports; and
a controller, to:
receive a configuration from a Network Management System (NMS); and
responsively to the configuration, configure the forwarding circuitry (i) to assign incoming packets, entering the network device via the endpoint-facing ports, to respective traffic domains that are associated with the endpoint-facing ports via which the incoming packets enter the network device, and (ii) to permit forwarding of the packets only within each of the traffic domains.

### Claim 6 (depends on 5)

The network device according to claim 5, wherein, responsively to the configuration, the forwarding circuitry is to mark an incoming packet with a domain identifier that is indicative of a traffic domain assigned to the incoming packet.

### Claim 7

A network management method, comprising:
defining a plurality of traffic domains for a communication network comprising multiple network devices that are connected (i) to one another via inter-device ports and (ii) to network endpoints via endpoint-facing ports, the traffic domains being arranged in a hierarchy having two or more levels;
associating the endpoint-facing ports of the network devices with respective ones of the traffic domains; and
configuring the network devices (i) to assign incoming packets to the respective traffic domains that are associated with the endpoint-facing ports via which the incoming packets enter the communication network, and (ii) to permit forwarding of packets only within each of the traffic domains.

### Claim 8 (depends on 7)

The method according to claim 7, wherein configuring the network devices to assign the incoming packets to the traffic domains comprises configuring the network devices to mark an incoming packet with a domain identifier that is (i) indicative of a traffic domain assigned to the incoming packet, but (ii) not indicative of the hierarchy.

### Claim 9 (depends on 7)

The method according to claim 7, and comprising, in response to adding a traffic domain to the plurality, (i) defining a location of the traffic domain in the hierarchy, (ii) defining a domain identifier for the traffic domain, (iii) updating association of the endpoint-facing ports to account for the traffic domain, and (iv) reconfiguring the network devices to account for the traffic domain.

### Claim 10 (depends on 7)

The method according to claim 7, and comprising, in response to terminating a traffic domain in the plurality, (i) removing the traffic domain from the hierarchy, (ii) releasing a domain identifier that was assigned to the traffic domain, and (iii) reconfiguring the network devices to account for removal of the traffic domain.

### Claim 11

A communication method, comprising:
in a network device comprising multiple ports for sending and receiving packets to and from a communication network, one or more of the ports serving as endpoint-facing ports for connecting to endpoints of the communication network, receiving a configuration from a Network Management System (NMS); and
responsively to the configuration, (i) assigning incoming packets, entering the network device via the endpoint-facing ports, to respective traffic domains that are associated with the endpoint-facing ports via which the incoming packets enter the network device, and (ii) permitting forwarding of the packets only within each of the traffic domains.

### Claim 12 (depends on 11)

The method according to claim 11, wherein assigning the incoming packets to the traffic domains comprises marking an incoming packet with a domain identifier that is indicative of a traffic domain assigned to the incoming packet.
