OTC000005 OTN Introduction ISSUE1.00

OTN Introduction
www.huawei.com
Copyright © 2008 Huawei Technologies Co., Ltd. All rights reserved.

Foreword
 This course will introduce OTN, includes:
 Optical transport hierarchy (OTH) , interface structure, overhead
 Maintenance signals, function for different layers
 Alarm and Performance events
 Some common application scenarios of OTN.
Copyright © 2008 Huawei Technologies Co., Ltd. All rights reserved. Page2
Objectives
 Upon completion of this course, you will be able to:
 Describe OTN frame structure, maintenance signals and function for
different layers
 Outline alarm and performance events generation mechanism
 Analyze the alarm and performance events and locate the failures in
OTN
Contents
1. Optical transport hierarchy
2. OTN interface structure
3. Multiplexing/mapping principles and bit rates
4. Overhead description
5. Maintenance signals and function for different layers
6. Alarm and performance events
7. Typical Scenarios of OTN
OTN
 OTN （ Optical Transport Network ）
 An Optical Transport Network (OTN) is composed of a set
of Optical Network Elements connected by optical fiber l
inks, able to provide functionality of transport, multip
lexing, routing, management, supervision and survivabili
ty of client signals, according to the requirements give
n in Rec. G.872
Features of OTN
 Compared with SDH and SONET ：
 Ultra capacity with high accuracy, Terabit/second per fiber
via DWDM lines
 Service transparency for client signals
 Asynchronous mapping, powerful FEC function, predigest
network design and reduce the cost
 Compared with traditional WDM
 Enhanced OAM & networking functionality for all services
 Dynamically electrical/optical layer grooming
OTN system
OTN
Jitter Equipment Structure Physic

management Network
and function and and layer Architecture
protection
wander features mapping features
G.874 G.8251 G.873.1 G.798 G.709 G.959.1 G.872
G.874.1 G.8201 G.873.2 G.806 G.7041 G.693 G.8080
G.7042 G.694
Contents
OTN network layers and interface
structure
 OPUk: Optical channel Payload Unit-k
IP/MPLS ATM Ethernet STM-N
 ODUk: Optical channel Data Unit-k
 OTUk: completely standardized Optical channel Transport
Unit-k
 OTUkV: functionally standardized Optical channel Transport OPUk
Unit-k
ODUk （ ODUkP 、 ODUkT ）
 OCh: Optical Channel with full functionality
 OChr: Optical Channel with reduced functionality
OTUk OTUkV OTUk OTUkV
 OMS: Optical Multiplex Section
 OTS: Optical Transmission Section OCh OChr
 OPS: Optical Physical Section
OMSn
 OTM: Optical Transport Module OPSn
OTSn
OTM-n.m OTM-0.m
OTM-nr.m
OTM-n.m Containment Relationships
Clinet signal
n
OPUk OH OPUk payload
ODUk OH OPUk
OTM-n. m
OTUk[V] OH ODUk FEC 

OCh OChOH OCh payload
 OSC
OCG-n.m
OCCo
OCCo
OCCo
OCCp OCCp OCCp

Non-associated OH
OTM Overhead Signal (OOS)

OMU-n.m OMSn payload
comms OH
OMSn OH
OTM-n.m OTSn OH OTSn payload

OOS
 n represents the maximum number of wavelengths that can be supported at the lowest bit rate supported on
the wavelength, m=1,2,3,12,23,123 ；
 OTS_OH, OMS_OH, OCh_OH and COMMS OH information fields are contained within the OOS
 OSC ： Optical Supervisory Channel used to transmit OOS
OTM-nr.m Containment Relationships
Client signal
16
OTM-16r.m
ODUk OH OPUk

OTUk[V] OH ODUk FEC 
OChr OCh payload
OCG-nr.m OCCp OCCp OCCp
OTM-nr.m OPSn
 Fixed channel spacing, irrespective of signal level

 1<n≤16, m=1,2,3,12,23,123
 Without optical supervisory channel
OTM-0.m Containment Relationships
Client signal
OTM-0.m
ODUk OH OPUk
OTUk[V] OH ODUk FEC
OChr OCh payload
OTM-0.m OPS0
 The OTM 0.m supports a non coloured optical channel on a single optical span with 3R
regeneration at each end.
 m=1,2,3
 Without optical supervisory channel
