Source: https://patents.google.com/patent/US8605735B2/en
Timestamp: 2019-09-17 03:33:14
Document Index: 527971963

Matched Legal Cases: ['Application No. 60', 'Application No. 07846021', 'application No. 07846180', 'application No. 07846180', 'application No. 07846181', 'application No. 07846181']

US8605735B2 - Method of supporting an open provider backbone network - Google Patents
US8605735B2
US8605735B2 US13/396,895 US201213396895A US8605735B2 US 8605735 B2 US8605735 B2 US 8605735B2 US 201213396895 A US201213396895 A US 201213396895A US 8605735 B2 US8605735 B2 US 8605735B2
US13/396,895
US20120147896A1 (en
2007-01-16 Priority to US88516807P priority Critical
2007-10-17 Priority to US11/873,560 priority patent/US8149837B2/en
2012-02-15 Application filed by FutureWei Technologies Inc filed Critical FutureWei Technologies Inc
2012-02-15 Priority to US13/396,895 priority patent/US8605735B2/en
2012-06-14 Publication of US20120147896A1 publication Critical patent/US20120147896A1/en
2013-09-10 Assigned to FUTUREWEI TECHNOLOGIES, INC. reassignment FUTUREWEI TECHNOLOGIES, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: DUNBAR, LINDA, SULTAN, ROBERT, YONG, LUCY
2013-12-10 Publication of US8605735B2 publication Critical patent/US8605735B2/en
This application is a divisional of U.S. patent application Ser. No. 11/873,560 filed Oct. 17, 2007, which claims priority to U.S. Provisional Patent Application No. 60/885,168 filed Jan. 16, 2007 by Yong et al. and entitled “Method of Multiplexing Parallel S and B Interfaces of a Backbone Edge Bridge on a Single Interface,” both of which are incorporated herein by reference as if reproduced in their entireties. The present application includes subject matter related to U.S. patent application Ser. No. 11/691,556 filed Mar. 27, 2007 by Sultan et al. and entitled “Method of Preventing Transport Leaks in Hybrid Switching Networks,” now abandoned, and U.S. patent application Ser. No. 11/691,558 filed Mar. 27, 2007 by Sultan et al. and entitled “Method of Detecting Transport Leaks in Hybrid Switching Networks”, now abandoned, both of which are incorporated herein by reference as if reproduced in their entireties.
Modern communication and data networks are comprised of nodes that transport data through the network. The nodes may include routers, switches, and/or bridges that transport the individual data frames and/or packets through the network. A service provider may offer data transport services to customers to promote linking of otherwise disparate and segregated local area networks (LANs). Virtual Local Area Networks (VLANs) may use a VLAN identifier (VID) to associate data frames together.
One type of network is a provider bridged network (PBN). A PBN may transport data between a customer and a communication network. PBNs may comply with an Institute of Electrical and Electronics Engineers (IEEE) 802.1ad standard and may employ a 12-bit VID. A PBN may comprise provider edge bridges (PEBs) at the edges of the network and provider bridges (PBs) in the core of the network. A PBN may also comprise other communication nodes.
Another type of network is a provider backbone bridge network (PBBN). A PBBN may be a core network that transports data between PBNs. PBBNs may comply with an IEEE 802.1ah standard and may employ a 24-bit Service Instance Identifier (ISID), thereby promoting a substantially larger pool of unique Service Instances than may be supported by the 12-bit VID associated with the PBNs. A PBBN may comprise provider backbone edge bridges (BEBs) and provider backbone core bridges (BCBs). PBBNs may provide an Ethernet-like mechanism for interconnecting PBNs, which structures the network hierarchically and promotes end-to-end bridged networks that support low cost, low configuration effort network solutions.
In a third aspect, the disclosure includes a method comprising migrating a first PBN comprising a plurality of service provider VLAN (S-VLAN) bridges to an open provider backbone network comprising a second PBN comprising some of the S-VLAN bridges and a PBBN comprising the remaining S-VLAN bridges, wherein at least one of the S-VLAN bridges at an edge of the PBBN is converted to a BEB and at least one of the S-VLAN bridges at the edge of the PBBN remains as a S-VLAN bridge.
FIG. 2 illustrates a PBBN 112 used to provide an interconnection service for PBNs 102A, 102B, 102C, 102D. The PBBN 112, which may be configured as defined in IEEE 802.1ah, contains BEBs 114A, 114B, 114C, 114D and BCBs 120A, 120B, 120C. Because the BCBs 120A, 120B, 120C are structurally similar to PBs 106A, 106B, 106C, the BCBs 120A, 120B, 120C may be referred to as S-VLANs bridges as well. A service instance transiting the PBBN 112 may be mapped to one of the backbone VLANs (B-VLANs) 118A, 118B (sometimes called backbone service instances), which has a larger identifier space than an S-VLAN 108A, 108B. Each such service instance is mapped to one of the Backbone VLANs (B-VLANs) 118A, 118B at the BEBs 114A, 114B, 114C, 114D. This method allows a large number of service instances to be supported by the PBBN 112. As explained below, traffic transiting the PBBN 112 may also be encapsulated with Backbone Media Access Control (MAC) Addresses (B-tagged) to reduce the number of MAC Addresses to which a BCB 120A, 120B, 120C must have visibility, and to isolate the PBBN 112 from sensitivity to customer MAC addresses. B-tagged traffic may still contain an S-tag, but the S-tag is not read by the nodes within the PBBN 112.
FIG. 3 illustrates a PBN 102A comprising a plurality of PBs 106A, 106B, 106C, 106D, 106E, 106F, 106G, 106H, 1061, 106J, 106K, 106L, 106M. Sometimes it is desirable to partition the single PBN 102A into a plurality of smaller PBNs 102B, 102C, 102D, 102E interconnected across a single PBBN 112, particularly when the PBN 102A is relatively large. This allows the nodes within the core of the PBBN 112 to support a larger number of service instances than could be supported by the single PBN 102A. Because both the PBs 106 and the BCBs 120 are S-VLAN bridges, the migration may require only minimal or no modification to PB 106D for PB 106D to become BCB 120. However, this migration may require that the PBs 106C, 106E, 106K at the edge of the newly formed PBBN 112 be replaced by BEBs 114A, 114B, 114C.
When the various nodes are upgraded, the changes are commonly made in increments. Specifically, FIG. 4 illustrates that PBs 106C, 106K have been replaced with BEBs 114A, 114C, but PB 106E remains. Such incremental implementation may reduce the time during which traffic is disrupted and avoid the expense of requiring technicians to be dispatched concurrently to multiple locations. The incremental implementation may also be necessitated by budgetary constraints. In many cases, the transition from PBs 106C, 106E, 106K to BEBs 114A, 114B, 114C is simplified because the BEBs 114A, 114B, 114C are required to perform all the functions of the S-VLAN bridges that they replace, e.g. PBs 106C, 106E, and 106K. Thus, when BEB 114A replaces PB 106C, BEB 114A can exchange B-tagged 118 traffic with BEB 114C and can concurrently exchange non-backbone-encapsulated S-VLAN (S-tagged) 108A traffic with PB 106E. As such, the PBBN 112 supports both PBN and PBBN traffic, and may be referred to as an Open Provider Backbone (OPB) network.
The TPID 224 may be used to identify the forwarding type associated with the frame, and the B-VID 226 may be used to identify the VID associated with the frame. In an embodiment, the TPID 224 or B-VID 226 may be used to distinguish between traffic types, e.g. PBN traffic (bridged), PBBN traffic (backbone bridged), and provider backbone bridged-traffic engineered (PBB-TE; switched). Specifically, PBN is non-backbone traffic, PBBN and PBB-TE are backbone traffic. For example, the value “88A8” in the TPID 224 field may indicate that the VID identified in the B-VID 226 field identifies a bridged VID. Similarly, other values such as “8100” or any other assigned value may indicate that the VID identified in the B-VID 226 field identifies a switched VID. If other forwarding types exist within the network, then the TPID 224 and the VID 226 fields may be used to associate the frames with those forwarding types. Persons of ordinary skill in the art are aware of other entries that can be used to associate one of the TPID 224 fields with the various forwarding types.
migrating a first provider bridged network (PBN) comprising a plurality of service provider virtual local area network (S-VLAN) bridges to an open provider backbone network comprising a second PBN comprising some of the S-VLAN bridges and a provider backbone bridged network (PBBN) comprising the remaining S-VLAN bridges,
wherein at least one of the S-VLAN bridges at an edge of the PBBN is converted to a backbone edge bridge (BEB) and at least one of the S-VLAN bridges at the edge of the PBBN remains as a S-VLAN bridge.
2. The method of claim 1, wherein the BEB directly communicates with the second PBN.
3. The method of claim 1, wherein the BEB comprises a customer network port and does not comprise a customer instance port.
4. The method of claim 1, wherein the BEB comprises a provider network port and does not comprise a provider backbone port.
5. The method of claim 1, wherein the BEB adds a first B-tag to the backbone traffic before the backbone traffic is transmitted over the PBBN, and wherein the BEB removes a second B-tag from any backbone traffic received from the PBBN.
6. The method of claim 1, wherein the BEB is configured to transmit multiplexed backbone and non-backbone traffic on a provider network port (PNP), wherein the B-tags are added to backbone traffic that will be transmitted on the PNP, and wherein the B-tags are removed from the backbone traffic that is received on the PNP.
7. The method of claim 1, wherein the BEB does not add any B-tags to the any traffic before the traffic is transmitted over the PBN.
8. The method of claim 1, wherein converting the S-VLAN bridge at the edge of the PBBN comprises replacing the S-VLAN bridge at the edge of the PBBN with the BEB.
9. The method of claim 1, wherein BEB is configured to transmit multiplexed backbone and non-backbone traffic on a customer network port.
a processor coupled to the memory, wherein the memory includes instructions that when executed by the processor cause the network component to perform the following:
migrate a first provider bridged network (PBN) comprising a plurality of service provider virtual local area network (S-VLAN) bridges to an open provider backbone network comprising a second PBN comprising some of the S-VLAN bridges and a provider backbone bridged network (PBBN) comprising the remaining S-VLAN bridges,
11. The network component of claim 10, wherein the BEB directly communicates with the second PBN.
12. The network component of claim 11, wherein the BEB comprises a customer network port and does not comprise a customer instance port.
13. The network component of claim 11, wherein the BEB comprises a provider network port and does not comprise a provider backbone port.
14. The network component of claim 11, wherein the BEB comprises a provider network port, a provider backbone port, and a customer instance port.
15. The network component of claim 10, wherein the BEB adds a first B-tag to the backbone traffic before the backbone traffic is transmitted over the PBBN, and wherein the BEB removes a second B-tag from any backbone traffic received from the PBBN.
16. The network component of claim 10, wherein the BEB is configured to transmit multiplexed backbone and non-backbone traffic on a provider network port (PNP), wherein the B-tags are added to backbone traffic that will be transmitted on the PNP, and wherein the B-tags are removed from the backbone traffic that is received on the PNP.
17. The network component of claim 10, wherein the BEB does not add any B-tags to the any traffic before the traffic is transmitted over the PBN.
18. The network component of claim 10, wherein converting the S-VLAN bridge at the edge of the PBBN comprises replacing the S-VLAN bridge at the edge of the PBBN with the BEB.
19. The network component of claim 10, wherein BEB is configured to transmit multiplexed backbone and non-backbone traffic on a customer network port.
modifying a provider bridged network (PBN) such that it transmits a plurality of frames over a provider backbone bridged network (PBBN) that comprises a PBBN Virtual Local Area Network (VLAN) space,
US13/396,895 2007-01-16 2012-02-15 Method of supporting an open provider backbone network Active 2028-02-14 US8605735B2 (en)
US88516807P true 2007-01-16 2007-01-16
US11/873,560 US8149837B2 (en) 2007-01-16 2007-10-17 Method of supporting an open provider backbone network
US13/396,895 US8605735B2 (en) 2007-01-16 2012-02-15 Method of supporting an open provider backbone network
US11/873,560 Division US8149837B2 (en) 2007-01-16 2007-10-17 Method of supporting an open provider backbone network
US20120147896A1 US20120147896A1 (en) 2012-06-14
US8605735B2 true US8605735B2 (en) 2013-12-10
US11/873,560 Active 2029-08-29 US8149837B2 (en) 2007-01-16 2007-10-17 Method of supporting an open provider backbone network
US13/396,895 Active 2028-02-14 US8605735B2 (en) 2007-01-16 2012-02-15 Method of supporting an open provider backbone network
US20090109848A1 (en) 2005-03-08 2009-04-30 Kunio Hato Flooding reduction method
KR100354245B1 (en) 1999-06-30 2002-09-28 삼성에스디아이 주식회사 Tension mask for a CRT
2007-10-17 US US11/873,560 patent/US8149837B2/en active Active
2007-12-05 EP EP07846021.9A patent/EP2100412B1/en active Active
2007-12-05 WO PCT/CN2007/071172 patent/WO2008086719A1/en active Application Filing
2012-02-15 US US13/396,895 patent/US8605735B2/en active Active
Foreign Communication From A Counterpart Application, European Application No. 07846021.9, Office Action dated Nov. 16, 2012, 5 pages.
Foreign Communication From a Related Counterpart Application, PCT Application PCT/CN2007/071172, International Search Report dated Mar. 20, 2008, 8 pages.
Foreign Communication From a Related Counterpart Application, PCT Application PCT/CN2007/071172, Written Opinion dated Mar. 20, 2008, 7 pages.
Foreign Communication From a Related Counterpart Application, PCT Application PCT/CN2007/071354, International Search Report dated Apr. 10, 2008, 6 pages.
Foreign Communication From a Related Counterpart Application, PCT Application PCT/CN2007/071354, Written Opinion dated Apr. 10, 2008, 4 pages.
Foreign Communication From a Related Counterpart Application, PCT Application PCT/CN2007/071355, International Search Report dated Apr. 3, 2008, 4 pages.
Foreign Communication From a Related Counterpart Application, PCT Application PCT/CN2007/071355, Written Opinion dated Apr. 3, 2008, 5 pages.
Foreign Communication From a Related Counterpart Application-Supplementary European Search Report, EP application No. 07846180.3, Aug. 24, 2009, 5 pages.
Foreign Communication From a Related Counterpart Application—Supplementary European Search Report, EP application No. 07846180.3, Aug. 24, 2009, 5 pages.
Foreign Communication From a Related Counterpart Application-Supplementary European Search Report, EP application No. 07846181.1, Aug. 24, 2009, 3 pages.
Foreign Communication From a Related Counterpart Application—Supplementary European Search Report, EP application No. 07846181.1, Aug. 24, 2009, 3 pages.
LAN/MAN Standards Committee of the IEEE Computer Society, "IEEE Standard for Local and metropolitan area networks: Virtual Bridged Local Area Networks—Amendment 4: Provider Bridges," IEEE Std 802.1ad™-2005, May 26, 2006, 74 pgs. (Front cover (2); i-xii; 1-60).
Maarten, Vissers, "Ethernet Transport Interfaces 1.5Mbitt/s to 10Tbit/s," IEEE 802 LAN/MAN Standards Committee, URL: http://www.ieee802.org/1/files/public/docs2006/ah-vissers-802.1-pb-pbb-models-1006.ppt, 4 pages.
Notice of Allowance dated Jan. 3, 2012, U.S. Appl. No. 11/873,560, 7 pages.
Office Action dated Apr. 15, 2009, U.S. Appl. No. 11/691,556, filed Mar. 27, 2007, 25 pages.
Office Action dated Apr. 16, 2009, U.S. Appl. No. 11/691,558, filed Mar. 27, 2007, 21 pages.
Office Action dated Aug. 4, 2011, U.S. Appl. No. 11/873,560-6 pages.
Office Action dated Aug. 4, 2011, U.S. Appl. No. 11/873,560—6 pages.
Office Action dated Jan. 15, 2010, U.S. Appl. No. 11/873,560-19 pages.
Office Action dated Jan. 15, 2010, U.S. Appl. No. 11/873,560—19 pages.
Office Action dated Jun. 29, 2010, U.S. Appl. No. 11/873,560-22 pages.
Office Action dated Jun. 29, 2010, U.S. Appl. No. 11/873,560—22 pages.
Office Action dated Mar. 2, 2011, U.S. Appl. No. 11/873,560-15 pages.
Office Action dated Mar. 2, 2011, U.S. Appl. No. 11/873,560—15 pages.
Sultan, R., et al., Provisional Application entitled "Method of Detecting Transport Leaks in Hybrid Switching Networks," U.S. Appl. No. 60/882,404, filed Dec. 28, 2006, 14 pages.
Wei, Cao, et al., et al. "IEEE 802.1ah Mode for Ethernet Over MPLS", draft-cao-pwe3-802-1ah-00.txt, Oct. 16, 2006, 10 pages.
EP2100412B1 (en) 2016-05-11
US20120147896A1 (en) 2012-06-14
US8149837B2 (en) 2012-04-03
WO2008086719A1 (en) 2008-07-24
EP2100412A1 (en) 2009-09-16
US20080170583A1 (en) 2008-07-17
EP2100412A4 (en) 2010-01-06
US8085676B2 (en) 2011-12-27 Method and system for looping back traffic in QIQ ethernet rings and 1:1 protected PBT trunks
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SULTAN, ROBERT;YONG, LUCY;DUNBAR, LINDA;REEL/FRAME:031175/0940