# US 2010/0169506 A1 · Network interface device management using management transport channel

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

- Number: US 2010/0169506 A1
- Document ID: US20100169506A1
- Status: Published application
- Kind: A1
- Application number: 12/347,678
- Filed: 2008-12-31
- Published: 2010-07-01
- Earliest claimed: 2008-12-31
- Assignees: Verizon Corporate Resources Group LLC; Canoga Perkins Corporation
- Inventors: Roman R. KRZANOWSKI; Hicham ZHIRI
- Web page: https://patentgrep.com/patent/US20100169506A1

## CPC

- H04L 41/04: Network management architectures or arrangements
- H04L 41/344: Out-of-band transfers
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A master network interface device (M-NID) receives, from a network management system (NMS) via a first peer-to-peer (P2P) transport channel, first data destined for a first client network interface device (C-NID), where the first data is associated with network management functions. The M-NID further receives, from the NMS via the first P2P transport channel, second data destined for a second C-NID, where the second data is associated with network management functions. The M-NID forwards the first data from the M-NID to the destination first C-NID via a second P2P transport channel that is different than the first P2P transport channel. The M-NID also forwards the second data from the M-NID to the destination second C-NID via a third P2P transport channel that is different than the first P2P transport channel.

## Claims

### Claim 1

A method, comprising:
receiving, at a master network interface device (M-NID) from a network management system (NMS) via a first peer-to-peer (P2P) transport channel, first data destined for a first client network interface device (C-NID), where the first data is associated with network management functions;
receiving, at the M-NID from the network management system (NMS) via the first P2P transport channel, second data destined for a second C-NID, where the second data is associated with network management functions:
forwarding the first data from the M-NID to the destination first C-NID via a second P2P transport channel that is different than the first P2P transport channel; and
forwarding the second data from the M-NID to the destination second C-NID via a third P2P transport channel that is different than the first P2P transport channel.

### Claim 2 (depends on 1)

The method of claim 1, where forwarding the first data further comprises:
determining a network address associated with the first C-NID; and
determining the second P2P transport channel based on the determined network address associated with the first C-NID.

### Claim 3 (depends on 2)

The method of claim 2, where forwarding the second data further comprises:
determining a network address associated with the second C-NID; and
determining the third P2P transport channel based on the determined network address associated with the second C-NID.

### Claim 4 (depends on 1)

The method of claim 1, where the first P2P transport channel comprises an emulated pseudowire.

### Claim 5 (depends on 1)

The method of claim 1, where the second P2P transport channel comprises a virtual local area network (VLAN).

### Claim 6 (depends on 1)

The method of claim 1, where the first P2P transport channel comprises a first virtual local area network (VLAN), where the second P2P transport channel comprises a second VLAN, and where the third P2P transport channel comprises a third VLAN that is different than the first and second VLANs.

### Claim 7 (depends on 1)

The method of claim 1, further comprising:
receiving, at the M-NID from the first C-NID via the second P2P transport channel, third data destined for the NMS, where the third data is associated with network management functions; and
forwarding the third data from the M-NID to the NMS via the first P2P transport channel.

### Claim 8 (depends on 7)

The method of claim 7, further comprising:
receiving, at the M-NID from the second C-NID via the third P2P transport channel, fourth data destined for the NMS, where the fourth is associated with network management functions; and
forwarding the fourth from the M-NID to the NMS via the first P2P transport channel.

### Claim 9

A master network interface device, comprising:
an interface to:
receive, from a network management system (NMS), first data destined for a first client network interface device (C-NID) via a first peer to peer (P2P) transport channel, where the first data is associated with network management functions;
receive, from the network management system (NMS), second data destined for a second C-NID via the first P2P transport channel, where the second data is associated with network management functions; and
a data router to:
forward the first data from the M-NID to the first C-NID via a second P2P transport channel that is different than the first P2P transport channel; and
forward the second data from the M-NID to the second C-NID via a third P2P transport channel that is different than the first P2P transport channel.

### Claim 10 (depends on 9)

The master network interface device of claim 9, where the first P2P transport channel comprises an emulated pseudowire or a virtual local area network (VLAN).

### Claim 11 (depends on 9)

The master network interface device of claim 9, where the first P2P transport channel comprises a first virtual local area network (VLAN), where the second P2P transport channel comprises a second VLAN, and where the third P2P transport channel comprises a third VLAN that is different than the first and second VLANs.

### Claim 12 (depends on 9)

The master network interface device of claim 9, where the interface is further configured to:
receive, from the first C-NID via the second P2P transport channel, third data destined for the NMS, where the third data is associated with network management functions, and
where the data router is further configured to:
forward the third data from the M-NID to the NMS via the first P2P transport channel.

### Claim 13 (depends on 12)

The master network device of claim 12, where the interface is further configured to:
receive, from the second C-NID via a third P2P transport channel, fourth data destined for the NMS, where the fourth data is associated with network management functions, and
where the data router is further configured to:
forward the fourth data from the M-NID to the NMS via the first P2P transport channel.

### Claim 14

A method, comprising:
receiving, at a master network interface device (M-NID) from a first client network interface device (C-NID) via a first peer-to-peer (P2P) transport channel, first data destined for a network management system (NMS), where the first data is associated with network management functions;
receiving, at the M-NID from a second C-NID via a second P2P transport channel, second data destined for the NMS, where the second data is associated with network management functions; and
forwarding the first data from the M-NID to the NMS via a third P2P transport channel that is different than the first and second P2P transport channels.
forwarding the second data from the M-NID to the NMS via the third P2P transport channel.

### Claim 15 (depends on 14)

The method of claim 14, where the first, second and third P2P transport channels comprise different emulated pseudowires or different virtual local area networks (VLANs).

### Claim 16 (depends on 14)

The method of claim 14, where the first P2P transport channel comprises a first virtual local area network (VLAN), where the second P2P transport channel comprises a second VLAN, and where the third P2P transport channel comprises a third VLAN, where the second and third VLANs are different than the first VLAN.