Contents
OTM multiplexing and mapping structure
OTM-0.m
1
i
OCCr OChr
1
1 ≤ i+j+k ≤ n
j 1
OTM-nr.m OCG-nr.m OCCr OChr Client signal
k 1 1 1
OTU3[V] ODU3 OPU3
1 1 16
OCCr OChr ODTUG3
1 4
Client signal
1 1
OTU2[V] ODU2 OPU2
Client signal
1 1
1 ODTUG2
OCC OCh
i 4 1
1 ≤ i+j+k ≤ n OTU1[V] 1 ODU1 OPU1
j 1 1
OTM-n.m OCG-n.m OCC OCh
 k
1 1
OCC OCh
1
1
Multiplexing
OSC OOS OTS, OMS, OCh, COMMS
Mapping
Types and capacity
Types nominal bit rate bit rate tolerance
OTU1 2 666 057.143 kbit/s
OTU2 10 709 225.316 kbit/s
OTU3 43 018 413.559 kbit/s
ODU1 2 498 775.126 kbit/s
ODU2 10 037 273.924 kbit/s ±20 ppm
ODU3 40 319 218.983 kbit/s
OPU1 2 488 320 kbit/s
OPU2 9 995 276.962 kbit/s
OPU3 40 150 519.322 kbit/s
ODUk （ TDM ）
 Low rate ODUk signals are multiplexed into high rate ODUk
signals using time‑division multiplexing :
 Up to 4 ODU1 signals are multiplexed into an ODU2 using
time‑division multiplexing
 A mixture of j (j  4) ODU2 and 16-4j ODU1 signals can be
multiplexed into an ODU3 using time‑division multiplexing.
ODU1 into ODU2 multiplexing method
 ODU1floats in ¼ of the OPU2 payload area.
 An ODU1 frame will cross multiple ODU2 frame boundaries.
Alignm
OPU1 OH
ODU1 Client layer signal
ODU1OH (e.g., STM-16, ATM, GFP)
x4
OPU1 OH
OPU2 OH
OPU1 OH
OPU1 OH
Alignm Client Layer Signal
Client Layer Signal
OPU1 OH
(e.g. STM-16)
ODU2 ODU1 OH
ODU1 OH Client(e.g.
Client
Layer
layer
Signal
STM-16)
signal
ODU2 OH ODU1 OH
ODU1 OH
(e.g. STM-16)
(e.g., STM-16, ATM, GFP)
OTU2
Alignm
OPU1 OH
OH
OPU1 OH
OPU2 OH
OPU1 OH
Client Layer Signal

OTU2 Alignm Client Layer Signal OTU2
OPU1 OH
ODU1 OH (e.g. STM-16)

ODU1 OH OPU2 PayloadClient
Client
Layer
(e.g.
layer
Signal
STM-16)
signal FEC
ODU2 OH ODU1 OH
ODU1 OH
(e.g. STM-16)
(e.g., STM-16, ATM, GFP)
Contents
OOS
FDI-O
n
TTI FDI-P 3
2
1
BDI-O BDI-O FDI-O
BDI-P OMSn BDI-P FDI-P

OTSn
OCh
PMI PMI OCI
General Management Communications

 TTI: Trail Trace Identifier
 PMI: Payload Missing Indication
 OCI: Open Connection Indication
 BDI-O: Backward Defect Indication –Overhead
 BDI-P: Backward Defect Indication – Payload
 FDI-O: Forward Defect Indication –Overhead
 FDI-P: Forward Defect Indication – Payload
OTN frame formats (k=1,2,3)
3824
3825
4080
14
15
16
17
1
7
8
OTUk
1 Alignm Client signal
OH
OPUk OH
2 mapped in
OTUK
OPUkk payload
OPU payload
3 ODUk FEC
OH
4
Client signal
OPUk - Optical Channel Payload Unit
ODUk – Optical Channel Data Unit k :
1 － 2.5G
OTUk – Optical Channel Transport Unit
2 － 10G
Alignment 3 － 40G
OTN electrical overhead overview
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
1 FAS MFAS SM GCC0 RES RES JC
TCM
2 RES ACT TCM6 TCM5 TCM4 FTFL RES JC
3 TCM3 TCM2 TCM1 PM EXP RES JC
4 GCC1 GCC2 APS/PCC RES PSI NJO
 ODUk OH
 TCMACT: Tandem Connection Monitoring
 Alignment OH
Activation/deactivation control channel
FAS: Frame Alignment Signal
MFAS: MultiFrame Alignment Signal
TCMi:Tandem Connection Monitoring i
 FTFL:Fault Type & Fault Location repo

 OTUk OH
rting channel
SM: Section Monitoring
GCC0:General Communication Channel0
PM: Path Monitoring
RES: Reserved for future international

EXP:Experimental
GCC1/2: General Communication Channel standardisation

