SlideServe
Menu
Préférences
© SlideServe · v2026

Overview of MECP: Mechanisms for Ethernet Connection Protection in Multipoint Networks

ave avatar
10 diapositives · 239 Views · Aug 21, 2014

The Joint IEEE-SA and ITU Workshop presents an overview of the Multipoint Ethernet Connection Protection (MECP) initiative led by Taesik Cheung, Principal Researcher at ETRI. MECP focuses on safeguarding single-rooted multipoint Ethernet connections in transport networks. It explores mechanisms based on G.8031 APS protocol to provide 1+1 and 1:1 protection strategies. The potential applications for MECP include mobile backhaul and administrative networks. The workshop emphasizes architecture discussions around per-leaf and per-tree protection methods, including monitoring approaches and trade-offs.

Overview of MECP: Mechanisms for Ethernet Connection Protection in Multipoint Networks - slide 1
01 / 10Overview of MECP: Mechanisms for Ethernet Connection Protection in Multipoint Networks
1 / 17

Télécharger la présentation

Overview of MECP: Mechanisms for Ethernet Connection Protection in Multipoint Networks
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation
  1. Joint IEEE-SA and ITU Workshop on Ethernet Multipoint Ethernet ConnectionProtection (MECP) Taesik Cheung Principal Researcher ETRI

  2. MECP Overview • MECP is a study point of Q9/WP3. • Scope of MECP is to protect single rooted-multipoint (RMP) Ethernet connections in Ethernet transport networks. • Contributions have been provided for a mechanism based on G.8031 APS protocol to support • 1+1 and 1:1 protection • Per-tree and per-leaf protection

  3. Problem Statements n x APS instances Root X Switch Switch Leaf 1 Leaf 2 Leaf 3 Leaf n • In case of a failure affecting many leaf nodes, there may be a need for many (R)-APS instances to switch-oversimultaneously. n x R-APS instances Root Switch Switch Leaf 1 Leaf 2 Leaf 3 Leaf n G.8031 (APS) or G.8032 (R-APS) can be used between root and each leaf node. Root node should process multiple (R)-APS instances.

  4. Use Cases of MECP • MECP could be used to protect RMP connections in a tree network topology. • Potential use cases: • Mobile backhaul networks • Administrative networks of provincial government (Connection between leaf nodes is not allowed.) PTS Single MECP instance Working tree Protection tree Aggr. Aggr. DU(1) DU(2) DU(3) DU(m) PTS: Packet Transport Switch, Aggr.: Aggregation switch, DU: Digital Unit

  5. Per-tree Protection • A working tree is protected by a dedicated protection tree. L1 Working tree L2 R A single failure on the working tree which affects only a portion of the leaf nodes causes the whole traffic flowing on the working tree to be switched to the protection tree. Protection tree Lm L1 X Working tree L2 R Protection tree Lm

  6. Per-leaf Protection • A working tree is protected by a dedicated protection tree. L1 Working tree L2 R Protection tree In the event of a failure on the working tree, per-leaf protection switches over the traffic that belongs to the affected leaf node. Lm L1 X Working tree L2 R Protection tree Lm

  7. A proposal tobase MECP protocol on G.8031 West node East node B S Working P2P EC S B APS Protection P2P EC B: Bridge S: Selector APS NR(0,0) NR(0,0) SF detected on working path Set bridge/selector to protection path 1-phase APS Protocol SF(1,1) Send request Accept request Set bridge/selector to protection path NR(1,1) Send confirmation

  8. Per-tree protection architecture Root node Leaf node (1) B S S B APS(R) APS(L1) Leaf node (2) Root node has one bridge and one selector. Each leaf node has one bridge and one selector. Root node sends identical APS messages to all the leaf nodes. (using multicast DA) Each leaf node sends APS messages to the root node. S B Protection RMP EC APS(L2) Working RMP EC Leaf node (m) S B APS(Lm)

  9. Per-leaf protection architecture Root node Leaf node (1) W N Wr B S P W1~Wm Selector bridge B Pr APS(R) S W P1~Pm N P APS(L1) Broadcast bridge Leaf node (2) Root node has one broadcastbridge and multiple selectors. Each leaf node has one bridge and one selector. Root node sends different APS messages to each leaf nodes. (using unicast DA) Each leaf node sends APS messages to the root node. S B Protection RMP EC APS(L2) Working RMP EC Leaf node (m) S B APS(Lm) Wr: Working tree (root  all leaves) Pr: Protection tree (root  all leaves) Wm: Working path (leaf m  root) Pm: Protection path (leaf m  root)

  10. Issues under discussion • Architecture and mechanism for per-leaf protection • Consideration on various triggers for per-tree protection • Benefits of per-tree protection comparing with per-leaf protection • Monitoring methods for working/protection tree • Trade-off in terms of processing/management of per-tree protection vs. using N APS/R-APS processes