OTN Tutorial

Steve Surek
Ciena Corporation
October 27-28, 2011
 Agenda

1 OTN Introduction

2 OTN Overhead

3 OTN and OTN Client Signal Fault Propagation

4 OTN Performance Monitoring

5 OTN Multiplexing and Mapping Trees

6 OTN Client Mappings

7 Other 5430 OTN Capabilities

2
OTN Introduction
 Motivation for OTN - The Original DWDM Problem

Proprietary DWDM systems

Carrier A
Domain
Vendor B
Vendor A Domain
Domain
NE NE End
NE NE
Customer

Carrier B
Domain Carrier C
Domain
NE
Vendor interop
NE NE
only at client level NE

End
Customer Lack of end-to-end service management

4
 Motivation for OTN - The OTN Solution
Standardized Inter-Domain Standardized Management


Interface Capability
 Single and multiple  Digital wrapper providing
wavelength interfaces Intra-domain Interfaces (IaDI) standard management
with or w/o OSC functions for signal quality
 Standard rates and
remain proprietary monitoring, connection and
connectivity monitoring,
formats (2.5G, 10G, 40G,
maintenance signal generation
100G interfaces)
and detection, etc.
 Standard forward error Carrier A
 Standardized management of
correction (FEC) Domain
optical layers and end-to-end
Vendor B
 Multiplexing and Vendor A Domain service transport
switching Domain
NE NE End
NE NE
Customer

Carrier B
Domain Carrier C
Domain
NE
Standarize
NE NE
Inter-domain NE
Interfaces (IrDI)

End
Customer End-to-end service management

5
 OTN Layers

 Physical Electrical Layers

OPU  End-to-End Monitoring
Electrical  Inter-Domain Interworking
(Digital) ODU
Domain  Client Transparency
OTU
 Sub-Wavelength ODU Switching
 High Efficiency Grooming

 Physical Optical Layers

OCh  Standardized Optical Layer Model
Optical
 Provides Inter-Domain Interworking
(Analog) OMS
Domain  Client Transparency
OTS
 Full-Wavelength OCh Switching
 Wavelength Selective Bypass

6
 Three Architectural Options for OTN

A B C
Framed G.709
Switched (Digital OTN)
Switched G.709
G.709 (Digital OTN)
(Digital OTN)
Dynamic
Flexible WDM
WDM (Analog OTN)
Static WDM (Analog OTN)
(Analog OTN)

 G.709 provides all  G.709 provides dynamic  G.709 provides framing

dynamic capabilities switching only
 WDM for capacity only  WDM with reconfigurable  WDM for all dynamic
connections capabilities

7
 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)

8
 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)

9
 OTN Frame Structure – Electrical Layers

Overhead for Frame Alignment

Overhead for the OTU Operations (Section)

Forward Error Correction

Column
Row 1 7 8 14 15 16 17 3824 3825 4080
1 FA OH OTUk OH O
2 P
OPUk Payload OTUk FEC
U
3 ODUk OH (4 x 3808 bytes) (4 x 256 bytes)
k
4 OH

Payload for Client Signal

Overhead for Client Mappings

Overhead for ODU Operations (Tandem Connection and Path)

 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)

10
 OTN Layers – End-to-End

Client Service
Client Port ODU SNC

OCH/OTU Link 2
OMS Link 1
OTS Link 1 OCH/OTU Link 1
OMS Link 2

OTS Link 2

Node 1 Node 2 Node 3 Node 4

ODU Path from ODU Switch OCH Switch ODU Switch

Source to Destination 3R
(ODU termination)
Integrated Optical Transponder/
SR Optics
WDM Optics Amplifier Regenerator Client Port
OTU Sections between ODU SNC SONET/SDH
Ethernet
Regeneration Points OCH/OTU
Fibre Channel

OCH/OTU
(OTU termination) Link 1 Link 2

OMS Sections between OMS Link 1 OMS Link 2

Optical Add/Drop Points OTS Link 1 OTS Link 2 OTS Link 3

(OMS termination)
OTS Sections between
Optical Amplifier Points
(OSC termination)

11
 Optical Transport Module (OTM) - Interface

Client

OPU
For Client Service Mapping OH
OCh Payload Unit (OPU) Payload

ODU
For Switching and Multiplexing OH
OCh Data Unit (ODU) Payload

OTU
For Transmission
OH
OCh Transport Unit (OTU) Payload FEC

Digital
For Management
E/O and O/E Adaptation
Analog
OCh
Optical Channel (OCh)
OH

OCC OCC Optical Channel Carrier (OCC)

OH OH OCC OCC OCC OCC

OMS
Optical Multiplex Section (OMS)
OTM OH
Overhead
Signal OTS
Optical Transmission Section (OTS)
(OOS) OH

12
 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)

IrDI

MPI-S λs MPI-R
3R 3R
MPI-S λs MPI-R
3R 3R

…
…

MPI-S λs MPI-R
3R 3R

Domain A Domain Z

MPI-S=Single channel Main Path Interface Source

MPI-R=Single channel Main Path Interface Receive

13
 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) supporting various 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

3R IrDI 3R
3R 3R
OM OA MPI-Sm MPI-Rm OD
OA
…

…
3R 3R
3R 3R
3R MPI-Rm MPI-Sm 3R
OD OA OA OM
…

…
3R 3R

Domain A Domain Z
MPI-Sm=Multi-channel Main Path Interface Source
MPI-Rm=Multi-channel Main Path Interface Receive

14
 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

15
 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

16
 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

17
 OTN Bitrates

G.709 Defined Rates Frame

Times
Based on support for GE
(1/2 of ODU1 payload) ODU0 1.244 × 255/239
98.354
OC48/STM16 × 239/238 ODU1 2.499 OTU1 2.666 48.971
OC192/STM64 × 239/237 ODU2 10.037 OTU2 10.709 12.191
OC768/STM256/40GE × 239/236 ODU3 40.319 OTU3 43.018 3.035
Based on support for 100GE
(10 × OC192/STM64 × 239/227 ODU4 104.794 OTU4 111.810 1.168

Non-Standard Supplemental Rates

10GE* × 239/238 ODU1e 10.356 OTU1e 11.049 11.816
10GE** × 239/237 ODU2e † 10.400 OTU2e 11.096 11.767
Based on support for 4 x ODU2e (@2.5G TS)
(4 x ODU2e × 239/238) ODU3e1 41.773 OTU3e1 44.569 2.929
Based on support for 4 x ODU2e (@1.25G TS)
(OC768/STM256 × 243/217 × 239/255) ODU3e2 41.786 OTU3e2 44.583 2.928

* Transparent 10.3125 Gbps Bitstream

** Transparent 10.3125 Gbps Bitstream (Includes Fixed Stuff Bytes) All rates provided in Gbps and times in μs
† ODU2e is included in G.709 OTU rate based on RS (255,239) FEC coding

18
 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)

ODUflex @ 5 x 1.25Gbps Tributary Slots

Re-usable Capacity
6 Gbps Client
Stranded Capacity
Traditional ODU2

* 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)

19
 Potential ODUflex (CBR) Client Rates
Client Rate ODUflex (CBR) Tolerance
Potential CBR Client Signal
(Gbps) Rate (Gbps) (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 Notes:
CPRI level 4 3.072000000 3.084907563 0.002
G.709 allows any ODUflex(CBR)
4G Fibre Channel 4.250000000 4.267857143 100 rate > 2.48832G
CPRI level 5 4.915200000 4.935852101 0.002 InfiniBand covers very broad
1xDDR InfiniBand 5.000000000 5.021008403 100 range of rates (2.5G-120G line
CPRI level 6 6.144000000 6.169815126 0.002 rate, 2G-96G data rate)
8G Fibre Channel 8.500000000 8.535714286 100 Video has pairs of closely
related rates (x and x/1.001)
CPRI level 7 9.840400000 9.881746218 0.002
4xSDR InfiniBand 10.000000000 10.042016807 100 CPRI requires very tight clock
tolerance (0.002ppm)
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 G.709 mapping defined
8xSDR/4xDDR InfiniBand 20.000000000 20.084033613 100
12xSDR InfiniBand 30.000000000 30.126050420 100 G.709v3 Appendix XI
8xDDR/4xQDR InfiniBand 40.000000000 40.168067227 100
12xDDR InfiniBand 60.000000000 60.252100840 100
G.709 Living List client
8xQDR InfiniBand 80.000000000 80.336134454 100
Other known CBR clients
12xQDR InfiniBand 120.000000000 120.504201681 100

20
 Differences between SONET/SDH & OTN

SONET/SDH OTN
Synchronous clocking Asynchronous clocking
architecture architecture
Originally specified to operate on a Designed to operate on multiple
single wavelength wavelengths (DWDM)
SONET/SDH only scales to 40G OTN scales to 100G (and beyond)
Uses a fixed frame rate and Uses a fixed frame size and
increases frame size as the speed increases the frame rate as the
increases speed increases
 Sized for voice data rate  Sized for error correction to
 64kb/s voice requires 8,000 correct 16 blocks per frame
bytes/s (1 byte/125 µs)  Reed Solomon RS(255/239)
 i.e. 1 frame/125 µs  i.e. Correct 8 bit errors/block
Section, Line, and Path layers Section and Path layers only

21
 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 jitter and wander within the optical transport network (OTN)
 G.Sup43 - Transport of IEEE 10G Base-R in Optical Transport Networks (OTN)

22
OTN Overhead Functions
 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

24
 OTN Overhead Functions – Electrical Layers

Tandem
Frame Section Path Payload
Connection
Alignment Monitoring Monitoring Management
Monitoring

Continuity Supervision Monitors the integrity of a link (LOS, OCI, LTC)

Connectivity Supervision Monitors the integrity of a sequence of connections by comparing source and
destination IDs (TIM)

Signal Quality Supervision Monitors performance after transmission via error parity check (DEG)

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)

