IP Library Granted Patent US 8,027,347
Granted Patent B2
US 8,027,347 · App. 12/015,685 · Granted Sep 27, 2011

Border gateway protocol extended community attribute for layer-2 and layer-3 virtual private networks using 802.1ah-based tunnels

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,027,347
App. No.
12/015,685
Granted
Sep 27, 2011
Kind
B2
Abstract

Described are a network, network device, and method for a method of distributing routing information for a virtual private network (VPN) application through a packet-switched network (PSN) having fully meshed provider edge (PE) routers through Provider Backbone Bridge (PBB) tunnels. Each PE router is configured to support at least one VPN and to run a BGP (Border Gateway Protocol) as an auto-discovery process for finding one or more other PE routers attached to the same VPN. A given VPN is associated with a PBB tunnel. A service instance identifier (I-SID), as defined in IEEE 802.1 ah , is assigned to the VPN. Each PE router advertises membership in the VPN by including the I-SID assigned to the VPN in a BGP message issued during the auto-discovery process.

Claims (25)

1. A method of distributing routing information for a virtual private network (VPN) application through a packet-switched network (PSN) having a plurality of provider edge (PE) routers that are fully meshed through Provider Backbone Bridge (PBB) tunnels, the method comprising:

configuring each PE router to support at least one VPN and to run a BGP (Border Gateway Protocol) as an auto-discovery process for finding one or more other PE routers attached to a same VPN as that PE router;

associating a given VPN with a PBB tunnel;

assigning an I-component service instance identifier (I-SID) to the given VPN;

advertising, by at least one PE router, membership in the given VPN by including the I-SID assigned to the given VPN in a BGP message issued during the auto-discovery process.

2. The method of claim 1 , wherein the BGP message includes an Extended Community attribute for carrying the I-SID assigned to the given VPN.

3. The method of claim 1 , wherein the BGP message includes an Extended Community having a type field and a value field, the type field having a value signifying that the Extended Community is a Route Target, and wherein the value field carries the I-SID assigned to the given VPN.

4. The method of claim 1 , wherein the BGP message includes an Extended Community having a type field and a value field, the type field having a value signifying that the Extended Community is a PBB Community, and wherein the value field carries the I-SID assigned to the given VPN.

5. The method of claim 1 , further comprising the step of encapsulating packets belonging to the given VPN for forwarding through the PBB tunnel in a PBB header that includes the I-SID.

6. The method of claim 1 , further comprising the step of encapsulating packets belonging to the given VPN associated with the PBB tunnel in a PBT (Provider Backbone Transport) tunnel.

7. A packet-switched network comprising a plurality of provider edge (PE) routers fully meshed by Provider Backbone Bridge (PBB) tunnels, each PE router being configured to support a virtual private network (VPN) and to run a Border Gateway Protocol (BGP) as an auto-discovery mechanism for finding one or more other PE routers in the same VPN, the VPN being associated with one of the PBB tunnels and having an assigned I-component service instance identifier (I-SID), each PE router advertising membership in the VPN by including the I-SID assigned to the VPN in a BGP message issued during the auto-discovery process.

8. The network of claim 7 , wherein the BGP message includes an Extended Community attribute for carrying the I-SID assigned to the VPN.

9. The network of claim 7 , wherein the BGP message includes an Extended Community having a type field and a value field, the type field having a value signifying that the Extended Community is a Route Target, and wherein the value field carries the I-SID assigned to the VPN.

10. The network of claim 7 , wherein the BGP message includes an Extended Community having a type field and a value field, the type field having a value signifying that the Extended Community is a PBB Community, and wherein the value field carries the I-SID assigned to the VPN.

11. The network of claim 7 , wherein one of the PE routers encapsulates packets belonging to the VPN for forwarding through the PBB tunnel in a PBB header that includes the I-SID.

12. The network of claim 7 , wherein one of the PE routers encapsulates packets belonging to the given VPN associated with the PBB tunnel in a PBT (Provider Backbone Transport) tunnel.

13. A provider edge (PE) router configured to support a virtual private network (VPN) over a packet-switched network through an Provider Backbone Bridge (PBB) tunnel, the PE router comprising:

a service processor assigning an I-component service instance identifier (I-SID) to the VPN;

memory storing a mapping of the VPN to the PBB tunnel and program code with computer-readable instructions for performing a Border Gateway Protocol (BGP) auto-discovery process for finding one or more other PE routers in the same VPN; and

a processor executing the computer-readable instructions to produce a BGP message that includes the I-SID assigned to the VPN in order to advertise membership in the VPN during the auto-discovery process.

14. The PE router of claim 13 , wherein the BGP message includes an Extended Community attribute for carrying the I-SID assigned to the VPN.

15. The PE router of claim 13 , wherein the BGP message includes an Extended Community having a type field and a value field, the type field having a value signifying that the Extended Community is a Route Target, and wherein the value field carries the I-SID assigned to the VPN.

16. The PE router of claim 13 , wherein the BGP message includes an Extended Community having a type field and a value field, the type field having a value signifying that the Extended Community is a PBB Community, and wherein the value field carries the I-SID assigned to the VPN.

17. The PE router of claim 13 , further comprising an encapsulator encapsulating packets belonging to the VPN for forwarding through the PBB tunnel in a PBB header that includes the I-SID.

18. The PE router of claim 17 , wherein the encapsulator further encapsulates the packets belonging to the VPN in a PBT (Provider Backbone Transport) header.

Assignments (6)
RELEASE OF SECURITY INTEREST Recorded Oct 26, 2020
From: JEFFERIES FINANCE LLC
To: RPX CLEARINGHOUSE LLC
Reel/Frame 054305/0505 →
SECURITY INTEREST Recorded Jun 29, 2018
From: RPX CLEARINGHOUSE LLC
To: JEFFERIES FINANCE LLC
Reel/Frame 046485/0644 →
RELEASE (REEL 038041 / FRAME 0001) Recorded Jan 2, 2018
From: JPMORGAN CHASE BANK, N.A.
To: RPX CORPORATION; RPX CLEARINGHOUSE LLC
Reel/Frame 044970/0030 →
SECURITY AGREEMENT Recorded Mar 9, 2016
From: RPX CORPORATION; RPX CLEARINGHOUSE LLC
To: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
Reel/Frame 038041/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 9, 2015
From: ROCKSTAR CONSORTIUM US LP; ROCKSTAR CONSORTIUM LLC; BOCKSTAR TECHNOLOGIES LLC; CONSTELLATION TECHNOLOGIES LLC; MOBILESTAR TECHNOLOGIES LLC; NETSTAR TECHNOLOGIES LLC
To: RPX CLEARINGHOUSE LLC
Reel/Frame 034924/0779 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 28, 2011
From: NORTEL NETWORKS LIMITED
To: ROCKSTAR BIDCO, LP
Reel/Frame 027143/0717 →