WO2009136252A1 - Système et procédé de mise en œuvre de services dans un réseau d’ingénierie de trafic à pont de dorsale de fournisseur (pbb-te) - Google Patents

Système et procédé de mise en œuvre de services dans un réseau d’ingénierie de trafic à pont de dorsale de fournisseur (pbb-te) Download PDF

Info

Publication number
WO2009136252A1
WO2009136252A1 PCT/IB2009/005477 IB2009005477W WO2009136252A1 WO 2009136252 A1 WO2009136252 A1 WO 2009136252A1 IB 2009005477 W IB2009005477 W IB 2009005477W WO 2009136252 A1 WO2009136252 A1 WO 2009136252A1
Authority
WO
WIPO (PCT)
Prior art keywords
backbone
frame
service instance
vid
service
Prior art date
Application number
PCT/IB2009/005477
Other languages
English (en)
Inventor
Balázs Peter GERO
Attila TAKÁCS
Original Assignee
Telefonaktiebolaget L M Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget L M Ericsson (Publ) filed Critical Telefonaktiebolaget L M Ericsson (Publ)
Publication of WO2009136252A1 publication Critical patent/WO2009136252A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4604—LAN interconnection over a backbone network, e.g. Internet, Frame Relay
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4604—LAN interconnection over a backbone network, e.g. Internet, Frame Relay
    • H04L12/462—LAN interconnection over a bridge based backbone
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]