Maintenance Information Suppress alarm escalation by informing upstream/downstream of defects (PMI,

FDI, AIS, BDI, IAE, BIAE)
Supports single-ended supervision of a connection (OCI, LCK)

Multiplexing Supervision Monitors the multiplex structure supporting single-stage multiplexing (MSIM)

Management Communications Provides communications channels for path and section management
communications and path protection communications (FOP)

25
 OTN Frame Structure – Electrical Layers

Overhead for Frame Alignment

Overhead for the OTU Operations (Section)

Forward Error Correction

Column
Row 1 7 8 14 15 16 17 3824 3825 4080
1 FA OH OTUk OH O
2 P
OPUk Payload OTUk FEC
U
3 ODUk OH (4 x 3808 bytes) (4 x 256 bytes)
k
4 OH

Payload for Client Signal

Overhead for Client Mappings

Overhead for ODU Operations (Path)

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

26
 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
Log No FEC
 16 added overhead bits: (6.7% overhead) BER
 Corrects for 8 or less bit errors in 239 bits With FEC
 8 x 16 x 4 = 512 bits per OTU frame
 Anything over 8 bits is completely uncorrected 10-12
~6.5dB Gain @ 10-12 BER

 Typical gain is ~6.5 dB at 1e-12 BER

OSNR (dB)

27
 Reed-Solomon FEC RS (255/239)

Overhead Payload FEC

1 2 238 1 2 16
Column
Row 1 16 17 32 33 48 3808 3824 3825 3840 3841 3856 4065 4080
1
2
3
4

16 OTU
Sub-rows
per OTUk 1 2 239 240 255 1 2 239 240 255 1 2 239 240 255
Frame OH Payload FEC OH Payload FEC OH Payload FEC
x 4 rows (1 byte) (238 bytes) (16 bytes) (1 byte) (238 bytes) (16 bytes) (1 byte) (238 bytes) (16 bytes)

239 255 239 255 239 255

Information Information Information
Parity Parity Parity
Check Check Check

28
 OTN Overhead Details – Electrical Layers

Column
PSI
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

1 Frame Alignment MFAS SM GCC0 RES RES JC

PT
PM& TCM
2 RES TCM ACT
TCM6 TCM5 TCM4 FTFL RES JC
Row 3 TCM3 TCM2 TCM1 PM EXP RES JC
MSI/RES

RES
4 GCC1 GCC2 APS/PCC RES PSI NJO

ACT Activation/deactivation control channel

APS Automatic Protection Switching channel Section, Path & Tandem Connection Monitor
BDI Backward Defect Indication
BEI Backward Error Indication 1 2 3
BIAE Backward Incoming Alignment Error TTI BIP-8
BIP-8 Bit Interleaved Parity – level 8
DAPI Destination Access Point Identifier
DMp Delay Measurement – path level
DMtn Delay Measurement – tandem level n 0
EXP Experimental SAPI
FTFL Fault Type and Fault Location channel
(source)
GCC General Communications Channel
IAE Incoming Alignment Error 15 SM BEI/BIAE BDI IAE RES
JC Justification Control 16
MFAS Multi-frame Alignment Signal
NJO Negative Justification Opportunity DAPI TCMi BEI/BIAE BDI STAT
PCC Protection Communication Channel (destination)
PM Path Monitor
31 PM BEI BDI STAT
PSI Payload Structure Identifier
PT Payload Type 32
RES Reserved
SAPI Source Access Point Identifier
Operator Path & Tandem Connection Delay
Specific PM&
SM Section Monitor
STAT Status TCM DMt1 DMt2 DMt3 DMt4 DMt5 DMt6 DMp RES
63
TCM Tandem Connection Monitor
TTI Trail Trace Identifier

29
 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

30
 OTN Framing
Column
1 2 3 4 5 6 7
LOF/LOM: OTUk Row 1 OA1 OA1 OA1 OA2 OA2 OA2 MFAS Framing Bytes (FAS & MFAS):
LOFLOM: ODUj demux OA1 = ‘1111 0110’
FAS
Set when OOF for >3ms OA2 = ‘0010 1000’
IF to OOF MFAS = 8-bit counter
Cleared when IF for >3ms
(ODUj demux)

IF to OOF
Frame IF Time (OTUk) Frame OOF
Type (μS) Type Time (μS)
ODU0 197 OOF to IF ODU0 492
(any 4 bytes for OTUk, all bytes for ODUj demux)
OTU1/ 97.9 OTU1/ 245
ODU1 ODU1
Invalid FAS/MFAS for 5 frames
OTU2/ 24.4 OTU2/ 61.0
ODU2 ODU2
ODU2e 23.5 In Out of ODU2e 58.8
OTU3/ 6.07 Frame Frame OTU3/ 15.2
ODU3 ODU3
OTU4/ 2.34 Valid FAS/MFAS for 2 frames OTU4/ 5.84
ODU4 ODU4

31
 OTN Signal Regeneration Model
OTUk Section Regenerator Chain

OTUk OTUk
ODUk ODUk ODUk
OTUk CDR OTUk OH OTUk CDR OTUk OH OTUk CDR & OTUk OH
& OH Generation & OH Generation OH Generation
Termination & Retiming Termination & Retiming Termination & Retiming
Incoming frame slip

OTUk frame slip (OTUk LOF) propagates until CDR switches to local clock

ODUj Path Mux/Demux Chain

ODUk/j ODUk/OTUk ODUk/j ODUk/OTUk ODUk/j ODUk/OTUk
Demux & OH Generation Demux & OH Generation Demux & OH Generation
ODUj CR (Local clock) ODUj CR (Local clock) ODUj CR (Local clock)

OTUk X X X OTUk

ODUj ODUj ODUj

OTUk CDR & ODUk/j OTUk CDR & ODUk/j OTUk CDR & ODUk/j
OTUk/ODUk OH Mux OTUk/ODUk OH Mux OTUk/ODUk OH Mux
Termination Termination Termination
Incoming frame slip

ODUj frame slip (ODUj LOFLOM) propagates until demultiplexer switches to local clock

32
 IAE and BIAE Processing (OTUk/section or ODUkT/path)

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

frame slip incoming

to section or OOF propagates downstream
tandem connection
OOF OOF
Detect incoming IAE,
IF IAE dIAE Suppress near/far end PM for
LOF/LOFLOM Inserted after
clear or switch current and previous second
reframe or switch
to local ref that IAE is active
to local clock
dBIAE (active for 4096 frames)
aBIAE

Node A Node Z

Detect incoming BIAE,

Suppress far end PM for
current and previous second OTUk section or
that BIAE is active
ODUkT tandem connection

33
 Path and Tandem Connection Monitoring (PM & TCM)

TCM6 TCM6 TCM6 TCM6 TCM6 TCM6 TCM6 TCM6 TCM6 TCM6 TCM6 TCM6
TCM5 TCM5 TCM5 TCM5 TCM5 TCM5 TCM5 TCM5 TCM5 TCM5 TCM5 TCM5
TCM4 TCM4 TCM4 TCM4 TCM4 TCM4 TCM4 TCM4 TCM4 TCM4 TCM4 TCM4 TCMi
TCM3 TCM3 TCM3 TCM3 TCM3 TCM3 TCM3 TCM3 TCM3 TCM3 TCM3 TCM3 Overhead
TCM2 TCM2 TCM2 TCM2 TCM2 TCM2 TCM2 TCM2 TCM2 TCM2 TCM2 TCM2
TCM1 TCM1 TCM1 TCM1 TCM1 TCM1 TCM1 TCM1 TCM1 TCM1 TCM1 TCM1

ODUk Operator C Client

Operator A User Signal
User Operator B
Client
Signal

NNI CM NNI CM NNI CM

UNI CM
QoS of Leased Connection is Monitored by User
Path CM

