Presentation is loading. Please wait.

Presentation is loading. Please wait.

Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and functionality.

Similar presentations


Presentation on theme: "Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and functionality."— Presentation transcript:

1 Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and functionality in terms of 802.1Q modelling Maarten Vissers

2 Introduction E-OTN and PTN are multi domain, traffic engineered transport networks which support P2P, P2MP, RMP and MP2MP Ethernet services OTN network contains multiple OTN carrier networks OTN carrier networks contain OTN access, metro and core domains OTN network contains OTN network termination (NT), electrical switching and optical switching (SW) equipment OTN equipment at edge of domains is extended with Ethernet Switch functionality

3 EOTN example OTN Core OTN Metro OEO OE OCH XC N-degree ROADM ODU XC OEO OE OCH XC/ADM N-degree ROADM ODU XC OEO OCH XC N-degree ROADM OEO OE OCH XC N-degree ROADM ODU XC OEO OCH XC N-degree ROADM OEO OCH XC N-degree ROADM OEO OE OCH XC/ADM N-degree ROADM ODU XC OEO OE OCH XC/ADM N-degree ROADM ODU XC OEO OE OCH XC/ADM N-degree ROADM ODU XC OEO OCH XC/ADM N-degree ROADM OEO OCH XC/ADM N-degree ROADM OEO OCH XC/ADM N-degree ROADM OEO OCH XC/ADM N-degree ROADM NT OE OEO OE OCH XC N-degree ROADM ODU XC Ethernet Switch OE OEO OE OCH XC N-degree ROADM ODU XC Ethernet Switch OE NT OE OEO OE OCH XC N-degree ROADM ODU XC Ethernet Switch OE OEO OE OCH XC N-degree ROADM ODU XC Ethernet Switch OE NT OTN Network Termination Ethernet Network Termination Hybrid Ethernet & OTN Network Termination ODU OTN Access SW OTN/EOTN Switch MAC Relay functions interconnected via OTN ODU connections MAC Relay functions are interconnected via OTN ODU connections MAC Relay functions interconnected via OTN ODU connections MAC Relay functions are interconnected via OTN ODU connections or S- or I-Tagged LANs

4 Ethernet functionality in EOTN SW ETH VC MAC Relay function Includes support for G.8031 Ethernet SNC protection OTN Network Ports Ethernet MEP and MIP functions Includes support for Y.1731 Ethernet OAM and G.8021 OAM processing Ethernet to OTN (de)mapping functions: Support of the EISS Question: which Tag to use? Support of the ISS by additional technologies GFP-F/OTN Up MPs (6.17, 19.2, 19.3) Port filtering entities (8.6.1/2/4/5) Down MPs (6.17, 19.2, 19.3) Linktrace Output Multiplexer (19.5) Queuing entities (8.6.6/7/8) Support of the EISS Support of the ISS by additional technologies (6.15) OTN ODU Down MP GFP-F 6.9 like (VLAN Tag) or 6.18 like (I-Tag) ? Up MPs (6.17, 19.2, 19.3) Port filtering entities (8.6.1/2/4/5) Down MPs (6.17, 19.2, 19.3) Linktrace Output Multiplexer (19.5) Queuing entities (8.6.6/7/8) Support of the EISS Support of the ISS by additional technologies (6.15) OTN ODU Down MP Frame filtering (8.6.3) EISS ISS EISS ISS OTN other functions Bridge Port Transmit and Receive (8.5) not present Supports G.8031 SNC Protection OTNNETWORKPORTsOTNNETWORKPORTs Supports Y.1731 OAM

5 Ethernet functionality in EOTN SW ETH VC Tag choice ETH VC Tag with 12-bit ETH VC ID (VID); TPMR Reserved Address transparency; EtherType deals with ETH VC frames with network MAC addresses (N-DA, S-DA) I-Tag with 24-bit I-SID; UCA-bit deals with ETH VC frames with or without network MAC addresses (N-DA, S-DA) Either Tag is terminated in the Support of the EISS functions vlan_identifier parameter represents in EM_UNITDATA the 12- bit VC ID or 24-bit I-SID Existing devices already support ETH VC Tag with 12-bit VC ID; EtherType is configurable; 802.1Q to be extended with additional VLAN Tag type in clause 9.5 Reuse of clause 6.9 Support of the EISS possible TPID = xxxETH VC IDPCP DEI New VLAN Tag 4-octets TPID = 88-E7I-SIDPCP DEI I-Tag 18-octets RES2 2 UCA 1 RES1 1 DA SA

6 Connecting EOTN SW to PEB NT Operators will reuse existing PEB type NT nodes EOTN SW nodes are required to connect to such PEB NT Solution is to use PNP port in EOTN SW Up MPs (6.17, 19.2, 19.3) Port filtering entities (8.6.1/2/4/5) Down MPs (6.17, 19.2, 19.3) Linktrace Output Multiplexer (19.5) Queuing entities (8.6.6/7/8) Support of the EISS Support of the ISS by additional technologies (6.15) OTN ODU Down MP Up MPs (6.17, 19.2, 19.3) Port filtering entities (8.6.1/2/4/5) Down MPs (6.17, 19.2, 19.3) Linktrace Output Multiplexer (19.5) Queuing entities (8.6.6/7/8) Support of the EISS (6.9) Support of the ISS (6.7) MAC Frame filtering (8.6.3) EISS ISS EISS ISS OTN other functions PNPPNP PEB S-Tagged LAN OTNNETWORKPORTOTNNETWORKPORT