1/2
 OPUk OH
APS/PCC:Automatic Protection Swiching
PSI: Payload Structure Identifier
JC: Justification Control
coordination channel/Protection Communica
NJO: negative justification opportunity
tion Control channel
Frame Alignment Signal
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
TCM
byte 1 byte 2 byte 3 byte 4 byte 5 byte 6

1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
OA1 OA1 OA1 OA2 OA2 OA2
 FAS (Frame Alignment Signal)

 A six byte OTUk-FAS signal is defined in row 1, columns 1 to 6
of the OTUk overhead.
 OA1 is 0xF6(1111 0110 ) ， OA2 is 0x28(0010 1000).
Multiframe alignment signal
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
TCM
MFAS OH Byte
 MFAS(MultiFrame Alignment Signal)
1 2 3 4 5 6 7 8
 defined in row 1, column 7 ；
.
.  The value of the MFAS byte will be incremented each OTUk/ODUk
0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 1
frame and provides as such a 256 frame multiframe.
0 0 0 0 0 0 1 0  Individual OTUk/ODUk overhead signals may use this central
MFAS sequence
0 0 0 0 0 0 1 1
0 0 0 0 0
..
1 0 0 multiframe to lock their 2-frame, 4 frame, 8-frame, 16-fra
..
me, 32-frame, etc., multiframes to the principal frame.
1 1 1 1 1 1 1 0
1 1 1 1 1 1 1 1
0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 1
..
OTUk section monitoring overhead
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
TCM
1 2 3  TTI (Trail Trace Identifier)

TTI BIP-8
 a one-byte overhead is defined to transport the 64 byt
0 1 2 3 4 5 6 7 8
e TTI signal
BDI
IAE
SAPI BEI/BIAE RES  The 64-byte TTI signal shall be aligned with the OTUk
15
16 multiframe and transmitted four times per multiframe.
DAPI
31  TTI struture ：
32
 16 bytes SAPI:Source Access Point Identifier
Operator
specific
 16 bytes DAPI:Destination Access Point Identifier
 32 bytes operator specific
63
 BIP-8 (Bit Interleaved Parity-8)
 For section monitoring, a one-byte error detection code signal is defined.
 This byte provides a bit interleaved parity-8 (BIP-8) code ；
 The OTUk BIP-8 is computed over the bits in the OPUk (columns 15 to 3824) area of
OTUk frame i, and inserted in the OTUk BIP-8 overhead location in OTUk frame i+2
1 14 15 3824
Frame i OPUk
BIP8
Frame i+1
Frame i+2
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
TCM
1 2 3  BEI/BIAE (Backward Error Indication/ Backward

TTI BIP-8
Incoming Alignment Error)
0 1 2 3 4 5 6 7 8
 A four-bit BEI and BIAE signal is defined.
BDI
IAE
SAPI BEI/BIAE RE
15
 This signal is used to convey in the upstream direction the
S
16
count of interleaved-bit blocks and incoming alignment
DAPI
31 error (IAE) condition.
32
 During an IAE condition the code "1011" is inserted into
Operator the BEI/BIAE field and the error count is ignored.
specific
Otherwise the error count (0-8) is inserted into the
63 BEI/BIAE field.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
TCM
1 2 3  BDI (Backward Defect Indication)

TTI BIP-8
 A single-bit backward defect indication (BD
0 1 2 3 4 5 6 7 8 I) signal is defined to convey the signal f
BDI
IAE
SAPI BEI/BIAE RES ail status detected in a section terminatio

15
16 n sink function in the upstream direction.
DAPI
31
32
 BDI is set to "1" to indicate an OTUk backward defect
indication; otherwise, it is set to "0"
Operator
specific
63
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
TCM
 IAE (Incoming Alignment Error)
1 2 3
 A single-bit incoming alignment error (IAE) signal
TTI BIP-8
is defined to allow the S-CMEP ingress point to inf
0 1 2 3 4 5 6 7 8
orm its peer S-CMEP egress point that an alignment
error in the incoming signal has been detected.
BDI
IAE
SAPI BEI/BIAE RES

15
16  IAE is set to "1" to indicate a frame alignment error, otherwise it
DAPI is set to "0".
31
32
 RES (Reserved)
Operator  two bits are reserved (RES) for future international
specific
standardization. They are set to "00".
63
OTUk GCC0 and RES overhead
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
TCM
 GCC0 (General Communication Channel)

 Two bytes are allocated in the OTUk overhead to support a general communications
channel between OTUk termination points
 A clear channel which are located in row 1, columns 11 and 12
 RES (Reserved)
 Two bytes of OTUk overhead are reserved for future international standardization
 located in row 1, columns 13 and 14
 set to all ZEROs