Provide management visibility at multiple (nested) levels

34
 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

35
 Tandem Connection Visibility
TCM6 TCM6 TCM6 TCM6 TCM6 TCM6 TCM6 TCM6
TCM5 TCM5 TCM5 TCM5 TCM5 TCM5 TCM5 TCM5
TCM4 TCM4 TCM4 TCM4 TCM4 TCM4 TCM4 TCM4
TCM3 TCM3 TCM3 TCM3 TCM3 TCM3 TCM3 TCM3
TCM2 TCM2 TCM2 TCM2 TCM2 TCM2 TCM2 TCM2
TCM1 TCM1 TCM1 TCM1 TCM1 TCM1 TCM1 TCM1

Backhaul Backhaul
Domain Underse Domain
a
Domain
Service Provider 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)

36
 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

37
 SNCP and TCM

Operational TCM Operational TCM

Non-intrusive TCMs Non-intrusive TCMs

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

38
 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.

ODUk Switch Nodes OTUk / OCh OTUk / OCh

Client OMS OMS

SM
TCM4
TCM3
PM

39
 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’)

40
 Trail Trace Identifier Format

1 2 3 4 5 6 7 8

0 SAPI[0] SAPI/DAPI Field Format

1 0 SAPI[1]
Source
2 0 SAPI[2]
Access
Point
IS character # NS character #
…..…
…..…

…..…

Identifier
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
15 0 SAPI[15] CC ICC UAPC
16 DAPI[0] CC ICC UAPC
17 0 DAPI[1]
CC ICC UAPC
Destination
18 0 DAPI[2]
Access CC ICC UAPC
Point
…..…
…..…

…..…

Identifier CC ICC UAPC

CC ICC UAPC
31 0 DAPI[15]

32 CC = ISO 3166 Country Code

ICC = ITU Carrier Code as per ITU-T Rec. M.1400
…………………………………..

UAPC = Unique Access Point Code is carrier specific

Operator
Specific
 All TTI characters are from the T.50 character set
 Only SAPI and DAPI fields used for TIM detection

63
 Operator Specific bytes are user specified

SAPI[0] and DAPI[0] are set to All-0s

41
 SAPI and DAPI Applications
Transmitted TTI Expected SAPI or SAPI+DAPI
Point-to-Point
Application
(unidirectional or bidirectional)
Expected SAPI

Transmitted TTI Expected SAPI

Point-to-Multipoint
Application
(unidirectional bridge)
Expected SAPI

Transmitted TTI

Transmitted TTI Expected DAPI

Multipoint-to-Point
Application
(unidirectional select)
Transmitted TTI
(Note: only supported on
5430 for 2:1 selector)

42
 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

43
 BIP-8 Generation

1 …………………………………… 14 15 ……………………………………… 3824

SM
1
BIP-8
TCM6 TCM5 TCM4
Frame n

2
BIP-8 BIP-8 BIP-8
TCM6 TCM5 TCM4 PM
3
BIP-8 BIP-8 BIP-8 BIP-8
4
BIP-8
SM
1
BIP-8
Frame n+1

TCM6 TCM5 TCM4

2
BIP-8 BIP-8 BIP-8
TCM6 TCM5 TCM4 PM
3
BIP-8 BIP-8 BIP-8 BIP-8
4
SM
1
BIP-8
Frame n+2

TCM6 TCM5 TCM4

2
BIP-8 BIP-8 BIP-8
TCM6 TCM5 TCM4 PM
3
BIP-8 BIP-8 BIP-8 BIP-8
4

 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)

44
 BIP-8 Error Detection and BEI Generation
1 …………………………………… 14 15 …………………………………… 3824

SM
1
BIP-8
TCM6 TCM5 TCM4
Frame n

2
BIP-8 BIP-8 BIP-8
TCM6 TCM5 TCM4 PM
3
BIP-8 BIP-8 BIP-8 BIP-8
4
BIP-8
SM
1
BIP-8
Frame n+1

TCM6 TCM5 TCM4

2
BIP-8 BIP-8 BIP-8
TCM6 TCM5 TCM4 PM
3
BIP-8 BIP-8 BIP-8 BIP-8
4
SM
1 XOR
BIP-8
Frame n+2

TCM6 TCM5 TCM4

2 XOR
BIP-8 BIP-8 BIP-8
TCM6 TCM5 TCM4 PM
3 XOR
BIP-8 BIP-8 BIP-8 BIP-8
# of # of # of
4 BIP BIP BIP
Errors Errors Errors

>0 >0 >0

 BBE/BEI counts used to calculate NE/FE PM
ODUkP ODUkT OTUk

 BBE count used to trigger DEG defect

BBE BBE BBE
ODUkP ODUkT OTUk
BEI BEI BEI

45
 TCM Latency Measurement

1 A-end node configured 2 Z-end node configured

to source and measure to loopback specified
Tframe specific PM/TCM DM bit PM/TCM DM bit

00001111
A Z
11110000

3 Insert bit transition 4 Detect bit transition 5 Calculate latency = (Nf – Ni)×Tframe/2,
into specified on specified where Tframe=ODU frame time
PM/TCM DM bit PM/TCM DM bit
and start frame and stop frame errormax ≤ Tframe + (Dr-Dt)/2,
counter (value=Ni) counter (value=Nf ) where Dr and Dt are receive and
transmit propagation delays

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

46
 5430 Latency Based Routing

Lowest Cost Routing - Default Lowest Cost Routing – Admin

AW: 5040 Weight
AW: 5040
5430
5430

AW: 5040 AW: 5040 AW: 10000 AW: 15000

TODAY

With
AW: 5040 AW: 5040 Addition of AW: 5040 AW: 5040
5430
Latency 5430

• Assuming all Admin Weights are the same then • Operator has modified Admin Weights on two center
algorithm will chose the lowest hop count for the route spans
• Default Admin Weight is 5040 • Route = lowest summed admin weight
Lowest Cost Routing – Latency

AW: 5040
5430
LT: 3ms

• Operator has enabled auto-latency calculation in the

AW: 10000 AW: 15000 network (or applied them manually) and selected
LT: 4ms LT: 5ms lowest latency option for the circuit
• Route = lowest summed latency

AW: 5040 AW: 5040 AW: Admin Weight

5430
LT: 1ms LT: 1.5ms LT: Latency

47
 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)

48
 OTN Overhead Signal Interactions
Signal Propagation Consequent Action Detect Generate Forward Operation Backward Operation
OCh OTUk ODUk ODUj or
Loss of Signal – Payload (LOS-P) Client
Optical
Loss of Frame (LOF), Loss of Lane (LOL),
Channel
Loss of Lane Frame (LOLFRAME)
(OCh)
OTU Alarm Indication Signal (AIS)
Loss of Multiframe (LOM)
ODUk-AIS
FEC Corrected Errors (FECcorrErr)

Backward Defect Indicator (BDI)

Section
Monitoring Trace Identifier Mismatch (TIM)
(SM) Backward Incoming Alignment Error (BIAE)
Incoming Alignment Error (IAE) Only applicable
Backward Error Indicator (BEI) DEG when TIM
Bit Interleaved Parity (BIP-8) consequent actions
are enabled
Alarm Indication Signal (AIS) (via STAT)
Path &
Tandem Connection Backward Defect Indicator (BDI)
Monitoring Trace Identifier Mismatch (TIM) All detection and
(PM & TCM) generation functions
Locked (LCK), Open Connection Indication (OCI),
specified for the
Loss of Tandem Connection (LTC, TCM only) (via STAT)
ODUk are repeated
Backward Incoming Alignment Error (BIAE) (TCM only) for the ODUj
Incoming Alignment Error (IAE) (via STAT,TCM only)
Backward Error Indicator (BEI) DEG
Bit Interleaved Parity (BIP-8)
Loss of Frame and Multiframe (LOFLOM, only
applicable to ODUk/ODUj multiplexing)

Payload Multiplex Structure identifier (MSI) ODUj-AIS

Structure Identifier Payload Type (PT)
(PSI)
Client Signal Fail (CSF) Client
Specific E.g., PN-11, LF, etc.

49
 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 operations for 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

50
 Control of OTN Timing
Adapted Synchronization Reference Chain
OTN SEC/ SEC/ SEC/
UTC PRC Island SSU
EEC EEC EEC

1 mapping NE
+ 9 muxing NEs

Intervening SECs
replaced with OTN
equipment 10x 20 SEC/EEC Sync network limit
bounded by SSUs
(100 OTN mapping/muxing operations) Reference point

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

51
 Bit-synchronous Mapping
Column
JC Bits NJO Byte PJO Byte
16
00 Justification (0x00) Client Data
1 JC
01 Not used Not used
2 JC 10 Not used Not used
Row
3 JC 11 Not used Not used

4 NJO PJO

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

