OTN Learning Series Part 6: OTN Mapping Vs Grooming

š—§š—µš—² š——š—¶š—³š—³š—²š—æš—²š—»š—°š—² š— š—¼š˜€š˜ š—˜š—»š—“š—¶š—»š—²š—²š—æš˜€ š— š—¶š˜€š˜€

Many engineers use the words š—ŗš—®š—½š—½š—¶š—»š—“ and š—“š—æš—¼š—¼š—ŗš—¶š—»š—“ interchangeably.

They are not the same.

If you confuse them, you misunderstand how OTN actually works.


š—Ŗš—µš—®š˜ š—¢š—§š—” š— š—®š—½š—½š—¶š—»š—“ š—„š—²š—®š—¹š—¹š˜† š—œš˜€

š— š—®š—½š—½š—¶š—»š—“ is the act of placing a client signal into an OTN container.

It happens at the š—¢š—£š—Ø layer.

You take:

10GbE 100GbE SONET OC 192

And you adapt it into structured payload.

Mapping answers one question:

Where does this signal live inside OTN?

It does not combine services. It does not switch containers. It does not optimize capacity.

It simply adapts and inserts.


Figure 6.1

Client signal entering OPU and becoming structured OTN payload.

Figure 6.1


š—Ŗš—µš—®š˜ š—¢š—§š—” š—šš—æš—¼š—¼š—ŗš—¶š—»š—“ š—„š—²š—®š—¹š—¹š˜† š—œš˜€

š—šš—æš—¼š—¼š—ŗš—¶š—»š—“ happens at the š—¢š——š—Ø layer.

It is switching and aggregation of containers.

Example:

10 x ODU0 services Mapped into 1 x ODU2

Or

Multiple ODU2 Aggregated into ODU4

Grooming answers a different question:

How do we efficiently transport multiple services across the backbone?

It involves:

š—¢š——š—Ø š˜€š˜„š—¶š˜š—°š—µš—¶š—»š—“ š—›š—¶š—²š—æš—®š—æš—°š—µš—¶š—°š—®š—¹ š—ŗš˜‚š—¹š˜š—¶š—½š—¹š—²š˜…š—¶š—»š—“ š—¦š—²š—æš˜ƒš—¶š—°š—² š—®š—“š—“š—æš—²š—“š—®š˜š—¶š—¼š—»

This is where transport engineering becomes architectural.


Figure 6.2

Multiple ODU containers entering an OTN cross connect and merging into higher rate container.

Figure 6.2


š— š—®š—½š—½š—¶š—»š—“ š—©š˜€ š—šš—æš—¼š—¼š—ŗš—¶š—»š—“ š—¦š—¶š—ŗš—½š—¹š—¶š—³š—¶š—²š—±

Here is the clean distinction:

Mapping is vertical. Client into container.

Grooming is horizontal. Container to container.

One prepares the signal. The other optimizes the network.


Figure 6.3

Side by side comparison showing mapping flow versus grooming flow.

Figure 6.3


š—Ŗš—µš˜† š—§š—µš—¶š˜€ š——š—¶š˜€š˜š—¶š—»š—°š˜š—¶š—¼š—» š— š—®š˜š˜š—²š—æš˜€

If you mislabel mapping as grooming:

You oversimplify network design. You misunderstand OTN cross connects. You confuse service adaptation with service optimization.

In large backbone deployments, that confusion leads to:

Poor capacity planning Inefficient hierarchy usage Operational complexity

Transport engineering demands precision.

š— š—®š—½š—½š—¶š—»š—“ is about structure. š—šš—æš—¼š—¼š—ŗš—¶š—»š—“ is about scale.

Both are essential. But they solve different problems.


Figure 6.4

End to end flow showing client mapping at ingress and grooming in core network.

Figure 6.4