ODUk path monitoring overhead
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
TCM
1 2 3  TTI / BIP-8 / BEI / BDI

TTI BIP-8
 For path monitoring, this overheads’ function
0 1 2 3 4 5 6 7 8 are the same as OTUk SM signal, except BEI si
BDI
SAPI BEI STAT

15
16
gnal which doesn’t support BIAE function.
DAPI
31
 in row 3, columns 10 to 12
32
Operator
specific
63
ODUk path monitoring overhead
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
TCM
 STAT (Status)
1 2 3  For path monitoring, three bits are defined as status bits
TTI BIP-8  They indicate the presence of a maintenance signal
0 1 2 3 4 5 6 7 8
BDI
SAPI BEI STAT

15 Bit 6 7 8 status
16
DAPI Reserved for future international standard
000
31 ization
32 001 Normal path signal
Reserved for future international standard
Operator 010
ization
specific
011
ization
63
100
ization
101 Maintenance signal: ODUk - LCK
110
Copyright © 2008 Huawei Technologies Co., Ltd. All rights reserved. Maintenance signal: ODUk - OCI
Page31
111 Maintenance signal: ODUk - AIS
ODUk TCM overhead
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
TCM
1 2 3  TTIi / BIP-8i / BEIi/BIAEi / BDIi

TTIi BIP-8i
 For each tandem connection monitoring field, this
overheads’ function are the same as OTUk SM sign
0 1 2 3 4 5 6 7 8
al
BDIi
SAPI BEIi/BIAEi STATi

15  Six fields of ODUk TCM overhead are defined in row 2,
16
DAPI columns 5 to 13 and row 3, columns 1 to 9 of the ODUk
31 overhead
32
Operator
specific
63
ODUk TCM overhead
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
TCM
 STAT (Status)
 For each tandem connection monitoring field, three bits are defined
1 2 3 as status bits.
TTIi BIP-8i  They indicate the presence of a maintenance signal, if there is an
incoming alignment error at the source TC-CMEP, or if there is no s
ource TC-CMEP active.
0 1 2 3 4 5 6 7 8
BDIi
SAPI BEIi/BIAEi STATi

15 Bit 6 7 8 status
16 000 No source TC
DAPI 001 In use without IAE
31 010 In use with IAE
32
Reserved for future international standar
011
dization
Operator
specific Reserved for future international standar
100
dization
63 101 Maintenance signal: ODUk -LCK
110 Maintenance signal: ODUk -OCI
111 Maintenance signal: ODUk -AIS
Nested and Cascaded ODUk monitored
connections
TCM6 TCM6 TCM6 TCM6 TCM6 TCM6 TCM6
A1 B1 C1 C2 B2 B3 B4 A2
C1 - C2
B1 - B2 B3 - B4
A1 - A2
TCMi TCM OH field not in use TCMi TCM OH field in use
Overlapping ODUk monitored connections
TCM6 TCM6 TCM6 TCM6 TCM6
A1 B1 C1 B2 C2 A2
C1 - C2
B1 - B2
A1 - A2
TCMi TCM OH field not in use TCMi TCM OH field in use
ODUk GCC1/GCC2
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
TCM
 GCC1 / GCC2 (General Communication Channel)

 Two fields of two bytes are allocated in the ODUk overhead to support two
general communications channels between any two network elements with acc
ess to the ODUk frame structure (i.e., at 3R regeneration points).
 The bytes for GCC1 are located in row 4, columns 1 and 2, and the bytes f
or GCC2 are located in bytes row 4, columns 3 and 4 of the ODUk overhead.
Other overheads
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
TCM
 TCMACT (TCM Activation/Deactivation)

 APS/PCC (Automatic Protection Switching/Protection Communication Control)
 EXP (Experimental)
 FTFL (Fault Type & Fault Location)
OPUk payload structure identifier
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
TCM
 PSI (Payload Structure Identifier)

0 PT
1
 One byte is allocated in the OPUk over
head to transport a 256-byte payload s
Mapping tructure identifier (PSI) signal
& concatenation
specific
 aligned with the ODUk multiframe.
 PSI[0] contains a one-byte payload type. PSI[1]
