# US 2021/0083901 A1 · Provider edge device and method implemented thereon for ethernet virtual private network

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

- Number: US 2021/0083901 A1
- Document ID: US20210083901A1
- Status: Published application
- Kind: A1
- Application number: 16/772,403
- Filed: 2017-12-18
- Published: 2021-03-18
- Earliest claimed: 2017-12-18
- Assignees: Telefonaktiebolaget LM Ericsson (publ)
- Applicants: Telefonaktiebolaget LM Ericsson (publ)
- Inventors: Jiang HE; Haifeng QU
- Web page: https://patentgrep.com/patent/US20210083901A1

## CPC

- H04L 12/4625: {Single bridge functionality, e.g. connection of two networks over a single bridge}
- H04L 12/4645: {Details on frame tagging (routing of packets H04L45/00; support for virtual LAN H04L49/354)}
- H04L 12/46: Interconnection of networks
- H04L 12/4633: {Interconnection of networks using encapsulation techniques, e.g. tunneling}
- H04L 12/4675: {Dynamic sharing of VLAN information amongst network nodes (configuration of the network or of network elements H04L41/08)}
- H04L 12/4679: {Arrangements for the registration or de-registration of VLAN attribute values, e.g. VLAN identifiers, port VLAN membership}
- H04L 45/50: using label swapping, e.g. multi-protocol label switch [MPLS]
- H04L 45/507: {Label distribution}
- H04L 45/66: {Layer 2 routing, e.g. in Ethernet based MAN's}
- H04L 45/74: Address processing for routing
- H04L 47/806: {Broadcast or multicast traffic}
- H04L 47/825: {Involving tunnels, e.g. MPLS}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A provider edge (PE) device and a method implemented thereon are disclosed for Ethernet virtual private network (EVPN). According to an embodiment, a first PE device performs label assignment procedure with a second PE device such that the first and second PE devices share an Ethernet segment identifier (ESI)-excluded label and know a correspondence between the ESI-excluded label and a label combination of an ESI label and a VPN label. The first PE device encapsulates a packet of broadcast, unknown unicast or multicast (BUM) traffic, with the ESI-excluded label instead of the label combination. The first PE device sends the encapsulated packet to the second PE device.

## Claims

### Claim 1

A method implemented at a first provider edge (PE) device in an Ethernet virtual private network (EVPN), the method comprising:
performing label assignment procedure with a second PE device such that the first and second PE devices share an Ethernet segment identifier (ESI)-excluded label and know a correspondence between the ESI-excluded label and a label combination of an ESI label and a VPN label;
encapsulating a packet of broadcast, unknown unicast or multicast (BUM) traffic, with the ESI-excluded label instead of the label combination; and
sending the encapsulated packet to the second PE device.

### Claim 2 (depends on 1)

The method according to claim 1, wherein performing the label assignment procedure with the second PE device comprises:
receiving, from the second PE device, a message that comprises the ESI label, the VPN label and the ESI-excluded label; and
wherein the encapsulated packet is sent to the second PE device through ingress replication.

### Claim 3 (depends on 1)

The method according to claim 1, wherein performing the label assignment procedure with the second PE device comprises:
generating, in correspondence with the label combination of the ESI and VPN labels, the ESI-excluded label; and
sending, to the second PE device, a message that comprises the ESI label, the VPN label and the ESI-excluded label; and
wherein the encapsulated packet is sent to the second PE device through point to multipoint (P2MP) label switched path (LSP).

### Claim 4 (depends on 2)

The method according to claim 2, wherein the message is an advertisement of border gateway protocol (BGP) comprising: information about Inclusive Multicast Ethernet Tag Route including the VPN label; and an extended community including the ESI label and the ESI-excluded label.

### Claim 5 (depends on 1)

The method according to claim 1, wherein each ESI-excluded label is configured to uniquely identify a different egress broadcast port list on the second PE.

### Claim 6

A method implemented at a second provider edge (PE) device in an Ethernet virtual private network (EVPN), the method comprising:
performing label assignment procedure with a first PE device such that the first and second PE devices share an Ethernet segment identifier (ESI)-excluded label and know a correspondence between the ESI-excluded label and a label combination of an ESI label and a VPN label;
receiving, from the first PE device, a packet of broadcast, unknown unicast or multicast (BUM) traffic that comprises the ESI-excluded label instead of the label combination;
determining the ESI-excluded label from the packet of BUM traffic; and
flooding the packet of BUM traffic according to the ESI-excluded label.

### Claim 7 (depends on 6)

The method according to claim 6, wherein performing label assignment procedure with the first PE device comprises:
generating, in correspondence with the label combination of the ESI and VPN labels, the ESI-excluded label; and
sending, to the first PE device, a message that comprises the ESI label, the VPN label and the ESI-excluded label; and
wherein the packet of BUM traffic is received from the first PE device through ingress replication.

### Claim 8 (depends on 6)

The method according to claim 6, wherein performing label assignment procedure with the first PE device comprises:
receiving, from the first PE device, a message that comprises the ESI label, the VPN label and the ESI-excluded label; and
wherein the packet of BUM traffic is received from the first PE device through point to multipoint (P2MP) label switched path (LSP).

### Claim 9 (depends on 7)

The method according to claim 7, wherein the message is an advertisement of border gateway protocol (BGP) comprising: information about Inclusive Multicast Ethernet Tag Route including the VPN label; and an extended community including the ESI label and the ESI-excluded label.

### Claim 10 (depends on 6)

The method according to claim 6, wherein each ESI-excluded label is configured to uniquely identify a different egress broadcast port list on the second PE.

### Claim 11

A first provider edge (PE) device in an Ethernet virtual private network (EVPN), the first PE device comprising:
a processor; and
a memory, the memory containing instructions executable by the processor, whereby the first PE device is operative to:
perform label assignment procedure with a second PE device such that the first and second PE devices share an Ethernet segment identifier (ESI)-excluded label and know a correspondence between the ESI-excluded label and a label combination of an ESI label and a VPN label;
encapsulate a packet of broadcast, unknown unicast or multicast (BUM) traffic, with the ESI-excluded label instead of the label combination; and
send the encapsulated packet to the second PE device.

### Claim 12 (depends on 11)

The first PE device according to claim 11, wherein the first PE device is operative to perform label assignment procedure with the second PE device by:
receiving, from the second PE device, a message that comprises the ESI label, the VPN label and the ESI-excluded label; and
wherein the first PE device is operative to send the encapsulated packet to the second PE device through ingress replication.

### Claim 13 (depends on 11)

The first PE device according to claim 11, wherein the first PE device is operative to perform label assignment procedure with the second PE device by:
generating, in correspondence with the label combination of the ESI and VPN labels, the ESI-excluded label; and
sending, to the second PE device, a message that comprises the ESI label, the VPN label and the ESI-excluded label; and
wherein the first PE device is operative to send the encapsulated packet to the second PE device through point to multipoint (P2MP) label switched path (LSP).

### Claim 14 (depends on 12)

The first PE device according to claim 12, wherein the message is an advertisement of border gateway protocol (BGP) comprising: information about Inclusive Multicast Ethernet Tag Route including the VPN label; and an extended community including the ESI label and the ESI-excluded label.

### Claim 15 (depends on 11)

The first PE device according to claim 11, wherein each ESI-excluded label is configured to uniquely identify a different egress broadcast port list on the second PE.

### Claim 16 (depends on 11)

The first PE device according to claim 11, wherein the processor comprises a chipset capable of supporting multi-protocol label switching (MPLS) label push, pop and forwarding.

### Claim 17

A second provider edge (PE) device in an Ethernet virtual private network (EVPN), the second PE device comprising:
a processor; and
a memory, the memory containing instructions executable by the processor, whereby the second PE device is operative to:
perform label assignment procedure with a first PE device such that the first and second PE devices share an Ethernet segment identifier (ESI)-excluded label and know a correspondence between the ESI-excluded label and a label combination of an ESI label and a VPN label;
receive, from the first PE device, a packet of broadcast, unknown unicast or multicast (BUM) traffic that comprises the ESI-excluded label instead of the label combination;
determine the ESI-excluded label from the packet of BUM traffic; and
flood the packet of BUM traffic according to the ESI-excluded label.

### Claim 18 (depends on 17)

The second PE device according to claim 17, wherein the second PE device is operative to perform label assignment procedure with the first PE device by:
generating, in correspondence with the label combination of the ESI and VPN labels, the ESI-excluded label; and
sending, to the first PE device, a message that comprises the ESI label, the VPN label and the ESI-excluded label; and
wherein the second PE device is operative to receive the packet of BUM traffic from the first PE device through ingress replication.

### Claim 19 (depends on 17)

The second PE device according to claim 17, wherein the second PE device is operative to perform label assignment procedure with the first PE device by:
receiving, from the first PE device, a message that comprises the ESI label, the VPN label and the ESI-excluded label; and
wherein the second PE device is operative to receive the packet of BUM traffic from the first PE device through point to multipoint (P2MP) label switched path (LSP).

### Claim 20 (depends on 18)

The second PE device according to claim 18, wherein the message is an advertisement of border gateway protocol (BGP) comprising: information about Inclusive Multicast Ethernet Tag Route including the VPN label; and an extended community including the ESI label and the ESI-excluded label.

### Claim 21 (depends on 17)

The second PE device according to claim 17, wherein each ESI-excluded label is configured to uniquely identify a different egress broadcast port list on the second PE.

### Claim 22 (depends on 17)

The second PE device according to claim 17, wherein the processor comprises a chipset capable of supporting multi-protocol label switching (MPLS) label push, pop and forwarding.

### Claim 23 (depends on 1)

A computer program product comprising instructions which when executed by at least one processor, cause the at least one processor to perform the method according to claim 1.

### Claim 24 (depends on 1)

A computer readable storage medium comprising instructions which when executed by at least one processor, cause the at least one processor to perform the method according to claim 1.
