OTN — OTU, ODU, OCh framing

When you carry a 100 GbE Ethernet client over DWDM, the bits don't just travel naked on a lambda. They're wrapped in an OTN (Optical Transport Network) frame structure that adds error correction, performance monitoring, and the ability to multiplex multiple clients onto one wavelength. OTN is the digital wrapper that sits between the client (Ethernet, etc.) and the lambda.

Defined in ITU-T G.709, OTN is what every modern long-haul transport platform — Ciena 6500, Cisco NCS 2000, Nokia 1830 — uses on its line side.

The three layers

OTN itself has three nested layers:

| Layer | Acronym | What it carries | |---|---|---| | Optical Channel | OCh | The actual wavelength (a lambda on the fiber) | | Optical Channel Transport Unit | OTU-k | The line-rate framed signal that fills an OCh (with FEC + line overhead) | | Optical Channel Data Unit | ODU-k | The "container" carrying client traffic, with path overhead |

Inside an ODU sits the client payload, called an OPU-k (Optical channel Payload Unit), into which Ethernet (or SONET/SDH, or even another ODU) is mapped.

Pictorially, going from client to fiber:

[ 100 GbE client ]
        ↓ mapped into
[ OPU4 ]
        ↓ wrapped in
[ ODU4 ]  ← path overhead, performance monitoring
        ↓ wrapped in
[ OTU4 ]  ← line FEC, section overhead, frame alignment
        ↓ modulated as
[ OCh = one DWDM lambda ]

The k in OTU-k / ODU-k

The k is a rate level. Each step is ~4× the previous:

| Rate | Line rate (approx.) | Typical client | |---|---|---| | OTU1 | 2.7 Gbps | STM-16 / 2.5G | | OTU2 | 10.7 Gbps | 10 GbE LAN PHY | | OTU3 | 43 Gbps | 40 GbE | | OTU4 | 112 Gbps | 100 GbE | | OTUCn (flex) | n × 100 Gbps | 200G / 400G coherent superchannels |

The line rate is bigger than the client rate because the OTN frame adds FEC overhead (~7% for hard-decision Reed-Solomon, more for soft-decision LDPC used in modern coherent).

Why OTN exists

Three reasons:

1. FEC. The Reed-Solomon FEC in classic OTN gives ~6 dB of coding gain — equivalent to doubling the optical reach for free. Modern coherent uses much stronger LDPC/soft-decision FEC for >11 dB gain.
2. Performance monitoring. OTN overhead carries trail trace identifiers (TTI), BIP-8 bit-interleaved parity, BER counters, and alarm signaling. You can see exactly where signal degradation begins along a multi-segment trail — vital for SLAs.
3. Multiplexing. Smaller ODUs can be packed into larger ones — ten ODU2 (10G) signals can ride inside one ODU4 (100G), letting one wavelength carry many client streams.

ODUflex and OTU-Cn — the modern world

Legacy OTU rates are fixed steps. ODUflex lets you allocate exactly the bandwidth a client needs (down to small increments). OTU-Cn (flexible OTUC) carries n × 100G and is the basis for 200G / 400G / 800G coherent transponders.

If you're commissioning a new 400G service on a Ciena 6500 today, you're working with OTUC4 carrying ODUC4 carrying ODUflex (or four ODU4 streams), modulated as a coherent QAM signal on one or more 50 GHz slots in a flex-grid network.

What to remember

• OTN sits between client (Ethernet) and lambda (DWDM): OPU → ODU → OTU → OCh.
• FEC is the main reason OTN exists — buys you significant reach.
• Performance monitoring at each layer = you can pinpoint where degradation starts.
• Modern coherent uses OTU-Cn / ODUflex for variable-rate superchannels — you'll see this on Ciena and other modern DWDM transponders.