52
 Bit-synchronous Mapping Procedure
Input Client
Datastream
OPU Overhead OPU Payload

00 •••
00 •••
00 •••
N P •••
Frame
Negative N 00 •••
Justification 00 •••
Threshold
First-In/ 00 •••
First-out N P •••
Data Buffer Frame
Positive
N+1
Justification
Threshold
00 •••
00 •••
00 •••
Frame
N+2
N P •••

00 •••
Frame
N+3
00 •••
00 •••
N P •••

53
 Asynchronous Mapping
Column
JC Bits NJO Byte PJO1 Byte PJO2 Byte
16
00 Justification (0x00) Client Data Client Data
1 JC
01 Client Data Client Data Client Data
2 JC 10 case used
10 Justification (0x00) Justification (0x00) Justification (0x00)
Row for multiplexing
3 JC 11 Justification (0x00) Justification (0x00) Client Data

4 NJO PJO1 PJO2 PJO2 used only for multiplexing

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

54
 Asynchronous Mapping Procedure – Fast Client
Input Client
Datastream
OPU Overhead OPU Payload

00 •••
00 •••
00 •••
No
Justification N P •••
Frame
N 01
00 •••
Negative Negative
Justification Justification 00
01 •••
Threshold
First-In/ 01
00 •••
First-out N P •••
NoFrame
Positive Data Buffer Justification
N+1
Justification
Threshold
00 •••
Negative
Justification
00 •••
00 •••
Frame
N+2
N P •••

01
00 •••
Frame
N+3
01
00 •••
01
00 •••
N P •••

55
 Asynchronous Mapping Procedure – Slow Client
Input Client
Datastream
OPU Overhead OPU Payload

00 •••
00 •••
00 •••
N P •••
No
Frame
Justification
N 00
11 •••
Negative Positive
Justification Justification 00
11 •••
Threshold
First-In/ 00
11 •••
First-out N P •••
Frame
Positive Data Buffer
N+1
Justification
Threshold
No 00 •••
Justification
00 •••
00 •••
Positive
Frame
Justification
N+2
N P •••

11
00 •••
Frame
N+3
11
00 •••
11
00 •••
N P •••

56
 Generic Mapping Procedure (GMP)
Column
15 16

1 JC1 JC4 JC1 Cm (bits 1-8) JC4 ΣCnD (bits 1-5)

Row 2 JC2 JC5 JC2 Cm (bits 9-14), II, DI JC5 ΣCnD (bits 1-5)

3 JC3 JC6 JC3 CRC-8 JC6 CRC-5

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

57
OTN and OTN Client Signal Fault Propagation
 Fault Propagation Example – Bidirectional Fiber Cut

ODUk Switch Nodes

Client
2/0 0/3 3/0 0/2/3 3rd Party OTN 4/2/0 0/4 4/0 0/2
× Domain
ODU0 XC ODU0 XC ODU0 XC ODU0 XC ODU0 XC ODU0 XC

OTU2 LOS OTU3 LOS OTU3 OTU4 OTU4 OTU2

SM
ODU3 ODU3-AIS ODU4
TCM4
ODU3-AIS
ODU2
PM (tunnel)
ODU0 ODU0-AIS Frame slip ODU0 ODU0-IAE
TCM3
ODU0-AIS ODU0-BIAE
ODU0 ODU0-AIS
TCMi (opt)
ODU0-AIS
ODU0-AIS
ODU0
PM
ODU0-AIS

59
 Fault Propagation Example – Deleted Cross-Connection

ODUk Switch Nodes

Client
2/0 0/3 3/0 0/2/3 3rd Party OTN 4/2/0 0/4 4/0 0/2
Domain
ODU0 XC ODU0 XC ODU0 XC ODU0 XC ODU0 XC ODU0 XC

SM
OTU2 OTU3 × OTU3 OTU4 OTU4 OTU2

ODU3 ODU4
TCM4
ODU2
PM (tunnel)
ODU0 ODU0-OCI Frame slip ODU0 ODU0-IAE
TCM3
ODU0-OCI ODU0-BIAE
ODU0 ODU0-OCI
TCMi (opt)
ODU0-OCI
ODU0-OCI
ODU0
PM
ODU0-OCI

60
 Fault Propagation Example – TCM4 Maintenance LCK

ODUk Switch Nodes

Client
3rd Party OTN
2/0
| 0/3 3/0 0/2/3
Domain
4/2/0 0/4 4/0 0/2

ODU0 XC ODU0 XC ODU0 XC ODU0 XC ODU0 XC ODU0 XC

OTU2 OTU3 OTU3 OTU4 OTU4 OTU2

SM
ODU3 ODU3-LCK ODU4
TCM4
ODU2
PM (tunnel)
ODU0 ODU0-AIS Frame slip ODU0 ODU0-IAE
TCM3
ODU0-AIS ODU0-BIAE
ODU0 ODU0-AIS
TCMi (opt)
ODU0-AIS
ODU0-AIS
ODU0
PM
ODU0-AIS

61
 Fault Propagation Example – TCM3 Maintenance LCK

ODUk Switch Nodes

Client
2/0 0/3 3/0 0/2/3 3rd Party OTN 4/2/0 0/4 4/0 0/2
Domain
ODU0 XC ODU0 XC ODU0 XC ODU0 XC ODU0 XC ODU0 XC

OTU2 | OTU3 OTU3 OTU4 OTU4 OTU2

SM
ODU3 ODU4
TCM4
ODU2
PM (tunnel)
ODU0 ODU0-LCK ODU0
TCM3
ODU0 ODU0-LCK
TCMi (opt)
ODU0-LCK
ODU0-LCK
ODU0
PM
ODU0-LCK

62
 Fault Propagation Example – PM Maintenance LCK

ODUk Switch Nodes

Client
2/0 0/3 3/0 0/2/3 3rd Party OTN 4/2/0 0/4 4/0 0/2
Domain
ODU0 XC ODU0 XC ODU0 XC ODU0 XC ODU0 XC ODU0 XC

| OTU2 OTU3 OTU3 OTU4 OTU4 OTU2

SM
ODU3 ODU4
TCM4
ODU2
PM (tunnel)
ODU0 ODU0
TCM3
ODU0
TCMi (opt)
ODU0-LCK
ODU0
PM

63
 5430 GbE OTN Fault Handling (GFP-T Mapped):
LOS, LOF, LOM, AIS, OCI, LCK, PLM

Link
ODU-AIS Cons. Action
Transmit Ingress Ingress X 3R Egress Egress
Down
Receive
GbE Client OTN OTN Client GbE
Regen
Client Adaptation Mapping Demapping Adaptation Client

Receive Egress Egress 3R Ingress Ingress Transmit

GbE Client OTN Regen OTN Client GbE
Client Adaptation Demapping Mapping Adaptation Client

• Egress client signal Consequent Action is provisionable to laser off, /V/ codes
(K30.7 error codes) or /C1/C2/ link fault sequences

64
 5430 GbE Client Fault Handling (GFP-T Mapped):
Client Faults - LOS, Loss-of-character-sync (LOCS)

GFP CMF (LOS, LOCS) Cons. Action Link

Transmit X Ingress Ingress Egress Egress Down
Receive
3R
GbE Client OTN OTN Client GbE
Regen
Client Adaptation Mapping Demapping Adaptation Client

Receive Egress Egress 3R Ingress Ingress Transmit

GbE Client OTN Regen OTN Client GbE
Client Adaptation Demapping Mapping Adaptation Client

• 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

65
 5430 GbE Client Fault Handling (GFP-T Mapped):
Link Fault or Auto-negotiation

/C1/C2/
Transmit Ingress Ingress Egress Egress /C1/C2
Receive
GbE Client OTN 3R
OTN Client GbE
Client Adaptation Mapping Regen
Demapping Adaptation Client

Receive Egress Egress Ingress Ingress Transmit

3R
GbE Client OTN OTN Client GbE
Regen
Client Adaptation Demapping Mapping Adaptation Client

• Link fault/auto-negotiation code words passed transparently end-to-end

66
 5430 GbE Error Handling (GFP-T Mapped)

Ingress client errors Transport error Transport error

/V/ code

Transmit Ingress Ingress Egress Egress Receive

GbE Client OTN 3R
OTN Client GbE
Client Adaptation Mapping Regen
Demapping Adaptation Client

Receive Egress Egress Ingress Ingress Transmit

3R
GbE Client OTN OTN Client GbE
Regen
Client Adaptation Demapping Mapping Adaptation Client

• Ingress 8B/10B coding violations (CV) or transport generated errors are

replaced with /V/ characters (K30.7 error codes) on egress

67
 5430 10GbE OTN Fault Handling (GFP-Mapped):
LOS, LOF, LOM, AIS, OCI, LCK, PLM

Idle ODU-AIS Cons. Action

