IP Library Granted Patent US 9,100,269
Granted Patent B2
US 9,100,269 · App. 12/259,560 · Granted Aug 4, 2015

Provisioned provider link state bridging (PLSB) with routed back-up

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 9,100,269
App. No.
12/259,560
Granted
Aug 4, 2015
Kind
B2
Abstract

A method of managing traffic flow in a packet network. A working sub-network is provided, which comprises one or more provisioned static working paths between at least one source node and one or more destination nodes in the network, and the working sub-network with a service instance. A backup sub-network is provided, which comprises one or more dynamic protection paths between the at least one source node and the one or more destination nodes, and the backup sub-network associated with the service instance. During a normal operation of the network, forwarding subscriber traffic associated with the service instance through the network using the working sub-network. Following detection of a network failure affecting the service instance, the subscriber traffic associated with the service instance is switched for forwarding through the network using the backup sub-network.

Claims (26)

1. A method of managing traffic flow in a packet network, the method comprising:

providing a working sub-network comprising one or more provisioned static working paths between at least one source node and one or more destination nodes in the network, and associating a service instance with the working sub-network;

providing a dynamic backup sub-network comprising one or more dynamically maintained protection paths between the at least one source node and the one or more destination nodes, and associating the service instance with the dynamic backup sub-network;

during a normal operation of the network, forwarding subscriber traffic associated with the service instance through the network using the working sub-network; and

following detection of a network failure affecting the service instance, switching the subscriber traffic associated with the service instance for forwarding through the network using the dynamic backup sub-network.

2. The method as claimed in claim 1 , wherein the working sub-network comprises a set of two or more static working paths provisioned between respective sets of source and destination nodes, and wherein, following detection of a network failure, the subscriber traffic being forwarded in each one of the set of two or more static working paths is switched for forwarding through corresponding dynamic protection paths of the dynamic backup sub-network.

3. The method as claimed in claim 1 , wherein, during normal operation of the network, respective forwarding state is installed in the network for both the static working paths and the dynamic protection paths.

4. The method as claimed in claim 3 , wherein forwarding traffic using the provisioned static working path comprises:

assigning a Backbone VLAN Identifier (B-VID) of the working sub-network to the subscriber traffic for the service instance, and

forwarding the subscriber traffic in accordance with the assigned B-VID.

5. The method as claimed in claim 4 , wherein switching the subscriber traffic of the service instance for forwarding using the backup sub-network comprises:

assigning a B-VID of the dynamic backup sub-network to the subscriber traffic; and

forwarding the subscriber traffic in accordance with the assigned B-VID.

6. The method as claimed in claim 1 , wherein providing the working sub-network comprises, for each provisioned working path of the working sub-network, installing respective state for the provisioned working path in a database of each node traversed by the provisioned working path, and wherein the state comprises information of a provisioned service instance identifier (I-SID) of the service.

7. The method as claimed in claim 6 wherein the information comprises the I-SID information encoded within a destination address of the provisioned working path.

8. The method as claimed in claim 6 wherein the information comprises a digest of two or more I-SIDs encoded within a data element associated with the provisioned working path.

9. The method as claimed in claim 8 wherein the digest is a bloom filter.

10. The method as claimed in claim 6 further comprising, at a node traversed by the provisioned working path:

detecting a network failure affecting at least one service; and

flooding a Link State Packet (LSP) containing the information of the provisioned service instance identifier (I-SID) of the at least one service.

11. The method as claimed in claim 10 , further comprising, at an edge node of the network:

receiving the LSP flooded by the node traversed by the provisioned working path; and

comparing the information contained in the received LSP to information of service instance identifiers (I-SIDs) of services hosted by the edge node, to identify any services hosted by the edge node that are affected by the detected network failure.

12. The method as claimed in claim 1 , further comprising providing a provisioned backup sub-network comprising one or more provisioned protection paths between the at least one source node and the one or more destination nodes in the network, and associating the service instance with the provisioned backup sub-network; and wherein:

following detection of a first network failure affecting the service instance, the subscriber traffic is forwarded using the provisioned backup sub-network; and

following detection of a second network failure affecting the service instance, the subscriber traffic is forwarded using the dynamic backup sub-network.

Assignments (8)
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 Mar 12, 2014
From: ROCKSTAR BIDCO, LP
To: ROCKSTAR CONSORTIUM US LP
Reel/Frame 032436/0804 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 28, 2011
From: NORTEL NETWORKS LIMITED
To: ROCKSTAR BIDCO, LP
Reel/Frame 027143/0717 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 28, 2008
From: ALLAN, DAVID; BRAGG, NIGEL; NASRALLAH, HADI; HUNNERUP, PREBEN
To: NORTEL NETWORKS LIMITED
Reel/Frame 021749/0338 →