OTN G.709 Framing: OTU, ODU and OTUCn Transport Layers

OTN is the layer that makes DWDM wavelengths into manageable, monitored, client-agnostic pipes - and the reason a 100G wavelength can carry Ethernet, Fibre Channel or SDH without the transport equipment caring which. Everything about OTN comes from the G.709 frame structure, which defines three nested containers with their own overhead. Once you can map a symptom to the right layer, OTN troubleshooting becomes systematic instead of a guessing game between vendors.

The Three Layers: OPU, ODU and OTU

The frame is a 4-row by 4080-column structure. The first 16 columns carry overhead - the OTU, ODU and OPU overhead areas plus the frame alignment signal - and the remaining 3808 columns are the OPU payload. The three layers nest inside each other:

• OPU (Optical Payload Unit) adapts the client signal into the payload area, adding stuffing and justification so any client rate can be carried in a fixed-size container.
• ODU (Optical Data Unit) adds path-layer overhead - tandem connection monitoring, PM and TCM fields - and represents the path layer that is cross-connected inside an OTN switch.
• OTU (Optical Transport Unit) adds the section-layer overhead and, for OTUk, the forward error correction, and represents the section between regenerators.

An ODU can be formed two ways: by mapping a single non-OTN client such as Ethernet or Fibre Channel, or by multiplexing lower-rate ODUs into a higher-rate one. That dual nature is what makes OTN a mux hierarchy rather than just an encapsulator.

Bit Rates and the k Notation

ODU0 carries roughly 1.25 Gbit/s and ODU1 approximately 2.5 Gbit/s, and both are still widely deployed for legacy services. ODU2 is the 10G container, ODU3 the 40G, and ODU4 the 100G container. The corresponding OTU rates are slightly higher because of the FEC and overhead - OTU2 runs at about 10.7 Gbit/s. Frame periods differ per rate: OTU0 completes a frame every 98.354 µs while OTU2 takes 12.191 µs.

Scaling Past 100G: OTUCn and FlexO

G.709 decoupled the OTU rate from the client rate in later editions by introducing OTUCn, an OTU signal of approximately n×100 Gbit/s that carries n instances of OTUC overhead and n instances of ODUC overhead. ODUCn carries an ODU4 signal inside its payload area, which is what allows a 400G or 800G wavelength to transport a 100G service without re-inventing the hierarchy.

FlexO is the companion interface: a flexible OTN information structure, each instance running near 100G, grouped into FlexO-x interfaces. Because FlexO instance rates were chosen to reuse 100G pluggable modules, a 400G coherent module can present itself as a group of four FlexO instances carrying an OTUC4 signal.

Overhead You Will Actually Read

SM   Section Monitoring      - section trace, BIP-8, defect indication
PM   Path Monitoring         - path trace, BIP-8, path status
TCM  Tandem Connection Mon.  - six levels of nested monitoring
MFAS Multi-frame Alignment   - selects which overhead byte set is valid
GCC  General Communication   - in-band management channel
FEC  Forward Error Correction - Reed-Solomon, adds ~7% line rate

MFAS increments per frame and is what makes the extended overhead unambiguous - without it, a byte in position 3 could mean several different things. The GCC channels are how a management network is carried out of band across a third-party transport, so a GCC alarm usually explains why the element manager lost the far end.

Reading Alarms Layer by Layer

The systematic approach is to read the failure in layer order. A LOS or LOF is a section problem: no light, or a framing mismatch - check the OTU layer, the FEC and the wavelength. An ODU-AIS or ODU-OCI is a path problem: the section is fine and the failure is happening inside the ODU cross-connect. An OPU payload mismatch (PLM) means the mapping declared in the payload structure identifier does not match what is actually arriving, which points at a client-rate or payload-type configuration error rather than an optical one.

Because the OTU section terminates at every regenerator while the ODU path crosses the whole network, the layer at which an alarm appears also tells you the failure domain. A TCM alarm on level 2 specifically isolates the failure to the span between the second and third monitoring points, which is exactly what TCM exists for. For alarm definitions in context, see common OTN alarms troubleshooting, and for the wavelength grid side of the design, 50GHz vs 100GHz channel spacing on the ITU grid.

Why FEC Changes Your Link Budget

OTUk uses Reed-Solomon RS(255,239) FEC, which adds about 7% overhead in exchange for several decibels of coding gain. That gain is why an OTU2 link can be built over a span that would be marginal for a bare 10G signal, and why comparing "10G Ethernet reach" against "OTU2 reach" on the same optic produces confusing numbers: the OTN rate is higher, so the dispersion and OSNR margins are worse even though the FEC help is better. Always compare like for like when budgeting a coherent or direct-detect span.

原文链接：https://www.itu.int/epublications/zh/publication/itu-t-g-709-y-1331-2020-cor-2-2022-11/en