Link
Transmit Ingress Ingress X 3R Egress Egress
Down
Receive
or LF
10GbE Client OTN OTN Client 10GbE
Regen
Client Adaptation Mapping Demapping Adaptation Client

Receive Egress Egress 3R Ingress Ingress Transmit

10GbE Client OTN Regen OTN Client 10GbE
Client Adaptation Mapping Mapping Adaptation Client
RF RF GFP CMF/CDF (RF) RF

• 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

68
 5430 10GbE Client Fault Handling (GFP-mapped):
Client Faults - LOS, Loss-of-block-sync (LOCS)
GFP CMF (LOS, LOCS)
Link
Idle Cons. Action
Transmit X GFP Ingress
CDF (LF ordered set)
Ingress Egress Egress
Down
Receive
or LF
10GbE Client OTN 3R
OTN Client 10GbE
Client Adaptation Mapping Regen
Demapping Adaptation Client

Receive Egress Egress Ingress Ingress Transmit

3R
10GbE Client OTN OTN Client 10GbE
Regen
Client Adaptation Mapping Mapping Adaptation Client

RF RF GFP CMF/CDF (RF) RF

• 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

69
 5430 10GbE Client Fault Handling: Local Fault

LF GFP CMF/CDF (LF) LF

Transmit
LF
Ingress Ingress 3R Egress Egress Receive
10GbE Client OTN OTN Client 10GbE
Regen
Client Adaptation Mapping Demapping Adaptation Client

Receive Egress Egress 3R Ingress Ingress Transmit

10GbE Client OTN Regen OTN Client 10GbE
Client Adaptation Mapping Mapping Adaptation Client
RF RF GFP CMF/CDF (RF) RF

• 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

70
 5430 10GbE Client Fault Handling: Remote Fault

RF GFP CMF/CDF (RF) RF

Transmit Ingress Ingress Egress Egress
RF
3R Receive
10GbE Client OTN OTN Client 10GbE
Client Adaptation Mapping Regen
Demapping Adaptation Client

Receive Egress Egress Ingress Ingress Transmit

3R
10GbE Client OTN OTN Client 10GbE
Regen
Client X Adaptation Mapping Mapping Adaptation Client

LOS Idle 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

71
 5430 10GbE Error Handling

Ingress client errors Transport error Transport error

Errors

Transmit Ingress Ingress Egress Egress Receive

10GbE Client OTN 3R
OTN Client 10GbE
Client Adaptation Mapping Regen
Demapping Adaptation Client

Receive Egress Egress Ingress Ingress Transmit

3R
10GbE Client OTN OTN Client 10GbE
Regen
Client Adaptation Demapping Mapping Adaptation Client

• 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

72
 5430 SONET/SDH/CBR OTN Fault Handling:
LOS, LOF, LOM, AIS, OCI, LCK, PLM

AIS-L/ (TS) AIS-L/

MS-AIS MS-AIS
ODU-AIS
Transmit
SONET/ Ingress Ingress X 3R Egress PN-11(CBR)
Egress
LOF
Receive
Client OTN OTN Client SONET/
SDH/CBR Regen
Adaptation Mapping Demapping Adaptation SDH/CBR
Client Client

Receive Egress Egress Transmit

3R Ingress Ingress
SONET/ Client OTN SONET/
Regen OTN Client
SDH/CBR Adaptation Demapping SDH/CBR
Mapping Adaptation
Client Client

• 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

73
 5430 SONET/SDH/CBR Client Fault Handling: LOS, LOF

AIS-L/ (TS) AIS-L/ (TS)

AIS-L/
MS-AIS MS-AIS
MS-AIS
Transmit
SONET/
X Ingress
PN-11(CBR)
Ingress Egress Egress Receive
Client OTN 3R
OTN
PN-11(CBR)
Client
LOF
SONET/
SDH/CBR Regen SDH/CBR
Client Adaptation Mapping Demapping Adaptation
Client

Receive Egress Egress Transmit

3R Ingress Ingress
SONET/ Client OTN SONET/
Regen OTN Client
SDH/CBR Adaptation Demapping SDH/CBR
Mapping Adaptation
Client Client

• 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

74
 5430 SONET/SDH/CBR Client Fault Handling: AIS-L/MS-AIS

AIS-L/MS-AIS
Transmit AIS-L/
Ingress Ingress Egress Egress Receive
MS-AIS
SONET/ 3R SONET/
SDH/CBR Client OTN OTN Client
Adaptation Mapping Regen SDH/CBR
Client Demapping Adaptation
Client

Receive Egress Egress Transmit

3R Ingress Ingress
SONET/ Client OTN SONET/
Regen OTN Client
SDH/CBR Adaptation Demapping SDH/CBR
Mapping Adaptation
Client Client

• Rx AIS-L/MS-AIS propagates end-to-end

75
 5430 SONET/SDH/CBR Error Handling

Ingress client errors Transport error Transport error

Errors
Transmit Receive
SONET/ Ingress Ingress Egress Egress
Client OTN 3R SONET/
SDH/CBR OTN Client
Adaptation Mapping Regen SDH/CBR
Client Demapping Adaptation
Client

Receive Egress Egress Transmit

Ingress Ingress
SONET/ 3R SONET/
Client OTN OTN Client
SDH/CBR Regen SDH/CBR
Adaptation Demapping Mapping Adaptation
Client Client

• Ingress as well as transport errors are propagated to the client

76
OTN Performance Monitoring
 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

78
 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

79
OTN Multiplexing and Mapping Trees
 OTN Optical Multiplexing Structure

x1 x1
OCC OCh OTU4
xm x1 x1
x1 xi OCC OCh OTU3
OTM-n.m OCG-n.m x1 x1
xj OCC OCh OTU2
x1
xk x1 x1
1 ≤ i+j+k+m ≤ n OCC OCh OTU1

x1
OSC OOS OTS, OMS, OCh, COMMS OH

Multiplexing Mapping

 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)

81
 Pre-2009 OTN Multiplexing Structure with SONET Mapping

SONET OC768 Client OPU3 ODU3 (L)

Rate x4
or OTU3 OCh 43.018G
Hierarchy OPU3 ODU3 (H)
40.319G
ODTU13
x16 ODTU23
x4

OC192 Client OPU2 ODU2 (L)

or OTU2 OCh 10.709G
x4 OPU2 ODU2 (H)
10.037G
ODTU12
x4

OC48 Client OPU1 ODU1 (L)

OTU1 OCh 2.666G
2.499G

Mapping ODUk (L) = Low Order ODU

Multiplexing ODUk (H) = High Order ODU

82
 Post-2009 OTN Multiplexing Structure

Client OPU4 ODU4 (L)

or OTU4 OCh 111.809G
OPU4 ODU4 (H)
104.794G
x80 ODTU4.ts
x40 x10 x80/ts
x10
x2

Client OPU3 ODU3 (L)

or OTU3 OCh 43.018G
OPU3 ODU3 (H)

ODTU3.ts 40.319G
x32 x3 ODTU13
x16 x32/ts
x4 ODTU23
10GbE OPU2e ODU2e (L)

Client OPU2 ODU2 (L)

or OTU2 OCh 10.709G
OPU2 ODU2 (H)
10.037G
ODTU2.ts
x8 ODTU12 x8/ts
x4

Client OPU1 ODU1 (L)

or OTU1 OCh 2.666G
OPU1 ODU1 (H)
2.499G
ODTU01 ODUflex (L) OPUflex Client
x2
Client
Mapping ODUk (L) = Low Order ODU
OPU0 ODU0 (L)
Multiplexing ODUk (H) = High Order ODU
1.244G

83
 OTN Electrical Multiplexing Structure (1 of 2)
ODU4 ODU4 x1 OPU4 100GBASE-LR4/-ER4 converted to serial 66b
Client Signal blocks (Annex E) and GMP mapped (17.7.5 –
(L) (L)
OTU4 x80 Amd.1)
ODTU4.1 ODU0
ODU4 x1 OPU4 (H) 19.3.7 19.6.3 GMP
19.2
ODU4 (H) PT=21 x40 ODTU4.2 ODU1
19.1.4 19.3.7 19.6.3 GMP
19.2
x10 ODU2
ODTU4.8

ODTUG4
19.3.7 ODU2e
19.6.3 GMP

PT=21
19.2
x2 ODTU4.31 ODU3
19.3.7 19.6.3 GMP
19.2
x80/ts ODTU4.ts ODUflex
19.3.7 19.6.3 GMP
19.2

