E-Trees over MPLS and PBB-TE networks
First Claim
1. A system, comprising:
- a root node associated with a Metro Ethernet network;
a first Virtual Bridge (VB), associated with the root node, configured to process Ethernet traffic using a first routing protocol;
a second node associated with the Metro Ethernet network;
a second VB, associated with the second node, configured to process Ethernet traffic and to allow interworking between at least the first routing protocol and a second routing protocol, the second routing protocol being substantially incompatible with the first routing protocol;
two or more third nodes associated with the Metro Ethernet network;
two or more third VBs associated with the third nodes, configured to process Ethernet traffic, wherein at least one of the third VBs is further configured to use the second routing protocol;
wherein all of the VBs are configured to facilitate communicative coupling between all of the nodes, such that the root node is communicatively coupled to the second node, and the second node is communicatively coupled to the two or more third nodes;
wherein the first VB is configured to permit transmission of Ethernet traffic from the root node to the two or more third nodes;
wherein the second VB is configured to;
permit transmission of Ethernet traffic from the root node to the two or more third nodes,prevent transmission of Ethernet traffic from one of the third nodes to another of the third nodes, andprocess Ethernet traffic addressed to the root node from one of the third nodes to determine whether to propagate transmission to the root node.
4 Assignments
0 Petitions
Accused Products
Abstract
An E-Tree is disclosed which includes a root node associated with a Metro Ethernet network. The E-Tree includes a first Virtual Bridge (VB), associated with the root node, which is configured to process Ethernet traffic, and a second node associated with the Metro Ethernet network. The E-Tree includes a second VB, associated with the second node, configured to process Ethernet traffic and having a first connection between the first VB and the second VB. The second VB is configured to be able to send Ethernet traffic to the first VB via the first connection, if appropriate. In the event there is a second connection between the second VB and a third VB and the second connection has been assigned a down direction from the point of view of the second VB, the second VB is not permitted to send traffic received from the second connection to another connection which from the point of view of the second VB has been assigned a down direction.
-
Citations
26 Claims
-
1. A system, comprising:
-
a root node associated with a Metro Ethernet network; a first Virtual Bridge (VB), associated with the root node, configured to process Ethernet traffic using a first routing protocol; a second node associated with the Metro Ethernet network; a second VB, associated with the second node, configured to process Ethernet traffic and to allow interworking between at least the first routing protocol and a second routing protocol, the second routing protocol being substantially incompatible with the first routing protocol; two or more third nodes associated with the Metro Ethernet network; two or more third VBs associated with the third nodes, configured to process Ethernet traffic, wherein at least one of the third VBs is further configured to use the second routing protocol; wherein all of the VBs are configured to facilitate communicative coupling between all of the nodes, such that the root node is communicatively coupled to the second node, and the second node is communicatively coupled to the two or more third nodes; wherein the first VB is configured to permit transmission of Ethernet traffic from the root node to the two or more third nodes; wherein the second VB is configured to; permit transmission of Ethernet traffic from the root node to the two or more third nodes, prevent transmission of Ethernet traffic from one of the third nodes to another of the third nodes, and process Ethernet traffic addressed to the root node from one of the third nodes to determine whether to propagate transmission to the root node. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22)
-
-
23. A method, comprising:
-
determining a set of nodes associated with a Metro Ethernet network, including a root node, a second node, and two or more third nodes; provisioning a first Virtual Bridge (VB), associated with the root node, configured to process Ethernet traffic using a first routing protocol; provisioning a second VB, associated with the second node, configured to process Ethernet traffic and to allow interworking between at least the first routing protocol and a second routing protocol, the second routing protocol being substantially incompatible with the first routing protocol; and provisioning two or more third VBs, associated with the two or more third nodes, configured to process Ethernet traffic, wherein at least one of the third VBs is further configured to use the second routing protocol; wherein all the VBs are configured to facilitate communicative coupling between all of the nodes, such that the root node is communicatively coupled to the second node, and the second node is communicatively coupled to the two or more third nodes; wherein the first VB is configured to permit transmission of Ethernet traffic from the root node to the two or more third nodes; wherein the second VB is configured to; permit transmission of Ethernet traffic from the root node to the two or more third nodes; prevent transmission of Ethernet traffic from one of the third nodes to another of the third nodes, and process Ethernet traffic addressed to the root node from one of the third nodes to determine whether to propagate transmission to the root node. - View Dependent Claims (24, 25, 26)
-
Specification