OTN_Tutorial_v9

Prévia do material em texto

OTN Tutorial 
Steve Surek 
Ciena Corporation 
October 27-28, 2011 
2 
Agenda 
 OTN Introduction 
 OTN Overhead 
 OTN and OTN Client Signal Fault Propagation 
 OTN Performance Monitoring 
 OTN Multiplexing and Mapping Trees 
 OTN Client Mappings 
 Other 5430 OTN Capabilities 
1 
2 
3 
4 
5 
6 
7 
OTN Introduction 
4 
Motivation for OTN - The Original DWDM Problem 
NE NE 
Vendor A 
Domain 
NE 
Vendor B 
Domain 
Carrier A 
Domain 
NE 
Carrier B 
Domain Carrier C 
Domain 
NE 
NE 
Proprietary DWDM systems 
Vendor interop 
only at client level 
Lack of end-to-end service management End Customer 
End 
Customer 
NE 
NE 
5 
Motivation for OTN - The OTN Solution 
NE NE 
Vendor A 
Domain 
NE 
Vendor B 
Domain 
Carrier A 
Domain 
NE 
Carrier B 
Domain Carrier C 
Domain 
NE 
NE 
End 
Customer 
End 
Customer 
NE 
NE 
Intra-domain Interfaces (IaDI) 
remain proprietary 
Standarize 
Inter-domain 
 Interfaces (IrDI) 
End-to-end service management 
Standardized Inter-Domain 
Interface 
 Single and multiple 
wavelength interfaces 
with or w/o OSC 
 Standard rates and 
formats (2.5G, 10G, 40G, 
100G interfaces) 
 Standard forward error 
correction (FEC) 
 Multiplexing and 
switching 
Standardized Management 
Capability 
 Digital wrapper providing 
standard management 
functions for signal quality 
monitoring, connection and 
connectivity monitoring, 
maintenance signal generation 
and detection, etc. 
 Standardized management of 
optical layers and end-to-end 
service transport 
 
6 
OTN Layers 
OTS 
OMS 
OCh 
OTU 
ODU 
Optical 
(Analog) 
Domain 
Electrical 
(Digital) 
Domain 
Physical Optical Layers 
Standardized Optical Layer Model 
Provides Inter-Domain Interworking 
Client Transparency 
Full-Wavelength OCh Switching 
Wavelength Selective Bypass 
Physical Electrical Layers 
End-to-End Monitoring 
 Inter-Domain Interworking 
Client Transparency 
Sub-Wavelength ODU Switching 
High Efficiency Grooming 
OPU 
7 
Three Architectural Options for OTN 
Switched 
G.709 
(Digital OTN) 
Static WDM 
(Analog OTN) 
Flexible 
WDM 
(Analog OTN) 
Switched 
G.709 
(Digital OTN) 
Dynamic 
WDM 
(Analog OTN) 
Framed G.709 
(Digital OTN) 
A B C 
 G.709 provides all 
dynamic capabilities 
 WDM for capacity only 
 G.709 provides dynamic 
switching 
 WDM with reconfigurable 
connections 
 G.709 provides framing 
only 
 WDM for all dynamic 
capabilities 
8 
OTN Layer Descriptions – Optical Layers 
Optical Transmission Section (OTS) 
 Physical optical signal consisting of multiplexed payload wavelengths plus an optical 
supervisory channel wavelength 
 Provides for optical amplification, dispersion compensation, and management overhead for the 
physical optical transmission section 
Optical Multiplex Section (OMS) 
 Optical signal consisting of multiplexed payload wavelengths (each wavelength representing 
an individual optical channel) 
 Provides for optical amplification, dispersion compensation, and management overhead for the 
physical optical multiplex section 
 Provides multiplexing/demultiplexing of optical channels and management overhead for the 
optical multiplex section 
Optical Physical Section (OPS) 
 Optical signal consisting of multiplexed payload wavelengths but with no optical supervisory 
channel (each wavelength representing an individual optical channel) 
 Provides for optical amplification and dispersion compensation for the optical physical section 
 Provides multiplexing/demultiplexing of optical channels for the optical physical section 
Optical Channel (OCh) 
 Represents a single traffic signal (single wavelength), contains optical functions which allow 
purely optical implementations and electrical functions some of which reside in the OTU frame 
 Provides traffic signal generation and recovery (framing, scrambling, FEC, etc.) and 
management overhead for the optical channel (electrical functions) 
9 
OTN Layer Descriptions – Digital Layers 
Optical Channel Transport Unit (OTU) 
 Provides the electrical functions to support the management of an optical channel section, 
i.e., section monitor (section trail trace identifier, section error detection code (BIP-8), 
defect indication functions, general communications channel) 
 Provides for transport of the optical channel data unit 
Optical Channel Data Unit (ODU) 
 Provides the electrical functions to support the management of an optical channel data 
path, i.e., path monitor (path trail trace identifier, path error detection code (BIP-8), defect 
indication functions), general communications channel, and automatic protection switching 
channel 
 Provides the electrical functions to support the management of optical channel data tandem 
connections, i.e., tandem connection monitors (tandem connection trail trace identifier, 
tandem connection path error detection code (BIP-8), defect indication functions), and 
automatic protection switching channel 
 Provides for transport of the optical channel payload 
Optical Channel Payload Unit (OPU) 
 Supports the mapping of a variety of client signal types (GFP, constant bit-rate (SDH), etc.) 
 Provides payload type defect detection 
 Provides payload structure information and defect detection (supports ODU multiplexing) 
10 
OTN Frame Structure – Electrical Layers 
ODUk OH 
FA OH OTUk OH 
OPUk Payload 
(4 x 3808 bytes) 
OTUk FEC 
(4 x 256 bytes) 
O 
P 
U 
k 
OH 
1 
2 
3 
4 
1 7 8 14 15 16 17 3824 3825 4080 
Column 
Row 
Overhead for Frame Alignment 
Overhead for ODU Operations (Tandem Connection and Path) 
Overhead for the OTU Operations (Section) 
Overhead for Client Mappings 
Payload for Client Signal 
Forward Error Correction 
Supports Forward Error Correction (FEC) for reach extension 
Supports section, tandem connection and end-to-end path monitoring (Fault & PM) 
Supports transparent client mapping and transport (data & timing) 
11 
OTN Layers – End-to-End 
OMS Link 1
OCH/OTU 
Link 1
ODU SNC
OCH/OTU 
Link 2
OMS Link 2
Node 2 Node 3 Node 4Node 1
Client Port
SONET/SDH 
Ethernet
Fibre Channel
OTS Link 1 OTS Link 2 OTS Link 3
3R
ODU SNC 
Client Service 
OMS Link 1 
OCH/OTU Link 1 
ODU Path from 
Source to Destination 
(ODU termination) 
Client Port 
OCH/OTU Link 2 
OMS Link 2 
Integrated 
WDM Optics SR Optics 
ODU Switch ODU Switch OCH Switch 
OTU Sections between 
Regeneration Points 
(OTU termination) 
Transponder/
Regenerator 
Optical 
Amplifier 
OTS Link 1 
OTS Link 2 
OMS Sections between 
Optical Add/Drop Points 
(OMS termination) 
OTS Sections between 
Optical Amplifier Points 
(OSC termination) 
12 
OTM 
Overhead 
Signal 
(OOS) 
Optical Transport Module (OTM) - Interface 
Optical Transmission Section (OTS) 
Optical Multiplex Section (OMS) 
OCC OCC OCC OCC 
Optical Channel (OCh) 
 OCh Transport Unit (OTU) Payload OTU OH FEC 
 OCh Data Unit (ODU) Payload ODU OH 
 OCh Payload Unit (OPU) Payload OPU OH 
Client 
OTS 
OH 
OMS 
OH 
OCC 
OH 
OCC 
OH 
OCh 
OH 
For Transmission 
For Switching and Multiplexing 
For Client Service Mapping 
For Management 
Optical Channel Carrier (OCC) 
Analog 
Digital 
E/O and O/E Adaptation 
13 
Single Channel Interfaces – OTM-0.m 
Reduced functionality interfaces (no OOS/OSC - OPS) 
supporting various OTUk data rates 
 OTM-0.m represents a single channel uncolored interface (m identifies the 
supported data rates, e.g., m=234 identifies supporting 10G/40G/100G data 
rates) 
Domain A Domain Z 
3R 
3R 
3R 
…
 
3R 
3R 
3R 
…
 
