What are the differences between SONET/SDH and OTN?

This blog posts highlights differences between OTN and SONET/SDH. It also provides links to other blog posts that focus on these differences in detail.

OTN Related Blog

Sharing is caring!

SONET/SDH and OTN are standard protocols for transporting signals from Point A to Point B on (mostly) optical fiber. 

However, there are some key differences:

  1. OTN (at least for OTU1 through OTU4) has a fixed frame size.  SONET/SDH does not.
  2. SONET/SDH has a fixed frame repetition rate (8000 frames/sec).  OTN does not.
  3. When mapping/muxing lower-speed tributary signals into higher-speed signals, SONET/SDH requires that all the lower-speed tributary signals be synchronous with each other and with the high-speed server signal.  OTN does not need this. 
  4. OTN has a standard FEC (Forward Error Correction) mechanism.  SONET/SDH does not have such a thing. 
  5. OTN offers more extensive TCM (Tandem Connection Monitoring) support than does SONET/SDH.
  6. The SONET/SDH standards only support data rates of up to 40Gbps (or OC-768).  The OTN standards support over 100Gbps (e.g., 200Gbps, 400Gbps, etc.)
  7. The mechanisms for handling rate differences are handled differences between the two standards.  SONET/SDH relies exclusively on something called “pointer processing.”  OTN uses different mechanisms altogether (Bit Synchronous Mapping, Asynchronous Mapping, and the Generic Mapping Procedure). 

Additional Questions (Topics) to be Answered in the Differences between OTN and SONET/SDH

  1. How does SONET/SDH support TCM?
  2. How does OTN support TCM?
  3. What is the framing format B100G OTN?
  4. What are the roles of the Individual Overheads Bytes for SONET/SDH?  How are they different from that for OTN?
  5. How do you map 3 STS-1 signals into an STS-3 signal?  How is this different from mapping ODU1s into an ODU2? 

Sharing is caring!

Author: Darrell Smith

Darrell Smith has more than 30 years of experience as an Electrical Engineer. He has about 20 years of experience as an Applications Engineer and the remainder of his time was spent in Hardware Design and Product Marketing. He will now be sharing his wealth of knowledge on this blog.

Leave a Reply

Your email address will not be published. Required fields are marked *