
SDH, or Synchronous Digital Hierarchy, is a family of ITU-T standards for synchronous digital transport over optical fiber and related media. It was developed from the late 1980s telecommunications standards work of the Consultative Committee for International Telegraph and Telephony (CCITT), now ITU-T, and became the international counterpart to North American SONET.
SDH gave carriers a standardized way to multiplex lower-speed circuits into higher-speed optical signals, monitor service quality, protect traffic from fiber or equipment failures, and interconnect equipment from multiple vendors. It became a foundation for international voice trunks, leased lines, mobile backhaul, enterprise private circuits, ISP transport, and early broadband aggregation.
Why SDH Was Needed
Before SDH, many carrier networks used plesiochronous digital hierarchy, or PDH. PDH systems were close in timing but not exactly synchronized, which made multiplexing and extracting individual lower-speed circuits cumbersome. To reach a lower-rate tributary inside a high-rate PDH stream, operators often had to demultiplex through multiple stages.
SDH solved that operational problem with a synchronous hierarchy, pointer mechanisms, standardized overhead, and a management model. Lower-rate payloads could be mapped into virtual containers and carried through higher-rate frames in a more flexible and observable way. This was a major improvement for carrier operations.
Relationship To SONET
SONET and SDH are closely related. SONET is the North American system based on STS and OC rates, while SDH is the international system based on STM rates. They align at common line rates. For example, SONET OC-3 and SDH STM-1 are both 155.52 Mbps.
The naming differs, but the practical goals are similar: synchronous optical transport, multiplexing hierarchy, operations overhead, protection switching, timing, and carrier-grade service delivery. Equipment and networks often interwork across SONET and SDH boundaries through standardized mappings and optical rates.
STM Rates
The base SDH signal is STM-1, with a line rate of 155.52 Mbps. Higher rates are multiples of STM-1:
- STM-1: 155.52 Mbps, corresponding to SONET OC-3.
- STM-4: 622.08 Mbps, corresponding to OC-12.
- STM-16: 2.488 Gbps, corresponding to OC-48.
- STM-64: 9.953 Gbps, corresponding to OC-192.
- STM-256: 39.813 Gbps, corresponding to OC-768.
These rates reflect SDH's role as a digital transport hierarchy. Services are mapped into containers, combined into higher-rate structures, and transported with overhead that supports monitoring, maintenance, and protection.
Virtual Containers And Mapping
SDH uses containers and virtual containers to carry different payload types. A tributary signal is adapted into a container, overhead is added to form a virtual container, and that virtual container is aligned into tributary units or administrative units for multiplexing into an STM frame.
This design lets SDH carry many client signals, including PDH circuits such as E1 and E3, packet services, ATM, and later Ethernet mappings. The network can transport a payload while maintaining path-level overhead and performance monitoring across the service.
Overhead And Operations
SDH frames include overhead bytes that support operations, administration, maintenance, and provisioning. Overhead is commonly thought of in layers, including regenerator section, multiplex section, and path overhead. Those bytes are used for alarms, error monitoring, orderwire, data communication channels, trace messages, pointer handling, and protection coordination.
This is one reason SDH was so valuable to carriers. It did not merely move bits. It gave operators tools to see where failures occurred, whether a path was degraded, and how protection switching behaved.
Protection Switching
SDH networks were built for high availability. Common protection methods include multiplex section protection, subnetwork connection protection, and ring-based designs. In a suitable architecture, traffic can switch to a protection path quickly after a fiber cut, card failure, or other service-affecting event.
Protection switching became one of SDH's defining operational strengths. The familiar carrier expectation of fast restoration, often discussed around 50 milliseconds for specific failure modes, influenced later MPLS fast reroute, Ethernet ring protection, optical restoration, and packet-optical protection designs.
Synchronization
SDH depends on network synchronization. A synchronous transport network requires careful clock distribution, holdover behavior, and timing quality. Timing errors can create slips, pointer activity, jitter, wander, and service degradation. This mattered for voice, mobile backhaul, private lines, and any service that depended on stable timing.
Modern packet networks still face timing problems, especially in mobile transport and industrial systems. PTP, SyncE, and packet timing profiles solve those problems differently, but SDH's timing discipline shaped the carrier mindset.
Ethernet Over SDH
As Ethernet services grew, carriers needed to carry packet traffic over installed SDH networks. Generic Framing Procedure, virtual concatenation, and Link Capacity Adjustment Scheme helped make Ethernet over SDH more efficient and flexible. GFP maps packet-oriented client signals into transport frames. Virtual concatenation lets multiple lower-rate containers behave like one larger logical pipe. LCAS allows capacity to be adjusted dynamically for a virtual concatenation group.
Ethernet over SDH extended the life of SDH networks by letting carriers sell Ethernet services without immediately replacing every transport shelf. It also showed the direction of the market: packet services were becoming dominant, while SDH remained the transport layer underneath.
Where SDH Was Used
SDH appeared across many carrier and enterprise transport environments:
- Long-haul and metro transport: high-capacity fiber routes between central offices, cities, and carrier points of presence.
- Leased lines: managed private circuits for enterprises, governments, financial networks, and service providers.
- Mobile backhaul: TDM and early packet backhaul for cellular networks.
- Voice trunking: circuit transport for public switched telephone networks.
- Broadband aggregation: transport for ATM, DSL, and early packet access networks.
- Broadcast and utility networks: reliable private transport with strong operations and protection requirements.
Why SDH Declined
SDH declined for new growth because network traffic became overwhelmingly packet-based. Ethernet became cheaper and faster. MPLS and IP gave providers flexible VPN and traffic-engineering services. DWDM increased optical capacity. OTN provided a newer digital wrapper for high-capacity optical transport. Packet-optical platforms combined transport, Ethernet, MPLS, OTN, and coherent optics in more efficient ways.
SDH is still present in many networks, but often as legacy transport, circuit emulation, or a service that is gradually being migrated. The challenge is not that SDH stopped working. The challenge is that maintaining SDH expertise, spares, management systems, and service contracts can become expensive compared with Ethernet, OTN, and packet-based alternatives.
Modern Replacements
Different SDH roles now map to different technologies:
- OTN: modern optical transport framing, multiplexing, monitoring, and forward error correction.
- DWDM: multiple high-capacity wavelengths over shared fiber.
- Carrier Ethernet: Ethernet private line, virtual private line, and multipoint Ethernet services.
- MPLS and segment routing: packet transport, VPNs, traffic engineering, and fast reroute.
- Packet-optical systems: combined packet switching, OTN, coherent optics, and service management.
- Circuit emulation: carrying legacy TDM services over packet or OTN when the endpoint cannot yet be replaced.
Legacy Operations
Networks that still carry SDH need disciplined documentation and monitoring:
- Record STM rate, tributary mapping, protection method, path endpoints, and timing source.
- Track regenerator section, multiplex section, and path alarms separately.
- Monitor bit errors, pointer events, loss of signal, loss of frame, and protection switches.
- Identify whether Ethernet services are native Ethernet, Ethernet over SDH, or circuit emulation over another layer.
- Preserve spares, software access, craft terminal knowledge, and management-system credentials while migration is pending.
- Test failover and timing behavior after moving a service from native SDH to OTN, MPLS, or packet transport.
Migration Guidance
A good SDH migration starts with service dependency mapping. Do not replace an STM circuit only by matching bandwidth. Identify the carried service, protection expectations, timing requirements, alarm visibility, demarcation point, customer contract, and operational owner.
For private-line and mobile services, timing may be the critical detail. For Ethernet over SDH, MTU, latency, and bandwidth granularity may matter. For voice and legacy TDM, circuit emulation quality and clock recovery must be tested. For carrier networks, migration should also consider wavelength plans, OTN grooming, router ports, restoration behavior, and how alarms map into new operations tools.
SDH's importance is not only historical. It established a disciplined model for synchronous transport, operations overhead, protection, and service monitoring. In 2026, most new transport growth is in OTN, DWDM, Ethernet, MPLS, segment routing, and packet-optical systems, but SDH remains a reference point for what carrier-grade transport is expected to deliver.
References
- ITU-T G.707/Y.1322: Network node interface for the synchronous digital hierarchy
- ITU-T G.783: SDH equipment functional blocks
- ITU-T G.803: Architecture of SDH-based transport networks
- ITU-T G.709/Y.1331: Interfaces for the Optical Transport Network
- ITU-T G.7041/Y.1303: Generic Framing Procedure
- ITU-T G.7042/Y.1305: Link Capacity Adjustment Scheme
- MEF: Carrier Ethernet service standards