MPI-S 
MPI-S 
MPI-S 
MPI-R 
MPI-R 
MPI-R 
IrDI 
λs 
λs 
λs 
MPI-S=Single channel Main Path Interface Source 
MPI-R=Single channel Main Path Interface Receive 
14 
Multi-Channel Interfaces – OTM-0.mvn, OTM-nr.m, OTM-n.m 
Reduced functionality interfaces (no OOS/OSC - OPS) and full functionality 
interfaces (include OOS/OSC – OTS/OMS) supportingvarious OTUk data rates 
 OTM-0.mvn represents a parallel optical multi-lane interface (reduced functionality only, n = # of lanes) 
 OTM-n[r].m represents a multi-wavelength interface with wavelengths on ITU grid (n = maximum number 
of supported wavelengths) 
 Wavelength multiplexing/demultiplexing and optional optical booster amplifiers or optical pre-amplifiers 
Domain A Domain Z 
MPI-Sm 
MPI-Rm 
IrDI 3R 
3R 
3R 
…
 
3R 
3R 
3R 
…
 
OM 
OD 
OA 
OA 
3R 
3R 
3R 
…
 
3R 
3R 
3R 
…
 OM 
OD 
OA 
OA MPI-Rm 
MPI-Sm 
MPI-Sm=Multi-channel Main Path Interface Source 
MPI-Rm=Multi-channel Main Path Interface Receive 
15 
OTN IrDI Application Codes 
G.959.1 application code format: PnWx-ytz[s] 
where 
 P - (if present) indicates application code applies to any optical tributary signal 
within the class 
 n - defines the maximum number of optical tributary signals supported by the 
application code 
 W – indicates the span distance/attenuation supported by the application code 
 x – maximum number of spans 
 y – indicates the highest class (rate and format) of optical tributary signal 
supported for the application code 
 t – indicates power level assumptions (amplifier configurations) for the application 
code 
 z – indicates the source wavelength and fiber type 
 s – optional, indicates additional restrictions for the application 
 
Only single span application codes are currently defined in G.959.1 
 
16 
CWDM Application Codes 
G.695 application code format: CnWx-ytz[F] 
where 
 C - (if present) indicates application code applies to any optical tributary signal 
within the class 
 n - defines the maximum number of optical tributary signals supported by the 
application code 
 W – indicates the span distance/attenuation supported by the application code 
 x – maximum number of spans 
 y – indicates the highest class (rate and format) of optical tributary signal 
supported for the application code 
 t – indicates power level assumptions (amplifier configurations) for the application 
code 
 z – indicates the source wavelength and fiber type 
 F – optional, indicates the application requires FEC bytes be transmitted 
 
Only single span application codes are currently defined in G.695 
 
17 
Intra-office Application Codes 
G.693 application code format: W-yAz[F] 
where 
 W – indicates the span distance/attenuation supported by the application code 
 y – indicates the highest class (rate and format) of optical tributary signal 
supported for the application code 
 A – indicates the attenuation category 
 z – indicates the source wavelength and fiber type 
 F – optional, indicates the application requires FEC bytes be transmitted 
 
 
 
18 
OTN Bitrates 
ODU0 
ODU1 
ODU2 
ODU3 
ODU4 
1.244 
2.499 
10.037 
40.319 
104.794 
OTU1 
OTU2 
OTU3 
OTU4 
2.666 
10.709 
43.018 
111.810 
ODU1e OTU1e 
ODU2e † OTU2e 10.400 
10.356 
11.096 
11.049 
OTU3e1 
OTU3e2 44.583 
44.569 ODU3e1 
ODU3e2 41.786 
41.773 
All rates provided in Gbps and times in μs 
OTU rate based on RS (255,239) FEC coding 
Based on support for 100GE 
(10 × OC192/STM64 × 239/227 
OC768/STM256/40GE × 239/236 
OC192/STM64 × 239/237 
OC48/STM16 × 239/238 
Based on support for GE 
(1/2 of ODU1 payload) 
10GE* × 239/238 
10GE** × 239/237 
Based on support for 4 x ODU2e (@1.25G TS) 
(OC768/STM256 × 243/217 × 239/255) 
G.709 Defined Rates 
Non-Standard Supplemental Rates 
* Transparent 10.3125 Gbps Bitstream 
** Transparent 10.3125 Gbps Bitstream (Includes Fixed Stuff Bytes) 
† ODU2e is included in G.709 
× 255/239 
Based on support for 4 x ODU2e (@2.5G TS) 
(4 x ODU2e × 239/238) 
48.971 
12.191 
3.035 
1.168 
11.767 
11.816 
2.928 
2.929 
98.354 
Frame 
Times 
19 
ODUFlex (2011 Update) 
Flexible ODU rate for transport of arbitrary client rates to 
improve ODUk bandwidth usage (transport efficiency) 
Constant Bit Rate (CBR) client signals 
ODUflex Rate = 239/238 x CBR rate with up to ± 100ppm clock tolerance 
(synchronous to client clock) 
For GFP-F mapped packet client signals 
ODUflex Rate (suggested) = N × ~1.25* Gbps with ± 100ppm clock tolerance 
(G.709 Amendment 2, 04/2011) 
* Bandwidth per tributary slot (ts) varies according to line rate: 
 ODU2: 1.249G/ts x up to 8ts  10.037G (max); 
 ODU3: 1.254G/ts x up to 32ts  40.319G (max); 
 ODU4: 1.301G/ts x up to 80ts  104.794G (max) 
Traditional ODU2 
ODUflex @ 5 x 1.25Gbps Tributary Slots 
Stranded Capacity 
Re-usable Capacity 
6 Gbps Client 
20 
Potential ODUflex (CBR) Client Rates 
Potential CBR Client Signal Client Rate (Gbps) 
ODUflex (CBR) 
Rate (Gbps) 
Tolerance 
(ppm) 
1xSDR InfiniBand 2.500000000 2.510504202 100 
3G-SDI Video (NTSC rate) 2.967032967 2.979499492 10 
3G-SDI Video (PAL rate) 2.970000000 2.982478992 10 
CPRI level 4 3.072000000 3.084907563 0.002 
4G Fibre Channel 4.250000000 4.267857143 100 
CPRI level 5 4.915200000 4.935852101 0.002 
1xDDR InfiniBand 5.000000000 5.021008403 100 
CPRI level 6 6.144000000 6.169815126 0.002 
8G Fibre Channel 8.500000000 8.535714286 100 
CPRI level 7 9.840400000 9.881746218 0.002 
4xSDR InfiniBand 10.000000000 10.042016807 100 
1xQDR InfiniBand 10.000000000 10.042016807 100 
10G-SDI Video (NTSC rate) 10.681318681 10.726198172 10 
10G-SDI Video (PAL rate) 10.692000000 10.736924370 10 
16G Fibre Channel 17.000000000 17.071428571 100 
8xSDR/4xDDR InfiniBand 20.000000000 20.084033613 100 
12xSDR InfiniBand 30.000000000 30.126050420 100 
8xDDR/4xQDR InfiniBand 40.000000000 40.168067227 100 
12xDDR InfiniBand 60.000000000 60.252100840 100 
8xQDR InfiniBand 80.000000000 80.336134454 100 
12xQDR InfiniBand 120.000000000 120.504201681 100 
Notes: 
G.709 allows any ODUflex(CBR) 
rate > 2.48832G 
InfiniBand covers very broad 
range of rates (2.5G-120G line 
rate, 2G-96G data rate) 
Video has pairs of closely 
related rates (x and x/1.001) 
CPRI requires very tight clock 
tolerance (0.002ppm) 
G.709 mapping defined 
 
G.709v3 Appendix XI 
 
G.709 Living List client 
 
Other known CBR clients 
21 
Differences between SONET/SDH & OTN 
Synchronous clocking 
architecture 
Originally specified to operate on a 
single wavelength 
SONET/SDH only scales to 40G 
Uses a fixed frame rate and 
increases frame size as the speed 
increases 
 Sized for voice data rate 
 64kb/s voice requires 8,000 
bytes/s (1 byte/125 µs) 
 i.e. 1 frame/125 µs 
Section, Line, and Path layers 
Asynchronous clocking 
architecture 
Designed to operate on multiple 
wavelengths (DWDM) 
OTN scales to 100G (and beyond) 
Uses a fixed frame size and 
increases the frame rate as the 
speed increases 
 Sized for error correction to 
correct 16 blocks per frame 
 Reed Solomon RS(255/239) 
 i.e. Correct 8 bit errors/block 
Section and Path layers only 
SONET/SDH OTN 
22 
Standards and References 
ITU-T Recommendations 
 G.693 - Optical interfaces for intra-office systems 
 G.695 - Optical interfaces for coarse wavelength division applications 
 G.709 - Interfaces for the Optical Transport Network (OTN) 
 G.798 - Characteristics of optical transport network hierarchy equipment functional blocks 
 G.808.1 - Generic protection switching - Linear trail and subnetwork protection 
 G.870 - Terms and definitions for Optical Transport Networks (OTN) 
 G.871 - Framework for optical transport network Recommendations 
 G.872 - Architecture of optical transport networks 
 G.873.1 - Optical Transport Network (OTN): Linear protection 
 G.874 - Management aspects of the optical transport network element 
 G.874.1 - Optical transport network (OTN): Protocol-neutral management information model for the network 
element view 
 G.959.1 - Optical transport network physical layer interfaces 
 G.8201 - Error performance parameters and objectives for multi-operator international paths within the 
Optical Transport Network (OTN) 
 G.8251 - The control of jitterand wander within the optical transport network (OTN) 
 G.Sup43 - Transport of IEEE 10G Base-R in Optical Transport Networks (OTN) 
OTN Overhead Functions 
24 
OTN Overhead – Optical Layers 
Overhead transported via Optical Supervisory Channel (OSC) 
 OSC and OOS (OTM Overhead Signal) signal format are not standardized 
 
Overhead covers payload channels and overhead channel (OSC) 
 OTS Layer: Trail Trace identifier (TTI) – used to verify fiber connectivity 
 Payload Missing indication (PMI) – used to suppress downstream LOS-P 
 Backward Defect Indication (BDI-P and BDI-O) – used for single-ended 
 maintenance 
 OMS Layer: Payload Missing indication (PMI) – used to suppress downstream LOS-P 
 Forward Defect Indication (FDI-P and FDI-O) – optical AIS 
 Backward Defect Indication (BDI-P and BDI-O) – used for single-ended 
 maintenance 
 OCh Layer: Forward Defect Indication (FDI-P and FDI-O) – optical AIS 
 Open Connection indication (OCI) – used to indicate cross-connection status 
 
Overhead termination/generation 
 OTS overhead is terminated/sourced at every node 
 OMS overhead is terminated/sourced at every OADM node, but passed through OLA nodes 
 OCh overhead is terminated/sourced or passed through at an OADM node 
25 
OTN Overhead Functions – Electrical Layers 
Continuity Supervision 
Connectivity Supervision 
Maintenance Information 
Signal Quality Supervision 
Management Communications 
Monitors the integrity of a link (LOS, OCI, LTC) 
Monitors the integrity of a sequence of connections by comparing source and 
destination IDs (TIM) 
Monitors performance after transmission via error parity check (DEG) 
Provides communications channels for path and section management 
communications and path protection communications (FOP) 
Suppress alarm escalation by informing upstream/downstream of defects (PMI, 
FDI, AIS, BDI, IAE, BIAE) 
Supports single-ended supervision of a connection (OCI, LCK) 
Frame 
Alignment 
Path 
Monitoring 
Section 
Monitoring 
Tandem 
Connection 
Monitoring 
Payload 
Management 
Payload Supervision Monitors for correct client payload at source and destination by matching 
payload type (PLM) and monitors for incoming client signal failure (CSF) 
Alignment Supervision Monitors alignment of OTN frames (LOF, LOM, LOFLOM, LOL, LOFLANE) 
Multiplexing Supervision Monitors the multiplex structure supporting single-stage multiplexing (MSIM) 
26 
OTN Frame Structure – Electrical Layers 
ODUk OH 
FA OH OTUk OH 
OPUk Payload 
(4 x 3808 bytes) 
OTUk FEC 
(4 x 256 bytes) 
O 
P 
U 
k 
OH 
1 
2 
3 
4 
1 7 8 14 15 16 17 3824 3825 4080 
Column 
Row 
Overhead for Frame Alignment 
Overhead for ODU Operations (Path) 
Overhead for the OTU Operations (Section) 
Overhead for Client Mappings 
Payload for Client Signal 
Forward Error Correction 
Add 1 overhead byte for every 238 payload bytes = 239 
Add 16 FEC bytes for every {238+1 = 239} bytes = 255 
Repeat 16 times per row x 4 rows = 16,320 bytes per frame 
27 
Forward Error Correction (FEC) 
Forward Error Correction (FEC) 
 Add redundancy to a message through encoding prior to transmission to enable 
the receiver (decoder) to correct errors induced in the communication channel 
 Roughly 7% of each OTN frame is dedicated to an error correcting code 
 Resulting in (choice of) lower error rates, lower transmission power, greater 
transport distance 
 Standardized G.975 (Reed-Solomon) code and proprietary enhanced codes 
 
Reed-Solomon Code (RS) 255/239 
 239 base data bits 
 16 added overhead bits: (6.7% overhead) 
 Corrects for 8 or less bit errors in 239 bits 
 8 x 16 x 4 = 512 bits per OTU frame 
 Anything over 8 bits is completely uncorrected 
 Typical gain is ~6.5 dB at 1e-12 BER 
OSNR (dB) 
Log 
BER 
10-12 ~6.5dB Gain @ 10
-12 BER 
With FEC 
No FEC 
28 
Reed-Solomon FEC RS (255/239) 
1 2 238 
1 
2 
3 
4 
1 16 17 3825 3840 
Column 
Row 32 33 48 3808 3824 
1 2 239 
OH 
(1 byte) 
Payload 
(238 bytes) 
240 255 
FEC 
(16 bytes) 
3841 3856 
16 
4065 4080 
2 1 
239 
1 2 239 
OH 
(1 byte) 
Payload 
(238 bytes) 
240 255 
FEC 
(16 bytes) 
1 2 239 
OH 
(1 byte) 
Payload 
(238 bytes) 
240 255 
FEC 
(16 bytes) 
Overhead Payload FEC 
255 239 255 239 255 
Information 
Parity 
Check 
Information 
Parity 
Check 
Information 
Parity 
Check 
16 OTU 
Sub-rows 
per OTUk 
Frame 
x 4 rows 
29 
DAPI 
(destination) 
OTN Overhead Details – Electrical Layers 
ACT Activation/deactivation control channel 
APS Automatic Protection Switching channel 
BDI Backward Defect Indication 
BEI Backward Error Indication 
BIAE Backward Incoming Alignment Error 
BIP-8 Bit Interleaved Parity – level 8 
DAPI Destination Access Point Identifier 
DMp Delay Measurement – path level 
DMtn Delay Measurement – tandem level n 
EXP Experimental 
FTFL Fault Type and Fault Location channel 
GCC General Communications Channel 
IAE Incoming Alignment Error 
JC Justification Control 
MFAS Multi-frame Alignment Signal 
NJO Negative Justification Opportunity 
PCC Protection Communication Channel 
PM Path Monitor 
PSI Payload Structure Identifier 
PT Payload Type 
RES Reserved 
SAPI Source Access Point Identifier 
SM Section Monitor 
STAT Status 
TCM Tandem Connection Monitor 
TTI Trail Trace Identifier 
Frame Alignment MFAS SM GCC0 RES 
RES TCM6 TCM5 TCM4 TCM ACT FTFL 
TCM3 TCM2 TCM1 PM EXP 
GCC1 GCC2 APS/PCC RES 
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 
1 
2 
3 
4 
Row 
Column 
TTI BIP-8 
1 2 3 
Section, Path & Tandem Connection Monitor 
SAPI 
(source) 
Operator 
Specific 
0 
15 
16 
31 
32 
63 
BEI/BIAE BDI RES 
BEI/BIAE BDI STAT 
BEI BDI STAT 
IAE SM 
TCMi 
PM 
RES 
RES 
RES 
PSI NJO 
JC 
JC 
JC 
PSI 
PT 
MSI/RES 
PM& 
TCM 
DMt1 
PM& 
TCM DMt2 DMt3 DMt4 DMt5 DMt6 DMp RES 
Path & Tandem Connection Delay 
RES 
30 
Overhead Descriptions – Alignment 
Frame Alignment Signal (FAS) 
 Provided in the OTU frame to allow determination of the beginning of the OTU frame 
 Detection of framing failure results in Loss of Frame (LOF) indication 
Multiframe Alignment Signal (MFAS) 
 Provided in the OTU frames to align overhead functions that require multiple frame operation 
(e.g., Trail Trace Identifier (TTI) functions at OTU/ODU layers; fault type and fault locate, 
tandem connection activation, mapping functions, and automatic protection switch functions 
at ODU layer) 
 Detection of multi-framing failure results in Loss of Multi-frame (LOM) indication 
Incoming Alignment Error (IAE, included in STAT field for TCMs) 
 Provided in the OTU and ODU frames to detect frame alignment errors detected by upstream 
equipment (occurs for through-timed equipment when incoming clock signal is lost) 
 Detection of alignment error results in suppression of near-end and far-end performance 
monitoring data for current and previous seconds 
Backward Incoming Alignment Error (BIAE, included in BEI field) 
 Provided in the OTU and ODU frames to detect frame alignment errors detected by 
downstream equipment (due to a detection of an IAE at a downstream node) 
 Detection of alignment error results in suppression of far-end performance monitoring data for 
current and previous seconds 
31 
OTN Framing 
Frame 
Type 
IF Time 
(μS) 
ODU0 197 
OTU1/
ODU1 
97.9 
OTU2/
ODU2 
24.4 
ODU2e 23.5 
OTU3/
ODU3 
6.07 
OTU4/
ODU4 
2.34 
OA1 Framing Bytes (FAS & MFAS): 
OA1 = ‘1111 0110’ 
OA2 = ‘0010 1000’ 
MFAS = 8-bit counter 
OA1 OA1 OA2 OA2 OA2 MFAS Row 1 
Column 
1 2 3 4 5 6 7 
Out of 
Frame 
In 
Frame 
IF to OOF 
(OTUk) 
OOF to IF 
(any 4 bytes for OTUk, all bytes for ODUj demux) 
Invalid FAS/MFAS for 5 frames 
Valid FAS/MFAS for 2 frames 
FAS 
Frame 
Type 
OOF 
Time (μS) 
ODU0 492 
OTU1/
ODU1 
245 
OTU2/
ODU2 
61.0 
ODU2e 58.8 
OTU3/
ODU3 
15.2 
OTU4/
ODU4 
5.84 
IF to OOF 
(ODUj demux) 
LOF/LOM:OTUk 
LOFLOM: ODUj demux 
Set when OOF for >3ms 
Cleared when IF for >3ms 
32 
OTN Signal Regeneration Model 
ODUj ODUj ODUj 
ODUk/OTUk 
OH Generation 
(Local clock) 
OTUk CDR & 
OTUk/ODUk OH 
Termination 
OTUk Section Regenerator Chain 
ODUk ODUk ODUk 
OTUk OH 
Generation 
& Retiming 
OTUk CDR 
& OH 
Termination 
OTUk OH 
Generation 
& Retiming 
OTUk CDR 
& OH 
Termination 
OTUk OH 
Generation 
& Retiming 
OTUk CDR & 
OH 
Termination 
OTUk OTUk 
OTUk OTUk 
OTUk CDR & 
OTUk/ODUk OH 
Termination 
OTUk CDR & 
OTUk/ODUk OH 
Termination 
ODUk/OTUk 
OH Generation 
(Local clock) 
ODUk/OTUk 
OH Generation 
(Local clock) 
ODUk/j 
Demux & 
ODUj CR 
ODUk/j 
Mux 
ODUk/j 
Mux 
ODUk/j 
Mux 
ODUk/j 
Demux & 
ODUj CR 
ODUk/j 
Demux & 
ODUj CR 
X X X 
ODUj Path Mux/Demux Chain 
OTUk frame slip (OTUk LOF) propagates until CDR switches to local clock 
ODUj frame slip (ODUj LOFLOM) propagates until demultiplexer switches to local clock 
Incoming frame slip 
Incoming frame slip 
33 
IAE and BIAE Processing (OTUk/section or ODUkT/path) 
frame slip incoming 
to section or 
tandem connection 
Inserted after 
reframe or switch 
to local clock 
(active for 4096 frames) 
Detect incoming IAE, 
Suppress near/far end PM for 
current and previous second 
that IAE is active 
Detect incoming BIAE, 
Suppress far end PM for 
current and previous second 
that BIAE is active 
OOF propagates downstream 
OOF OOF 
Node A Node Z 
OTUk section or 
ODUkT tandem connection 
IAE dIAE 
aBIAE 
IF 
LOF/LOFLOM 
clear or switch 
to local ref 
dBIAE 
Loss of upstream framing causes errors in performance monitoring of 
downstream sections and/or tandem connections 
 IAE function informs downstream nodes of upstream problems 
 BIAE function provides notification in backward direction 
 Generation/detection of IAE/BIAE does not affect end-to-end path monitoring 
34 
Path and Tandem Connection Monitoring (PM & TCM) 
Provide management visibility at multiple (nested) levels 
Path CM 
User 
User Operator A 
Operator B 
Operator C ODUk 
Client 
Signal 
Client 
Signal 
UNI CM 
NNI CM NNI CM NNI CM 
TCM6 
TCM5 
TCM4 
TCM3 
TCM2 
TCM1 
TCM6 
TCM5 
TCM4 
TCM3 
TCM2 
TCM1 
TCM6 
TCM5 
TCM4 
TCM3 
TCM2 
TCM1 
TCM6 
TCM5 
TCM4 
TCM3 
TCM2 
TCM1 
TCM6 
TCM5 
TCM4 
TCM3 
TCM2 
TCM1 
QoS of Leased Connection is Monitored by User 
TCM6 
TCM5 
TCM4 
TCM3 
TCM2 
TCM1 
TCM6 
TCM5 
TCM4 
TCM3 
TCM2 
TCM1 
TCM6 
TCM5 
TCM4 
TCM3 
TCM2 
TCM1 
TCM6 
TCM5 
TCM4 
TCM3 
TCM2 
TCM1 
TCM6 
TCM5 
TCM4 
TCM3 
TCM2 
TCM1 
TCM6 
TCM5 
TCM4 
TCM3 
TCM2 
TCM1 
TCMi 
Overhead 
TCM6 
TCM5 
TCM4 
TCM3 
TCM2 
TCM1 
35 
Tandem Connection Monitoring Modes 
Transparent Mode (source and sink ends) 
 Pass all TCM overhead unchanged 
Monitor Mode (sink end only) 
 Pass all TCM overhead unchanged but report state of TC (shadow data) 
 Extract TCM overhead including TTI, BIP-8, DMti, BDI, BEI, and STAT 
 Detect defects including AIS, OCI, LCK, LTC, TIM, DEG, IAE and BIAE 
 Compute BIP-8 and count errors and defect second in one second period to feed PM 
 Count number frames for delay measurements 
 Generate BDI, BEI and BIAE upstream 
Operational Mode 
 At source end: 
 Compute BIP-8 and insert TCM overhead including TTI, BIP-8, DMti, BDI, BEI and BIAE 
 Detect frame slip and insert IAE 
 Insert APS/PCC fields for protection switching (future) 
 At sink end: 
 Perform functions provided by Monitor mode but set downstream TCM overhead to all zeros 
 Perform downstream consequent actions (send AIS for OCI/LCK/TIM, send TSF/TSD) 
 Retrieve APS/PCC fields for protection switching (future) 
Non-Intrusive Monitor (sink function only) 
 Same functions as Monitor Mode except BDI, BEI and BIAE are not generated upstream 
 Generate TSF/TSD for protection switching 
36 
Tandem Connection Visibility 
Service Provider Domain 
Backhaul 
Domain Underse
a 
Domain 
TCM6 
TCM5 
TCM4 
TCM3 
TCM2 
TCM1 
TCM6 
TCM5 
TCM4 
TCM3 
TCM2 
TCM1 
TCM6 
TCM5 
TCM4 
TCM3 
TCM2 
TCM1 
TCM6 
TCM5 
TCM4 
TCM3 
TCM2 
TCM1 
TCM6 
TCM5 
TCM4 
TCM3 
TCM2 
TCM1 
TCM6 
TCM5 
TCM4 
TCM3 
TCM2 
TCM1 
TCM6 
TCM5 
TCM4 
TCM3 
TCM2 
TCM1 
TCM6 
TCM5 
TCM4 
TCM3 
TCM2 
TCM1 
Backhaul 
Domain 
Problem: Performance data within a nested TCM may not be available for 
sectionalization (example: drippling errors within a nested domain) 
Application: Multi-carrier domain configurations (example: end-to-end 
Service Provider providing service through 3rd party undersea link) 
37 
Tandem Connection Shadow 
Solution: TCM termination does not reset TCM overhead bytes at the 
destination end of the TCM, TCM shadow data continues to propagate and 
is monitored further downstream (capability recently added to G.798) 
Issues: Shadow data is affected by downstream domain performance 
degradation, implementation requires negotiation of TCM functionality 
across domains 
38 
SNCP and TCM 
Non-intrusive TCMs Non-intrusive TCMs 
Operational TCM Operational TCM 
TCM layer is used to provide SNCP service and protection switch criteria 
which is not subject to faults occurring outside of the domain 
 TCM layer is terminated on the drop and provides PM relative to service as 
opposed to either individual SNC 
 TCM monitors on the line side provide input to determine which path to select 
39 
5430 TCM Usage 
Problem: OTUk SM layer terminated at each segment 
 Provides direct fault isolation to a given segment in the network, however, failure across OTUk regenerators 
or between two DWDM transponders is only visible to ODUk switch at the PM layer 
Solution: TCM4 (default) used to isolate failures between two switching nodes 
 Every inter-switch line in the network utilizes this same TCM layer supporting role based usage of this TCM 
layer for providing link monitoring between switching nodes 
Problem: Domain SNCs may not terminate ODUk PM layer 
 No end-to-end SNC monitoring is available via the PM layer (intermediate path monitoring non-standard) 
Solution: TCM3 (default) used to provide per domain service level SNC monitoring associated 
 Every SNC in the network utilizes the same TCM layer supporting role based usage of this TCM layer for 
providing end-to-end SNC monitoring. 
OMS 
SM 
TCM4 
TCM3 
PM 
Client 
OTUk / OCh 
OMS 
OTUk / OCh ODUk Switch Nodes 
40 
Overhead Descriptions – Connectivity and Continuity 
TTI (Trail Trace Identifier) 
 Provided in the OTU/ODU frame to allow detection of connectivity errors 
 Supports provisioning of transmitted and expected values and allows retrieval of 
accepted value 
 Provides disabled, source access point identifier (SAPI), destination access point 
identifier (DAPI), and SAPI+DAPI modes; provides mode for disabling automatic actions 
due to trace identifier mismatch 
 Detection of trace identifier mismatch results in Trail trace Identifier Mismatch (TIM) 
indication 
OCI (Open Connection indication, provided by STAT field for TCM/PM) 
 Provided in the ODU frame to allow detection of continuity errors by indicating the status 
of a switch matrix connection 
 Generation/detection of ‘110’ results in Open Connection Indication (OCI) condition 
(entire ODU frame except framing and FTFL bytes replaced with ‘01100110’) 
41 
Trail Trace Identifier Format 
SAPI[0] and DAPI[0] are set to All-0s 
7 84 5 61 2 3
15
1
2
…
..…
SAPI[1]
SAPI[2]
SAPI[15]
…
..…
DAPI[1]
DAPI[2]
DAPI[15]
…
..…
31
17
18
…
..…
0
16
32
63
…
…
…
…
…
…
…
…
…
…
…
…
…
..
Operator
Specific
SAPI[0]
DAPI[0]
Destination
Access
Point
Identifier
Source
Access
Point
Identifier
0
0
0
…
..…
0
0
0
…
..…
NS character #IS character #
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
CC ICC
ICC
ICC
ICC
ICC
ICC
CC
CC
CC
CC
CC
UAPC
UAPC
UAPC
UAPC
UAPC
UAPC
CC = ISO 3166 Country Code 
ICC = ITU Carrier Code as per ITU-T Rec. M.1400 
UAPC = Unique Access Point Code is carrier specific 
 All TTIcharacters are from the T.50 character set 
 Only SAPI and DAPI fields used for TIM detection 
 Operator Specific bytes are user specified 
SAPI/DAPI Field Format 
42 
SAPI and DAPI Applications 
Point-to-Point 
Application 
(unidirectional or bidirectional) 
Point-to-Multipoint 
Application 
(unidirectional bridge) 
Multipoint-to-Point 
Application 
(unidirectional select) 
 
(Note: only supported on 
5430 for 2:1 selector) 
Transmitted TTI Expected SAPI or SAPI+DAPI 
Transmitted TTI 
Expected SAPI 
Expected SAPI 
Expected SAPI 
Transmitted TTI 
Expected DAPI Transmitted TTI 
Transmitted TTI 
43 
Overhead Descriptions – Signal Quality 
FEC (Forward Error Correction) 
 Provided in the OTU frame to allow detection and correction of line bit errors 
BIP-8 (Bit Interleaved Parity-8) 
 Provided in the OTU/ODU frame to allow detection of near-end bit errors and support 
performance monitoring and protection switching functions (Signal Degrade, Note: signal fail 
due to BER detection not provided) 
 Detection of bit error counts are reported to the far end via the backward error indication 
field (BEI) on a frame-by-frame basis 
 Detection of bit errors within a frame generates an errored block (errored block counts are 
the basis for near-end PM parameter value determination) 
 Detection of N successive degraded seconds (based on percentage of errored blocks) 
results in a Degraded (DEG) indication 
BEI (Backward Error Indication) 
 Provided in the OTU/ODU frame to allow detection of far-end bit errors and support 
performance monitoring (single-ended maintenance) 
 Detection of bit errors within a frame generates an errored block (errored block counts are 
the basis for far-end PM parameter value determination) which are reported back to the near-
end via BEI bits 
PM&TCM DMp & DMt[1-6] (path Delay Measurement) 
 Provided in the ODU frame to allow measurement of round trip latency 
44 
BIP-8 Generation 
BIP-8
Fr
am
e 
n
1
2
3
4
1
2
3
4
Fr
am
e 
n+
2
1
2
3
4
Fr
am
e 
n+
1
1 14 15 3824……………………………………
SM
BIP-8
PM
BIP-8
TCM4
BIP-8
TCM5
BIP-8
TCM6
BIP-8
TCM4
BIP-8
TCM5
BIP-8
TCM6
BIP-8
SM
BIP-8
PM
BIP-8
TCM4
BIP-8
TCM5
BIP-8
TCM6
BIP-8
TCM4
BIP-8
TCM5
BIP-8
TCM6
BIP-8
SM
BIP-8
PM
BIP-8
TCM4
BIP-8
TCM5
BIP-8
TCM6
BIP-8
TCM4
BIP-8
TCM5
BIP-8
TCM6
BIP-8
………………………………………
 BIP-8 computed over the OPU frame for all monitors 
 Allows ODU overhead to be modified without recomputing BIP-8 values 
(essential for tandem connection monitoring) 
45 
BIP-8 Error Detection and BEI Generation 
BIP-8
OTUk
BEI
OTUk
BBE
1 14 15 3824…………………………………………………………………………
>0
ODUkP
BEI
ODUkP
BBE
XOR
# of
BIP
Errors
ODUkT
BBE
ODUkT
BEI
Fr
am
e 
n
1
2
3
4
1
2
3
4
Fr
am
e 
n+
2
1
2
3
4
Fr
am
e 
n+
1
SM
BIP-8
PM
BIP-8
TCM4
BIP-8
TCM5
BIP-8
TCM6
BIP-8
TCM4
BIP-8
TCM5
BIP-8
TCM6
BIP-8
SM
BIP-8
PM
BIP-8
TCM4
BIP-8
TCM5
BIP-8
TCM6
BIP-8
TCM4
BIP-8
TCM5
BIP-8
TCM6
BIP-8
SM
BIP-8
PM
BIP-8
TCM4
BIP-8
TCM5
BIP-8
TCM6
BIP-8
TCM4
BIP-8
TCM5
BIP-8
TCM6
BIP-8
XOR
XOR
# of
BIP
Errors
# of
BIP
Errors
>0 >0
 BBE/BEI counts used to calculate NE/FE PM 
 BBE count used to trigger DEG defect 
46 
TCM Latency Measurement 
Latency measurement accuracy determined by frame time and delay 
asymmetry between transmit and receive directions 
 Receive and transmit frames are not synchronous nor in-phase resulting in 
latency variation of up to one frame time (single frame uncertainty at source and 
loopback divided by two) 
 Delay asymmetry results in latency error of one-half the delay differential 
between the transmit and receive delay 
0 0 0 0 1 1 1 1 
Calculate latency = (Nf – Ni)×Tframe/2, 
 where Tframe=ODU frame time 
 
 errormax ≤ Tframe + (Dr-Dt)/2, 
 where Dr and Dt are receive and 
 transmit propagation delays 
A-end node configured 
to source and measure 
specific PM/TCM DM bit 
A Z 
Z-end node configured 
to loopback specified 
PM/TCM DM bit 
1 2 
3 Insert bit transition 
into specified 
PM/TCM DM bit 
and start frame 
counter (value=Ni) 
4 Detect bit transition 
on specified 
PM/TCM DM bit 
and stop frame 
counter (value=Nf ) 
1 1 1 1 0 0 0 0 
5 
Tframe 
47 
5430 Latency Based Routing 
Lowest Cost Routing - Default 
• Assuming all Admin Weights are the same then 
algorithm will chose the lowest hop count for the route 
• Default Admin Weight is 5040 
AW: 5040 AW: 5040 
AW: 5040 AW: 5040 
AW: 5040 
Lowest Cost Routing – Admin 
Weight 
• Operator has modified Admin Weights on two center 
spans 
• Route = lowest summed admin weight 
AW: 10000 AW: 15000 
AW: 5040 AW: 5040 
AW: 5040 
Lowest Cost Routing – Latency 
• Operator has enabled auto-latency calculation in the 
network (or applied them manually) and selected 
lowest latency option for the circuit 
• Route = lowest summed latency 
AW: 10000 AW: 15000 
AW: 5040 AW: 5040 
AW: 5040 
AW: Admin Weight 
LT: Latency 
LT: 4ms LT: 5ms 
LT: 1.5ms LT: 1ms 
LT: 3ms 
TODAY 
5430 
5430 
5430 
5430 
5430 
5430 
With 
Addition of 
Latency 
48 
Overhead Descriptions – Maintenance Signals 
AIS (Alarm Indication Signal, provided by STAT field for 
TCM/PM) 
 Provided in the ODU frame to allow generation/detection of failure 
suppression signal 
 Generation/detection of ‘111’ results in Alarm Indication Signal (AIS) condition 
(entire ODU frame except framing and FTFL bytes replaced with all-1s) 
LCK (Locked, provided by STAT field for TCM/PM) 
 Provided in the ODU frame to allow maintenance locking of ODU channel 
 Generation/detection of ‘101’ results in Locked (LCK) condition (entire ODU 
frame except framing and FTFL bytes replaced with ‘01010101’) 
BDI (Backward Defect Indication) 
 Provided in the OTU/ODU frame to allow detection of far-end defect conditions 
for single-ended maintenance 
FTFL (Fault Type Fault Locate) 
 Provided in the ODU frame to support fault sectionalization (256-byte multi-
frame message format) 
49 
ODUj or 
Client 
OTN Overhead Signal Interactions 
OCh OTUk ODUk 
Loss of Signal – Payload (LOS-P) 
Loss of Frame (LOF), Loss of Lane (LOL), 
Loss of Lane Frame (LOLFRAME) 
OTU Alarm Indication Signal (AIS) 
Loss of Multiframe (LOM) 
FEC Corrected Errors (FECcorrErr) 
Bit Interleaved Parity (BIP-8) 
Backward Error Indicator (BEI) 
Trace Identifier Mismatch (TIM) 
Backward Defect Indicator (BDI) 
Incoming Alignment Error (IAE) 
Section 
Monitoring 
(SM) Backward Incoming Alignment Error (BIAE) 
Path & 
Tandem Connection 
Monitoring 
(PM & TCM) 
Bit Interleaved Parity (BIP-8) 
Backward Error Indicator (BEI) 
Trace Identifier Mismatch (TIM) 
Backward Defect Indicator (BDI) 
Locked (LCK), Open Connection Indication (OCI), 
Loss of Tandem Connection (LTC, TCM only) (via STAT) 
Multiplex Structure identifier (MSI) ODUj-AIS 
Detect Generate 
Payload 
Structure Identifier 
(PSI) 
Optical 
Channel 
(OCh) 
Incoming Alignment Error (IAE) (via STAT,TCM only) 
Backward Incoming Alignment Error (BIAE) (TCM only) 
Payload Type (PT) 
Client Signal Fail (CSF) Client 
Specific 
Only applicable 
when TIM 
consequent actions 
are enabled 
E.g., PN-11, LF, etc. 
Alarm Indication Signal (AIS) (via STAT) 
ODUk-AIS 
Loss of Frame and Multiframe (LOFLOM, only 
applicable to ODUk/ODUj multiplexing) 
DEG 
DEG 
All detection and 
generation functions 
specified for the 
ODUk are repeated 
for the ODUj 
Signal Propagation Consequent Action Forward Operation Backward Operation 
50 
Mapping Overhead 
PT (Payload Type, part of PSI multi-frame) 
 Provided in the ODU (OPU OH) frames to allow detection of client payload mismatches 
 Detection of mismatch between expected and received payload types results in Payload Label 
Mismatch (PLM) indication 
 Auto-payload type function for legacy multiplexing support 
JC (Justification Control), NJO/PJO 
 Provided in the ODU frames (OPU OH) to control stuffing operationsfor client signal and ODUjk 
multiplexing rate adaptation (~131ppm range for client, ~197ppm range for muxing) 
 Fixed payload format (predetermined data and fixed stuff positions) 
 Supports synchronous and asynchronous client mapping and asynchronous ODUjk multiplexing 
GMP Overhead 
 Provided in the ODU frames (OPU OH) to control client signal rate adaptation and ODU multiplexing 
with wide clock tolerance range 
 Variable payload format (dynamic data and fixed stuff positions based on modulo arithmetic) 
 Supports generic client mapping and ODUj-21 multiplexing 
Other Mapping/Multiplexing Specific Overhead 
 VCAT OH – virtual concatenation overhead (NxODUk container creation) 
 MSI – multiplex structure identifier overhead (part of PSI used for ODUjk multiplexing) 
 CSF – Client signal fail indication 
51 
Control of OTN Timing 
OTN timing aspects are dominated by client mapping and muxing 
functions 
 Asynchronous mapping and muxing functions introduce phase discontinuities in 
data plane clocking that must be filtered 
 Discontinuities controlled by limiting buffer hysteresis (variation due to justification 
operations), and/or by providing residual phase information between justification 
events (residual buffer fill); 6.4ns/NE  640ns total: 13% or SDH wander budget or 
34% of SONET wander budget, OTN not a significant source of wander 
 Discontinuities are filtered at demuxing and demapping points to maintain OTN 
and client timing compliance (jitter), filter bandwidths determined by simulation 
UTC PRC 
OTN 
Island SSU 
SEC/ 
EEC 
SEC/ 
EEC 
SEC/ 
EEC 
Sync network limit 
Reference point 
Adapted Synchronization Reference Chain 
10x 
(100 OTN mapping/muxing operations) 
20 SEC/EEC 
1 mapping NE 
+ 9 muxing NEs 
Intervening SECs 
replaced with OTN 
equipment 
bounded by SSUs 
52 
Bit-synchronous Mapping 
LO ODUk clock is derived from and synchronous to the recovered client 
clock (no justification or dynamic rate adaptation performed) 
 LO ODUk clock = recovered client clock × 239/238 
 Client signal into ODUflex(CBR) 
 OC-48 into ODU1 
 LO ODUk clock = recovered client clock × 239/237 
 OC-192 into ODU2 
 Transparent 10GbE and transcoded FC-1200 into ODU2e 
 LO ODUk clock = recovered client clock × 239/236 
 OC-768 mapping to ODU3 
16 
NJO 
JC 
JC 
JC 
Column 
1 
2 
3 
4 
Row 
PJO 
Client Data Justification (0x00) 
Not used 
Not used 11 
10 
01 
00 
JC Bits NJO Byte PJO Byte 
Not used 
Not used 
Not used 
Not used 
53 
Frame 
N 
Frame 
N+1 
Frame 
N+2 
Bit-synchronous Mapping Procedure 
P 
• • • 
• • • 
• • • 
• • • 
00 
00 
00 
N 
Negative 
Justification 
Threshold 
Positive 
Justification 
Threshold 
OPU Payload OPU Overhead 
P 
• • • 
• • • 
• • • 
• • • 
00 
00 
00 
N 
P 
• • • 
• • • 
• • • 
• • • 
00 
00 
00 
N 
P 
• • • 
• • • 
• • • 
• • • 
00 
00 
00 
N 
Input Client 
Datastream 
First-In/ 
First-out 
Data Buffer 
Frame 
N+3 
54 
Asynchronous Mapping 
For client signal mapping, LO ODUk clock is derived from a local oscillator and the client signal 
is rate adapted using positive/zero/negative justification process (supports +/-45ppm client clock 
range) 
 Justification control overhead used to provide the positive/zero/negative indication 
 Negative justification opportunity (NJO) byte provides an additional client data position when required (client 
bandwidth > payload bandwidth) 
 Positive justification opportunity (PJO) byte (first payload byte following NJO byte) provides unused position 
when required (client bandwidth < payload bandwidth) 
 Supports OC-48/192/768 or STM-16/64/256 mapping into LO ODU1/2/3 
For ODUjk multiplexing, HO ODUk clock is derived from a local oscillator and the LO ODUk 
(ODUj) signal is rate adapted using positive/zero/negative justification process 
 Same mechanism as asynchronous client mapping except two PJO positions are defined (+1, +2 justification 
supported in order to provide required ppm range) 
 ODU0 mapped to ODU1 
 ODU1 mapped to ODU2/ODU3 
 ODU2 mapped to ODU3 
16 
NJO 
JC 
JC 
JC 
Column 
1 
2 
3 
4 
Row 
PJO1 
Client Data 
PJO2 
Justification (0x00) 
Client Data 
Justification (0x00) 
Justification (0x00) 
Client Data 
Client Data 
11 
10 
01 
00 
JC Bits NJO Byte PJO1 Byte PJO2 Byte 
PJO2 used only for multiplexing 
Justification (0x00) 
Client Data 
Justification (0x00) 
Justification (0x00) 
Client Data 
10 case used 
for multiplexing 
55 
Frame 
N 
No 
Justification 
Frame 
N+1 
Negative 
Justification 
Frame 
N+2 
No 
Justification 
Frame 
N+3 
Negative 
Justification 
Asynchronous Mapping Procedure – Fast Client 
P 
• • • 
• • • 
• • • 
• • • 
00 
00 
00 
N 
Negative 
Justification 
Threshold 
Positive 
Justification 
Threshold 
OPU Payload OPU Overhead 
P 
• • • 
• • • 
• • • 
• • • 
00 
00 
00 
N 
P 
• • • 
• • • 
• • • 
• • • 
00 
00 
00 
N 
P 
• • • 
• • • 
• • • 
• • • 
00 
00 
00 
N 
Input Client 
Datastream 
First-In/ 
First-out 
Data Buffer 
01 
01 
01 
01 
01 
01 
56 
Frame 
N 
No 
Justification 
Frame 
N+1 
Positive 
Justification 
Frame 
N+2 
No 
Justification 
Frame 
N+3 
Positive 
Justification 
Asynchronous Mapping Procedure – Slow Client 
P 
• • • 
• • • 
• • • 
• • • 
00 
00 
00 
N 
Negative 
Justification 
Threshold 
Positive 
Justification 
Threshold 
OPU Payload OPU Overhead 
P 
• • • 
• • • 
• • • 
• • • 
00 
00 
00 
N 
P 
• • • 
• • • 
• • • 
• • • 
00 
00 
00 
N 
P 
• • • 
• • • 
• • • 
• • • 
00 
00 
00 
N 
Input Client 
Datastream 
First-In/ 
First-out 
Data Buffer 
11 
11 
11 
11 
11 
11 
57 
Generic Mapping Procedure (GMP) 
For client signal mapping, LO ODUk clock is derived from a local oscillator and the client signal 
is rate adapted using GMP process (supports nearly unlimited client clock range) 
 GMP overhead used to signal the number of payload bytes carrying client data each payload frame (Cm) plus 
residual phase information (CnD) 
 Client data positions and unused payload bytes identified through modulo arithmetic algorithm 
 For payload positions j=1 to Cmax, if (j × Cm) mod Cmax < Cm, j is a client data byte 
 For payload positions j=1 to Cmax, if (j × Cm) mod Cmax ≥ Cm, j is a stuff byte (0x00) 
 Supports various client mappings 
 STM-1/4, OC-3/12, timing transparent GbE, and FC-200 into ODU0 
 HD-SDI video and FC-200 into ODU1 
 Transcoded 40GbE into ODU3 
 100GbE into ODU4 
For ODUj-21 multiplexing, HO ODUk clock is derived from a local oscillator and the LO ODUk 
signal is rate adapted using GMP process 
 Same mechanism as GMP client mapping except CnD fixed at C8D 
 Supports payload type 21 multiplexing 
 Any LO ODUk to ODU4 
 ODU0/2E/flex into ODU3 
 ODU0/flex into ODU2 
15 
JC3 
JC2 
JC1 
Column 
1 
2 
3 
Row 
Cm (bits 1-8) 
Cm (bits 9-14), II, DI 
CRC-5 
ΣCnD (bits 1-5) 
ΣCnD (bits 1-5) 
JC3 
JC2 
JC1 
CRC-8 
16 
JC6 
JC5 
JC4 
JC6 
JC5 
JC4 
OTN and OTN Client Signal Fault Propagation 
59 
Fault Propagation Example – Bidirectional Fiber Cut 
SM 
TCM4 
TCMi (opt) 
PM 
Client 
ODUk Switch Nodes 
ODU0 
OTU2 OTU3 OTU4 OTU2 OTU3 OTU4 
ODU0 
ODU3 
PM 
ODU2 
ODU4 
ODU0 XC ODU0 XC ODU0 XC ODU0 XC 
(tunnel) 
3rd Party OTN 
Domain 
2/0 0/3 3/0 0/2/3 4/2/0 0/4 4/0 0/2 
ODU0 
TCM3 
ODU0 
× 
LOS 
ODU0-AIS 
ODU0-AIS 
ODU0-AIS 
ODU3-AIS 
ODU0-IAE 
ODU0-BIAE 
LOS 
ODU3-AIS 
ODU0-AIS 
ODU0-AIS 
ODU0-AIS 
Frame slip 
ODU0 XC ODU0 XC 
60 
Fault Propagation Example – Deleted Cross-Connection 
SM 
TCM4 
TCMi (opt) 
PM 
Client 
ODU0 
OTU2 OTU3 OTU4 OTU2 OTU3 OTU4 
ODU0 
ODU3 
PM 
ODU2 
ODU4 
ODU0 XC ODU0 XC ODU0 XC ODU0 XC 
(tunnel) 
3rd Party OTN 
Domain 
2/0 0/3 3/0 0/2/3 4/2/0 0/4 4/0 0/2 
ODU0 
TCM3 
ODU0 
× 
ODU0-OCI 
ODU0-OCI 
ODU0-OCI 
ODU0-IAE 
ODU0-BIAE ODU0-OCI 
ODU0-OCI 
ODU0-OCI 
Frame slip 
ODU0 XC ODU0 XC 
ODUk Switch Nodes 
61Fault Propagation Example – TCM4 Maintenance LCK 
SM 
TCM4 
TCMi (opt) 
PM 
Client 
ODU0 
OTU2 OTU3 OTU4 OTU2 OTU3 OTU4 
ODU0 
ODU3 
PM 
ODU2 
ODU4 
ODU0 XC ODU0 XC ODU0 XC ODU0 XC 
(tunnel) 
3rd Party OTN 
Domain 
2/0 0/3 3/0 0/2/3 4/2/0 0/4 4/0 0/2 
ODU0 
TCM3 
ODU0 
| 
ODU0-AIS 
ODU0-AIS 
ODU0-AIS 
ODU0-AIS 
ODU0-AIS 
ODU0-AIS 
ODU3-LCK 
ODU0 XC ODU0 XC 
ODUk Switch Nodes 
ODU0-IAE 
ODU0-BIAE 
Frame slip 
62 
Fault Propagation Example – TCM3 Maintenance LCK 
SM 
TCM4 
TCMi (opt) 
PM 
Client 
ODU0 
OTU2 OTU3 OTU4 OTU2 OTU3 OTU4 
ODU0 
ODU3 
PM 
ODU2 
ODU4 
ODU0 XC ODU0 XC ODU0 XC ODU0 XC 
(tunnel) 
3rd Party OTN 
Domain 
2/0 0/3 3/0 0/2/3 4/2/0 0/4 4/0 0/2 
ODU0 
TCM3 
ODU0 
| 
ODU0-LCK 
ODU0-LCK 
ODU0-LCK 
ODU0-LCK 
ODU0-LCK 
ODU0 XC ODU0 XC 
ODUk Switch Nodes 
63 
Fault Propagation Example – PM Maintenance LCK 
SM 
TCM4 
TCMi (opt) 
PM 
Client 
ODU0 
OTU2 OTU3 OTU4 OTU2 OTU3 OTU4 
ODU0 
ODU3 
PM 
ODU2 
ODU4 
ODU0 XC ODU0 XC ODU0 XC ODU0 XC 
(tunnel) 
3rd Party OTN 
Domain 
2/0 0/3 3/0 0/2/3 4/2/0 0/4 4/0 0/2 
ODU0 
TCM3 
ODU0 
| 
ODU0-LCK 
ODU0 XC ODU0 XC 
ODUk Switch Nodes 
64 
5430 GbE OTN Fault Handling (GFP-T Mapped): 
LOS, LOF, LOM, AIS, OCI, LCK, PLM 
Transmit 
GbE 
Client 
Ingress 
Client 
Adaptation 
Ingress 
OTN 
Mapping 
Egress 
OTN 
Demapping 
Egress 
Client 
Adaptation 
Receive 
GbE 
Client 
Receive 
GbE 
Client 
Egress 
Client 
Adaptation 
Egress 
OTN 
Demapping 
Ingress 
OTN 
Mapping 
Ingress 
Client 
Adaptation 
Transmit 
GbE 
Client 
3R 
Regen 
3R 
Regen 
X ODU-AIS Cons. Action 
Link 
Down 
• Egress client signal Consequent Action is provisionable to laser off, /V/ codes 
(K30.7 error codes) or /C1/C2/ link fault sequences 
65 
Transmit 
GbE 
Client 
Ingress 
Client 
Adaptation 
Ingress 
OTN 
Mapping 
Egress 
OTN 
Demapping 
Egress 
Client 
Adaptation 
Receive 
GbE 
Client 
Receive 
GbE 
Client 
Egress 
Client 
Adaptation 
Egress 
OTN 
Demapping 
Ingress 
OTN 
Mapping 
Ingress 
Client 
Adaptation 
Transmit 
GbE 
Client 
5430 GbE Client Fault Handling (GFP-T Mapped): 
Client Faults - LOS, Loss-of-character-sync (LOCS) 
3R 
Regen 
3R 
Regen 
X GFP CMF (LOS, LOCS) Link Down 
Cons. Action 
• Rx Failure causes immediate insertion of GFP Loss of Signal (LOS) or Loss of Character 
Synchronization (LOCS) client management frames (CMF) at ingress 
 
• Egress client signal Consequent Action is provisionable to laser off, /V/ codes (K30.7 
error codes) or /C1/C2/ link fault sequences 
 
• Egress consequent action clears within 3 seconds after clearing of GFP LOS/LOCS CMF 
(failure recovery time limited by LOS/LOCS CMF 3 second clear time), receipt of valid data 
frames causes immediate clearing 
66 
Transmit 
GbE 
Client 
Ingress 
Client 
Adaptation 
Ingress 
OTN 
Mapping 
Egress 
OTN 
Demapping 
Egress 
Client 
Adaptation 
Receive 
GbE 
Client 
Receive 
GbE 
Client 
Egress 
Client 
Adaptation 
Egress 
OTN 
Demapping 
Ingress 
OTN 
Mapping 
Ingress 
Client 
Adaptation 
Transmit 
GbE 
Client 
5430 GbE Client Fault Handling (GFP-T Mapped): 
Link Fault or Auto-negotiation 
3R 
Regen 
3R 
Regen 
/C1/C2/ 
• Link fault/auto-negotiation code words passed transparently end-to-end 
/C1/C2 
67 
Transmit 
GbE 
Client 
Ingress 
Client 
Adaptation 
Ingress 
OTN 
Mapping 
Egress 
OTN 
Demapping 
Egress 
Client 
Adaptation 
Receive 
GbE 
Client 
Receive 
GbE 
Client 
Egress 
Client 
Adaptation 
Egress 
OTN 
Demapping 
Ingress 
OTN 
Mapping 
Ingress 
Client 
Adaptation 
Transmit 
GbE 
Client 
5430 GbE Error Handling (GFP-T Mapped) 
3R 
Regen 
3R 
Regen 
/V/ code 
• Ingress 8B/10B coding violations (CV) or transport generated errors are 
replaced with /V/ characters (K30.7 error codes) on egress 
Ingress client errors Transport error Transport error 
68 
5430 10GbE OTN Fault Handling (GFP-Mapped): 
LOS, LOF, LOM, AIS, OCI, LCK, PLM 
Transmit 
10GbE 
Client 
Ingress 
Client 
Adaptation 
Ingress 
OTN 
Mapping 
Egress 
OTN 
Demapping 
Egress 
Client 
Adaptation 
Receive 
10GbE 
Client 
Receive 
10GbE 
Client 
Egress 
Client 
Adaptation 
Egress 
OTN 
Mapping 
Ingress 
OTN 
Mapping 
Ingress 
Client 
Adaptation 
Transmit 
10GbE 
Client 
3R 
Regen 
3R 
Regen 
X ODU-AIS 
RF RF 
Cons. Action 
Link 
Down 
or LF 
RF GFP CMF/CDF (RF) 
Idle 
• Egress client signal consequent action is provisionable to laser off, /I/ Idle 
Ordered Sets (will not cause link down at receive 10GbE client interface), or 
Local Fault (LF) ordered sets 
 
• Egress consequent action clears immediately upon clearing of the OTN fault 
 
69 
Transmit 
10GbE 
Client 
Ingress 
Client 
Adaptation 
Ingress 
OTN 
Mapping 
Egress 
OTN 
Demapping 
Egress 
Client 
Adaptation 
Receive 
10GbE 
Client 
Receive 
10GbE 
Client 
Egress 
Client 
Adaptation 
Egress 
OTN 
Mapping 
Ingress 
OTN 
Mapping 
Ingress 
Client 
Adaptation 
Transmit 
10GbE 
Client 
5430 10GbE Client Fault Handling (GFP-mapped): 
Client Faults - LOS, Loss-of-block-sync (LOCS) 
3R 
Regen 
3R 
Regen 
X 
GFP CMF (LOS, LOCS) 
RF RF 
Link 
Down 
or LF 
Cons. Action 
GFP CMF/CDF (RF) RF 
Idle 
• Rx Failure causes immediate insertion of GFP Loss of Signal (LOS) or Loss of Character 
Synchronization (LOCS) client management frames (CMF) at ingress if the mapping uses 
CMF for non-transparent ordered set fault propagation, or GFP client data frames (CDF) 
carrying Local Fault (LF) if mapping uses CDF for transparent ordered set fault propagation 
 
• Egress client signal consequent action is provisionable to laser off, /I/ Idle Ordered Set 
(will not cause link down at receive 10GbE client interface), or /LF/ Local Fault 
 
• If provisioned, egress LF clears 3 seconds after clearing of GFP LOS/LOCS CMF (failure 
recovery time limited by LOS/LOCS CMF 3 second clear time ), receipt of valid data frames 
causes immediate clearing 
GFP CDF (LF ordered set) 
70 
Transmit 
10GbE 
Client 
Ingress 
Client 
Adaptation 
Ingress 
OTN 
Mapping 
Egress 
OTN 
Demapping 
Egress 
Client 
Adaptation 
Receive 
10GbE 
Client 
Receive 
10GbE 
Client 
Egress 
Client 
Adaptation 
Egress 
OTN 
Mapping 
Ingress 
OTN 
Mapping 
Ingress 
Client 
Adaptation 
Transmit 
10GbE 
Client 
5430 10GbE Client Fault Handling: Local Fault 
3R 
Regen 
3R 
Regen 
GFP CMF/CDF (LF) 
RF RF 
LF LF 
GFP CMF/CDF (RF) RF 
LF 
• Rx Local Fault (LF) ordered set causes immediate insertion at ingress of 
GFP LF client management frame (CMF used if mapping provides non-
transparent ordered set fault propagation) or client data frame (CDF used if 
mapping provides transparent ordered set fault propagation) 
 
• Egress Local Fault clears within 3 seconds after clearing of GFP LF CMF 
(failure recovery time limited by LF CMF 3 second clear time ), receipt of valid 
data frame cause immediate clearing 
 
71 
Transmit 
10GbE 
Client 
Ingress 
Client 
Adaptation 
Ingress 
OTN 
Mapping 
Egress 
OTN 
Demapping 
Egress 
Client 
Adaptation 
Receive 
10GbE 
Client 
Receive 
10GbE 
Client 
Egress 
Client 
Adaptation 
Egress 
OTN 
Mapping 
Ingress 
OTN 
Mapping 
Ingress 
Client 
Adaptation 
Transmit 
10GbE 
Client 
5430 10GbE Client Fault Handling: Remote Fault 
3R 
Regen 
3R 
Regen 
GFP CMF/CDF (RF) 
Idle LOS 
RF RF RF 
X 
Idle 
• Rx Remote Fault (RF) ordered set causes immediate insertion at ingress of 
GFP LF client management frame (CMF used if mapping provides non-
transparent ordered set fault propagation) or client data frame (CDF used if 
mapping provides transparent ordered set fault propagation) 
 
• Egress Local Fault clears within 3 seconds after clearing of GFP LF CMF 
(failure recovery time limited by LF CMF 3 second clear time ), receipt of valid 
data frame cause immediate clearing 
 
72 
Transmit 
10GbE 
Client 
Ingress 
Client 
Adaptation 
Ingress 
OTN 
Mapping 
Egress 
OTN 
DemappingEgress 
Client 
Adaptation 
Receive 
10GbE 
Client 
Receive 
10GbE 
Client 
Egress 
Client 
Adaptation 
Egress 
OTN 
Demapping 
Ingress 
OTN 
Mapping 
Ingress 
Client 
Adaptation 
Transmit 
10GbE 
Client 
5430 10GbE Error Handling 
3R 
Regen 
3R 
Regen 
Errors 
• Ingress MAC frame errors produce Ethernet CRC errors resulting in dropped 
frames, errors outside the MAC frame are ignored 
 
• Transport errors in client data frames are propagated through to the client, 
errors in client data frames do not produce egress errors toward the client 
Ingress client errors Transport error Transport error 
73 
5430 SONET/SDH/CBR OTN Fault Handling: 
LOS, LOF, LOM, AIS, OCI, LCK, PLM 
Transmit 
SONET/ 
SDH/CBR 
Client 
Ingress 
Client 
Adaptation 
Ingress 
OTN 
Mapping 
Egress 
OTN 
Demapping 
Egress 
Client 
Adaptation 
Receive 
SONET/ 
SDH/CBR 
Client 
Receive 
SONET/ 
SDH/CBR 
Client 
Egress 
Client 
Adaptation 
Egress 
OTN 
Demapping 
Ingress 
OTN 
Mapping 
Ingress 
Client 
Adaptation 
Transmit 
SONET/ 
SDH/CBR 
Client 
3R 
Regen 
3R 
Regen 
X ODU-AIS 
AIS-L/ 
MS-AIS 
• AIS-L/MS-AIS transmitted for Transparent SONET/SDH service and PN-11 
for CBR service 
 
• Egress AIS-L/MS-AIS/PN-11 clears immediately upon detection of OTN 
failure clear 
LOF PN-11(CBR) 
AIS-L/ 
MS-AIS 
(TS) 
74 
Transmit 
SONET/ 
SDH/CBR 
Client 
Ingress 
Client 
Adaptation 
Ingress 
OTN 
Mapping 
Egress 
OTN 
Demapping 
Egress 
Client 
Adaptation 
Receive 
SONET/ 
SDH/CBR 
Client 
Receive 
SONET/ 
SDH/CBR 
Client 
Egress 
Client 
Adaptation 
Egress 
OTN 
Demapping 
Ingress 
OTN 
Mapping 
Ingress 
Client 
Adaptation 
Transmit 
SONET/ 
SDH/CBR 
Client 
5430 SONET/SDH/CBR Client Fault Handling: LOS, LOF 
3R 
Regen 
3R 
Regen 
X 
AIS-L/ 
MS-AIS 
• Rx Failure causes insertion of AIS-L/MS-AIS for Transparent SONET/SDH 
service and PN-11 for CBR service at ingress 
 
• Egress AIS-L/MS-AIS/PN-11 clears immediately upon detection of client 
failure clear 
 
PN-11(CBR) LOF PN-11(CBR) 
AIS-L/ 
MS-AIS 
(TS) AIS-L/ 
MS-AIS 
(TS) 
75 
Transmit 
SONET/ 
SDH/CBR 
Client 
Ingress 
Client 
Adaptation 
Ingress 
OTN 
Mapping 
Egress 
OTN 
Demapping 
Egress 
Client 
Adaptation 
Receive 
SONET/ 
SDH/CBR 
Client 
Receive 
SONET/ 
SDH/CBR 
Client 
Egress 
Client 
Adaptation 
Egress 
OTN 
Demapping 
Ingress 
OTN 
Mapping 
Ingress 
Client 
Adaptation 
Transmit 
SONET/ 
SDH/CBR 
Client 
5430 SONET/SDH/CBR Client Fault Handling: AIS-L/MS-AIS 
3R 
Regen 
3R 
Regen 
AIS-L/ 
MS-AIS 
AIS-L/MS-AIS 
• Rx AIS-L/MS-AIS propagates end-to-end 
 
76 
Transmit 
SONET/ 
SDH/CBR 
Client 
Ingress 
Client 
Adaptation 
Ingress 
OTN 
Mapping 
Egress 
OTN 
Demapping 
Egress 
Client 
Adaptation 
Receive 
SONET/ 
SDH/CBR 
Client 
Receive 
SONET/ 
SDH/CBR 
Client 
Egress 
Client 
Adaptation 
Egress 
OTN 
Demapping 
Ingress 
OTN 
Mapping 
Ingress 
Client 
Adaptation 
Transmit 
SONET/ 
SDH/CBR 
Client 
5430 SONET/SDH/CBR Error Handling 
3R 
Regen 
3R 
Regen 
Errors 
• Ingress as well as transport errors are propagated to the client 
Ingress client errors Transport error Transport error 
OTN Performance Monitoring 
78 
OTN Performance Monitoring Basics 
Standard OTN PM Parameters Based on BIP-8 EDC 
 BIP-8 byte is provided within the SM, the TCMi, and the PM overhead fields 
 BIP-8 computed only over OPU payload and overhead (OTU/ODU overhead is not included 
in the BIP-8 computation) avoiding the need to recompute BIP-8 values due to ODU 
overhead value changes occurring along the path (GCC, APS/PCC, etc) 
 BIP-8 computed after any FEC error correction (if present) is performed 
 BIP-8 EDC used to determine background block errors (BBE) 
 BBE used to compute standard ES, SES, CSES, and UAS parameters 
 SES threshold ≥15% errored blocks (1526@ODU0, 3064@ODU1, 12304@ODU2, 
12748@ODU2e, and 49424@ODU3) or a defect second 
 CSES thresholds are user provisionable (2-9 consecutive SES) 
 OTN layer PM provides both Near-end (NE, directly via the BIP-8) and Far-end (FE, via the 
BEI field) PM data 
 NE and FE PM collection affected by IAE and BIAE functions (only applies to section and 
tandem connection monitoring) 
 OTN supports standard defect second processing (automatic creation of ES/SES during 
defect seconds and suppression of BBE counts 
 Support for parameter thresholding and TCA generation 
 15-min and 24-hr PM collection intervals 
79 
Additional 5430 OTN Performance Monitoring Parameters 
Additional OTU Layer (SM) PM Parameters 
 Corrected FEC errors 
 Severely Errored Frame Seconds 
 Severely Errored Multi-frame Seconds 
 Additional ODU Layer (TCMi and PM) PM Parameters 
 Protection Switch Counts 
 Delay Measurements 
 GFP PM Parameters 
 Corrected cHEC and tHEC errors 
 Dropped frames 
 Errored superblocks (GFP-T only) 
 Client Specific PM Parameters 
OTN Multiplexing and Mapping Trees 
81 
OTN Optical Multiplexing Structure 
Multiplexing Mapping
OTM-n.m OCG-n.m
OCC
OCC
OCC
OOSOSC
OCh
OCh
OCh
OTU4
OTU2
OTU1
x 1
x 1
x 1
x 1
x 1
x 1
x 1
x 1
x 1
x k
x j
x m
OTS, OMS, OCh, COMMS OH
OCC OCh OTU3
x 1 x 1
x i
1 ≤ i+j+k+m ≤ n
 OTUk frames mapped (E-O) to uncolored optical channels (OCh) 
 Optical channels mapped (wavelength conversion) to colored 
optical channel carrier (OCC) 
 Optical channel carriers optically multiplexed into optical carrier 
group (OCG) 
 OCG combined with optical supervisory channel (OSC) to create 
the optical transport module (OTM) 
82 
Multiplexing 
Mapping ODUk (L) = Low Order ODU 
ODUk (H) = High Order ODU 
Pre-2009 OTN Multiplexing Structure with SONET Mapping 
OPU1 
OPU2 ODU2 (H) 
OPU2 Client 
OPU3 ODU3 (H) 
OPU3 Client ODU3 (L) 
OTU1 
OTU2 
OTU3 
Client 
OCh 
OCh 
OCh 
ODU1 (L) 
ODTU12 
ODU2 (L) 
ODTU13 
ODTU23 
x4 
x16 
x4 
2.666G 
10.709G 
43.018G or 
or 
10.037G 
2.499G 
40.319G 
OC48 
OC192 
OC768 
x4 
x4 
SONET 
Rate 
Hierarchy 
83 
Multiplexing 
Mapping ODUk (L) = Low Order ODU 
ODUk (H) = High Order ODU 
Post-2009 OTN Multiplexing Structure 
OPU0 
OPU1 ODU1 (H) 
ODTU01 
OPU1 
OPU2 ODU2 (H) 
OPU2 Client 
OPU3 ODU3 (H) 
OPU3 Client ODU3 (L) 
OTU1 
OTU2 
OTU3 
OPU4 ODU4 (H) 
OPU4 Client ODU4 (L) 
OTU4 
Client 
Client 
OCh 
OCh 
OCh 
OCh 
ODU0 (L) 
ODU1 (L) 
ODTU2.ts 
ODTU12 
ODU2 (L) 
ODTU3.ts 
ODTU13 
ODTU23 
ODTU4.ts 
x2 
x8 
x32 
x80 
x4 
x16 
x40 
x4 
x10 
x2 
or 
or 
or 
or 2.666G 
10.709G 
43.018G 
111.809G 
10.037G 
2.499G 
40.319G 
104.794G 
1.244G 
OPU2e 10GbE ODU2e (L) 
x10 
x3 
OPUflex Client ODUflex (L) 
x80/ts 
x32/ts 
x8/ts 
84 
OTN Electrical Multiplexing Structure (1 of 2) 
19.6.3 GMP 
19.6.2 GMP 
19.5.3 AMP 
19.5.2 AMP 19.3.2 
19.3.6 
19.3.6 19.2 
OR 
ODU3 
(L) 
OPU3-X 
ODU3 
(H) 
OPU3 
(L) 
OTU3 
ODU4 
(L) 
ODU4 
(H) 
OPU4 
(L) 
OTU4 
ODTU4.1 
ODTU4.2 
ODTU4.8 
ODTU4.31 
Client Signal 
Client Signal 
Client Signal 
x32 
x40 
x80 
x1 
x2 
x10 
x1 
x1 
x1/X 
x1 
ODTU4.ts x80/ts 
CBR40G (17.2.3) STM-256 - AMP/BMP (17.2) 
40GBASE-LR4 (17.7.4.1) converted to serial 66b 
blocks (Annex E) then transcoded into 513b 
blocks (Annex B) then 1027b framed (Annex F) 
and GMP mapped (17.7.4 – Amd.1) 
19.1.2 
19.1.4 
19.2 19.3.7 19.6.3 GMP 
100GBASE-LR4/-ER4 converted to serial 66b 
blocks (Annex E) and GMP mapped (17.7.5 – 
Amd.1) 
19.6.3 GMP 
19.6.3 GMP 
19.6.3 GMP 
ODTU3.1 
ODTU13 
ODTU3.9 
x16 
x4 
x3 
19.2 19.6.2 GMP 
19.2 
19.2 19.3.3 
ODU2e 
(L) 
OPU2e 
(L) Client Signal 
x1 
CBR10G3 (17.2.4) 10GBASE-R - BMP (17.2) 
FC-1200 (17.8.2) - 66b blocks transcoded into a 
513b block (Annex B) then assembled into a 
superblock then mapped into a special GFP 
frame then byte sync mapped 
OPU3 (H) 
PT=21 
OPU3 (H) 
PT=20 
19.1.2 
x1 
ODTU3.ts x32/ts 
19.2 19.3.6 19.6.2 GMP 
19.3.3 
19.3.2 
x16 ODTU13 
ODTU23 x4 
19.2 19.5.2 AMP 
19.2 
19.5.3AMP 
OPU4 (H) 
PT=21 
19.2 
19.2 
19.2 
19.2 
19.3.7 
19.3.7 
19.3.7 
19.3.7 
ODU2 
ODU0 
ODU2e 
ODU1 
ODUflex 
ODU3 
ODU4 
ODU4 
O
D
TU
G
4 
P
T=
21
 
ODU3 to 
ODU (H) 
ODU3 to 
ODU (H) 
ODU2e to 
ODU (H) 
O
D
TU
G
3 
P
T=
21
 
O
D
TU
G
3 
P
T=
20
 
ODU1 
ODU2 
ODU2e 
ODU0 
ODUflex 
ODU2 
ODU1 
ODTU23 
85 
OTN Electrical Multiplexing Structure (2 of 2) 
19.3.1 
Sketch derived from: December 2009 G.709v3 published & June 2010 Amd.1 consented (TD 221r1/PLEN) 
David W. Martin – July 16, 2010 
ODU0 
(L) 
OPU0 
(L) 
ODU1 
(L) 
OPU1-X 
ODU1 
(H) 
OPU1 
(L) 
OTU1 
OPU1 (H) 
PT=20 ODTU01 
Client Signal 
Client Signal 
Client Signal 
x2 
x1 
x1 
x1/X 
ODUflex 
(L) 
OPUflex 
(L) Client Signal 
x1 
19.1.3 
19.3.4 19.2 19.5.4 AMP 
CBR2G5 (17.2.1) STM-16, CMGPON D/U2 - 
AMP/BMP (17.2) 
FC-200 (17.7.2) - GMP 
1.5G HD SDI (Living List) - GMP 
CPRI Option 3 (Appendix VIII, Amd.1) - GMP 
1.238Gb/s < X ≤ 2.488Gb/s (17.7.2) - GMP 
1000BASE-X (17.7.1.1) - TTT+GMP 
STM-1, STM-4 (17.7.1) - GMP 
FC-100 (17.7.1) - GMP 
ESCON, DVB-ASI, SDI (Living List) - GMP 
CPRI Options 1, 2 (Appendix VIII, Amd.1) - GMP 
X ≤ 1.238Gb/s (17.7.1) - GMP 
FC-400, FC-800 (17.9) - BMP 
3G HD SDI (Living List) - BMP 
IB 2G, 4G, 8G, CPRI 7 (Living List) 
CPRI Options 4 - 6 (App. VIII, Amd.1) - BMP 
X > 2.488Gb/s (17.9) - BMP 
X > 0 possible (17.4) - GFP-F 
X = Nx~1.244Gb/s recommended 
OPUflex(CBR) 
OPUflex(GFP) 
x1 
19.3.5 
ODU2 
(L) 
OPU2-X 
ODU2 
(H) 
OPU2 
(L) 
OTU2 
OPU2 (H) 
PT=21 
ODTU2.1 
Client Signal 
Client Signal 
x1/X 
x1 
x8 
x4 
ODTU2.ts x8/ts 
19.2 19.3.5 19.6.1 GMP 
19.2 
19.5.1 AMP 
19.2 
19.6.1 GMP 
19.1.1 
CBR10G (17.2.2) STM-64 - AMP/BMP (17.2) 
GFP / Extended OPU2 (17.4.1) - 10GBASE-R 
payload + preamble + OS, G.7041 (7.9) 
GFP (17.4) - 10GBASE-R payload G.sup43 (6.2) x1 
OPU2 (H) 
PT=20 
19.1.1 
OR 
ODTU12 x4 
19.2 
19.3.1 19.5.1 AMP 
x1 
ODU2 to 
ODU (H) 
ODU2 to 
ODU (H) ODU1 
ODU1 
ODU0 
ODUflex 
O
D
TU
G
2 
P
T=
21
 
O
D
TU
G
2 
P
T=
20
 
ODU0 
ODU1 to 
ODU (H) 
ODU1 to 
ODU (H) 
O
D
TU
G
1 
P
T=
20
 
ODU0 to 
ODU (H) 
ODUflex to 
ODU (H) 
Mapping Multiplexing OTU/ODU OH 
ODTU12 
86 
Single Stage (Flat) vs. Multi-Stage (Step) Multiplexing 
Single stage multiplexing recommended by ITU in G.872 
 All LO ODUk muxed directly to HO ODUk (no LO to HO to even higher HO) 
 Reduces complexity of networking topologies 
 Reduces complexity of equipment multiplexing structure 
 Reduces complexity of control plane bandwidth advertisement (available 
timeslots) 
 Adopted by Ciena for line side (Intra-domain, I-NNI) interfaces 
 
Multi-stage muxing likely to be required due to network migration 
 Allows LO ODUk to HO ODUk to even higher HO ODUk 
 May be required when muxponders are used on line system (e.g., 40G switch 
interface to line system 40G-to-100G muxponder to 100G switch interface) 
 Significantly increases networking and muxing complexity 
 Control plane bandwidth advertisement more complex than just available timeslots 
 Supported by Ciena for client side (Inter-domain, E-NNI) interfaces 
87 
HO ODUk Timeslot Rate Differences 
Timeslot rates are different for various HO ODUk (k=2,3,4) 
 HO ODU2 timeslot ~ 1.249Gbps 
 HO ODU3 timelsot ~ 1.254Gbps 
 HO ODU4 timeslot ~ 1.301Gbps 
Variation in timeslot rate may result in ODUk/flex tributary ports 
containing different numbers of HO ODUk timeslots for different 
HO timeslot rates 
 ODUk/flex to HO ODUk multiplexing must address timeslot utilization 
efficiency 
 Most efficient mapping required for ODUk/flex(CBR) clients 
 Equal timeslot mapping required for ODUflex(GFP) clients (to support ODUflex resizing) 
 Cross-connect function should be based on tributary ports NOT timeslots, 
HO ODUk timeslots are associated with tributary ports 
88 
Auto-Payload Type Function 
Provide automatic interworking between legacy equipment supporting 
only 2.5G timeslots (PT=20) and new equipment supporting 1.25G (PT=21) 
timeslots (applies to muxing into HO ODU2 and ODU3 only) 
 Set outgoing PT=20 if 
 AutoPayloadType is enabled and 
 Incoming PT=20 and 
 HO ODU source has no provisioned traffic or LO ODU traffic provisioned with PT=20 
timeslot arrangement 
 HO ODU2 with ODU1s in TSi/TSj where j=i+4 
 HO ODU3 with ODU1s in TSi/TSj where j=i+16 
 HO ODU3 with ODU2s in TSa/TSa+16/TSb/TSb+16/TSc/TSc+16/TSd/TSd+16 
 Otherwise set outgoing PT=21 (default value) 
89 
ODTU Mapping Methods 
Mapping methods provide a means for rate adapting a client or lower rate 
container into a server or higher rate container 
 Used to map ODUj or ODUflex into an ODTU (same mechanisms are also used 
for mapping client signals into and ODUj or ODUflex) 
 Two methods: Asynchronous Mapping Procedure (AMP) and Generic Mapping 
Procedure (GMP) 
 
Asynchronous Mapping Procedure 
 Monitors client rate relative to server rate and performs stuffing operations once 
per lower rate container frame (negative and positive justification operations) 
 Signals stuffing operations through justification control bits to far end (demux) 
 
Generic Mapping Procedure 
 Monitors client rate relative to server rate, adjusts number of bytes sent per server 
frame, and distributes bytes evenly throughout server frame 
 Signals bytes per frame via Cm and CnD control bits to far end (demux) 
90 
OPU1 Tributary Slots 
1 16 17 38
24Frame
Row
Column
18 19 20 38
23
15
1.25G TS#
TS
O
H
TS
1
1 2 1 2 1 2
1
2
3
4
MFAS
bit
8
1
2
3
4
0
1
Multi
Frame
Row
1
2
3
4
5
6
7
8
TS
O
H
TS
2
• Timeslots assigned to specific column positions 
for mapping/muxing purposes (column interleaving) 
• Timeslot overhead for mapping/muxing control 
assigned to HO OPU overhead area on a per frame 
basis (frame interleaving) using multi-frame values 
91 
OPU2 Tributary Slots 
1 16 17 38
24Frame
Row
Column
18 19 20 38
23
2115
1.25G TS#
2.5G TS#
1 2 3 4 5 6 7 8
1 2 3 4 1 2 3 4
1 2
1 2
7 8
3 4
1
2
3
4
MFAS
bits
(6)78
1
2
3
4
(0)00
(0)01
Multi
Frame
Row
1
2
3
4
5
6
7
8
1
2
3
4
1
2
3
4
(0)11
(1)00
13
14
15
16
17
18
19
20
1
2
3
4
(1)11
29
30
31
32
1
2
3
4
13
14
15
16
TS
OH TS
2
TS
OH
 
TS
4
TS
OH
TS
1 o
r T
S5
TS
OH
TS
4 o
r T
S8
23 24 25 2622
TS
OH TS
1
92 
OPU3 Tributary Slots 
1 16 17 38
24Frame
Row
Column
18 31 38
23
3215
1.25G TS#
2.5G TS#
TS
OH TS
1
1 2 15 16 17 18
1 2 15 16 1 2
31 32
15 16
1
2
3
4
1
2
3
4
1
2
3
4
1
2
3
4
1
2
3
4
TS
OH TS
2
TS
OH
TS
16
TS
OH
TS
1 
or
 T
S1
7
TS
OH
TS
16
 o
r T
S3
2
3433
MFAS
bits
(4)5678
(0)0000
(0)0001
Multi
Frame
Row
1
2
3
4
5
6
7
8
(0)1111
(1)0000
61
62
63
64
65
66
76
68
(1)1111
125
126
127
128
1
2
3
4
61
62
63
64
47 48
31 32 1 2
15 16 1 2
5049
93 
OPU4 Tributary Slots 
1 16 17 38
24Frame
Row
Column
18 55 3
82
3
5615
1
2
3
4
1
2
3
4
1
2
3
4
1
2
3
4
5857
OMFI
bits
2345678
0000000
0000001
Multi
Frame
Row
1
2
3
4
5
6
7
8
1001110
1001111
313
314
315
316
317
318
319
320
95 96 9897
1
41
1
41
2
42
2
42
39
79
39
79
40
80
40
80
41
1
41
1
42
2
42
2
79
39
79
39
80
40
80
40
1
41
1
41
2
42
2
42
79
39
79
39
80
40
80
40 F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
38
22
38
21
38
20
38
19
38
18
38
17
38
16
38
15
1
41
1
41
2
42
2
42
39
79
39
79
40
80
40
80
41
1
41
1
42
2
42
2
79
39
79
39
80
40
80
40
1
41
1
41
2
42
2
42
79
39
79
39
80
40
80
40 F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
1
41
1
41
2
42
2
42
39
79
39
79
40
80
40
80
41
1
41
1
42
2
42
2
79
39
79
39
80
40
80
40
1
41
1
41
2
42
2
42
79
39
79
39
80
40
80
40 F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
SF
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
1
41
1
41
2
42
2
42
39
79
39
79
40
80
40
80
41
1
41
1
42
2
42
2
79
39
79
39
80
40
80
40
1
41
1
41
2
42
2
42
79
39
79
39
80
40
80
40 F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
F
S
TS
O
H
TS
1
OM
FIPSI
TS
O
H
TS
2
OM
FIPSI
TS
O
H
TS
79
OM
FIPSI
TS
O
H
TS
80
OM
FIPSI
94 
ODTUjk Structure 
2.5G TS c r ts 
ODTUjk 
payload 
bytes 
ODTUjk 
overhead 
bytes 
ODTU12 952 16 1 15232 1 x 4 
ODTU13 238 64 1 15232 1 x 4 
ODTU23 952 64 4 60928 4 x 4 
1
2
3
r-1
r
1 2 3 c
-1 c
1
ts ODTUjk Payload
ODTUjk
Overhead
jk=01,12,13,23
1.25G TS c r ts 
ODTUjk 
payload 
bytes 
ODTUjk 
overhead 
bytes 
ODTU01 1904 8 1 15232 1 × 4 
ODTU12 952 32 2 30464 2 × 4 
ODTU13 238 128 2 30464 2 × 4 
ODTU14 952 128 8 121856 8 × 4 
95 
ODTU.ts Structure 
1
2
3
r-1
r
1 2 3 j 
x t
s -
1
j x
 ts
ts
ODTUk.ts Payload
ODTUk.ts
Overhead
k=2,3,4
j r ts ODTUk.ts payload bytes 
ODTUk.ts overhead 
bytes 
ODTU2.ts 476 32 1 to 8 15232 × ts 1 × 6 
ODTU3.ts 119 128 1 to 32 15232 × ts 1 × 6 
ODTU4.ts 95 160 1 to 80 15200 × ts 1 × 6 
96 
SWIO 
ODU2e Cross Connect 
ODU4XX SWIO 
SWIO 
ODU-4 Cross Connect 
5430 OTU4 Single Stage Multiplexing Tree (TDM Switching) 
ODU421 
OTU-4 
ODU3 Cross Connect 
Sw
itch Fabric 
Li
ne
/C
lie
nt
 
Cross Connect Multiplexing/Demultiplexing 
ODU3xx 
ODU1XX 
ODU0XX 
ODUFXX 
SWIO 
SWIO 
SLP SWIO 
ODU2XX SWIO 
ODU2 Cross Connect 
ODU1 Cross Connect 
ODU0 Cross Connect 
ODUFlex Cross Connect 
ODU2exx 
Note: 
Packet Termination and OTN 
Switching are supported 
concurrently but illustrated here 
separately 
97 
PP 
ODU3 40G Termination 
ODU402 PP 
PP 
ODU4 100GbE Termination 
5430 OTU4 Single Stage Multiplexing Tree (Packet Switching) 
ODU421 
OTU-4 
ODU3 40GbE Termination 
Sw
itch Fabric 
Li
ne
/C
lie
nt
 
Packet Processing Multiplexing/Demultiplexing 
and Mapping/Demapping 
ODU302 
ODU209 
ODU205 
ODUF05 
PP 
PP 
SLP PP 
ODU2e03 PP 
ODU2e 10GbE CBR Termination 
ODU2 10GbE Termination 
ODU2 10G Termination 
ODUFlex Termination 
ODU305 
100GbE 
MAC 
1024B/ 
1027B 
40GbE 
MAC 
GFP-F 
10GbE 
MAC 
GFP-F 
GFP-F 
GFP-F 
Note: 
Up to a maximum of 10 ODUk 
terminations are supported 
Packet Termination and OTN 
Switching are supported 
concurrently but illustrated here 
separately 
WAN MAC refers to a MAC with no 
PCS layer 
10GbE 
MAC 
40G 
WAN MAC 
10G 
WAN MAC 
XG 
WAN MAC 
98 
ODU402 SWIO 
PP 
Transparent 100GbE 
5430 100G Client Mapping Tree 
100GbE 
MAC 
100GbE 
100GbE Termination 
Sw
itch Fabric 
C
lie
nt
 
Cross Connect Mapping/Demapping 
100GbE 
99 
ODU3XX SWIO 
SWIO 
ODU-3 Cross Connect 
5430 OTU3 Single Stage Multiplexing Tree 
ODU321 
OTU3 
ODU2e Cross Connect 
Sw
itch Fabric 
Li
ne
/C
lie
nt
 
Cross Connect Multiplexing/Demultiplexing 
ODU2exx 
ODU1XX 
ODU0XX 
ODUFXX 
SWIO 
SWIO 
SLP SWIO 
ODU2XX SWIO 
ODU2 Cross Connect 
ODU1 Cross Connect 
ODU0 Cross Connect 
ODUFlex Cross Connect 
100 
ODU3XX SWIO 
SWIO 
ODU-3Cross Connect 
SWIO 
ODU320 
OTU3 
ODU2 Cross Connect 
ODU-1 Cross Connect 
Sw
itch Fabric 
C
lie
nt
 
Cross Connect Multiplexing/Demultiplexing 
ODU220 
ODU1XX SWIO 
ODU1 Cross Connect 
ODU2XX 
ODU1XX 
ODU0XX 
ODUFXX 
ODU221 
SWIO 
ODU0 Cross Connect 
SWIO 
ODUFlex Cross Connect 
5430 OTU3 Two Stage Multiplexing Tree 
101 
Sw
itch Fabric 
C
lie
nt
s 
Cross Connect Mapping/Demapping 
SWIO OTU3e2 ODU3e2 
4xODU2e 
SWIO ODU302/0
3 
OC768/ 
STM256 
40GbE 
Transparent OC768/STM256 
ODU302 SWIO 
Transparent 40GbE 
ODU2eXX 
1024B/ 
1027B 
5430 40G Client Mapping Tree 
ODU-3Cross Connect 
ODU2e Cross Connect 
ODU-3Cross Connect 
102 
ODU2XX SWIO 
ODU2 Cross Connect 
OTU2 
Sw
itch Fabric 
Li
ne
/C
lie
nt
 
Cross Connect Multiplexing/Demultiplexing 
SWIO 
ODU1 Cross Connect ODU221 ODU1XX 
ODU0XX 
ODUFXX 
SWIO 
ODU0 Cross Connect 
SWIO 
ODUFlex Cross Connect 
5430 OTU2 Single Stage Multiplexing Tree 
103 
ODU2XX SWIO 
SWIO 
ODU2 Cross Connect 
SWIO 
ODU220 
OTU2 
ODU1 Cross Connect 
ODU0 Cross Connect Sw
itch Fabric 
C
lie
nt
 
Cross Connect Multiplexing/Demultiplexing 
ODU120 
SWIO 
ODU1 Cross Connect 
ODU1XX 
ODU0XX 
ODU221 ODU1XX 
ODU0XX 
ODUFXX 
SWIO 
ODU0 Cross Connect 
SWIO 
ODUFlex Cross Connect 
5430 OTU2 Two Stage Multiplexing Tree 
104 
Sw
itch Fabric 
C
lie
nt
s 
Cross Connect Mapping/Demapping 
SWIO OTU2e ODU2exx 
ODU2e Cross Connect 
SWIO 
SWIO 
Standard 10GbE mappings to ODU2 
ODU202/03 OC192/ STM-64 
10GbE 
GFP-F MAC 
Transparent OC192/STM64 
ODU2e03 SWIO 
Transparent 10GbE at 11.096G 
10GbE mapping to ODU2 supports standard 
G.709 payload mapping, and payload + preamble 
+ ordered set as defined in G.7041 (3 variants) 
ODU205/09 10GbE 
5430 10G Client Mapping Tree 
ODU2e Cross Connect 
ODU2 Cross Connect 
ODU2 Cross Connect 
105 
ODU1XX SWIO 
SWIO 
ODU1 Cross Connect 
ODU120 
OTU1 
ODU0 Cross Connect 
Sw
itch Fabric 
C
lie
nt
 
Cross Connect Mapping/Demapping 
ODU0XX 
ODU102/0
3 SWIO 
OC-48/STM-16 Transparency OC-48/ 
STM16 
SWIO 
GbE Transparency 
GbE GFP-T ODU007 
5430 OTU1/2.5G Multiplexing/Mapping Tree 
ODU1 Cross Connect 
ODU0 Cross Connect 
SWIO 
Client Transparency Future 
Clients 
GFP-T 
CBR ODU0/1xx 
ODU0/1 Cross Connect 
106 
Multiplex Structure Identifier (MSI) 
OTUk / OCh 
ODUk Switch Nodes 
OTUk / OCh 
Independent 
MSI values 
Multiplexing arrangement at 
each end of link must match 
MSI bytes (within PSI) indicate the multiplexing arrangement of tributaries 
 Must match at each end of the link for proper interoperation 
 Multiplexing arrangement of each link is independent 
 Arrangement allows for flexible/arbitrary assignment of ODUs to timeslots 
 Interconnection between arrangements defined by cross-connection 
 Tributaries assigned to arbitrary timeslots (SW controlled, eliminate BW stranding) 
 Cross-connections made between tributaries (trigger timeslot assignment, Auto-MSI) 
Xmt MSI Exp MSI 
Exp MSI Xmt MSI 
Xmt MSI Exp MSI 
Exp MSI Xmt MSI 
Multiplexing arrangement at 
each end of link must match 
107 
Multiplex Structure Identifier (1 of 4) 
(PT=20 (AMP): 2.5G TS ODU2/ODU3, 1.25G TS ODU1) 
ODU2 
MSI 
1 2 3 4 5 6 7 8 2.5G
TS # 
PSI[2] 00 00 0000 1 
PSI[3] 00 00 0001 2 
PSI[4] 00 00 0010 3 
PSI[5] 00 00 0011 4 
ODU3 
MSI 
1 2 3 4 5 6 7 8 2.5G
TS # 
PSI[2] ODTU type Tributary Port # 1 
PSI[3] ODTU type Tributary Port # 2 
PSI[4] ODTU type Tributary Port # 3 
PSI[5] ODTU type Tributary Port # 4 
PSI[6] ODTU type Tributary Port # 5 
PSI[7] ODTU type Tributary Port # 6 
PSI[8] ODTU type Tributary Port # 7 
PSI[9] ODTU type Tributary Port # 8 
PSI[10] ODTU type Tributary Port # 9 
PSI[11] ODTU type Tributary Port # 10 
PSI[12] ODTU type Tributary Port # 11 
PSI[13] ODTU type Tributary Port # 12 
PSI[14] ODTU type Tributary Port # 13 
PSI[15] ODTU type Tributary Port # 14 
PSI[16] ODTU type Tributary Port # 15 
PSI[17] ODTU type Tributary Port # 16 
ODU Tributary 
Type Port # 
00: ODTU13 00 0000: 1 
01: ODTU23 00 0001: 2 
10: RES ... 
11: RES 00 1111: 16 
Notes: (1) ODTU23 Tributary port # = 1-4 
 (2) Default ODTU type is ODTU13 
ODU1 
MSI 
1 2 3 4 5 6 7 8 1.25G
TS # 
PSI[2] 00 00 0000 1 
PSI[3] 00 00 0001 2 
108 
Multiplex Structure Identifier (2 of 4) (PT=21 (GMP): 1.25G TS ODU2) 
ODU2 
MSI 
1 2 3 4 5 6 7 8 1.25G
TS # 
PSI[2] ODTU type Tributary Port # 1 
PSI[3] ODTU type Tributary Port # 2 
PSI[4] ODTU type Tributary Port # 3 
PSI[5] ODTU type Tributary Port # 4 
PSI[6] ODTU type Tributary Port # 5 
PSI[7] ODTU type Tributary Port # 6 
PSI[8] ODTU type TributaryPort # 7 
PSI[9] ODTU type Tributary Port # 8 
ODU Tributary 
Type Port # 
00: ODTU12 00 0000: 1 
01: RES 00 0001: 2 
10: ODTU2.ts ... 
11: Unallocated 00 0111: 8 
109 
Multiplex Structure Identifier (3 of 4) (PT=21 (GMP): 1.25G TS ODU3) 
ODU3 
MSI 
1 2 3 4 5 6 7 8 1.25G
TS # 
PSI[2] ODTU type Tributary Port # 1 
PSI[3] ODTU type Tributary Port # 2 
PSI[4] ODTU type Tributary Port # 3 
PSI[5] ODTU type Tributary Port # 4 
PSI[6] ODTU type Tributary Port # 5 
PSI[7] ODTU type Tributary Port # 6 
PSI[8] ODTU type Tributary Port # 7 
PSI[9] ODTU type Tributary Port # 8 
PSI[10] ODTU type Tributary Port # 9 
PSI[11] ODTU type Tributary Port # 10 
PSI[12] ODTU type Tributary Port # 11 
: : : : 
PSI[30] ODTU type Tributary Port # 29 
PSI[31] ODTU type Tributary Port # 30 
PSI[32] ODTU type Tributary Port # 31 
PSI[33] ODTU type Tributary Port # 32 
ODU Tributary 
Type Port # 
00: ODTU13 00 0000: 1 
01: ODTU23 00 0001: 2 
10: ODTU3.ts ... 
11: Unallocated 01 1111: 32 
110 
Multiplex Structure Identifier (4 of 4) 
(PT=21 (GMP): 1.25G TS ODU4, only ODTU4.ts supported) 
ODU4 
MSI 
1 2 3 4 5 6 7 8 1.25G
TS # 
PSI[2] Occupation Tributary Port # 1 
PSI[3] Occupation Tributary Port # 2 
PSI[4] Occupation Tributary Port # 3 
PSI[5] Occupation Tributary Port # 4 
PSI[6] Occupation Tributary Port # 5 
PSI[7] Occupation Tributary Port # 6 
PSI[8] Occupation Tributary Port # 7 
PSI[9] Occupation Tributary Port # 8 
PSI[10] Occupation Tributary Port # 9 
PSI[11] Occupation Tributary Port # 10 
PSI[12] Occupation Tributary Port # 11 
: : : : 
PSI[78] Occupation Tributary Port # 77 
PSI[79] Occupation Tributary Port # 78 
PSI[80] Occupation Tributary Port # 79 
PSI[81] Occupation Tributary Port # 80 
TS Tributary 
Occupation Port # 
0: Unallocated 000 0000: 1 
1: Allocated 000 0001: 2 
 ... 
 100 1111: 80 
Protection Switching 
112 
OTN Automatic Protection Support 
 Linear and Ring OTN Protection Architectures 
 Linear protection mechanisms (G.873.1) 
 All supported linear protection mechanisms are forms of Subnetwork Connection 
Protection (SNCP) at the ODUk level 
 ODUk SNC/N – utilizes non-intrusive monitoring (non-intrusive monitor generates 
trail SF/SD to trigger protection operations for associated trail, TCM or PM) 
 ODUk SNC/I – utilizes inherent monitoring (inherent server layer termination of HO 
ODU layer generates server SF/SD to trigger protection operations for all associated 
clients) 
 ODUk SNC/S – utilizes sub-layer monitoring (TCM server layer termination 
generates server SF/SD to trigger protection operations) 
 1+1 unidirectional with or without reversion and 1:N bidirectional revertive switching 
supported 
 OTN does not support line switching (no line concept in OTN), however the 
equivalent of line level operation can be provided through SNCP with sub-layer 
monitoring 
 Ring protection (G.873.2, work in progress) 
 Automatic Protection Switch/Protection Communications Channel 
overhead provided across path and tandem connection layers to support 
end-to-end protection operations 
113 
Supported OTN Protection Architectures 
G.873.1/Table 7-1 Overview of linear OTN protection architectures and related monitoring 
Protection 
Architecture 
Switching 
Type 
Protection 
Subclass 
Entity Set 
Switched 
APS 
Channel 
Protected Entity 
Server Layer 
Protection 
Switched Entity 
Trigger Criteria 
1+1 uni SNC/I Individual no one HO ODUk or one 
OTUk 
ODUkP ODU(/OTU?) SSF/SSD 
1+1 bi SNC/I individual 111 one OTUk ODUkP ODU SSF/SSD 
1:n bi SNC/I individual 111 one OTUk ODUkP ODU SSF/SSD 
1+1 uni SNC/N individual no one or more HO ODUk 
and/or OTUk 
ODUkP ODU TSF/TSD 
1+1 uni SNC/S individual no one or more HO ODUk 
and/or OTUk 
ODUkT (/P?) ODUkT(/OTUk?) 
SSF/SSD 
1+1 bi SNC/S individual 001-110 one or more HO ODUk 
and/or OTUk 
ODUkT (/P?) ODUkT(/OTUk?) 
SSF/SSD 
1:n bi SNC/S individual 001-110 one or more HO ODUk 
and/or OTUk 
ODUkT (/P?) ODUkT(/OTUk?) 
SSF/SSD 
1+1 uni CL-SNCG/I group no one HO ODUk LO ODU HO ODUkP SSF/SSD 
and HO ODUdPLM 
1+1 bi CL-SNCG/I group HO 000 one HO ODUk LO ODU HO ODUkP SSF/SSD 
and HO ODUdPLM 
1:1 bi CL-SNCG/I group HO 000 one HO ODUk LO ODU HO ODUkP SSF/SSD 
and HO ODUdPLM 
Note 1 - bidir LO ODU SNC/I can not be supported over HO ODUk; reason is that there is only one HO ODUk Path APS channel and there are many 
LO ODUk signals. No sharing of one APS channel by multiple protection switching instances is defined. 
Note 2 - Bidir SNC/N, is not supported because it requires the transport of an APS signal between the Headend and the Tail end. This APS signal is to 
be inserted on the ODUk signal which may contain AIS OCI or LCK signal. This ODUk AIS/OCI/LCK signal with APS cannot be distinguished from a 
ODUk AIS/OCI/LCK signal without APS inserted at an intermediate point of the protection connection at the Tail-end. It is recommended to use 1+1 
Bidir SNC/S instead. 
Note 3 - CL-SNCG/I can assign all Normal signal to the Na subgroup and leave the Nb subgroup empty. 
Case 1 
Case 2 
Case 3 
Case 4 
Case 5 
Case 6 
Case 7 
Case 8 
Case 9 
Case 10 
Other issues: No bidirectional or 1:N SNC/N, no CL-SNCG/S (nearest equivalent to Line APS) 
114 
SNC/I and CL-SNCG/I Protection Configurations (cases 1-2, 8-10) 
Monitoring occurs at 
server layer of the layer 
cross-connected 
(protection group rate != 
cross-connect rate) 
For bidirectional SNC/I, Working and 
Protection transport entities must be 
at the same rate (OTUk), 
Other forms may be different rates 
For SNC/I, a single entity is 
switched per protection group 
For CL-SNCG/I multiple LO 
entities are switched 
Defects outside the Protected 
domain have no effect on 
protection switching operations 
115 
1+1 SNC/N Protection Configuration (case 4) 
E E
Working transport entity 
Protection transport entity 
Protected domain 
CI 
CI 
CI 
CI 
AI AI 
Working transport entity 
Protection transport entity 
Protected domain 
CI 
CI 
CI 
CI 
AI AI E ECI 
Defects outside 
protection domain 
may cause false 
switching 
(not recommended, 
use SNC/S) 
Monitoring occurs at same 
layer as cross-connections 
(protection group rate = 
cross-connect rate) 
Working and 
Protection transport 
entities may be 
carried across any 
HO facilities 
116 
SNC/S Protection Configurations (cases 5-7) 
Monitoring occurs at same 
layer as cross-connections 
(protection group rate = 
cross-connect rate) 
Working and 
Protection transport 
entities may be 
carried across any 
HO facilities 
Defects outside 
protection domain do 
not affect protection 
switching operation 
117 
OTN APS Channel Assignment 
 The OTN standard provides 8 individual APS/PCC Channels in the ODU 
overhead. 
 Each channel is identified with a particular protection layer in the network. The 
channel assignments are shown in the table below from G.709. 
118 
OTN APS Channel Protocol 
 The OTN linear protection standard uses a similar APS Signaling Protocol to 
SONET/SDH APS including; 
 Switch Requests/States 
 Protection Types 
 Requested Signal 
 Bridged Signal 
 The transmission and acceptance of the APS Signaling is on a individual channel 
basis (TCMs and PM channels). 
 All SONET/SDH Manual Switch Requests are supported for OTN. 
 Manual Switch 
 Forced Switch 
 Lockout of Protection 
 Ring protection is being based on existing SONET/SDH ring protection functions 
119 
APS Channel Format 
Request/State field values 
 Lockout of Protection (1111), Forced Switch (1110), Signal Fail (1100), Signal 
Degrade (1010), Manual Switch (1000), Wait-To-Restore (0110), Exercise (0100), 
Reverse Request (0010), Do Not Revert (0001), No Request (0000), others reserved 
Protection Type field values 
 APS Channel (A): No APS Channel (0), APS Channel (1) 
 Permanent Bridge (B): 1+1 (0), 1:N (1) 
 Direction (D): Unidirectional (0), Bidirectional (1) 
 Revertive(R): Non-revertive (0), Revertive (1) 
Requested Signal field values 
 Null Signal (0), Normal Traffic Signal (1-254), Extra Traffic Signal (255) 
Bridged Signal field values 
 Null Signal (0), Normal Traffic Signal (1-254), Extra Traffic Signal (255) 
1 2 3 4 
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 
Request/ 
state 
Protection 
type 
Requested Signal Bridged Signal Reserved 
A B D R 
OTN Client Mappings 
121 
Client Signal Mapping Methods 
Mapping methods provide a means for rate adapting a client signal into a server 
layer container (ODUj or ODUflex) 
 Three methods: Asynchronous Mapping Procedure (AMP), Bit-synchronous Mapping 
Procedure (BMP) and Generic Mapping Procedure (GMP) 
 Mapping may also utilize client signal transcoding (e.g., GFP, 1024B/1027B, etc) 
 
Bit-synchronous Mapping Procedure (server rate synchronous to client rate) 
 Bit synchronously maps client signal into server layer payload area 
 
Asynchronous Mapping Procedure (client and server rates asynchronous) 
 Monitors client rate relative to server rate (derived from local oscillator) and performs stuffing 
operations once per lower rate container frame (negative and positive justification operations) 
 Signals stuffing operations through justification control bits to far end (demux) 
 
Generic Mapping Procedure (client and server rates synchronous or asynchronous) 
 Monitors client rate relative to server rate, adjusts number of bytes sent per server frame, and 
distributes bytes evenly throughout server frame 
 Signals bytes (and residual bits) per frame via Cm and CnD control bits to far end (demux) 
122 
GbE Timing Transparent Transcoding (TTT) Mapping (GFP-T) 
 GFP-T mapping of GbE LAN PHY into OPU0 per G.7041 and 
G.709 using timing transparent transcoding 
 Apply GFP-T encapsulation of Ethernet data (full data stream including 
the Preamble, SFD and Inter Frame Gap (IFG)) per G.709 clause 17.7.1.1 
and G.7041 clause 8 (and applicable sub-clauses) 
 Synchronously encode data stream into 75-byte GFP-T frames using 64B/65B 
encoding without 65B Pad characters operating at 15/16 times incoming GbE 
clock rate 
 GFP payload FCS not supported 
 Ignore (do not modify) Ethernet FCS 
 Map GFP-T frames into OPU2 using Generic Mapping Procedure (GMP) 
per G.709 clause 17.7.1 
 
123 
GbE GFP-T Mapping 
OTN 
 OPU0 Payload Clock Rate: 1.239Gbps 
 OPU Payload Area: Row 1, 2, 3, 4 / Column 17 – 3824 
 PSI/PT Assignment: 0x05 (GFP) 
GFP-T Header Assignments 
 Core Header: Byte 1 - 4 
 Payload Header Byte 5 - 8 
 PTI 000 
 PFI 0 
 EXI 0000 
 UPI 0x06 
 tHEC per G.7041 
Client Management Frame (CSF, LF, RF) GFP Header Byte Assignments 
 Core Header: Byte 1 - 4 
 Payload Header Byte 5 – 8 
 PTI 100 
 PFI 0 
 EXI 0000 
 UPI 0x01 (Ethernet Ordered Set: LOS) 
 0x02 (Ethernet Ordered Set: LOCS) 
 tHEC per G.7041 
 
124 
10GbE LAN GFP-F Mapping – MAC Frames Only 
 GFP-F mapping of 10GbE LAN PHY into OPU2 per G.7041 
and G.709 
 Terminate 64/66B (PCS layer) line code 
 Apply GFP framing to Ethernet data (without the Preamble, SFD and Inter 
Frame Gap (IFG)) per G.7041 clause 7.1 
 GFP-F payload FCS not support 
 Ignore (do not modify) Ethernet FCS 
 Discard incoming Ethernet frames based on invalid Ethernet FCS 
 Map Ethernet LF and RF into GFP Client Management Frames per 
G.7041 clause 6.1.3.2 
 Map GFP frame into OPU2 per G.709 clause 17.4 
 
125 
10GbE LAN GFP-F Mapping – MAC Frames Only Details 
OTN 
 OTN Clock Rate: 10.7Gbps 
 OPU Payload Area: Row 1, 2, 3, 4 / Column 17 – 3824 
 PSI/PT Assignment: 0x05 (GFP) 
GFP Header Assignments 
 Core Header: Byte 1 - 4 
 Payload Header Byte 5 - 8 
 PTI 000 
 PFI 0 
 EXI 0000 
 UPI 0x01 (Frame-mapped Ethernet) 
 tHEC per G.7041 
Client Management Frame (CSF, LF, RF) GFP Header Byte Assignments 
 Core Header: Byte 1 - 4 
 Payload Header Byte 5 – 8 
 PTI 100 
 PFI 0 
 EXI 0000 
 UPI 0x01 (Ethernet Ordered Set: LOS) 
 0x02 (Ethernet Ordered Set: LOCS) 
 0x03 (Ethernet Ordered Set: Clear) 
 0x04 (Ethernet Ordered Set: LF) 
 0x05 (Ethernet Ordered Set: RF) 
 tHEC per G.7041 
126 
10GbE LAN GFP-F Mapping – MAC Frames + Preamble 
(Ordered Sets via Client Management Frames) 
 GFP-F mapping of 10GbE LAN PHY into OPU2 per G.7041 
and G.709 
 Terminate 64/66B (PCS layer) line code 
 Apply GFP framing to Ethernet data (without the Preamble, SFD and Inter 
Frame Gap (IFG)) per G.7041 clause 7.9 (except clause 7.9.2.2) 
 GFP-F payload FCS not support 
 Ignore (do not modify) Ethernet FCS 
 Discard incoming Ethernet frames based on invalid Ethernet FCS 
 Map Ethernet LF and RF into GFP Client Management Frames per 
G.7041 clause 6.1.3.2 
 Map GFP frame into OPU2 using 7 OPU2 overhead bytes for data 
mapping per G.709 clause 17.4.1 
 
127 
10GbE LAN GFP-F Mapping – MAC Frames + Preamble Details 
(Ordered Sets via Client Management Frames) 
OTN 
 OTN Clock Rate: 10.7Gbps 
 OPU Payload Area: Row 1, 2, 3, 4 / Column 17 – 3824 
 PSI/PT Assignment: 0x09 (GFP into Extended OPU2) 
GFP Header Assignments 
 Core Header: Byte 1 - 4 
 Payload Header Byte 5 - 8 
 PTI 000 
 PFI 0 
 EXI 0000 
 UPI 0x13 (Frame-mapped 64B/66B encoded Ethernet w/Preamble) 
 tHEC per G.7041 
Client Management Frame (CSF, LF, RF) GFP Header Byte Assignments 
 Core Header: Byte 1 - 4 
 Payload Header Byte 5 – 8 
 PTI 100 
 PFI 0 
 EXI 0000 
 UPI 0x01 (Ethernet Ordered Set: LOS) 
 0x02 (Ethernet Ordered Set: LOCS) 
 0x03 (Ethernet Ordered Set: Clear) 
 0x04 (Ethernet Ordered Set: LF) 
 0x05 (Ethernet Ordered Set: RF) 
 tHEC per G.7041 
128 
10GbE LAN GFP-F Mapping – MAC Frames + Preamble 
(Ordered Sets via Client Data Frames) 
 GFP-F mapping of 10G LAN PHY into OPU2 plus RES Bytes 
 Terminate 64/66B (PCS layer) line code 
 Apply GFP framing to Ethernet data (with Preamble) per G.7041 clause 7.9 
 GFP-F payload FCS not supported 
 Ignore Ethernet FCS 
 Discard incoming Ethernet frames based on invalid Ethernet FCS 
 Map Ethernet LF and RF into GFP Client Data Frames per G.7041 clause 7.9.2.2 
 Map GFP frame into OPU2 using 7 OPU2 overhead bytes for data mapping per 
G.709 clause 17.4.1 
 
129 
10GbE LAN GFP-F Mapping – MAC + Preamble Frames Details 
(Ordered Sets via Client Data Frames) 
OTN 
 OTN Clock Rate: 10.7Gbps 
 OPU Payload Area: Row 1, 2, 3, 4 / Column 17 – 3824 
 Add’l OPU Payload Area: Row 1, 2, 3 / Column 15 – 16, Row 4 / Column 16 
 PSI/PT Assignment: 0x09 (GFP into Extended OPU2) 
Ethernet Data Frame GFP Payload Mapping 
 Core Header: Byte 1 – 4 
 Payload Header Byte 5 - 8 
 PTI 000 
 PFI 0 
 EXI 0000 
 UPI 0x13 (Frame-mapped 64B/66B encoded Ethernet w/Preamble) 
 tHEC per G.7041 
Ordered Set (LF, RF) Data Frame GFP Mapping 
 Core Header: Byte 1 - 4 
 Payload Header Byte 5 – 8 
 PTI 000 
 PFI 0 
 EXI 0000 
 UPI 0x14 (Frame-mapped 64B/66B encoded Ethernet ordered sets) 
 tHEC per G.7041 
 
130 
10GbE LAN Transparent Mapping Details 
 Operate OTU2 at 11.09Gbps and map 10GbE PCS layer 
into OPU2 payload per G.709 clauses 17.2 and 17.2.4 
 Maintain 64 Fixed Stuffing bytes 
 Maintain Ethernet PCS layer Bit transparency 
 OTU2 line rate is non-standard 
 
OTN OTU2 Payload Frame Byte Allocation and PSI/PT 
Assignment 
 OTN Clock: 11.096G ± 100ppm 
 OPU Payload Area: Row 1, 2, 3, 4 / Column 17 – 1904 
 & 1921 – 3824 
 PSI/PT Assignment: 0x03 (bit-synchronous) 
 
131 
Bit-synchronous Mapping of OC-192 
 Operate OTU2 at 10.7Gbps and bit-synchronously map OC-
192 into OPU2 payload per G.709 clauses 17.2 and 17.2.2 
 Maintain 64 Fixed Stuffing bytes 
 OTU2 line interface running on local clock 
 
OTN OTU2 Payload Frame Byte Allocation and PSI/PT 
Assignment 
 OTN Clock: 10.709G ± 20ppm 
 OPU PayloadArea: Row 1, 2, 3, 4 / Column 17 – 1904 
 & 1921 – 3824 
 PSI/PT Assignment: 0x02 (asynchronous) 
 0x03 (bit-synchronous) 
 
Note: Although the OC-192 mapping is always performed in a bit-synchronous manner, 
5430 supports bit-synchronous and asynchronous demapping, and therefore allows the PT 
value to be set to either 0x02 (asynchronous) or 0x03 (bit-synchronous) mapping in order to 
support vendor interoperability 
Other 5430 OTN Capabilities 
133 
Other 5430 OTN Capabilities 
 
Connection Provisioning and Restoration 
 Control plane based setup and restoration of OTN connections 
 Mesh Restorable OTN SNCs with high and low priority service class 
 OTN SNCP with Mesh Restoration 
 Unprotected SNCs 
 Exclusive and Preferred Designated Transit list routing for home and protection 
routes 
 Cost based routing and latency based routing 
 Shared Risk Link Groups (SRLG) – up to 20 Bundle IDs per Link 
OTN Maintenance 
 Test Access, Remote Test Access 
 Port level equipment and facility loopbacks 
 Connection level loopbacks 
134 
5430 OTN ODUflex Hitless Circuit Resizing (future) 
OTN Circuit Resizing being defined as part of ITU G.7044/Y.1347 
(formerly G.hao) 
 Standard being developed for ODUflex (GFP) resizing 
 Significant effort still required (e.g., affect on control plane operation) 
Designed to be “Hitless” for increases and decreases 
 “Red” / LCR (Link Connection Resize) protocol is used to increase/decrease the 
timeslots of the ODUflex between two adjacent nodes 
 “Blue” / BWR (Bandwidth Resize) protocol is used to change the signal itself within 
the set of timeslots from end to end 
 Fabric connection resizing is vendor specific 
ODU Link ODU Link 
OPUx TS4 and TS5 exist 
Add TS9 
OPUx TS4 and TS7 exist 
Add TS11 
Add/Remove Timeslots Add/Remove Timeslots 
Increase/Decrease underlying signal itself 
10GbE 
10GbE 
Increase 
client rate 
from 4G to 
6G 
135 
ODUflex Resizing Overhead 
Resizing overhead provided in OPU overhead during resizing operation 
- HO OPUk Tributary Slot Overhead (TSOH) of added/removed timeslots used for LCR (“Red”) and BWR 
(“Blue”) protocol functions (all added/removed timeslots carry identical resizing overhead values) 
- OPUflex OH used for BWR (“Blue”) protocol functions 
136 
LCR (“Red”) Protocol Fields and Functions 
Tributary Port Identifier (TPID) Field 
- Identifies tributary port ID to/from which tributaries slots are to be added/removed 
- Encodes row 1 bits 4-8 and row 2 bits 7&8 as a single 7-bit tributary port ID 
 
 
 
 
Control (CTRL) Field 
- Used to transfer LCR protocol operation indication from source end to sink end 
- Carried in row 2 bits 5&6 
 
 
 
 
 
 
 
Tributary Slot Group Status (TSGS) Field 
- Link connection acknowledgement indication sent by HO OPU sink to acknowledge tributary slot 
match 
- Carried in row 2 bit 4, ACK=1, NACK=0 
21
7 8
TPID Field Bit Number
4 5 6 7 8
6 71 2 3 4 5
HO OPUk TSOH Row #
HO OPUk TSOH Col #
Value Command Comments
00
01
10
11
IDLE
ADD
REMOVE
NORM
Indication that the node has completed LCR and there is no new LCR 
operation
Indication that the Tributary Slot is to be added to the ODUflex 
Connection
Indication that the Tributary Slot is to be removed from the ODUflex 
Connection
Indication that LCR will be started at the next resize multiframe 
boundary when sending out NORM command after ADD or REMOVE 
command at the resize multiframe boundary
Resizing CTRL Words
137 
BWR (“Blue”) Protocol Fields and Functions 
Tributary Slot Connectivity Check (TSCC) Field 
- Used to check the connectivity of the link connection and the ODUflex connection 
- Carried in row 2 bit 1 of the HO OPUk TSOH 
- TSCC=0: initial value, also used by the source to indicate the completion of bandwidth resizing and 
exit from GMP special mode in the source to sink direction, triggers the exit of GMP special mode at 
intermediate nodes and the sink node, and is only forwarded by intermediate nodes after exit from 
GMP special mode 
- TSCC=1: confirms GMP special mode at intermediate nodes during the resizing period and signals 
to the sink node that all nodes in the source to sink direction are ready to support bandwidth resizing 
Resizing Protocol Indicator (RP) Field 
- Indicates whether resizing protocol is being carried in RCOH bytes 
- Carried in row 2 bit 4 of HO OPUk TSOH 
- RP=0: initial value, set by source to indicate all resizing operations have been exited and causes the 
termination of TSCC information relay and all other resizing operations at intermediate nodes in the 
source to sink direction, forwarded by intermediate nodes after they exit GMP special mode and 
terminate nay LCR processing, when received by sink it confirms exit from resizing protocol by the 
source and all intermediate nodes and reports completion to the management or control plane 
- RP=1: set by management plane or control plane to indicate the start of the resizing operation 
138 
BWR (“Blue”) Protocol Fields and Functions (cont’d) 
Network Connectivity Status (NCS) Field 
- Used for end-to-end network connection acknowledgement (passed transparently through 
intermediate nodes) 
- Carried in row 2 bit 2 of OPUflex overhead 
- NCS=0: initial value, also used by sink to acknowledge completion of bandwidth resizing 
- NCS=1: sent by sink when received TSCC=1 to acknowledge path resize preparation completion 
Bandwidth Resizing Indicator (BWR_IND) Field 
- Indicates whether the ODUflex source is adjusting the bit rate of the ODUflex signal; signals the start 
and end of rate adjustment ramp 
- Carried in bit 1 of rows 1 and 2 of OPUflex overhead 
- BWR_IND=0 (detected at receiver when both bits set to 0, or either set to 0 and CRC-3 indicates 
BWR_IND=0 and NCS=1): initial value, set indicate ODUflex rate adjustment is not active; transition 
from 1 to 0 indicates the ODUflex source will stop rate adjustment ramping within Y μs (Y is in the 
range of 125-250) 
- BWR_IND=1 (detected at receiver when both bits set to 1, or either bit is set to 0 and CRC-3 
indicates BWR_IND=0 and NCS=1): set to indicate the start of ODUflex rate adjustment ramping will 
begin within X μs (X is close to Y and is in the range of 125-250) 
139 
Error Resiliency Overhead (CRC-3 and CRC-5) 
CRC-5 used to perform error checking 
on LCR protocol overhead 
- Uses x5 + x + 1 generator polynomial 
- Contents rejected if CRC check fails 
 
 
 
 
 
 
 
CRC-3 used to perform error checking 
on BWR protocol overhead 
- Uses x3 + x2 + 1 generator polynomial 
- Contents rejected if CRC check fails 
Mapping
OH Bits
CRC Checksum Bits
RCOH1 bit 4
crc1 crc2 crc3 crc4 crc5
RCOH1 bit 5
RCOH1 bit 6
RCOH1 bit 7
RCOH1 bit 8
RCOH2 bit 4
RCOH2 bit 5
RCOH2 bit 6
RCOH2 bit 7
RCOH2 bit 8
X XX
X X X
X X
X X
X X
X XX
X X
X X
X X
X X
X indicates a mapping OH bit used in the EXOR equation of the associated CRC bit
Mapping
OH Bits
CRC Checksum Bits
RCOH1 bit 1
crc1 crc2 crc3
RCOH1 bit 2
RCOH1 bit 3
RCOH2 bit 1
RCOH2 bit 2
RCOH2 bit 3
X
X
X
X X
X
X X
X X
X indicates a mapping OH bit used in the EXOR equation of the associated CRC bit
X
140 
Resizing Protocols 
ODUkP/ODUj-21 ODUkP/ODUj-21ODUkP/ODUj-21ODUkP/ODUj-21
A1 B1 B2 C1
ODUfP/PKT ODUfP/PKT
BWR_Generator
BWR_Generator_Relay
LCR_Generator
BWR_Receiver
RP TSCC
LCR_Receiver
LCR_Receiver
BWR_Generator
BWR_Receiver
BWR_Receiver_Relay
LCR_Generator
BWR_Generator_Relay
RP TSCC
RP TSCC
A1 C1
NCS
NCS
BWR_Receiver_Relay
B1
LCR_Generator
BWR_Generator_Relay
LCR_Receiver
BWR_Receiver_Relay
RP TSCCBWR_Receiver_Relay
BWR_Generator_Relay
LCR_Receiver
LCR_Generator
RP TSCC
RP CTRL TPID TSGS
 RP CTRL TPID TSGS
RP TSCC
RP TSCC
 RP CTRL TPID TSGS
 RP CTRL TPID TSGS
 RP CTRL TPID TSGS RP CTRL TPID TSGS RP CTRL TPID TSGS
RP TSCC
 RP CTRL TPID TSGS
ODUfP/PCK
ODUkP/ODUj-21 ODUkP/ODUj-21 ODUkP/ODUj-21 ODUkP/ODUj-21
ODUfP/PCKRP TSCC 
NCS
RP TSCC 
NCS
 LCR protocol operates between ODUkP/ODUj-21 adaptation source and sink functions of 
adjacent nodes (mux/demux functions) 
 BWR protocol operates between ODUkP/ODUj-21 adaptation source and sink functions of 
adjacent nodes (BWR relay functions) and between ODUfP/PCK adaptation source and sink 
functions of end-to-end source and sink nodes (packet mapping functions) 
141 
Resize Procedure – Bandwidth Increase 
1. Management or control plane issues a bandwidth increase (ADD) command to add M timeslots to each 
connection and timeslot availability is verified 
2. Each nodes starts LCR and BWR protocols: each ODUkP/ODUj-21 source issues RP=1, TSCC=0, and an LCR 
ADD command (CTRL=ADD, TPID=TP#, TSGS=NACK); each ODUfP/PCK source issues NCS=NACK 
3. Each ODUkP/ODUj-21 sink checks received set of added timeslots against provisioned set and if they match 
sends ACK (CTRL=ADD, TPID=TP#, TSGS=ACK) 
4. When ODUkP/ODUj-21 sink receives an ACK and source has sent an ACK, link resize process is entered on the 
next multiframe boundary by sending NORM command (CTRL=NORM, TPID=TP#, TSGS=ACK) and link resize 
occurs one multiframe later (Cm  Cm x N/(N+M), link resize results in step change of Cm) 
5. After completion of link resizing in both direction (and for an intermediate node, on both sides), fabric resizing 
(method TBD) is performed (for TDM fabric may require increase in XC timeslots filled with backplane idles) 
6. Once fabric resizing is completed the link resizing process is exited, GMP special mode is entered, and an IDLE 
command (CTRL=IDLE, TPID=TP#, TSGS=NACK) is sent by each ODUkP/ODUj-21 source; in addition, a source 
node begins sending TSCC=1 and intermediate nodes begin relaying the incoming TSCC value 
7. Once the sink node receives TSCC=1 which is forwarded to the associated ODUfP/PCK sink, the corresponding 
ODUfP/PCK source issues NCS=ACK 
8. Once the ODUfP/PCK function at a node has sent and received NCS=ACK, the bandwidth resizing process is 
entered and the value of Cm is gradually increased to its final stable value (Cm x N/(N+M)  Cm); the fabric cross-
connection must adapt dynamically to the gradual increase in Cm (may require XC timeslots to gradually 
decrease idle fill) 
9. Once bandwidth resizing is complete the source node sends TSCC=0 signaling completion and enters GMP 
normal mode; intermediate nodes enter GMP normal mode and relay the incoming TSCC value; the sink node 
enters GMP normal mode and issues NCS=NACK 
10. When the source node receives NCS=NACK it sends RP=0 and exits the resizing protocol; intermediate nodes 
receive RP=0, exit the resizing protocol and send RP=0; the sink node receives RP=0, exits resizing and reports 
the resizing completion to the management or control plane 
 
142 
Resize Procedure – Bandwidth Decrease 
1. Management or control plane issues a bandwidth decrease (REMOVE) command to remove M timeslots from 
each connection and timeslot availability is verified 
2. Each nodes starts LCR and BWR protocols: each ODUkP/ODUj-21 source issues RP=1, TSCC=0, and an LCR 
REMOVE command (CTRL=REMOVE, TPID=TP#, TSGS=NACK); each ODUfP/PCK source issues NCS=NACK 
3. Each ODUkP/ODUj-21 sink checks received set of removed timeslots against provisioned set and if they match 
sets the GMP processor to special mode, pauses the LCR protocol and runs the BWR protocol in that direction 
4. After entering GMP special mode, the source node begins sending TSCC=1; intermediate nodes begin relaying 
the TSCC value once GMP special mode has been entered in that direction; when TSCC=1 reaches the sink 
node it enters GMP special mode and sends NCS=ACK 
5. Once the end node receives TSCC=1 and NCS=ACK and has sent NCS=ACK in response to receiving TSCC=1, 
the bandwidth resizing process is entered at the next multiframe boundary and Cm is gradually decreased to its 
final stable value (Cm  Cm x N/(N-M), for TDM fabric may require increasing backplane XC timeslot idle fill) 
6. Once bandwidth resizing is complete the source node sends TSCC=0 signaling completion and enters GMP 
normal mode; intermediate nodes enter GMP normal mode and relay the incoming TSCC value; the sink node 
enters GMP normal mode and issues NCS=NACK completing the bandwidth resizing; after entering normal 
mode in one direction, node sends TSGS=ACK in opposite direction 
7. After sending and receiving TSGS=ACK on both sides of the node, fabric resizing (method TBD) is performed 
(for TDM fabric may require decrease in XC timeslots) 
8. Once fabric resizing is completed the link resizing process is entered on the next multiframe boundary by 
sending NORM command (CTRL=NORM, TPID=TP#, TSGS=ACK) and link resize occurs one multiframe later; 
link resize results in step change of Cm x N/(N-M)  Cm) 
9. After completing link resize process and receiving a NORM command the node exists the LCR protocol by 
sending an IDLE command (CTRL=IDLE, TPID=TP#, TSGS=NACK) at the next multiframe boundary 
10. Once the source node has sent and received NCS=ACK and the LCR protocol finishes, it sends RP=0; an 
intermediate node relays RP=0 after it finishes the LCR protocol; once the sink node has sent and received 
RP=0, it reports the resize completion status to the management or control plane 
Q & A 
	OTN Tutorial
	Agenda
	OTN Introduction
	Motivation for OTN - The Original DWDM Problem
	Motivation for OTN - The OTN Solution
	OTN Layers
	Three Architectural Options for OTN
	OTN Layer Descriptions – Optical Layers
	OTN Layer Descriptions – Digital Layers
	OTN Frame Structure – Electrical Layers
	OTN Layers – End-to-End
	Optical Transport Module (OTM) - Interface
	Single Channel Interfaces – OTM-0.m
	Multi-Channel Interfaces – OTM-0.mvn, OTM-nr.m, OTM-n.m
	OTN IrDI Application Codes
	CWDM Application Codes
	Intra-office Application Codes
	OTN Bitrates
	ODUFlex (2011 Update)
	Potential ODUflex (CBR) Client Rates
	Differences between SONET/SDH & OTN
	Standards and References
	OTN Overhead Functions
	OTN Overhead – Optical Layers
	OTN Overhead Functions – Electrical Layers
	OTN Frame Structure – Electrical Layers
	Forward Error Correction (FEC)
	Reed-Solomon FEC RS (255/239)
	OTN Overhead Details – Electrical Layers
	Overhead Descriptions – Alignment
	OTN Framing
	OTN Signal Regeneration Model
	IAE and BIAE Processing (OTUk/section or ODUkT/path)
	Path and Tandem Connection Monitoring (PM & TCM)
	Tandem Connection Monitoring Modes
	Tandem Connection Visibility
	Tandem Connection Shadow
	SNCP and TCM
	5430 TCM Usage
	Overhead Descriptions – Connectivity and Continuity
	Trail Trace Identifier Format
	SAPI and DAPI Applications
	Overhead Descriptions – Signal Quality
	BIP-8 Generation
	BIP-8 Error Detection and BEI Generation
	TCM Latency Measurement
	5430 Latency Based Routing
	Overhead Descriptions – Maintenance Signals
	OTN Overhead Signal Interactions
	Mapping Overhead
	Control of OTN Timing
	Bit-synchronous Mapping 
	Bit-synchronous Mapping Procedure
	Asynchronous Mapping 
	Asynchronous Mapping Procedure – Fast Client
	Asynchronous Mapping Procedure – Slow Client
	Generic Mapping Procedure (GMP)
	OTN and OTN Client Signal Fault Propagation
	Fault Propagation Example – Bidirectional Fiber Cut
	Fault Propagation Example – Deleted Cross-Connection
	Fault Propagation Example – TCM4 Maintenance LCK
	Fault Propagation Example – TCM3 Maintenance LCK
	Fault Propagation Example – PM Maintenance LCK
	5430 GbE OTN Fault Handling (GFP-T Mapped):�LOS, LOF, LOM, AIS, OCI, LCK, PLM
	5430 GbE Client Fault Handling (GFP-T Mapped):�Client Faults - LOS, Loss-of-character-sync (LOCS)
	5430 GbE Client Fault Handling (GFP-T Mapped):�Link Fault or Auto-negotiation
	5430 GbE Error Handling (GFP-T Mapped)
	5430 10GbE OTN Fault Handling (GFP-Mapped):�LOS, LOF, LOM, AIS, OCI, LCK, PLM
	5430 10GbE Client Fault Handling (GFP-mapped):�Client Faults - LOS, Loss-of-block-sync (LOCS)
	5430 10GbE Client Fault Handling: Local Fault
	5430 10GbE Client Fault Handling: Remote Fault
	543010GbE Error Handling
	5430 SONET/SDH/CBR OTN Fault Handling:�LOS, LOF, LOM, AIS, OCI, LCK, PLM
	5430 SONET/SDH/CBR Client Fault Handling: LOS, LOF
	5430 SONET/SDH/CBR Client Fault Handling: AIS-L/MS-AIS
	5430 SONET/SDH/CBR Error Handling
	OTN Performance Monitoring
	OTN Performance Monitoring Basics
	Additional 5430 OTN Performance Monitoring Parameters
	OTN Multiplexing and Mapping Trees
	OTN Optical Multiplexing Structure
	Pre-2009 OTN Multiplexing Structure with SONET Mapping
	Post-2009 OTN Multiplexing Structure
	OTN Electrical Multiplexing Structure (1 of 2)
	OTN Electrical Multiplexing Structure (2 of 2)
	Single Stage (Flat) vs. Multi-Stage (Step) Multiplexing
	HO ODUk Timeslot Rate Differences
	Auto-Payload Type Function
	ODTU Mapping Methods
	OPU1 Tributary Slots
	OPU2 Tributary Slots
	OPU3 Tributary Slots
	OPU4 Tributary Slots
	ODTUjk Structure
	ODTU.ts Structure
	Slide Number 96
	Slide Number 97
	Slide Number 98
	Slide Number 99
	Slide Number 100
	Slide Number 101
	Slide Number 102
	Slide Number 103
	Slide Number 104
	Slide Number 105
	Multiplex Structure Identifier (MSI)
	Multiplex Structure Identifier (1 of 4)�(PT=20 (AMP): 2.5G TS ODU2/ODU3, 1.25G TS ODU1)
	Multiplex Structure Identifier (2 of 4) (PT=21 (GMP): 1.25G TS ODU2)
	Multiplex Structure Identifier (3 of 4) (PT=21 (GMP): 1.25G TS ODU3)
	Multiplex Structure Identifier (4 of 4)�(PT=21 (GMP): 1.25G TS ODU4, only ODTU4.ts supported)
	Protection Switching
	OTN Automatic Protection Support
	Supported OTN Protection Architectures
	SNC/I and CL-SNCG/I Protection Configurations (cases 1-2, 8-10)
	1+1 SNC/N Protection Configuration (case 4)
	SNC/S Protection Configurations (cases 5-7)
	OTN APS Channel Assignment
	OTN APS Channel Protocol
	APS Channel Format
	OTN Client Mappings
	Client Signal Mapping Methods
	GbE Timing Transparent Transcoding (TTT) Mapping (GFP-T)
	GbE GFP-T Mapping
	10GbE LAN GFP-F Mapping – MAC Frames Only
	10GbE LAN GFP-F Mapping – MAC Frames Only Details
	10GbE LAN GFP-F Mapping – MAC Frames + Preamble �(Ordered Sets via Client Management Frames)
	10GbE LAN GFP-F Mapping – MAC Frames + Preamble Details �(Ordered Sets via Client Management Frames)
	10GbE LAN GFP-F Mapping – MAC Frames + Preamble�(Ordered Sets via Client Data Frames)
	10GbE LAN GFP-F Mapping – MAC + Preamble Frames Details�(Ordered Sets via Client Data Frames)
	10GbE LAN Transparent Mapping Details
	Bit-synchronous Mapping of OC-192
	Other 5430 OTN Capabilities
	Other 5430 OTN Capabilities�
	5430 OTN ODUflex Hitless Circuit Resizing (future)
	ODUflex Resizing Overhead
	LCR (“Red”) Protocol Fields and Functions
	BWR (“Blue”) Protocol Fields and Functions
	BWR (“Blue”) Protocol Fields and Functions (cont’d)
	Error Resiliency Overhead (CRC-3 and CRC-5)
	Resizing Protocols
	Resize Procedure – Bandwidth Increase
	Resize Procedure – Bandwidth Decrease
	Q & A