Professional Documents
Culture Documents
Understanding OTN Optical Transport Network (G.709)
Understanding OTN Optical Transport Network (G.709)
March 9, 2010
Presenter: Mike Jamgochian Director of Business Development
C t ib t
Contributor:
St
Steve T
Trowbridge
b id Standards
St d d T
Team, O
Optics
ti CTO Group
G
Agenda
1. Alphabet Soup
2. History Lesson
3 OTN 101
3.
Network Application
ALU OTN Support
OTN Hierarchy
Hi
h
ODUflex
Alphabet Soup
Acronyms
ITU-T: International Telecommunications
Union Telecommunications Section
OTN: Optical
p
Transport
p
Network
OPU: Optical
p
channel Payload
y
Unit
LAN PHY(10GBase
PHY(10GBase-R):
R): LAN Physical
interface
History Lesson
Telecom History
Async
SONET
Async
SONET
SONET
Ethernet
OTN
Transport Mechanism
Copper
Analog Radio
Fiber
Digital Radio
Fiber
Transmission Medium
1970
1970s
1980
1980s
1990
1990s
2000
2000s
What is OTN?
OTN is an industry-standard optical transport protocol
ITU G.872 "Architecture for the Optical Transport Network (OTN) (Oct 2001)
Further refined in ITU-T
ITU T G.709
G 709 (Jan 2003,
2003 Amendment 3 Oct 2009) and ITU
ITU-T
TG
G.798
798
(May 2002, xxxx Jun 2010)
TRANSPARENCY across th
the optical
ti l d
domain
i
Integrates physical and optical layers for seamless networking
Promotes integration across disparate networks via common transport framework
Differentiated Services
New Service Level Agreement (SLA) options
Via OTN Control-Plane mesh
OTN 101
HO-ODU
HO ODU networking
ki is
i used
d
IP/MPLS
SONET/SDH
LO-ODU
LO-ODU
LO-ODU
LO-ODU
HO-ODU
HO-ODU
HO-ODU
HO-ODU
HO-ODU
level networking
12 | Understanding OTN | December 10, 2009
HO-ODU
HO-ODU
Existing Products
New Products
1625 LX (DWDM)
1626 LM (DWDM)
1675 LU (Cross-connect)
1678 MCC (Cross
(Cross-connect)
connect)
IP
Ethernet
SONET/SDH
Video
FEC
Header
Payload
(Transparent)
OTN Multiplexing
Optical Channel
14 | Understanding OTN | December 10, 2009
OTN supports
range of protocols
OTN digital
g
wrapper
pp
provides complete
transparency for
clients in flexible
containers
Optical Channel
Och Overhead
Och Payload
FEC Area
COLUMN
1
R
O
W
14 15 16 17
OTU Overhead
2
3
ODU Overhead
OPU Overhead
3824 3825
OPU
(Payload)
4080
FEC
Electrical
Domain
Client Signal
Client
Optical
p
Payload
y
Unit
(OPU)
OPU
ODU
OTU
Och
Optical Channel
(Och)
Optical
O
ti l
Domain
OPU
OH
ODU
OH
OTU
OH
OTN Rates
OTU
ODU
Marketing
Rate
True
Signal
(OTU)
True
Payload
(OPU)
1.25G
NA
1.238G/s
2 5G
2.5G
2 666G/
2.666G/s
2 488G/
2.488G/s
10G
10.709G/s
9.953G/s
40G
43.018G/s
39.813G/s
OTN Hierarchy
ODU clients
1000BASE-X
CBR2G5
STM-16/OC-48
CBRx
GFP data
CBR10G
STM-64/OC-192
10GBASE-R
FC1200
CBR40G
STM-256/OC-768
40GBASE-R
100GBASE-R
100GBASE
R
ODU0
ODU1
ODU2
ODU2e
OTU1
4
16
ODUflex
ODU1
80
OTU
32
n
n 40
n
ODU2
OTU2
4
10
3
ODU3
10
OTU3
ODU3
2
ODU4
ODU4
OTU4
AMP BMP,
AMP,
BMP or GFP-F
GFP F
GMP
All Rights Reserved Alcatel-Lucent 2009
ODU0 Definition
Smallest contained defined in G.709 (OTN Standard)
1.25G container size (specifically 1.244160 Gbit/s20ppm)
Established in October 2009 for transport of 1000BASE-X
1000BASE X (Gigabit Ethernet)
ODU1 Definition
Original tier of the hierarchy to transport 2.5G signals
ODU1 = 2.498775Gbit/s
OTU1 = 2.666057Gbit/s
2 666057Gbit/s
Can be used as a higher order ODU to carry lower order ODU0s
ODU2 Definition
Original tier of the hierarchy to transport 10G signals
ODU2 = 10.037273Gbit/s
OTU2 = 10.709224Gbit/s
10 709224Gbit/s
Can be used as a higher order ODU to carry lower order ODUs
ODU2e Definition
New Low Order (LO) tier of the hierarchy (Oct 2009) to transport proprietary
10G signals
Serves as a logical wrapper for 10GBASE
10GBASE-R
R when carried over a standardized physical
layer of OTU3 or OTU4
Part of compromise made to enable standards progress - most commonly deployed
proprietary transparent mapping of 10GBASE-R
Over-clocked physical OTU2e signal remains in G.sup43
ODU3 Definition
Original tier of the hierarchy to transport 40G signals
ODU3 = 40.319218Gbit/s
OTU3 = 43.018410Gbit/s
43 018410Gbit/s
Can be used as a higher order ODU to carry lower order ODUs
ODU4 Definition
New tier of the hierarchy (Oct-09)
ODU4 = 104.794445Gbit/s
OTU4 = 111.809973Gbit/s
111 809973Gbit/s
Can be used as a higher order ODU to carry lower order ODUs
ODUflex Overview
New to hierarchy (Oct-09)
Two flavors of ODUflex standardization
n FC PHY
Circuit ODUflex
ODUflex n
HO ODUk ()
SSupports
t any possible
ibl client
li t bit rate
t as a
service in circuit transport networks
CBR clients use a bit-sync mapping into
ODUflex (239/238xthe client rate)
N Eth PHY
ODUflex m
TDM CBR
Packet
P k ODUflex
ODUfl
Creates variable size packet trunks (containing
GFP-F mapped packet data) for transporting
packet flows using L1 switching of a LO ODU
Logical Flow
(VLAN #1)
ODUflex 1
Logical flow
(VLAN #n)
ODUflex n
N Eth PHY
Eth PHY
ODUflex m
TDM CBR
HO ODUk ()
ODU k
ODUk
ODUflex
Circuit ODUflex
ODUfl
ODUflex
P k t ODUflex
Packet
ODUfl
ODUflex Resizing
Not yet defined in G.709; draft revision under discussion
Mixed operator views
Component vendor hesitation due to fear of delay
Some vendor opposition (Ciena/Nortel)
Revised G.709 adds over 100 new multiplexing routes (ODUflex into 1-80 TS of OPU4, 132 TS of OPU3, 1-8 TS of OPU2, ODU0 ODU2,3,4, ODU2e OPU3, ODU1,2,2e,3 OPU4)
If a traditional justification approach is employed, almost all of the new multiplexing routes would
be messy
messy with number and location of justification opportunities varying according to the
particular TSs assigned
Location of even fixed stuff would have to be determined algorithmically, because there are too
many combinations to draw them all explicitly.
Offers possibility to support hitless resizing of packet ODUflex (precluded by traditional justification
approach)
The server frame (or multi-frame) is divided into a certain number of GMP words,
where each word may contain either data or stuff.
Words containing
g data are distributed as evenlyy as p
possible (q
(quantized to word size)) across server
frame using sigma/delta distribution algorithm
Correct operation depends only on mapper and demapper knowing the number of data words which
are filled into each frame (or multi-frame)
Larger GMP word sizes are used for higher bit-rate clients to avoid the need for large
barrel shifters in the implementation.
If necessary to meet the timing requirements of the client,
client additional timing information
may be transmitted from the mapper to the demapper
Enables the demapper to know how many client bytes (or bits) are to be emitted by the demapper
during each server frame period
N
Note
t that
th t th
the GMP word
d size
i ffor some mappings
i
may b
be as llarge as 80 b
bytes,
t
which
hi h could
ld otherwise
th
i produce
d
significant mapping jitter
30 | Understanding OTN | December 10, 2009
OTN Protection
Linear Protection
G.873.1 outdated revision to align with new base documents underway
SNC/I compound group protection is proposed for ODU
OTN Standardization
Non-controversial work items
Elevate 40GBASE-R/100GBASE-R mappings into OTU3/OTU4 to standard when
IEEE P802.3ba is approved (expected June 2010)
Complete the Equipment model (revision of G.798) corresponding to the
recently revised G.709
Complete the Equipment management model (revision of G.874) corresponding
to recently revised G.709 and parallel revision of G.798
Revise the OTN jitter specification G.8251 to cover new client and tributary
mappings introduced by the revision of G.709
www.alcatel-lucent.com
l
t
l
l
t
www.alcatel-lucent.com