ODU3 to
ODU (H) x1/X
OPU3-X Client Signal
ODU3 CBR40G (17.2.3) STM-256 - AMP/BMP (17.2)
OTU3 (L) x1 OPU3 40GBASE-LR4 (17.7.4.1) converted to serial 66b
(L) Client Signal
blocks (Annex E) then transcoded into 513b
x32 ODTU3.1 ODU0 blocks (Annex B) then 1027b framed (Annex F)
ODU3 to ODU3 x1 OPU3 (H) 19.3.6 19.6.2 GMP
19.2 and GMP mapped (17.7.4 – Amd.1)
ODU (H) (H) PT=21
x16 ODTU13 ODU1
19.1.2 19.3.2 19.5.2 AMP
19.2
ODTUG3

x4 ODTU23 ODU2
19.3.3 19.5.3 AMP
PT=21

19.2
x3 ODTU3.9 ODU2e
OR 19.3.6 19.6.2 GMP
x1 19.2
x32/ts ODTU3.ts ODUflex
19.3.6 19.6.2 GMP
19.2
x16 ODTU13
3 PT=20
ODTUG

ODU1
OPU3 (H) 19.3.2 19.5.2 AMP
19.2
PT=20 x4 ODTU23 ODU2
19.1.2 19.3.3 19.5.3 AMP
19.2

CBR10G3 (17.2.4) 10GBASE-R - BMP (17.2)

ODU2e to ODU2e x1 OPU2e FC-1200 (17.8.2) - 66b blocks transcoded into a
ODU (H) Client Signal
(L) (L) 513b block (Annex B) then assembled into a
superblock then mapped into a special GFP
frame then byte sync mapped

84
 OTN Electrical Multiplexing Structure (2 of 2)
ODU2 to
ODU (H) x1/X
OPU2-X Client Signal
ODU2 CBR10G (17.2.2) STM-64 - AMP/BMP (17.2)
OTU2 (L) x1 OPU2 GFP / Extended OPU2 (17.4.1) - 10GBASE-R
Client Signal
(L) payload + preamble + OS, G.7041 (7.9)

ODTUG2
x8 ODTU2.1 ODU0

PT=21
19.3.5 19.6.1 GMP GFP (17.4) - 10GBASE-R payload G.sup43 (6.2)
ODU2 to ODU2 x1 OPU2 (H) 19.2
ODU (H) (H) PT=21 x4 ODTU12 ODU1
19.3.1 19.5.1 AMP
19.1.1 19.2
x1 x8/ts ODTU2.ts ODUflex
OR 19.3.5 19.6.1 GMP
19.2

ODTUG2
PT=20
OPU2 (H) x4 ODTU12 ODU1
PT=20 19.3.1 19.5.1 AMP
19.2
19.1.1

ODU1 to
x1/X CBR2G5 (17.2.1) STM-16, CMGPON D/U2 -
ODU (H) OPU1-X Client Signal AMP/BMP (17.2)
ODU1
(L) x1 OPU1 FC-200 (17.7.2) - GMP
OTU1 Client Signal
(L) 1.5G HD SDI (Living List) - GMP
ODTUG1
PT=20

ODU1 to ODU1 x1 OPU1 (H) x2 CPRI Option 3 (Appendix VIII, Amd.1) - GMP
ODTU01 ODU0
(H) PT=20 19.3.4 19.5.4 AMP
ODU (H) 19.2 1.238Gb/s < X ≤ 2.488Gb/s (17.7.2) - GMP
19.1.3
1000BASE-X (17.7.1.1) - TTT+GMP
STM-1, STM-4 (17.7.1) - GMP
ODU0 to ODU0 OPU0 FC-100 (17.7.1) - GMP
x1
ODU (H) Client Signal
(L) (L) 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
OPUflex(CBR)
3G HD SDI (Living List) - BMP

ODUflex to IB 2G, 4G, 8G, CPRI 7 (Living List)

ODUflex x1 OPUflex
ODU (H) Client Signal CPRI Options 4 - 6 (App. VIII, Amd.1) - BMP
(L) (L)
X > 2.488Gb/s (17.9) - BMP
X > 0 possible (17.4) - GFP-F OPUflex(GFP)
OTU/ODU OH Multiplexing Mapping
X = Nx~1.244Gb/s recommended

Sketch derived from: December 2009 G.709v3 published & June 2010 Amd.1 consented (TD 221r1/PLEN)
David W. Martin – July 16, 2010
85
 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

86
 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

87
 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)

88
 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)

89
 OPU1 Tributary Slots

MFAS Multi Column

3823
3824
bit Frame Frame 1

15
16
17
18
19
20
8 Row Row
1 1

TSOH
2 2

TS1
0
3 3
4 4
5 1

TSOH
6 2

TS2
1
7 3
1 2 1 2 1 2 1.25G TS#
8 4

• 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

90
 OPU2 Tributary Slots

MFAS Multi Column

3823
3824
bits Frame Frame

15
16
17
18
19
20
21
22
23
24
25
26
1
(6)78 Row Row
1 1

TSOH
2 2

TS1
(0)00
3 3
4 4
5 1

TSOH
6 2

TS2
(0)01
7 3
8 4

13 1
14 2 TSOH
(0)11
15 3
TS4
16 4
TS1 or TS5

17 1 1
TSOH

18 2 2
(1)00
19 3 3
20 4 4
TS4 or TS8

29 13 1
TSOH

30 14 2
(1)11 1 2 3 4 5 6 7 8 1 2 7 8 1.25G TS#
31 15 3
32 16 4 1 2 3 4 1 2 3 4 1 2 3 4 2.5G TS#

91
 OPU3 Tributary Slots

MFAS Multi Column

3823
3824
bits Frame Frame

15
16
17
18

31
32
33
34

47
48
49
50
1
(4)5678 Row Row
1 1

TSOH
2 2

TS1
(0)0000
3 3
4 4
5 1

TSOH
6 2

TS2
(0)0001
7 3
8 4

61 1

TSOH
TS16
62 2
(0)1111
63 3
64 4 TS1 or TS17
65 1 1
TSOH

66 2 2
(1)0000
76 3 3
68 4 4
TS16 or TS32

125 61 1
TSOH

15
16
17
18

15 31
16 32

15 31
16 32
126 62 2 1.25G TS#
1 1

1 1
2 2
2 2

(1)1111
127 63 3
16
15

2.5G TS#
1
2

128 64 4

92
93
bits
OMFI

0000001
0000000

1001111
1001110
8
7
6
5
4
3
2
1

320
319
318
317
316
315
314
313
2345678 Row
Multi
Frame
Row
Frame

4
3
2
1
4
3
2
1
4
3
2
1
4
3
2
1
1
Column

PSI
PSI
PSI
PSI

TSOH TSOH TSOH TSOH 15

FI
FI
FI
FI

OM
OM
OM
OM

TS80 TS79 TS2 TS1 16

41 1 41 1 41 1 41 1 41 1 41 1 41 1 41 1 17
42 2 42 2 42 2 42 2 42 2 42 2 42 2 42 2 18

79 39 79 39 79 39 79 39 79 39 79 39 79 39 79 39 55
80 40 80 40 80 40 80 40 80 40 80 40 80 40 80 40 56
1 41 1 41 1 41 1 41 1 41 1 41 1 41 1 41 57
2 42 2 42 2 42 2 42 2 42 2 42 2 42 2 42 58

39 79 39 79 39 79 39 79 39 79 39 79 39 79 39 79 95
OPU4 Tributary Slots

40 80 40 80 40 80 40 80 40 80 40 80 40 80 40 80 96
41 1 41 1 41 1 41 1 41 1 41 1 41 1 41 1 97
42 2 42 2 42 2 42 2 42 2 42 2 42 2 42 2 98

79 39 79 39 79 39 79 39 79 39 79 39 79 39 79 39 3815
80 40 80 40 80 40 80 40 80 40 80 40 80 40 80 40 3816
FS FS FS FS FS FS FS FS FS FS FS FS FS FS FS FS 3817
FS FS FS FS FS FS FS FS FS FS FS FS FS FS FS FS 3818
FS FS FS FS FS FS FS FS FS FS FS FS FS FS FS FS 3819
FS FS FS FS FS FS FS FS FS FS FS FS FS FS FS FS 3820
FS FS FS FS FS FS FS FS FS FS FS FS FS FS FS FS 3821
FS FS FS FS FS FS FS FS FS FS FS FS FS FS FS FS 3822
FS FS FS FS FS FS FS FS FS FS FS FS FS FS FS FS 3823
FS FS FS FS FS FS FS FS FS FS FS FS FS FS FS FS 3824
 ODTUjk Structure

ODTUjk

c-1
Overhead 1 2 3

c
1 1
2
3

ODTUjk Payload
ts

r-1
jk=01,12,13,23 r

ODTUjk ODTUjk ODTUjk ODTUjk

2.5G TS c r ts payload overhead 1.25G TS c r ts payload overhead
bytes bytes bytes bytes
ODTU12 952 16 1 15232 1x4 ODTU01 1904 8 1 15232 1×4

ODTU13 238 64 1 15232 1x4 ODTU12 952 32 2 30464 2×4

