IP Library Granted Patent US 8,787,377
Granted Patent B2
US 8,787,377 · App. 13/097,224 · Granted Jul 22, 2014

Usage of masked BMAC addresses in a provider backbone bridged (PBB) network

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,787,377
App. No.
13/097,224
Granted
Jul 22, 2014
Kind
B2
Abstract

Techniques disclosed herein include features and methods that extend functionality of provider networks including Provider Backbone Bridges (PBB) networks. Techniques include using a portion of information within Ethernet address encapsulation headers for purposes other than identifying source and destination device addresses. The system limits a number of bits in an address header that should be considered by a provider network node when doing an address lookup in forwarding tables of a provider network node, such as by masking the portion of bits or otherwise disregarding that portion of bits during address lookup. The remaining bits in the address field(s) become free bits that can be used for a variety of application purposes, such as flow path selection. By using information fields that already exist in the Mac-In-Mac (MIM) encapsulation header, such Techniques provide additional information without increasing packet size or requiring new protocols.

Claims (43)

1. A computer-implemented method for packet switching in a provider network, the computer-implemented method comprising:

receiving a data packet at a first data switching device, the data packet having an existing header and being received from a customer network, the first data switching device being an edge node of a provider network;

encapsulating the data packet using an Ethernet header, the Ethernet header having a data structure that includes a provider device address space and a virtual local area network (VLAN) indicator space;

encapsulating the data packet includes setting a first portion of bits, within the provider device address space, that indicates a data switching device address that is a node within the provider network;

encapsulating the data packet includes setting a second portion of bits, within the provider device address space, that indicates information distinct from the data switching device address and indicating, within the VLAN indicator space, which bits of the provider device address space indicate the data switching device address, and which bits of the provider device address space indicate the information distinct from the data switching device address; and

forwarding the data packet via the provider network.

2. The computer-implemented method of claim 1 , wherein encapsulating the data packet using the Ethernet header includes indicating, within the provider device address space, that the provider device address space uses locally administered Media Access Control addresses.

3. The computer-implemented method of claim 2 , wherein encapsulating the data packet using the Ethernet header includes indicating, within the provider device address space, that the data packet is a unicast transmission.

4. The computer-implemented method of claim 2 , wherein the provider network is a Provider Backbone Bridge (PBB) network, and wherein encapsulating the data packet using the Ethernet header includes using Mac-in-Mac encapsulation, the provider device address space being a backbone address space having 48 available bits.

5. The computer-implemented method of claim 1 , wherein setting a second portion of bits that indicates information distinct from the data switching device address includes indicating a User Network Interface (UNI) identity, the UNI identity indicating an interface that the data packet used to enter the provider network.

6. The computer-implemented method of claim 5 , further comprising:

selecting a forwarding path by using the UNI identity from the provider device address space as computational input for selecting the forwarding path; and

wherein forwarding the data packet via the provider network includes forwarding the data packet to a next node within the provider network via the selected forwarding path.

7. The computer-implemented method of claim 1 , wherein setting a second portion of bits that indicates information distinct from the data switching device address includes indicating a flow path identifier.

8. The computer-implemented method of claim 1 , further comprising:

wherein encapsulating the data packet includes setting a first portion of bits, within the VLAN space, that indicates a customer VLAN; and

wherein encapsulating the data packet includes setting a second portion of bits, within the VLAN space, that indicates a time to live (TTL) of the data packet.

9. The computer-implemented method of claim 1 , wherein the Ethernet header includes a Backbone Media Access Control (MAC) destination address, and a Backbone Media Access Control source address;

wherein encapsulating the data packet includes using bits from the Backbone MAC destination address and the Backbone MAC source address to indicate information distinct from the data switching device addresses.

10. A computer program product including a non-transitory computer-storage medium having instructions stored thereon for processing data information, such that the instructions, when carried out by a processing device, cause the processing device to perform the operations of:

receiving a data packet at a first data switching device, the data packet having an existing header and being received from a customer network, the first data switching device being an edge node of a provider network;

encapsulating the data packet using an Ethernet header, the Ethernet header having a data structure that includes a provider device address space and a virtual local area network (VLAN) indicator space;

encapsulating the data packet includes setting a first portion of bits, within the provider device address space, that indicates a data switching device address that is a node within the provider network;

encapsulating the data packet includes setting a second portion of bits, within the provider device address space, that indicates information distinct from the data switching device address; and indicating, within the VLAN indicator space, which bits of the provider device address space indicate the data switching device address, and which bits of the provider device address space indicate the information distinct from the data switching device address; and

forwarding the data packet via the provider network.

11. A computer-implemented method for packet switching in a provider network, the computer-implemented method comprising:

receiving a data packet at a data switching device, the data switching device being a node within a provider network, the data packet received from another node within the provider network, the data packet having a customer network Ethernet header encapsulated by a provider network Ethernet header;