255
to PSI[255] are mapping and concatenation
specific .
Payload type code points
MSB 1 2 3 4 LSB 1 2 3 4 Hex code Interpretation
0000 0001 01 Experimental mapping
0000 0010 02 Asynchronous CBR mapping
0000 0011 03 Bit synchronous CBR mapping
0000 0100 04 ATM mapping
0000 0101 05 GFP mapping
0000 0110 06 Virtual Concatenated signal
0001 0000 10 Bit stream with octet timing mapping
0001 0001 11 Bit stream without octet timing mapping
0010 0000 20 ODU multiplex structure
0101 0101 55 Not available
0110 0110 66 Not available
1000 xxxx 80-8F Reserved codes for proprietary use
1111 1101 FD NULL test signal mapping
1111 1110 FE PRBS test signal mapping
1111 1111 FF Not available
Contents
Maintenance signals
 FDI （ forward defect indication ）
 FDI is a signal sent downstream as an indication that an upstream defect has been
detected.
 An FDI signal is detected in a trail termination sink function to suppress defects or
failures that would otherwise be detected as a consequence of the interruption of
the transport of the original signal at an upstream point..
 AIS and FDI are similar signals. AIS is used as term when the signal is in the
digital domain. FDI is used as the term when the signal is in the optical domain.
 FDI is transported as non associated overhead in the OTM overhead signal (OOS).
Maintenance signals
 AIS （ alarm indication signal ）
 AIS is a signal sent downstream as an indication that an upstream
defect has been detected. An AIS signal is generated in an adaptation
sink function
 An AIS signal is detected in a trail termination sink function to
suppress defects or failures that would otherwise be detected as a
consequence of the interruption of the transport of the original signal
at an upstream point.
Maintenance signals
 AIS （ alarm indication signal ）
 ODUk-AIS is specified as all "1"s in the entire ODUk signa
l, excluding the frame alignment overhead (FA OH), OTUk ov
erhead (OTUk OH) and ODUk FTFL
 The presence of ODUk-AIS is detected by monitoring the ODUk STAT
bits in the PM and TCMi overhead fields
1 78 14 17 3824
1 FA OH OTUk OH
FTFL
STAT
STAT
STAT
2
All-1s pattern
STAT
STAT
STAT
STAT
3
4
Maintenance signals
 BDI (Backward Defect Indication)
 Backward Defect Indication Payload defect (dBDI-P) is
monitored at the OTS and OMS layers. The purpose of
monitoring this parameter is to allow for single ended
supervision of the trail
 During signal fail conditions of the overhead signal, dBDI-P
shall be set to false
Maintenance signals
 OCI (open connection indication)
 A signal sent downstream as an indication that upstream the signal is not
connected to a trail termination source
 The presence of ODUk-OCI is detected by monitoring the ODUk ST
AT bits in the PM and TCMi overhead fields.
 The repeating "0110 0110" pattern is the default pattern; othe
r patterns are also allowed as long as the STAT bits in the PM
and TCMi overhead fields are set to "110".
1 78 14 17 3824
1 FA OH OTUk OH
FTFL
STAT
STAT
STAT
2
Repeating “0110 0110” pattern
STAT
STAT
STAT
STAT
3
4
Maintenance signals
 LCK (locked)
 A signal sent downstream as an indication that upstream the connection is "locked",
and no signal is passed through.
 The presence of ODUk-LCK is detected by monitoring the ODUk STAT b
its in the PM and TCMi overhead fields.
 dLCK shall be declared if the accepted STAT information (AcSTAT) is “101”.
dLCK shall be cleared if the accepted STAT information is not equal to “101”.
 During signal fail conditions of the data signal, dLCK shall be set to false.
1 78 14 17 3824
1 FA OH OTUk OH
FTFL
STAT
STAT
STAT
2
Repeating “0101 0101”pattern
STAT
STAT
STAT
STAT
3
4
Maintenance signals
 IAE (Incoming Alignment Error)
 IAE at the OTUk layer: dIAE shall be declared/cleared if the IAE bit
in the SM overhead field (byte 3, bit 6) is “1”/ “0” for X co
nsecutive frames. X shall be 5.
 IAE at the ODUkT layer: dIAE shall be declared/cleared if the accepted STAT
information (AcSTAT) is/is not “010”.
 During signal fail conditions of the data signal, dIAE shall be set to false .
 BIAE (Backward Incoming Alignment Error)
 dBIAE shall be declared/cleared if the BEI/BIAE bits in the SM/TCM overhead
field (byte 3, bit 1 to 4) are/are not “1011” for X consecutive frames. X shall be 3.
 During signal fail conditions of the data signal, dBIAE shall be set to false .