ODTU23 952 64 4 60928 4x4 ODTU13 238 128 2 30464 2×4

ODTU14 952 128 8 121856 8×4

94
 ODTU.ts Structure

j x ts -1
j x ts
ODTUk.ts
Overhead 1 2 3
1
2
3

ODTUk.ts Payload
ts

r-1
k=2,3,4 r

ODTUk.ts payload ODTUk.ts overhead

j r ts
bytes 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

95
Line/Client 5430 OTU4 Single Stage Multiplexing Tree (TDM Switching)

ODU-4 Cross Connect

OTU-4 ODU4XX SWIO

ODU3 Cross Connect

ODU421 ODU3xx SWIO

ODU2e Cross Connect

ODU2exx SWIO

Switch Fabric
ODU2 Cross Connect
Note: ODU2XX SWIO
Packet Termination and OTN
Switching are supported
concurrently but illustrated here ODU1 Cross Connect
separately ODU1XX SWIO

ODU0 Cross Connect

ODU0XX SWIO

ODUFlex Cross Connect

ODUFXX SWIO
SLP

Multiplexing/Demultiplexing Cross Connect

96
Line/Client 5430 OTU4 Single Stage Multiplexing Tree (Packet Switching)

100GbE ODU4 100GbE Termination

OTU-4 ODU402 PP
MAC

ODU3 40GbE Termination

ODU421 1024B/ 40GbE PP
ODU302
1027B MAC

ODU3 40G Termination

ODU305 40G PP
GFP-F

Switch Fabric
WAN MAC
Note:
Up to a maximum of 10 ODUk ODU2e 10GbE CBR Termination
terminations are supported ODU2e03 10GbE PP
MAC
Packet Termination and OTN
Switching are supported
concurrently but illustrated here 10GbE ODU2 10GbE Termination
separately ODU209 GFP-F PP
MAC

WAN MAC refers to a MAC with no

PCS layer
ODU2 10G Termination
ODU205 10G PP
GFP-F
WAN MAC

XG ODUFlex Termination
ODUF05 GFP-F SLP
PP
WAN MAC

Multiplexing/Demultiplexing Packet Processing

and Mapping/Demapping

97
 5430 100G Client Mapping Tree

Switch Fabric
Transparent 100GbE
Client

100GbE ODU402 SWIO

100GbE 100GbE Termination

100GbE PP
MAC

Mapping/Demapping Cross Connect

98
Line/Client 5430 OTU3 Single Stage Multiplexing Tree

ODU-3 Cross Connect

OTU3 ODU3XX SWIO

ODU2e Cross Connect

ODU321 ODU2exx SWIO

Switch Fabric
ODU2 Cross Connect
ODU2XX SWIO

ODU1 Cross Connect

ODU1XX SWIO

ODU0 Cross Connect

ODU0XX SWIO

ODUFlex Cross Connect

ODUFXX SWIO
SLP

Multiplexing/Demultiplexing Cross Connect

99
Client 5430 OTU3 Two Stage Multiplexing Tree

ODU-3Cross Connect
OTU3 ODU3XX SWIO

ODU2 Cross Connect

ODU320 ODU2XX SWIO

Switch Fabric
ODU-1 Cross Connect
ODU220 ODU1XX SWIO

ODU1 Cross Connect

ODU221 ODU1XX SWIO

ODU0 Cross Connect

ODU0XX SWIO

ODUFlex Cross Connect

ODUFXX SWIO

Multiplexing/Demultiplexing Cross Connect

100
 5430 40G Client Mapping Tree

4xODU2e ODU2e Cross Connect

OTU3e2 ODU3e2 ODU2eXX SWIO

Switch Fabric
Clients

1024B/ Transparent 40GbE ODU-3Cross Connect

40GbE ODU302 SWIO
1027B

OC768/ ODU302/0 Transparent OC768/STM256 ODU-3Cross Connect

SWIO
STM256 3

Mapping/Demapping Cross Connect

101
Line/Client 5430 OTU2 Single Stage Multiplexing Tree

ODU2 Cross Connect

OTU2 ODU2XX SWIO

Switch Fabric
ODU1 Cross Connect
ODU221 ODU1XX SWIO

ODU0 Cross Connect

ODU0XX SWIO

ODUFlex Cross Connect

ODUFXX SWIO

Multiplexing/Demultiplexing Cross Connect

102
Client 5430 OTU2 Two Stage Multiplexing Tree

ODU2 Cross Connect

OTU2 ODU2XX SWIO

ODU1 Cross Connect

ODU220 ODU1XX SWIO

ODU0 Cross Connect

ODU120 SWIO

Switch Fabric
ODU0XX

ODU1 Cross Connect

ODU221 ODU1XX SWIO

ODU0 Cross Connect

ODU0XX SWIO

ODUFlex Cross Connect

ODUFXX SWIO

Multiplexing/Demultiplexing Cross Connect

103
 5430 10G Client Mapping Tree

ODU2e Cross Connect

OTU2e ODU2exx SWIO

Transparent 10GbE at 11.096G ODU2e Cross Connect

10GbE ODU2e03 SWIO

Switch Fabric
Standard 10GbE mappings to ODU2
Clients

ODU2 Cross Connect

10GbE MAC GFP-F ODU205/09 SWIO

10GbE mapping to ODU2 supports standard

G.709 payload mapping, and payload + preamble
+ ordered set as defined in G.7041 (3 variants)

Transparent OC192/STM64 ODU2 Cross Connect

OC192/ ODU202/03 SWIO
STM-64

Mapping/Demapping Cross Connect

104
 5430 OTU1/2.5G Multiplexing/Mapping Tree

ODU1 Cross Connect

OTU1 ODU1XX SWIO

ODU0 Cross Connect

ODU120 ODU0XX SWIO

Switch Fabric
Client

OC-48/ ODU102/0 OC-48/STM-16 Transparency ODU1 Cross Connect

STM16 3
SWIO

GbE Transparency ODU0 Cross Connect

GbE GFP-T ODU007 SWIO

Future GFP-T Client Transparency ODU0/1 Cross Connect

ODU0/1xx SWIO
Clients CBR

Mapping/Demapping Cross Connect

105
 Multiplex Structure Identifier (MSI)

ODUk Switch Nodes

OTUk / OCh OTUk / OCh

Xmt MSI Exp MSI Xmt MSI Exp MSI
Exp MSI Xmt MSI Exp MSI Xmt MSI

Independent
MSI values

Multiplexing arrangement at Multiplexing arrangement at

each end of link must match 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)

106
 Multiplex Structure Identifier (1 of 4)
(PT=20 (AMP): 2.5G TS ODU2/ODU3, 1.25G TS ODU1)
ODU1 1 2 3 4 5 6 7 8 1.25G ODU3 1 2 3 4 5 6 7 8 2.5G
MSI TS # MSI TS #
PSI[2] 00 00 0000 1 PSI[2] ODTU type Tributary Port # 1
PSI[3] 00 00 0001 2 PSI[3] ODTU type Tributary Port # 2
PSI[4] ODTU type Tributary Port # 3
PSI[5] ODTU type Tributary Port # 4
ODU2 1 2 3 4 5 6 7 8 2.5G
MSI TS # PSI[6] ODTU type Tributary Port # 5
PSI[2] 00 00 0000 1 PSI[7] ODTU type Tributary Port # 6
PSI[3] 00 00 0001 2 PSI[8] ODTU type Tributary Port # 7
PSI[4] 00 00 0010 3 PSI[9] ODTU type Tributary Port # 8
PSI[5] 00 00 0011 4 PSI[10] ODTU type Tributary Port # 9
PSI[11] ODTU type Tributary Port # 10
ODU
 Tributary PSI[12] ODTU type Tributary Port # 11
Type
 Port #
PSI[13] ODTU type Tributary Port # 12
00: ODTU13
 00 0000: 1 PSI[14] ODTU type Tributary Port # 13
01: ODTU23
 00 0001: 2 PSI[15] ODTU type Tributary Port # 14
10: RES
 ... PSI[16] ODTU type Tributary Port # 15

11: RES
 00 1111: 16 PSI[17] ODTU type Tributary Port # 16

Notes: (1) ODTU23 Tributary port # = 1-4

(2) Default ODTU type is ODTU13

107
 Multiplex Structure Identifier (2 of 4) (PT=21 (GMP): 1.25G TS ODU2)

ODU2 1 2 3 4 5 6 7 8 1.25G
MSI TS #

PSI[2] ODTU type Tributary Port # 1

PSI[3] ODTU type Tributary Port # 2

PSI[4] ODTU type Tributary Port # 3

ODU
 Tributary
Type
 Port #
PSI[5] ODTU type Tributary Port # 4
00: ODTU12
 00 0000: 1
PSI[6] ODTU type Tributary Port # 5
01: RES
 00 0001: 2
