š§šµš² šš¶š³š³š²šæš²š»š°š² š š¼šš šš»š“š¶š»š²š²šæš š š¶šš
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