Definitions

  • the present invention relates generally to communications networks, and in particular, to a system and method of implement services in a Provider Backbone Bridging Traffic Engineering (PBB-TE) network.
  • PBB-TE Provider Backbone Bridging Traffic Engineering
  • Backbone Bridge Traffic Engineering defines how to support provisioning systems that explicitly select traffic engineered paths within Provider Backbone Bridge Networks by allowing a network operator to disable unknown destination address forwarding and source address learning. In addition, Provider Backbone Bridge Traffic Engineering extends the operation of Connectivity Fault Management to support provisioned paths.
  • the Metro Ethernet Forum (MEF) which is independent of the IEEE PBB-TE 1 defines services that a bridge network should provide, such as a point-to-point Ethernet Virtual Connection (EFC) or multipoint-to-multipoint EVC.
  • EFC Ethernet Virtual Connection
  • PBB-TE offers transport tunnels between backbone edge bridges (BEB).
  • PBB-TE defines point-to-point and point- to-multipoint service instances.
  • a point-to-point PBB-TE service instance consists of two unidirectional point-to-point basic connectivity units called Ethernet Switched Paths (ESPs), one for each direction.
  • ESPs Ethernet Switched Paths
  • a point-to-multipoint service instance consists of a downstream multicast point-to-multipoint ESP and "n" upstream point-to-point ESPs.
  • BEBs assign a service identifier (I-SID) to traffic that arrives from customer networks. Services associated with the I-SID are multiplexed to transport tunnels. In particular, the transport tunnels support transferring traffic of more service instances identified by the I-SID.
  • MEF standardizes services that Ethernet service providers should offer to their customers. The standard types of MEF services are point-to-point (E- Line), multipoint-to-multipoint (E-LAN) and rooted multipoint (E-Tree). An E- Line service is between two provider-customer user network interfaces (UNIs). An E-LAN provides unicast, multicast and broadcast connectivity between all connected UNIs.
  • an E-Tree supports unicast and multicast connectivity from root UNIs to leaf UNIs and unicast connectivity from leaf UNIs to root UNIs.
  • the supported MEF services are not explicitly specified.
  • PBB-TE supports all MEF services that may be implemented by the mechanisms defined by the PBB-TE standard.
  • FIG. 1 is a simplified block diagram of a port structure 10 of a PBB-TE BEB 12.
  • Customer frames arrive to customer network ports (CNP) 14.
  • the frames are forwarded by an l-component (I-Comp) MAC relay entity 16 to internal Provider Instance Ports (PIPs) 18.
  • I-Comp l-component
  • PIPs Provider Instance Ports
  • the customer frames are encapsulated with an I-TAG. Specifically, the PIP adds the I-SID.
  • the PIP After adding the service identifier, the PIP encapsulates the frame with a backbone source MAC address (B-SA) and a backbone destination MAC address (B-DA).
  • B-SA is the MAC address of the BEB's Customer Backbone Port (CBP) 20
  • the B-DA is either a learned B-DA contained in the filtering database of the l-component 16 or it is the per I-SID default B-DA.
  • the B-DA is the MAC address of the CBP 20 of the BEB where the frame leaves the PBB-TE domain.
  • the PIP sends the untagged frame to a CBP. In the case of PBB-TE, the CBP and the connected PIP MAC address is the same.
  • the BEB also includes a B-Comp 22.
  • the CBP searches for the I-SID in the frame and adds a B-VID based on the Backbone Service Instance Table, which contains I-SID and B-VID mappings. Subsequently, the frames are forwarded through the B-Comp MAC relay 22 based on the B-VID and the B-DA only.
  • FIG. 2 is a simplified block diagram of B-VID assignments in an existing PBB-TE service instance.
  • the system includes a first ESP 30, a second ESP 32, a third ESP 34, a first BEB 36, a second BEB 38, and a third BEB 40.
  • the B-VIDs must be the same in all three ESPs if they are supporting a multipoint service identified by an I-SID.
  • PBB-TE defines protection mechanisms for point-to-point PBB-TE service instances.
  • a parallel backup point-to- point PBB-TE service instance is provisioned between the same two BEBs.
  • the active and the backup PBB-TE service instances are provisioned with the same B-SA, B-DA pairs, and only differ in the provisioned B-VID.
  • the B-VID in the backbone service instance table is overwritten for all involved l-SIDs. Specifically, traffic is switched to the protection PBB-TE service instance for all services (I-SID) that have used the failed PBB-TE tunnel.
  • I-SID all services
  • FIG. 3 illustrates a simplified block diagram of B-VID assignments during a protection switch of B-VID dependent TE service instances.
  • ESP 30 a single defect
  • all the ESPs 30, 32, and 34 change over to ESPs 130, 132, and 134.
  • MEF standard multipoint service such as E-LAN and E-Tree
  • B-VID allocation of ESPs that transfer MEF multipoint services is restricted.
  • the same B-VID has to be used in all outbound ESPs that transmit traffic of a given service (I-SID) as illustrated in FIG. 2.
  • protection switching swaps the B-VID in backbone service instance tables per I-SID. As a consequence of this, in the case of a defect of a single TE service instance, all TE service instances involved in transferring traffic of the I-SID are switched to the protection ESPs.
  • the present invention keeps protection switching of individual point-to- point TE service instances independent of how customer traffic, identified by the 1-SID, is mapped to transport tunnels.
  • the present invention allows unrestricted support of multipoint MEF services.
  • the present invention is directed to a method of implementing a service in a PBB-TE network.
  • the method begins by configuring a backbone service instance table in a Customer Backbone Port, CBP.
  • the table is provided with at least one backbone destination address, B- DA, and backbone VLAN identifier, B-VID, pair.
  • An incoming frame is then received by the CBP and processed.
  • the frame is multiplexed to a transport tunnel based on the configured backbone service instance table.
  • the present invention is directed to a system for implementing a service in a PBB-TE network.
  • the system includes a CBP for configuring a backbone service instance table.
  • the table has at least one B- DA and B-VID pair.
  • the CBP receives an incoming frame.
  • the frame is then processed.
  • the processed frame is then multiplexed to a transport tunnel based on the configured backbone service instance table.
  • the present invention is directed to a node for node for implementing a service in a PBB-TE, network.
  • the node includes a CBP for configuring a backbone service instance table.
  • the table has at least one B-DA and B-VID pair.
  • An incoming frame is received by the CBP and processed.
  • the processed frame is then multiplexed to a transport tunnel based on the configured backbone service instance table.
  • the node may be a Backbone Edge Bridge.
  • FIG. 1 (prior art) is a simplified block diagram of a port structure of a PBB-TE BEB;
  • FIG. 2 is a simplified block diagram of B-VID assignments in an existing PBB-TE service instance;
  • FIG. 3 illustrates a simplified block diagram of B-VID assignments during a protection switch of B-VID dependent TE service instances
  • FIG. 4 illustrates the operation of CBPs in an existing implementation
  • FIG. 5 illustrates the operation of CBPs in one embodiment of the present invention
  • FIG. 6A (prior art) illustrates a VLAN identifier field in the existing configuration
  • FIG. 6B illustrates a VLAN identifier field in one embodiment of the present invention.
  • FlG. 7 is a flow chart illustrating the steps of implementing a service in a PBB-TE network according to one embodiment of the present invention.
  • the present invention is a system and method of implementing services in a PBB-TE network.
  • FIG. 4 illustrates the operation of CBPs in an existing implementation.
  • the backbone service instance table is defined in a "Support of the EISS for CBPs" shim 100.
  • the Backbone Service Instance Table has one entry for each backbone service instance supported on the CBP.
  • the Backbone Service Instance Table's original purpose was to filter frames containing an I-SID value that is not configured on the specific customer backbone port.
  • the Backbone Service Instance Table may also be used to provide backbone service instance specific assignment of a B-VID, to translate I-SID values, and/or to translate backbone destination addresses.
  • Entries of the backbone service instance table include a backbone service instance identifier (Backbone-SID), a backbone VLAN identifier (B-VID), a local service instance identifier (Local-SID), and a default backbone destination (B-DAdefauit)-
  • Backbone-SID backbone service instance identifier
  • B-VID backbone VLAN identifier
  • Local-SID local service instance identifier
  • B-DAdefauit a default backbone destination
  • FIG. 6A illustrates a VLAN identifier field 300 in the existing configuration.
  • the VLAN identifier field 300 includes a backbone service instance identifier (Backbone-SID) 302, a backbone VLAN identifier (B-VID) 304, a local service instance identifier (Local-SID) 306, and a default backbone destination (B-DAdefauit) 308.
  • the present invention replaces the backbone VLAN identifier field with a list of B-DA/B-VID pairs.
  • FIG. 6B illustrates a VLAN identifier field 320 in one embodiment of the present invention.
  • the entries of the backbone service instance table include a backbone service instance identifier (Backbone-SID) 322, a default backbone VLAN identifier (B-VID de fauit) 324, a local service instance identifier (Local-SID) 36, a default backbone destination (B-DAdefaui t ) 328, a list of backbone destination address (B-DA) 330, and backbone VLAN identifiers (B-VID) pairs 332.
  • the default B-VID 324 may be used to map l-SIDs to Provider Backbone Bridge networks (PBBN) VLAN.
  • PBBN Backbone Bridge networks
  • FIG. 7 is a flow chart illustrating the steps of implementing a service in a PBB-TE network according to one embodiment of the present invention. With reference to FIGs. 5, 6B, and 7, the method of the present invention will now be explained.
  • the method begins in step 400 where a backbone service instance table is configured in a CBP with B-DA and B-VID pairs.
  • the revised backbone service instance table now contains a backbone service instance identifier (Backbone-SID) 322, a default backbone VLAN identifier (B- VID defa ui t ) 324, a local service instance identifier (Local-SID) 36, a default backbone destination (B-DA defa ui t ) 328, a list of backbone destination address (B-DA) 330, and backbone VLAN identifiers (B-VID) pairs 332.
  • Backbone-SID backbone service instance identifier
  • B- VID defa ui t a default backbone VLAN identifier
  • Local-SID local service instance identifier
  • B-DA defa ui t a default backbone destination
  • B-VID backbone VLAN identifiers
  • step 402 an incoming frame is received by a customer network port where the frame is processed.
  • the frame is forwarded by an l-component MAC relay entity to PIPs and encapsulated with an I-TAG, such as an I-SID.
  • step 404 the frame is sent to a CBP.
  • the I-SID for the frame is determined and a B-VID is added based on the backbone service instance table utilized in step 400.
  • step 408 the frame is forward through the B-Component MAC relay based on 1-SfD and B-VID/B-DA pairings.
  • step 410 the frame is multiplexed to a transport tunnel based on the pairings.
  • the present invention enables traffic mapped to an I-SID to be transferred through independent ESPs. This is possible because the B-VID is configured for I-SID and B-DA pairs.
  • the present invention supports independent protection switching of PBB-TE service instances supporting a multipoint service because the B-VID may be switched per I-SID and B-DA pair.
  • the present invention provides many advantages over existing systems.
  • the present invention refrains from utilizing protection paths unnecessarily and removes the restriction in B-VID allocation for multipoint MEF services.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente invention concerne un système et un procédé de mise en œuvre d’un service dans un réseau PBB-TE. Le procédé commence par la configuration d’une table d’instances de services de dorsale dans un port de dorsale client, CBP. La table comprend au moins une paire d’une adresse de destination de dorsale, B-DA, et d’un identifiant VLAN de dorsale, B-VID. Une trame entrante est ensuite reçue par le CBP et traitée. Ensuite, la trame est multiplexée vers un tunnel de transport sur la base de la table d’instances de services de dorsale configurée.
