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 - PowerPoint PPT Presentation

About This Presentation
Title:

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

Description:

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

Number of Views:19
Avg rating:3.0/5.0
Slides: 15
Provided by: MVis5
Learn more at: https://www.ieee802.org
Category:

less

Transcript and Presenter's Notes

Title: 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


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

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 Access
NT
OTN Metro
ODU XC
OE
OE
NT
OE
OE
OE
OE
OTN Core
OEO
OCH XC/ADM N-degree ROADM
OEO
OEO
NT
ODU XC
OE
OE
NT
OE
OE
OE
OE
OEO
OCH XC N-degree ROADM
OEO
NT
OEO
NT
OTN Metro
NT
ODU XC
OE
OE
ODU XC
OE
OE
OE
OE
OE
OE
OEO
OCH XC/ADM N-degree ROADM
NT
OEO
OE
OE
OE
OE
OEO
OEO
OCH XC N-degree ROADM
OEO
OEO
NT
Ethernet Network Termination
Hybrid Ethernet OTN Network Termination
OTN/EOTN Switch
NT
OTN Network Termination
NT
NT
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

Frame filtering (8.6.3)
Supports G.8031 SNC Protection
Up MPs (6.17, 19.2, 19.3)
Up MPs (6.17, 19.2, 19.3)
O T N N E T W O R K P O R T s
Port filtering entities (8.6.1/2/4/5)
Port filtering entities (8.6.1/2/4/5)
Supports Y.1731 OAM
Down MPs (6.17, 19.2, 19.3)
Down MPs (6.17, 19.2, 19.3)
Linktrace Output Multiplexer (19.5)
Linktrace Output Multiplexer (19.5)
6.9 like (VLAN Tag) or 6.18 like (I-Tag) ?
Queuing entities (8.6.6/7/8)
Queuing entities (8.6.6/7/8)
Support of the EISS
Support of the EISS
Bridge Port Transmit and Receive (8.5) not present
Support of the ISS by additional technologies
(6.15)
Support of the ISS by additional technologies
(6.15)
GFP-F
OTN ODU Down MP
OTN ODU Down MP
OTN other functions
OTN other functions
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 89-10
    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

16
3
1
12
TPID xxx
ETH VC ID
PCP
DEI
New VLAN Tag 4-octets
16
3
1
24
2
1
1
TPID 88-E7
I-SID
PCP
DEI
I-Tag 18-octets
RES2
UCA
RES1
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

Frame filtering (8.6.3)
Up MPs (6.17, 19.2, 19.3)
Up MPs (6.17, 19.2, 19.3)
O T N N E T W O R K P O R T
Port filtering entities (8.6.1/2/4/5)
Port filtering entities (8.6.1/2/4/5)
Down MPs (6.17, 19.2, 19.3)
Down MPs (6.17, 19.2, 19.3)
P N P
Linktrace Output Multiplexer (19.5)
Linktrace Output Multiplexer (19.5)
Queuing entities (8.6.6/7/8)
Queuing entities (8.6.6/7/8)
Support of the EISS
Support of the EISS (6.9)
Support of the ISS by additional technologies
(6.15)
Support of the ISS (6.7)
OTN ODU Down MP
MAC
PEB
OTN other functions
S-Tagged LAN
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

Frame filtering (8.6.3)
Up MPs (6.17, 19.2, 19.3)
Up MPs (6.17, 19.3)
O T N N E T W O R K P O R T
Port filtering entities (8.6.1/2/4/5)
Port filtering entities (8.6.1/2/4/5)
N E W P O R T
Down MPs (6.17, 19.2, 19.3)
Down MPs (6.17, 19.3)
Linktrace Output Multiplexer (19.5)
Linktrace Output Multiplexer (19.5)
6.18 terminates the I-Tag and provides N x ISS
EISS
Queuing entities (8.6.6/7/8)
Queuing entities (8.6.6/7/8)
Support of the EISS
Support of the I-EISS (6.18 like)
Support of the ISS by additional technologies
(6.15)
Support of the ISS (6.7)
OTN ODU Down MP
MAC
I-BEB
OTN other functions
I-Tagged LAN
8
Ethernet functionality in EOTN NT
  • UNI-N or V-UNI-N interface ports
  • UNI/V-UNI Facing Port (e.g. CEP, CNP,
    RCAPPAPCEP, RCAPPAPCNP, )
  • (V-)UNI LAN termination
  • Ethernet MEP and MIP functions
  • Service selection (MAC Relay)
  • Ethernet VC Network Port (e.g. PEPCNP, )
  • 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
(8.6.1/2/4/5)
P E P v 2
(6.9, 9.5)
6.X MAC encapsulation shim inserts TYPE89-10,
N-SA, N-DA in a PEPv2
(8.5)
PEPv2 is backwards compatible with PEP
MAC encaps (6.X)
(6.14 or 6.7)
Frame filtering (8.6.3)
Up MPs (6.17, 19.2, 19.3)
CNP
CNP
CBP
CNP
CNP
Frame filtering (8.6.3)
Frame filtering (8.6.3)
O T N N E T W O R K P O R T
Port filtering entities (8.6.1/2/4/5)
PEP
CEP
PEP v2
CEP
Down MPs (6.17, 19.2, 19.3)
Linktrace Output Multiplexer (19.5)
S-Tagged peering service Port-based peering or
client/server service
C-Tagged peering or client/server
service ----- S-Tagged peering or client/server
service Transparent peering service ()
C-Tagged, S-Tagged, Port-based and Transparent
peering or client/server service () with
optional MAC encapsulation
I-Tagged client/server service
Queuing entities (8.6.6/7/8)
Support of the EISS
Frame filtering (8.6.3)
Frame filtering (8.6.3)
Support of the ISS by additional technologies
(6.15)
CEP
PEP
RCAP
PAP
OTN ODU Down MP
() CNPCEP 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
C-Tagged peering or client/server service
OTN other functions
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

impact on 802.1Q to be added in v02
13
Backup
14
header formats
16
3
1
12
S-VLAN Tag 4-octets
TPID 88-A8
S-/B-VLAN ID
PCP
DEI
16
3
1
12
New VLAN Tag 4-octets
TPID xxx
ETH VC ID
PCP
DEI
16
3
1
24
2
1
1
TPID 88-E7
I-SID
PCP
DEI
I-Tag 18-octets
RES2
UCA
RES1
DA
SA
16
16
PLI
cHEC
GFP-F header 8-octets
tHEC
UPI
PTI
PFII
EXI
3
1
12
4
Write a Comment
User Comments (0)
About PowerShow.com