# US 2015/0092775 A1 · Using context labels to scale mac tables on computer network edge devices

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

- Number: US 2015/0092775 A1
- Document ID: US20150092775A1
- Status: Published application
- Kind: A1
- Application number: 14/563,979
- Filed: 2014-12-08
- Published: 2015-04-02
- Earliest claimed: 2011-01-31
- Assignees: Cisco Technology, Inc.
- Applicants: Cisco Technology, Inc.
- Inventors: Sami Boutros; Yuri Tsier; Muthurajah Sivabalan; Pradosh Mohapatra; Clarence Filsfils; John H.W. Bettink; Luca Martini
- Web page: https://patentgrep.com/patent/US20150092775A1

## CPC

- H04L 45/502: {Frame based}
- H04L 12/18: for broadcast or conference {, e.g. multicast}
- H04L 45/04: {Interdomain routing, e.g. hierarchical routing}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

In one embodiment, an access component of a local network edge device receives traffic, and generates a frame for the traffic that includes a remote context label that identifies an access component of the remote network edge device to which the traffic is to be forwarded upon arrival at the remote network edge device, and a virtual circuit label corresponding to a particular virtual service of the traffic. The local network edge device forwards the frame towards the remote network edge device. In another embodiment, the frame may be received at a core component of the remote network edge device, an in response to the remote context label identifying an access component of the remote network edge device, forwarded to the access component, which determines the particular virtual service, and forwards the traffic from the frame out the access component towards an endpoint for the traffic.

## Claims

### Claim 1

A method, comprising:
receiving traffic at an access component of a local network edge device in a computer network; and
when the local network edge device is not aware of a remote network edge device in the computer network used to reach a destination of the traffic:
generating a multicast frame for the traffic, the multicast frame comprising,
a virtual circuit label corresponding to a particular virtual service of the traffic, and
a multicast context label, and
multicasting the multicast frame from the local network edge device toward one or more remote network edge devices.

### Claim 2 (depends on 1)

The method as in claim 1, wherein the virtual service is one of a virtual private local area network (LAN) service (VPLS) or a virtual private wire service (VPWS).

### Claim 3 (depends on 1)

The method as in claim 1, wherein each access component is selected from a group consisting of: a line card (LC), an interface, and a bundle.

### Claim 4 (depends on 1)

The method of claim 1, wherein the local network edge device is not aware of the remote network edge device when the local network edge device is unable to determine an access component of the remote network edge device.

### Claim 5 (depends on 1)

The method of claim 1, wherein the multicast frame is generated at an ingress access component of the local network edge device.

### Claim 6 (depends on 1)

The method of claim 1, wherein the multicast frame further comprises a local context label.

### Claim 7 (depends on 1)

The method of claim 1, wherein the multicast frame further comprises a transport label.

### Claim 8 (depends on 1)

The method of claim 1, further comprising:
forwarding the multicast frame from the local network edge device to a specific remote network edge device, wherein a virtual circuit for the specific remote network edge device is known but an address for the specific remote network edge device is unknown.

### Claim 9

A method, comprising:
receiving a frame of traffic at a core component of a remote network edge device in a computer network, the frame including a label stack with a remote context label that identifies an access component of the remote network edge device to which the traffic is to be forwarded for determination of a particular virtual service, and a virtual circuit label corresponding to the particular virtual service;
when the remote context label corresponds to one of either a multicast label or an unknown address label,
determining, by the access component of the remote network edge device, the particular virtual service of the frame from the virtual circuit label, and
forwarding the frame of traffic to one or more relevant access components of the remote network edge device.

### Claim 10 (depends on 9)

The method as in claim 9, wherein the virtual service is one of either a virtual private local area network (LAN) service (VPLS) or a virtual private wire service (VPWS).

### Claim 11 (depends on 9)

The method as in claim 9, wherein each access component and core component is each selected from a group consisting of: a line card (LC), an interface, and a bundle.

### Claim 12 (depends on 9)

The method as in claim 9, wherein the virtual circuit label and remote context label are a unified remote virtual circuit context label, wherein a first portion of the unified remote virtual circuit context label represents the remote context label, and a second portion represents the virtual circuit label.

### Claim 13 (depends on 9)

The method of claim 9, wherein the remote context label corresponds to the multicast label when the remote context label does not indicate a destination access component.

### Claim 14 (depends on 9)

The method of claim 9, wherein the remote context label corresponds to the multicast label when the remote context label does not indicate a receiving device.

### Claim 15 (depends on 9)

The method of claim 9, wherein the one or more relevant access components are responsible for the particular virtual service.

### Claim 16 (depends on 15)

The method of claim 15, wherein the particular virtual service is indicated by at least one of the remote context label or the virtual circuit label,

### Claim 17 (depends on 9)

The method of claim 9, further comprising:
dropping the frame of traffic at one or more non-responsible access components of the remote network edge device.

### Claim 18 (depends on 9)

The method of claim 9, further comprising:
forwarding, at a responsible access component, the frame of traffic toward a destination address, wherein the destination resides behind the responsible access component.

### Claim 19

An apparatus comprising:
an access component;
a processor coupled to the access component and configured to execute processes; and
a memory configured to store a process executable by the processor, the process, when executed, operable to,
receive traffic at the access component;
when the apparatus is not aware of a remote network edge device in the computer network used to reach a destination of the traffic:
generating a broadcast frame for the traffic, the broadcast frame comprising,
a virtual circuit label corresponding to a particular virtual service of the traffic, and
a broadcast context label, and
broadcasting the broadcast frame toward one or more remote network edge devices.

### Claim 20 (depends on 19)

The apparatus of claim 19, wherein the apparatus is not aware of the remote network edge device when the apparatus is unable to determine an access component of the remote network edge device.