PCT/IB2009/005477 2008-05-08 2009-05-04 Système et procédé de mise en œuvre de services dans un réseau d’ingénierie de trafic à pont de dorsale de fournisseur (pbb-te) WO2009136252A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US5139308P 2008-05-08 2008-05-08
US61/051,393 2008-05-08

Publications (1)

Publication Number Publication Date
WO2009136252A1 true WO2009136252A1 (fr) 2009-11-12

Family

ID=40910027

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2009/005477 WO2009136252A1 (fr) 2008-05-08 2009-05-04 Système et procédé de mise en œuvre de services dans un réseau d’ingénierie de trafic à pont de dorsale de fournisseur (pbb-te)

Country Status (1)

Country Link
WO (1) WO2009136252A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010048697A1 (fr) * 2008-10-28 2010-05-06 Nortel Networks Limited Formation de pont à état de lien fournisseur (plsb) avec secours routé
WO2011072448A1 (fr) * 2009-12-17 2011-06-23 上海贝尔股份有限公司 Procédé et dispositif permettant de déterminer une règle de transmission de paquets de données

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1705840A1 (fr) * 2004-01-16 2006-09-27 Nippon Telegraph and Telephone Corporation Procede de transfert de trames mac d'utilisateurs, dispositif de transfert de bords, et programme
WO2007041860A1 (fr) * 2005-10-14 2007-04-19 Nortel Networks Limited Commande gmpls d'ethernet

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1705840A1 (fr) * 2004-01-16 2006-09-27 Nippon Telegraph and Telephone Corporation Procede de transfert de trames mac d'utilisateurs, dispositif de transfert de bords, et programme
WO2007041860A1 (fr) * 2005-10-14 2007-04-19 Nortel Networks Limited Commande gmpls d'ethernet

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
IEEE COMPUTER SOCIETY: "Provider Backbone Bridge Traffic Engineering", INTERNET CITATION, 15 February 2008 (2008-02-15), pages 1 - 114, XP002524603 *
SALAM S ET AL: "Provider backbone bridging and MPLS: complementary technologies for next-generation carrier ethernet transport", IEEE COMMUNICATIONS MAGAZINE, IEEE SERVICE CENTER, PISCATAWAY, US, vol. 45, no. 3, 1 March 2008 (2008-03-01), pages 77 - 83, XP011205400, ISSN: 0163-6804 *

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010048697A1 (fr) * 2008-10-28 2010-05-06 Nortel Networks Limited Formation de pont à état de lien fournisseur (plsb) avec secours routé
US9100269B2 (en) 2008-10-28 2015-08-04 Rpx Clearinghouse Llc Provisioned provider link state bridging (PLSB) with routed back-up
WO2011072448A1 (fr) * 2009-12-17 2011-06-23 上海贝尔股份有限公司 Procédé et dispositif permettant de déterminer une règle de transmission de paquets de données
CN102656847A (zh) * 2009-12-17 2012-09-05 上海贝尔股份有限公司 确定数据分组的转发规则的方法及装置
EP2515484A1 (fr) * 2009-12-17 2012-10-24 Alcatel Lucent Procédé et dispositif permettant de déterminer une règle de transmission de paquets de données
EP2515484A4 (fr) * 2009-12-17 2014-07-30 Alcatel Lucent Procédé et dispositif permettant de déterminer une règle de transmission de paquets de données
US9197550B2 (en) 2009-12-17 2015-11-24 Alcatel Lucent Method and device for determining forwarding rule for data packet