PSI[7] ODTU type Tributary Port # 6
10: ODTU2.ts
 ...
PSI[8] ODTU type Tributary Port # 7
11: Unallocated
 00 0111: 8
PSI[9] ODTU type Tributary Port # 8

108
 Multiplex Structure Identifier (3 of 4) (PT=21 (GMP): 1.25G TS ODU3)

ODU3 1 2 3 4 5 6 7 8 1.25G
MSI 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 ODU
 Tributary
Type
 Port #
PSI[8] ODTU type Tributary Port # 7
PSI[9] ODTU type Tributary Port # 8 00: ODTU13
 00 0000: 1
PSI[10] ODTU type Tributary Port # 9 01: ODTU23
 00 0001: 2
PSI[11] ODTU type Tributary Port # 10 10: ODTU3.ts
 ...
PSI[12] ODTU type Tributary Port # 11 11: Unallocated
 01 1111: 32
: : : :
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

109
 Multiplex Structure Identifier (4 of 4)
(PT=21 (GMP): 1.25G TS ODU4, only ODTU4.ts supported)

ODU4 1 2 3 4 5 6 7 8 1.25G
MSI 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
TS
 Tributary
PSI[7] Occupation Tributary Port # 6
Occupation
 Port #
PSI[8] Occupation Tributary Port # 7
0: Unallocated
 000 0000: 1
PSI[9] Occupation Tributary Port # 8
PSI[10] Occupation Tributary Port # 9
1: Allocated
 000 0001: 2

PSI[11] Occupation Tributary Port # 10  ...

PSI[12] Occupation Tributary Port # 11  100 1111: 80
: : : :
PSI[78] Occupation Tributary Port # 77
PSI[79] Occupation Tributary Port # 78
PSI[80] Occupation Tributary Port # 79
PSI[81] Occupation Tributary Port # 80

110
Protection Switching
 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

112
 Supported OTN Protection Architectures
G.873.1/Table 7-1 Overview of linear OTN protection architectures and related monitoring
Protection Switching Protection Entity Set APS Protected Entity Protection Trigger Criteria
Architecture Type Subclass Switched Channel Server Layer Switched Entity

Case 1 1+1 uni SNC/I Individual no one HO ODUk or one ODUkP ODU(/OTU?) SSF/SSD
OTUk

Case 2 1+1 bi SNC/I individual 111 one OTUk ODUkP ODU SSF/SSD

Case 3 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 ODUkP ODU TSF/TSD
Case 4 and/or OTUk
1+1 uni SNC/S individual no one or more HO ODUk ODUkT (/P?) ODUkT(/OTUk?)
Case 5 and/or OTUk SSF/SSD

Case 6 1+1 bi SNC/S individual 001-110 one or more HO ODUk ODUkT (/P?) ODUkT(/OTUk?)
and/or OTUk SSF/SSD

Case 7 1:n bi SNC/S individual 001-110 one or more HO ODUk ODUkT (/P?) ODUkT(/OTUk?)
and/or OTUk SSF/SSD
1+1 uni CL-SNCG/I group no one HO ODUk LO ODU HO ODUkP SSF/SSD
Case 8 and HO ODUdPLM

Case 9 1+1 bi CL-SNCG/I group HO 000 one HO ODUk LO ODU HO ODUkP SSF/SSD
and HO ODUdPLM

Case 10 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.

Other issues: No bidirectional or 1:N SNC/N, no CL-SNCG/S (nearest equivalent to Line APS)

113
 SNC/I and CL-SNCG/I Protection Configurations (cases 1-2, 8-10)

For bidirectional SNC/I, Working and

Protection transport entities must be
at the same rate (OTUk), For SNC/I, a single entity is
Monitoring occurs at Other forms may be different rates switched per protection group
server layer of the layer For CL-SNCG/I multiple LO
cross-connected entities are switched
(protection group rate !=
cross-connect rate)

Defects outside the Protected

domain have no effect on
protection switching operations

114
 1+1 SNC/N Protection Configuration (case 4)
Working transport entity

CI CI
AI AI
E E

Monitoring occurs at same CI Protection transport entity CI

layer as cross-connections
(protection group rate =
cross-connect rate) Protected domain

Working transport entity

Working and
CI CI
Protection transport
AI CI AI
entities may be E E

carried across any CI Protection transport entity CI

HO facilities
Defects outside
Protected domain
protection domain
may cause false
switching
(not recommended,
use SNC/S)

115
 SNC/S Protection Configurations (cases 5-7)

Defects outside
protection domain do
not affect protection
switching operation

Working and
Protection transport
entities may be
carried across any
HO facilities

Monitoring occurs at same

layer as cross-connections
(protection group rate =
cross-connect rate)

116
 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.

117
 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

118
 APS Channel Format

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/ Protection Requested Signal Bridged Signal Reserved
state type
A B D R

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)

119
OTN Client Mappings
 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)

121
 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


122
 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

123
 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


124
 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

125
 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


126
 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

127
 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


128
 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

129
 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)


130
 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 Payload Area: 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

131
Other 5430 OTN Capabilities
 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

133
 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
Increase  Fabric connection resizing is vendor specific
client rate
from 4G to
6G

Increase/Decrease underlying signal itself

Add/Remove Timeslots Add/Remove Timeslots

ODU Link ODU Link

10GbE
10GbE

OPUx TS4 and TS5 exist OPUx TS4 and TS7 exist
Add TS9 Add TS11

134
 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

135
 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

TPID Field Bit Number

1 2 3 4 5 6 7
HO OPUk TSOH Row # 1 2
HO OPUk TSOH Col # 4 5 6 7 8 7 8
Control (CTRL) Field
- Used to transfer LCR protocol operation indication from source end to sink end
- Carried in row 2 bits 5&6
Resizing CTRL Words
Value Command Comments
Indication that the node has completed LCR and there is no new LCR
00 IDLE operation
Indication that the Tributary Slot is to be added to the ODUflex
01 ADD Connection
Indication that the Tributary Slot is to be removed from the ODUflex
10 REMOVE Connection
Indication that LCR will be started at the next resize multiframe
11 NORM boundary when sending out NORM command after ADD or REMOVE
command at the resize multiframe boundary

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

136
 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

137
 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)

138
 Error Resiliency Overhead (CRC-3 and CRC-5)

CRC-5 used to perform error checking Mapping CRC Checksum Bits

on LCR protocol overhead OH Bits crc1 crc2 crc3 crc4 crc5
RCOH1 bit 4 X X X
- Uses x5 + x + 1 generator polynomial
RCOH1 bit 5 X X X
- Contents rejected if CRC check fails RCOH1 bit 6 X X
RCOH1 bit 7 X X
RCOH1 bit 8 X X
RCOH2 bit 4 X X X
RCOH2 bit 5 X X
RCOH2 bit 6 X X
RCOH2 bit 7 X X
RCOH2 bit 8 X X
X indicates a mapping OH bit used in the EXOR equation of the associated CRC bit

CRC-3 used to perform error checking Mapping CRC Checksum Bits

OH Bits crc1 crc2 crc3
on BWR protocol overhead RCOH1 bit 1 X
- Uses x3 + x2 + 1 generator polynomial RCOH1 bit 2 X
RCOH1 bit 3 X X
- Contents rejected if CRC check fails RCOH2 bit 1 X X
RCOH2 bit 2 X X X
RCOH2 bit 3 X X
X indicates a mapping OH bit used in the EXOR equation of the associated CRC bit

139
 Resizing Protocols

 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)

ODUfP/PKT ODUfP/PKT

ODUkP/ODUj-21 ODUkP/ODUj-21 ODUkP/ODUj-21 ODUkP/ODUj-21

A1 B1 B2 C1

NCS
BWR_Generator BWR_Receiver

RP TSCC RP TSCC
NCS NCS
NCS
BWR_Receiver BWR_Generator
ODUfP/PCK ODUfP/PCK

RP TSCC RP TSCC RP TSCC

BWR_Generator_Relay BWR_Receiver_Relay BWR_Generator_Relay BWR_Receiver_Relay
RP TSCC

RP TSCC RP TSCC RP TSCC

BWR_Receiver_Relay BWR_Generator_Relay BWR_Receiver_Relay BWR_Generator_Relay
RP TSCC

RP CTRL TPID TSGS RP CTRL TPID TSGS

LCR_Generator LCR_Receiver LCR_Generator LCR_Receiver

RP CTRL TPID TSGS RP CTRL TPID TSGS RP CTRL TPID TSGS RP CTRL TPID TSGS

RP CTRL TPID TSGS RP CTRL TPID TSGS

LCR_Receiver LCR_Generator LCR_Receiver LCR_Generator

ODUkP/ODUj-21 ODUkP/ODUj-21 ODUkP/ODUj-21 ODUkP/ODUj-21

A1 B1 C1

140
 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

141
 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

142
Q&A