7 Connecting an EOTN SW to an I-BEB NT Operators will reuse existing I-BEB type NT nodes EOTN SW nodes are required to connect to such I-BEB NT Solution is to use a new port in EOTN, which terminates I- Tag Clause 16.8 like function provides this functionality Up MPs (6.17, 19.2, 19.3) Port filtering entities (8.6.1/2/4/5) Down MPs (6.17, 19.2, 19.3) Linktrace Output Multiplexer (19.5) Queuing entities (8.6.6/7/8) Support of the EISS Support of the ISS by additional technologies (6.15) OTN ODU Down MP Up MPs (6.17, 19.3) Port filtering entities (8.6.1/2/4/5) Down MPs (6.17, 19.3) Linktrace Output Multiplexer (19.5) Queuing entities (8.6.6/7/8) Support of the I-EISS (6.18 like) Support of the ISS (6.7) MAC Frame filtering (8.6.3) EISS ISS EISS ISS OTN other functions NEWPORTNEWPORT I-BEB I-Tagged LAN OTNNETWORKPORTOTNNETWORKPORT 6.18 terminates the I-Tag and provides N x ISS = EISS

8 Ethernet functionality in EOTN NT UNI-N or V-UNI-N interface ports UNI/V-UNI Facing Port (e.g. CEP, CNP, RCAP+PAP+CEP, RCAP+PAP+CNP, …) (V-)UNI LAN termination Ethernet MEP and MIP functions Service selection (MAC Relay) Ethernet VC Network Port (e.g. PEP+CNP, …) Traffic conditioning (c8.6.5) Service encapsulation Ethernet MEPs ETH VC MAC Relay function Includes support for G.8031 Ethernet SNC protection OTN Network Ports Ethernet MEP and MIP functions Ethernet to OTN (de)mapping functions: Support of the EISS Question: which Tag to use? Support of the ISS by additional technologies GFP-F/OTN

9 Ethernet functionality in EOTN NT Up MPs (6.17, 19.2, 19.3) Port filtering entities (8.6.1/2/4/5) Down MPs (6.17, 19.2, 19.3) Linktrace Output Multiplexer (19.5) Queuing entities (8.6.6/7/8) Support of the EISS Support of the ISS by additional technologies (6.15) OTN ODU Down MP Frame filtering (8.6.3) EISS ISS OTN other functions S-Tagged peering service Port-based peering or client/server service (*) CNP=CEP; CEP operates in c9.5a mode, CNP operates in c9.5b mode; CEP can be operated in Transparent mode as well after disabling c6.9 CNP PEPCEP Frame filtering (8.6.3) CBP C-Tagged peering or client/server service S-Tagged peering or client/server service Transparent peering service (*) I-Tagged client/server service CNP PEP v2 CEP Frame filtering (8.6.3) C-Tagged, S-Tagged, Port- based and Transparent peering or client/server service (*) with optional MAC encapsulation PEPv2 is backwards compatible with PEP (6.14 or 6.7) MAC encaps (6.X) ISS (8.5) (6.9, 9.5) (8.6.1/2/4/5) ISS EISS ISS EISS 6.X MAC encapsulation shim inserts TYPE=89-10, N-SA, N-DA in a PEPv2 PEPv2PEPv2 CNP CEPPEP Frame filtering (8.6.3) RCAPPAP Frame filtering (8.6.3) C-Tagged peering or client/server service OTNNETWORKPORTOTNNETWORKPORT

10 Ethernet functionality in EOTN NT New dedicated MAC encapsulation function in a version 2 PEP Top part of PIP function (6.10) Separated from I-Tag encapsulation Separation enables alarm suppression Backwards compatible with existing PEP function P2P and P2MP services do not require MAC encapsulation RMP and MP2MP services may be better scalable when using MAC encapsulation; preferred mode of operation RMP and MP2MP services with one or more endpoints on PEB NTs can not deploy MAC encapsulation RMP and MP2MP services with one or more endpoints on I- BEB NTs must deploy MAC encapsulation in EOTN NT Version 2 PEPs can be deployed in PEB nodes as well

11 EOTN Summary EOTN requires a minimal extension of 802.1Q functions and ports OTN Network Port with additional Support of the EISS function supporting a Tag associated with TPMR Reserved Address transparency Version 2 PEP with MAC encapsulation function New I-Tagged LAN terminating port with a clause 6.18 based Support of the EISS function to interconnect EOTN SW with I-BEB NT

12 PTN PTN network contains multiple PTN carrier networks PTN carrier networks contain PTN access, metro and core domains PTN network contains PTN network termination (NT), VC switching (VC SW) and VP switching (VP SW) equipment

13 Backup

14 TPID = xxxETH VC IDPCP DEI New VLAN Tag 4-octets TPID = 88-A8S-/B-VLAN IDPCP DEI S-VLAN Tag 4-octets TPID = 88-E7I-SIDPCP DEI I-Tag 18-octets RES2 2 UCA 1 RES1 1 DA SA GFP-F header 8-octets PLI 16 tHEC UPIPTI PFII cHEC EXI 4 header formats


Download ppt "Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and functionality."

Similar presentations


Ads by Google