Similar Documents

Publication Publication Date Title
EP2417735B1 (fr) Permettre à un réseau en anneau ethernet de supporter de façon évolutive un modèle de connectivité en étoile
US9338052B2 (en) Method and apparatus for managing the interconnection between network domains
US9166929B1 (en) Performing scalable L2 wholesale services in computer networks using customer VLAN-based forwarding and filtering
US8837299B2 (en) Connectivity fault management in a provider backbone bridge traffic engineering (PBB-TE) domain
US8605735B2 (en) Method of supporting an open provider backbone network
US20080080535A1 (en) Method and system for transmitting packet
EP2053834A1 (fr) Procédé, réseau et dispositif nodal pour la retransmission de données dans un réseau à double couche
US20080019385A1 (en) System and method of mapping between local and global service instance identifiers in provider networks
US8549178B2 (en) Using provider backbone bridged network to reduce the number of media access control addresses visible to core bridges in the data center
US9893929B2 (en) Protection switching method and system for a multi-rooted point-to-multi-point service in a provider backbone bridge (PBB) network
US8594088B2 (en) Multicasting in a provider backbone bridge network
US8520680B1 (en) Address learning in a layer two bridging network
WO2009136252A1 (fr) Système et procédé de mise en œuvre de services dans un réseau d’ingénierie de trafic à pont de dorsale de fournisseur (pbb-te)
US8761034B2 (en) System and method of demultiplexing provider backbone bridging traffic engineering instances
US9258140B2 (en) Architecture for routing data of a customer network over provider's network in provider backbone bridges
Bottorf et al. Provider backbone transport overview
Lee et al. Autonomous client discovery in backbone edge bridges for multipoint PBB-TE networks
Gerö et al. Upgrading the metro ethernet network
Lee et al. Point-to-multipoint and multipoint-to-multipoint services on pbb-te system

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 09742425

Country of ref document: EP

Kind code of ref document: A1

DPE1 Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101)
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 09742425

Country of ref document: EP

Kind code of ref document: A1