# US 2010/0306415 A1 · Using Provider Backbone Bridged Network to Reduce the Number of Media Access Control Addresses Visible to Core Bridges in the Data Center

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

- Number: US 2010/0306415 A1
- Document ID: US20100306415A1
- Status: Published application
- Kind: A1
- Application number: 12/786,651
- Filed: 2010-05-25
- Published: 2010-12-02
- Earliest claimed: 2009-05-29
- Assignees: Futurewei Technologies, Inc.
- Inventors: Robert Sultan; T. Benjamin Mack-Crane
- Web page: https://patentgrep.com/patent/US20100306415A1

## CPC

- H04L 12/462: {LAN interconnection over a bridge based backbone}
- H04L 12/4654: {wherein a VLAN tag represents a customer VLAN, e.g. C-Tag}
- H04L 12/4658: {wherein a VLAN tag represents a service provider backbone VLAN, e.g. B-Tag, S-Tag}
- H04L 12/4662: {wherein a VLAN tag represents a service instance, e.g. I-SID in PBB}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A system comprising a backbone core bridge (BCB) in a provider backbone bridged network (PBBN), and a backbone edge bridge (BEB) coupled to the BCB via a provider network port (PNP) and to a customer bridge in a customer bridged network via a C-tagged service interface, wherein the C-tagged service interface maps a service instance from the customer bridged network that is identified by a customer-virtual local area network identifier (C-VID) to a backbone service instance on the PBBN that is identified by a service instance identifier (I-SID).

## Claims

### Claim 1

A system comprising:
a backbone core bridge (BCB) in a provider backbone bridged network (PBBN); and
a backbone edge bridge (BEB) coupled to the BCB via a provider network port (PNP) and to a customer bridge in a customer bridged network via a C-tagged service interface,
wherein the C-tagged service interface maps a service instance from the customer bridged network that is identified by a customer-virtual local area network identifier (C-VID) to a backbone service instance on the PBBN that is identified by a service instance identifier (I-SID).

### Claim 2 (depends on 1)

The system of claim 1, wherein the BEB is in the PBBN, and wherein the PBBN provides the C-tagged service interface for attachment to the customer bridged network.

### Claim 3 (depends on 1)

The system of claim 1, wherein the customer bridge provides port-based or C-tagged service interfaces to a customer bridge customers.

### Claim 4 (depends on 1)

The system of claim 1, wherein the C-tagged service interface comprises a one-to-one C-tagged service interface that performs one-to-one mapping of the C-VID to the I-SIDs, wherein the one-to-one C-tagged service interface does not carry a C-tag over the PBBN, wherein frames that are mapped to the I-SID are carried over the PBBN, and wherein frames that are not mapped to the I-SID are not carried over the PBBN.

### Claim 5 (depends on 4)

The system of claim 4, wherein a Canonical Format Identifier (CFI) bit and priority code point (PCP) bits are extracted from the C-Tag on ingress and are then carried in a drop eligible indicator (I-DEI) bit and I-PCP bits in an I-Tag across the PBBN.

### Claim 6 (depends on 5)

The system of claim 5, wherein on egress from the one-to-one C-tagged interface, the C-Tag is deduced from the I-Tag received from the PBBN, and wherein the I-SID is mapped to a C-VID, the CFI bit and the PCP bits are regenerated from the I-DEI bit and the I-PCP bits of the I-Tag, and carried in the CFI bit and the PCP bits of the C-Tag.

### Claim 7 (depends on 1)

The system of claim 1, wherein the C-tagged service interface comprises a bundling C-tagged interface that maps multiple C-VIDs to a single I-SID for delivery over the PBBN, and wherein the bundling C-tagged service interface carries a C-Tag over the PBBN to allow the remote end to reconstruct the C-VID.

### Claim 8 (depends on 7)

The system of claim 7, wherein the bundling C-tagged interface regenerates a Canonical Format Identifier (CFI) bit and a priority code point (PCP) bit of the C-Tag and carries the CFI bit and the PCP bit of the C-Tag in both the CFI bit and the PCP bit of the C-Tag and an Service instance drop eligible indicator (I-DEI) bit and I-PCP bit of the I-Tag over the PBBN.