Maintenance and management signal
Network layers
Management
signal
function OTUk ODUkP ODUkT
Alignment LOF/LOM Y Y –
Connectivity TTI Y Y Y
AIS Y Y Y
OCI – Y Y
Maintenance LCK – Y Y
Signal LTC – – Y
BDI Y Y Y
BEI Y Y Y
IAE/BIAE Y – Y
Signal quality BIP-8 Y Y Y
OTN Layer Network Trail
Client signal
ODUkP
ODUkT
OTU/OCH OTU/OCH OTU/OCH
OMS OMS OMS
OTS OTS OTS
NODE A NODE B NODE C NODE D

TM REG ODU ADM TM
 NODE A using general OTU, generate SM,PM,TCM1.
 NODE B using regenerator OTU, terminate SM, generate SM.
 NODE C using Line unit OTU, terminate SM,TCM1, generate SM.
 NODE D using general OTU, terminate SM,PM.
Contents
Alarm
Layer Alarm
OTUk OTUk_LOF 、 OTUk_AIS 、 OTUk_LOM 、 OTUk_TIM 、 OTUk_DEG 、 OTUk_

EXC 、 OTUk_BDI 、 BEFFEC_EXC
ODUk_PM ODUk_PM_TIM 、 ODUk_PM_DEG 、 ODUk_PM_EXC 、 ODUk_PM_BDI 、 ODU

k_PM_LCK 、 ODUk_PM_OCI 、 ODUk_PM_AIS 、 ODUk_LOFLOM
ODUk_TCMi ODUk_TCMi_TIM 、 ODUk_TCMi_DEG 、 ODUk_TCMi_EXC 、 ODUk_TCMi_

BDI 、 ODUk_TCMi_LCK 、 ODUk_TCMi_OCI 、 ODUk_TCMi_AIS 、 ODUk_
TCMi_LTC
OPUk OPUk_PLM 、 OPU2_MSIM 、 OPU3_MSIM
Remark: k=1,2,3,5G, i=1 ～ 6;
Suppression mechanisms of electrical layer
alarm
OTUk_AIS ODUk_LOFLOM
OTUk_LOF ODUk_TCMi_LTC/OCI/LCK/AIS
OTUk_LOM ODUk_TCMi_TIM
ODUk_TCMi_BDI
OTUk_TIM ODUk_PM_OCI/LCK/AIS ODUk_TCMi_IAE
ODUk_TCMi_BIAE
OTUk_IAE OTUk_BIAE OPUk_PLM OTUk_BDI ODUk_PM_TIM ODUk_TCMi_DEG
OTUk_DEG OPUk_MSIM OPUk_PLM ODUk_PM_BDI ODUk_PM_DEG
 IAE and BIAE are not alarms, but IAE can suppress DEG which on the same level .
Performance events
layer Performance events
OTUk OTUk_BBE 、 OTUk_BBER 、 OTUk_BIAES 、 OTUk_ES 、 OTUk_FEBBE 、 OTUk_FEBBER 、

OTUk_FEES 、 OTUk_FESES 、 OTUk_FESESR 、 OTUk_FEUAS 、 OTUk_IAES 、 OTUk_SES
、 OTUk_SESR 、 OTUk_UAS 、 FEC_AFT_COR_ER
ODUk_PM ODUk_PM_BBE 、 ODUk_PM_BBER 、 ODUk_PM_ES 、 ODUk_PM_FEBBE 、 ODUk_PM_FEBBER

、 ODUk_PM_FEES 、 ODUk_PM_FESES 、 ODUk_PM_FESESR 、 ODUk_PM_FEUAS 、 ODUk_P
M_SES 、 ODUk_PM_SESR 、 ODUk_PM_UAS
ODUk_TCMi ODUk_TCMi_BBE 、 ODUk_TCMi_BBER 、 ODUk_TCMi_BIAES 、 ODUk_TCMi_ES 、 ODUk_TC

Mi_FEBBE 、 ODUk_TCMi_FEBBER 、 ODUk_TCMi_FEES 、 ODUk_TCMi_FESES 、 ODUk_TCM
i_FESESR 、 ODUk_TCMi_FEUAS 、 ODUk_TCMi_IAES 、 ODUk_TCMi_SES 、 ODUk_TCMi_S
ESR 、 ODUk_TCMi_UAS
K=1,2,3,5G i=1 ～ 6.
Contents
Scenarios hypothesis
 These hypothesis apply to all scenarios ：
 TIM insert AIS downward, TIM suppression enable
 Monitoring both SAPI and DAPI to report TIM
 ALS 、 APR function disable