identifying a provider device Media Access Control (MAC) address from a provider device address space within the provider network Ethernet header, the provider device address space having a first portion of bits that indicates a data switching device address of a second data switching device, and the provider device address space having a second portion of bits that indicates information distinct from the data switching device address;

executing a lookup in a forwarding table of the data switching device based on the data switching device address indicated in the first portion of bits and identifying the first portion of bits identifying the data switching device address and the second portion of bits identifying information distinct from the data switching device address based on information from a virtual local area network (VLAN) indicator space of the provide Ethernet header; and

forwarding the data packet via the provider network.

12. The computer-implemented method of claim 11 , wherein executing the lookup includes masking the second portion of bits within the provider device address space prior to executing the lookup.

13. The computer-implemented method of claim 11 , wherein the provider Ethernet header indicates, within the provider device address space, that the provider device address space uses locally administered Media Access Control addresses that are unicast addresses.

14. The computer-implemented method of claim 13 , wherein the provider network is a Provider Backbone Bridge (PBB) network, the provider network Ethernet header being Mac-in-Mac encapsulation, the provider device address space being a backbone address space having 48 available bits.

15. The computer-implemented method of claim 11 , further comprising:

selecting a forwarding path by executing a hashing operation using a User-Network Interface (UNI) identity, indicated within the second portion of the provider device address space, as computational input for the hashing operation; and

wherein forwarding the data packet via the provider network includes forwarding the data packet to a next node within the provider network via the selected forwarding path.

16. The computer-implemented method of claim 11 , further comprising:

selecting a forwarding path by executing a hashing operation using a flow path identifier indicated within the second portion of the provider device address space, as computational input for the hashing operation; and

wherein forwarding the data packet via the provider network includes forwarding the data packet to a next node within the provider network via the selected forwarding path.

17. The computer-implemented method of claim 11 , wherein the provider network Ethernet header includes a Backbone Media Access Control (MAC) destination address, and a Backbone Media Access Control source address, the provider network Ethernet header using bits across both the Backbone MAC destination address and the Backbone MAC source address to indicate information distinct from the data switching device addresses.

18. The computer-implemented method of claim 11 , further comprising:

wherein the data packet includes a first portion of bits, within a VLAN space of the provider network Ethernet header, that indicates a customer VLAN, and a second portion of bits, within the VLAN space, that indicates a time to live (TTL) of the data packet; and

decrementing a TTL value indicated within the VLAN space.

Assignments (13)
AMENDED SECURITY AGREEMENT Recorded Aug 18, 2023
From: EXTREME NETWORKS, INC.; AEROHIVE NETWORKS, INC.
To: BANK OF MONTREAL
Reel/Frame 064782/0971 →
SECURITY INTEREST Recorded May 1, 2018
From: EXTREME NETWORKS, INC.
To: BANK OF MONTREAL
Reel/Frame 046050/0546 →
RELEASE OF SECURITY INTEREST Recorded May 1, 2018
From: SILICON VALLEY BANK
To: EXTREME NETWORKS, INC.
Reel/Frame 046051/0775 →
BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 029608/0256 Recorded Dec 15, 2017
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
To: AVAYA INC.
Reel/Frame 044891/0801 →
BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 030083/0639 Recorded Dec 15, 2017
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
To: AVAYA INC.
Reel/Frame 045012/0666 →
BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 041576/0001 Recorded Dec 15, 2017
From: CITIBANK, N.A.
To: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS INC.; OCTEL COMMUNICATIONS LLC (FORMERLY KNOWN AS OCTEL COMMUNICATIONS CORPORATION); VPNET TECHNOLOGIES, INC.
Reel/Frame 044893/0531 →
THIRD AMENDED AND RESTATED PATENT AND TRADEMARK SECURITY AGREEMENT Recorded Oct 31, 2017
From: EXTREME NETWORKS, INC.
To: SILICON VALLEY BANK
Reel/Frame 044639/0300 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 15, 2017
From: AVAYA INC.; AVAYA COMMUNICATION ISRAEL LTD; AVAYA HOLDINGS LIMITED
To: EXTREME NETWORKS, INC.
Reel/Frame 043569/0047 →
SECOND AMENDED AND RESTATED PATENT AND TRADEMARK SECURITY AGREEMENT Recorded Jul 14, 2017
From: EXTREME NETWORKS, INC.
To: SILICON VALLEY BANK
Reel/Frame 043200/0614 →
SECURITY INTEREST Recorded Jan 27, 2017
From: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS INC.; OCTEL COMMUNICATIONS CORPORATION; VPNET TECHNOLOGIES, INC.
To: CITIBANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 041576/0001 →
SECURITY AGREEMENT Recorded Mar 13, 2013
From: AVAYA, INC.
To: BANK OF NEW YORK MELLON TRUST COMPANY, N.A., THE
Reel/Frame 030083/0639 →
SECURITY AGREEMENT Recorded Jan 10, 2013
From: AVAYA, INC.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Reel/Frame 029608/0256 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 29, 2011
From: KEESARA, SRIKANTH
To: AVAYA INC.
Reel/Frame 026200/0354 →