### Claim 9 (depends on 1)

The system of claim 1, wherein the C-tagged service interface comprises an all-to-one bundling C-tagged service interface that maps all C-VIDs to a single I-SID, and wherein an I-component that is used for the all-to-one bundled C-tagged service interface is constrained to supporting a single C-tagged service interface.

### Claim 10

A network comprising:
a provider backbone bridged network (PBBN) that comprises a plurality of core bridges; and
a plurality of customer bridges (CBs) coupled to the PBBN,
wherein at least some of the core bridges do not support Institute of Electrical and Electronics Engineers (IEEE) 802.1ad for provider bridging but do support IEEE 802.1Q for virtual local area network (V LAN) bridging.

### Claim 11 (depends on 10)

The network of claim 10, wherein the PBBN comprises a plurality of backbone-virtual local area networks (B-VLANs), wherein the CBs are coupled to a plurality of backbone edge bridges (BEBs) in the PBBN via a plurality of customer-virtual local area networks (C-VLANs), wherein the BEBs are configured to forward Customer-tagged (C-tagged) traffic between the CBs and the core bridges, and wherein the C-tagged traffic is mapped to a plurality of backbone service instances and hence to the B-VLANs.

### Claim 12 (depends on 11)

The network of claim 11, wherein the BEBs use a Customer-tag (C-tag) Ethertype, a Service-tag (S-tag) Ethertype to identify the different B-VLANs, or both.

### Claim 13 (depends on 11)

The network of claim 11, wherein the CBs are coupled to a plurality of backbone core bridges (BCBs) in the PBBN via a plurality of customer-virtual local area networks (C-VLANs), and wherein the BEBs are configured to forward Customer-tagged (C-tagged) traffic between the CBs and the backbone core bridges (BCBs).

### Claim 14 (depends on 13)

The network of claim 13, wherein the C-VLANs are extended across the PBBN, and wherein the C-tagged traffic is forwarded along the C-VLANs without mapping the C-tagged traffic to a plurality of backbone-virtual local area networks (B-VLANs).

### Claim 15 (depends on 14)

The network of claim 14, wherein the C-tagged traffic is forwarded using a frame carrying an encapsulated address types (EAT) instead of a backbone service instance-tag (I-tag) to save about four bytes in each transmitted data frame.

### Claim 16

A network component comprising:
at least one processor coupled to a memory and configured to:
transfer a plurality of bridge protocol data units (BPDUs) between a core bridge in a provider backbone bridged network (PBBN) and a customer bridge in a data center network (DCN) coupled to the PBBN; and
transfer a plurality of multiple registration protocol (MRP) protocol data units (PDUs) between the core bridge and the customer bridge,
wherein the customer bridge's media access control (MAC) address in the DCN is not visible to the core bridge in the PBBN.

### Claim 17 (depends on 16)

The network component of claim 16, wherein the BPDUs are used to span a plurality of Customer-Virtual Local Area Networks (C-VLANs) that extend the PBBN and the DCN from the core bridge to the customer bridge, and wherein the processor is further configured to transfer a plurality of data frames that comprise a plurality of Customer-Virtual Local Area Network (C-VLAN) Identifiers (CVIDs) and a plurality of Encapsulated Address Types (EATs) across the C-VLANs.

### Claim 18 (depends on 17)

The network component of claim 17, wherein the processor is further configured to transfer a plurality of multicast frames that comprise a group Customer-Destination MAC (C-DMAC) that indicates a plurality of Customer-Destination Addresses (C-DAs) across the C-VLANs.

### Claim 19 (depends on 18)

The network component of claim 18, wherein the multicast frames are transferred without mapping the group C-DMAC to a backbone service instance group address (BSIGA) or a group backbone-destination MAC (B-DMAC) that indicates a plurality of MAC address in the core of the PBBN.