Case ： point to point ODU2
ODU2P
OTU2 OTU2
A B C
 Bidirectional client service between A and C station.

 A, C (ODU TM) ： general OTU (LSX)
 B (OTU REG ）： regenerator OTU (LSXR)
Functional block
ODU2P OTU2 OCh sou
source source rce funct
function function ion
A,C
ODU2P OTU2 OCh sin
sink sink k functio
function function n
OCh sin OTU2 sin OTU2 OCh so

k functio k functio source urce fun
n n function ction
B
OCh so OTU2 so OTU2 sin OCh si

urce fun urce fun k functio nk functi
ction ction n on
Insert LCK at node A
ODU2_PM_LCK
ODU2_LCK
ODU2_PM_aBDI
A B C
ODU2_PM_BDI
Fiber broken between A and B
R_LOS ODU2_PM_AIS
ODU2_aAIS
Fiber broken OTU2_aBDI

X
A B C
OTU2_BDI
ODU2_PM_BDI
Fiber degrade between A and B
OTU2_DE
ODU2_PM_DEG
G
OTU2_aBEI ODU2_PM_aBEI
Fiber degrade
/
A B C
OTU2_BEI performance
ODU2_PM_BEI performance
Fiber badly degrade
OTU2_LOF
ODU2_aAIS ODU2_PM_AIS
OTU2_aBDI ODU2_PM_aBDI
Fiber degrade
/
A B C
OTU2_BDI
ODU2_PM_B
DI
Receiving TTI is mismatch at B
SM_ExDAPI mismatch
OTU2_TIM ODU2_PM_AIS
ODU2_aAIS
OTU2_aBDI ODU2_PM_aBDI
A B C
OTU2_BDI
ODU2_PM_BDI
Receiving TTI is mismatch at C
PM_ExDAPI mismatch
ODU2_PM_TIM
ODU2_PM_aBDI
A B C
ODU2_PM_BDI
Client signal lost at A
R_LOS ClientSF
Fiber broken
x
A B C
Questions
 What kinds of the components the OTM-n.m have?
 OTSn, OMSn, OCh, OTUk/OTUkV, ODUk, OPUk
 What’s the difference with the BIP-8 byte function a

mong SM, PM, TCMi ?
 All of them the BIP-8 is computed over the bits in the OPUk
(columns 15 to 3824) area, but for different layers on OTUk
, ODUkP, ODUKT.
 How many types of the TCM applications we have?

 Nested, cascaded and overlapping
Summary
Abbreviations and Acronyms
 3R Re-amplification, Reshaping and Retiming
 AI Adapted Information
 AIS Alarm Indication Signal
 APS Automatic Protection Switching
 BDI Backward Defect Indication
 BDI-O Backward Defect Indication Overhead
 BDI-P Backward Defect Indication Payload
 BEI Backward Error Indication
 BI Backward Indication
 BIAE Backward Incoming Alignment Error
 BIP Bit Interleaved Parity
 CBR Constant Bit Rate
 CMEP Connection Monitoring End Point
 DAPI Destination Access Point Identifier
 EXP Experimental
 ExTI Expected Trace Identifier
 FAS Frame Alignment Signal
 FDI Forward Defect Indication
 FDI-O Forward Defect Indication Overhead
 FDI-P Forward Defect Indication Payload
 FEC Forward Error Correction
 GCC General Communication Channel
 IaDI Intra-Domain Interface
 IAE Incoming Alignment Error
 IrDI Inter-Domain Interface
 JOH Justification Overhead
 MFAS MultiFrame Alignment Signal
 MFI Multiframe Indicator
 MSI Multiplex Structure Identifier
 NNI Network Node Interface
 OCC Optical Channel Carrier
 OCCo Optical Channel Carrier – overhead
 OCCp Optical Channel Carrier – payload
 OCCr Optical Channel Carrier with reduced functionality
 OCG Optical Carrier Group
 OCGr Optical Carrier Group with reduced functionality
 OCh Optical channel with full functionality
 OChr Optical channel with reduced functionality
 OCI Open Connection Indication
 ODTUG Optical channel Data Tributary Unit Group
 ODTUjk Optical channel Data Tributary Unit j into k
 ODU Optical Channel Data Unit
 ODUk Optical Channel Data Unit-k
 OH Overhead
 OMS Optical Multiplex Section
 OMU Optical Multiplex Unit
 ONNI Optical Network Node Interface
 OOS OTM Overhead Signal
 OPS Optical Physical Section
 OPU Optical Channel Payload Unit
 OPUk Optical Channel Payload Unit-k
 OSC Optical Supervisory Channel
 OTH Optical Transport Hierarchy
 OTM Optical Transport Module
 OTN Optical Transport Network
 OTS Optical Transmission Section
 OTU Optical Channel Transport Unit
 OTUk completely standardized Optical Channel Transport Unit-k
 OTUkV functionally standardized Optical Channel Transport Unit-k
 PCC Protection Communication Channel
 PLD Payload
 PMI Payload Missing Indication
 PRBS Pseudo Random Binary Sequence
 PSI Payload Structure Identifier
 PT Payload Type
 RES Reserved for future international standardization
 SAPI Source Access Point Identifier
 Sk Sink
 SM Section Monitoring
 So Source
 TCM Tandem Connection Monitoring
 TS Tributary Slot
 TxTI Transmitted Trace Identifier
 UNI User-to-Network Interface
Thank you
www.huawei.com

OTC000005 OTN Introduction ISSUE1.00

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OTC000005 OTN Introduction ISSUE1.00

Uploaded by

Copyright:

Available Formats

OTN Introduction

Copyright © 2008 Huawei Technologies Co., Ltd. All rights reserved.

Jitter Equipment Structure Physic

OCCp OCCp OCCp

OTM Overhead Signal (OOS)

OTM-n.m OTSn OH OTSn payload

OChr OCh payload

OCG-nr.m OCCp OCCp OCCp

 Fixed channel spacing, irrespective of signal level

OTUk[V] OH ODUk FEC

OChr OCh payload

OTU2 10 709 225.316 kbit/s

OTU3 43 018 413.559 kbit/s

ODU1 2 498 775.126 kbit/s

ODU2 10 037 273.924 kbit/s ±20 ppm

ODU3 40 319 218.983 kbit/s

OPU1 2 488 320 kbit/s

OPU3 40 150 519.322 kbit/s

Client Layer Signal

ODU1 OH (e.g. STM-16)

BDI-P OMSn BDI-P FDI-P

General Management Communications

 FTFL:Fault Type & Fault Location repo

RES: Reserved for future international

GCC1/2: General Communication Channel standardisation

byte 1 byte 2 byte 3 byte 4 byte 5 byte 6

 FAS (Frame Alignment Signal)

1 2 3  TTI (Trail Trace Identifier)

1 2 3  BEI/BIAE (Backward Error Indication/ Backward

1 2 3  BDI (Backward Defect Indication)

SAPI BEI/BIAE RES ail status detected in a section terminatio

SAPI BEI/BIAE RES

 GCC0 (General Communication Channel)

1 2 3  TTI / BIP-8 / BEI / BDI

SAPI BEI STAT

SAPI BEI STAT

1 2 3  TTIi / BIP-8i / BEIi/BIAEi / BDIi

SAPI BEIi/BIAEi STATi

SAPI BEIi/BIAEi STATi

TCMi TCM OH field not in use TCMi TCM OH field in use

TCMi TCM OH field not in use TCMi TCM OH field in use

 GCC1 / GCC2 (General Communication Channel)

 TCMACT (TCM Activation/Deactivation)

 PSI (Payload Structure Identifier)

NODE A NODE B NODE C NODE D

OTUk OTUk_LOF 、 OTUk_AIS 、 OTUk_LOM 、 OTUk_TIM 、 OTUk_DEG 、 OTUk_

ODUk_PM ODUk_PM_TIM 、 ODUk_PM_DEG 、 ODUk_PM_EXC 、 ODUk_PM_BDI 、 ODU

ODUk_TCMi ODUk_TCMi_TIM 、 ODUk_TCMi_DEG 、 ODUk_TCMi_EXC 、 ODUk_TCMi_

OPUk OPUk_PLM 、 OPU2_MSIM 、 OPU3_MSIM

Remark: k=1,2,3,5G, i=1 ～ 6;

OTUk_DEG OPUk_MSIM OPUk_PLM ODUk_PM_BDI ODUk_PM_DEG

OTUk OTUk_BBE 、 OTUk_BBER 、 OTUk_BIAES 、 OTUk_ES 、 OTUk_FEBBE 、 OTUk_FEBBER 、

ODUk_PM ODUk_PM_BBE 、 ODUk_PM_BBER 、 ODUk_PM_ES 、 ODUk_PM_FEBBE 、 ODUk_PM_FEBBER

ODUk_TCMi ODUk_TCMi_BBE 、 ODUk_TCMi_BBER 、 ODUk_TCMi_BIAES 、 ODUk_TCMi_ES 、 ODUk_TC

 Bidirectional client service between A and C station.

OCh sin OTU2 sin OTU2 OCh so

OCh so OTU2 so OTU2 sin OCh si

Fiber broken OTU2_aBDI

 What’s the difference with the BIP-8 byte function a

 How many types of the TCM applications we have?

You might also like