Recent from talks
Nothing was collected or created yet.
Synchronous optical networking
View on Wikipedia
This article needs additional citations for verification. (July 2007) |
Synchronous Optical Networking (SONET) and Synchronous Digital Hierarchy (SDH) are standardized protocols that transfer multiple digital bit streams synchronously over optical fiber using lasers or highly coherent light from light-emitting diodes (LEDs). At low transmission rates, data can also be transferred via an electrical interface. The method was developed to replace the plesiochronous digital hierarchy (PDH) system for transporting large amounts of telephone calls and data traffic over the same fiber without the problems of synchronization.
SONET and SDH, which are essentially the same, were originally designed to transport circuit mode communications, e.g. DS1, DS3, from a variety of different sources. However, they were primarily designed to support real-time, uncompressed, circuit-switched voice encoded in PCM format.[1] The primary difficulty in doing this prior to SONET/SDH was that the synchronization sources of these various circuits were different. This meant that each circuit was actually operating at a slightly different rate and with different phase. SONET/SDH allowed for the simultaneous transport of many different circuits of differing origin within a single framing protocol. SONET/SDH is not a complete communications protocol in itself, but a transport protocol (not a "transport" in the OSI Model sense).
Due to SONET/SDH's essential protocol neutrality and transport-oriented features, SONET/SDH was the choice for transporting the fixed length Asynchronous Transfer Mode (ATM) frames also known as cells. It quickly evolved mapping structures and concatenated payload containers to transport ATM connections. In other words, for ATM (and eventually other protocols such as Ethernet), the internal complex structure previously used to transport circuit-oriented connections was removed and replaced with a large and concatenated frame (such as STS-3c) into which ATM cells, IP packets, or Ethernet frames are placed.

Both SDH and SONET are widely used today: SONET in the United States and Canada, and SDH in the rest of the world. Although the SONET standards were developed before SDH, it is considered a variation of SDH because of SDH's greater worldwide market penetration. SONET is subdivided into four sublayers with some factor such as the path, line, section and physical layer.
The SDH standard was originally defined by the European Telecommunications Standards Institute (ETSI), and is formalised as International Telecommunication Union (ITU) standards G.707,[2] G.783,[3] G.784,[4] and G.803.[5][6] The SONET standard was defined by Telcordia[7] and American National Standards Institute (ANSI) standard T1.105.[6][8] which define the set of transmission formats and transmission rates in the range above 51.840 Mbit/s.
Difference from PDH
[edit]SDH differs from Plesiochronous Digital Hierarchy (PDH) in that the exact rates that are used to transport the data on SONET/SDH are tightly synchronized across the entire network, using atomic clocks. This synchronization system allows entire inter-country networks to operate synchronously, greatly reducing the amount of buffering required between elements in the network. Both SONET and SDH can be used to encapsulate earlier digital transmission standards, such as the PDH standard, or they can be used to directly support either Asynchronous Transfer Mode (ATM) or so-called packet over SONET/SDH (POS) networking. Therefore, it is inaccurate to think of SDH or SONET as communications protocols in and of themselves; they are generic, all-purpose transport containers for moving both voice and data. The basic format of a SONET/SDH signal allows it to carry many different services in its virtual container (VC), because it is bandwidth-flexible.
Protocol overview
[edit]SONET and SDH often use different terms to describe identical features or functions. This can cause confusion and exaggerate their differences. With a few exceptions, SDH can be thought of as a superset of SONET.
SONET is a set of transport containers that allow for delivery of a variety of protocols, including traditional telephony, ATM, Ethernet, and TCP/IP traffic. SONET therefore is not in itself a native communications protocol and should not be confused as being necessarily connection-oriented in the way that term is usually used.
The protocol is a heavily multiplexed structure, with the header interleaved between the data in a complex way. This permits the encapsulated data to have its own frame rate and be able to "float around" relative to the SDH/SONET frame structure and rate. This interleaving permits a very low latency for the encapsulated data. Data passing through equipment can be delayed by at most 32 μs, compared to a frame rate of 125 μs; in many competing protocols, which buffer the data during such transits for at least one frame or packet before sending it on. Extra padding is allowed for the multiplexed data to move within the overall framing, as the data is clocked at a different rate than the frame rate. The protocol is made more complex by the decision to permit this padding at most levels of the multiplexing structure, but it improves all-around performance.
Basic transmission unit
[edit]The basic unit of framing in SDH is a STM-1 (Synchronous Transport Module, level 1), which operates at 155.520 megabits per second (Mbit/s). SONET refers to this basic unit as an STS-3c (Synchronous Transport Signal 3, concatenated). When the STS-3c is carried over OC-3, it is often colloquially referred to as OC-3c, but this is not an official designation within the SONET standard as there is no physical layer (i.e. optical) difference between an STS-3c and 3 STS-1s carried within an OC-3.
SONET offers an additional basic unit of transmission, the STS-1 (Synchronous Transport Signal 1) or OC-1, operating at 51.84 Mbit/s—exactly one third of an STM-1/STS-3c/OC-3c carrier. This speed is dictated by the bandwidth requirements for PCM-encoded telephonic voice signals: at this rate, an STS-1/OC-1 circuit can carry the bandwidth equivalent of a standard DS-3 channel, which can carry 672 64-kbit/s voice channels.[1] In SONET, the STS-3c signal is composed of three multiplexed STS-1 signals; the STS-3c may be carried on an OC-3 signal. Some manufacturers also support the SDH equivalent of the STS-1/OC-1, known as STM-0.
Framing
[edit]In packet-oriented data transmission, such as Ethernet, a packet frame usually consists of a header and a payload. The header is transmitted first, followed by the payload (and possibly a trailer, such as a CRC). In synchronous optical networking, this is modified slightly. The header is termed the overhead, and instead of being transmitted before the payload, is interleaved with it during transmission. Part of the overhead is transmitted, then part of the payload, then the next part of the overhead, then the next part of the payload, until the entire frame has been transmitted.
In the case of an STS-1, the frame is 810 octets in size, while the STM-1/STS-3c frame is 2,430 octets in size. For STS-1, the frame is transmitted as three octets of overhead, followed by 87 octets of payload. This is repeated nine times, until 810 octets have been transmitted, taking 125 μs. In the case of an STS-3c/STM-1, which operates three times faster than an STS-1, nine octets of overhead are transmitted, followed by 261 octets of payload. This is also repeated nine times until 2,430 octets have been transmitted, also taking 125 μs. For both SONET and SDH, this is often represented by displaying the frame graphically: as a block of 90 columns and nine rows for STS-1, and 270 columns and nine rows for STM1/STS-3c. This representation aligns all the overhead columns, so the overhead appears as a contiguous block, as does the payload.
The internal structure of the overhead and payload within the frame differs slightly between SONET and SDH, and different terms are used in the standards to describe these structures. Their standards are extremely similar in implementation, making it easy to interoperate between SDH and SONET at any given bandwidth.
In practice, the terms STS-1 and OC-1 are sometimes used interchangeably, though the OC designation refers to the signal in its optical form. It is therefore incorrect to say that an OC-3 contains 3 OC-1s: an OC-3 can be said to contain 3 STS-1s.
SDH frame
[edit]

The Synchronous Transport Module, level 1 (STM-1) frame is the basic transmission format for SDH—the first level of the synchronous digital hierarchy. The STM-1 frame is transmitted in exactly 125 μs, therefore, there are 8,000 frames per second on a 155.52 Mbit/s OC-3 fiber-optic circuit.[nb 1] The STM-1 frame consists of overhead and pointers plus information payload. The first nine columns of each frame make up the section overhead and administrative unit pointers, and the last 261 columns make up the information payload. The pointers (H1, H2, H3 bytes) identify administrative units (AU) within the information payload. Thus, an OC-3 circuit can carry 150.336 Mbit/s of payload, after accounting for the overhead.[nb 2]
Carried within the information payload, which has its own frame structure of nine rows and 261 columns, are administrative units identified by pointers. Also within the administrative unit are one or more virtual containers (VCs). VCs contain path overhead and VC payload. The first column is for path overhead; it is followed by the payload container, which can itself carry other containers. Administrative units can have any phase alignment within the STM frame, and this alignment is indicated by the pointer in row four.
The section overhead (SOH) of a STM-1 signal is divided into two parts: the regenerator section overhead (RSOH) and the multiplex section overhead (MSOH). The overheads contain information from the transmission system itself, which is used for a wide range of management functions, such as monitoring transmission quality, detecting failures, managing alarms, data communication channels, service channels, etc.
The STM frame is continuous and is transmitted in a serial fashion: byte-by-byte, row-by-row.
Transport overhead
[edit]The transport overhead is used for signaling and measuring transmission error rates, and is composed as follows:
- Section overhead
- Called regenerator section overhead (RSOH) in SDH terminology: 27 octets containing information about the frame structure required by the terminal equipment.
- Line overhead
- Called multiplex section overhead (MSOH) in SDH: 45 octets containing information about error correction and Automatic Protection Switching messages (e.g., alarms and maintenance messages) as may be required within the network. The error correction is included for STM-16 and above.[9]
- Administrative unit (AU) pointer
- Points to the location of the J1 byte in the payload (the first byte in the virtual container).[10]
Path virtual envelope
[edit]Data transmitted from end to end is referred to as path data. It is composed of two components:
- Payload overhead (POH)
- 9 octets used for end-to-end signaling and error measurement.
- Payload
- User data (774 bytes for STM-0/STS-1, or 2,430 octets for STM-1/STS-3c)
For STS-1, the payload is referred to as the synchronous payload envelope (SPE), which in turn has 18 stuffing bytes, leading to the STS-1 payload capacity of 756 bytes.[11]
The STS-1 payload is designed to carry a full PDH DS3 frame. When the DS3 enters a SONET network, path overhead is added, and that SONET network element (NE) is said to be a path generator and terminator. The SONET NE is line terminating if it processes the line overhead. Note that wherever the line or path is terminated, the section is terminated also. SONET regenerators terminate the section, but not the paths or line.
An STS-1 payload can also be subdivided into seven virtual tributary groups (VTGs). Each VTG can then be subdivided into four VT1.5 signals, each of which can carry a PDH DS1 signal. A VTG may instead be subdivided into three VT2 signals, each of which can carry a PDH E1 signal. The SDH equivalent of a VTG is a TUG-2; VT1.5 is equivalent to VC-11, and VT2 is equivalent to VC-12.
Three STS-1 signals may be multiplexed by time-division multiplexing to form the next level of the SONET hierarchy, the OC-3 (STS-3), running at 155.52 Mbit/s. The signal is multiplexed by interleaving the bytes of the three STS-1 frames to form the STS-3 frame, containing 2,430 bytes and transmitted in 125 μs.
Higher-speed circuits are formed by successively aggregating multiples of slower circuits, their speed always being immediately apparent from their designation. For example, four STS-3 or AU4 signals can be aggregated to form a 622.08 Mbit/s signal designated OC-12 or STM-4.
The highest rate commonly deployed is the OC-768 or STM-256 circuit, which operates at rate of just under 38.5 Gbit/s.[12] Where fiber exhaustion is a concern, multiple SONET signals can be transported over multiple wavelengths on a single fiber pair by means of wavelength-division multiplexing, including dense wavelength-division multiplexing (DWDM) and coarse wavelength-division multiplexing (CWDM). DWDM circuits are the basis for all modern submarine communications cable systems and other long-haul circuits.[13]
SONET/SDH and relationship to 10 Gigabit Ethernet
[edit]Another type of high-speed data networking circuit is 10 Gigabit Ethernet (10GbE). The Gigabit Ethernet Alliance created two 10 Gigabit Ethernet variants: a local area variant (LAN PHY) with a line rate of 10.3125 Gbit/s, and a wide area variant (WAN PHY) with the same line rate as OC-192/STM-64 (9,953,280 kbit/s).[14]
The WAN PHY variant encapsulates Ethernet data using a lightweight SDH/SONET frame, so as to be compatible at a low level with equipment designed to carry SDH/SONET signals, whereas the LAN PHY variant encapsulates Ethernet data using 64B/66B line coding.
However, 10 Gigabit Ethernet does not explicitly provide any interoperability at the bitstream level with other SDH/SONET systems. This differs from WDM system transponders, including both coarse and dense wavelength-division multiplexing systems (CWDM and DWDM) that currently support OC-192 SONET signals, which can normally support thin-SONET–framed 10 Gigabit Ethernet.
SONET/SDH data rates
[edit]| SONET Optical Carrier level | SONET frame format | SDH level and frame format | Payload bandwidth[nb 3] (kbit/s) | Line rate (kbit/s) |
|---|---|---|---|---|
| OC-1 | STS-1 | STM-0 | 50,112 | 51,840 |
| OC-3 | STS-3 | STM-1 | 150,336 | 155,520 |
| OC-12 | STS-12 | STM-4 | 601,344 | 622,080 |
| OC-24 | STS-24 | – | 1,202,688 | 1,244,160 |
| OC-48 | STS-48 | STM-16 | 2,405,376 | 2,488,320 |
| OC-192 | STS-192 | STM-64 | 9,621,504 | 9,953,280 |
| OC-768 | STS-768 | STM-256 | 38,486,016 | 39,813,120 |
User throughput must not deduct path overhead from the payload bandwidth, but path-overhead bandwidth is variable based on the types of cross-connects built across the optical system.
Note that the data-rate progression starts at 155 Mbit/s and increases by multiples of four. The only exception is OC-24, which is standardized in ANSI T1.105, but not a SDH standard rate in ITU-T G.707.[2][8] Other rates, such as OC-9, OC-18, OC-36, OC-96, and OC-1536, are defined but not commonly deployed; most are considered orphaned rates.[1][15][16]
Physical layer
[edit]The physical layer refers to the first layer in the OSI networking model.[17] The ATM and SDH layers are the regenerator section level, digital line level, transmission path level, virtual path level, and virtual channel level.[18] The physical layer is modeled on three major entities: transmission path, digital line and the regenerator section.[19] The regenerator section refers to the section and photonic layers. The photonic layer is the lowest SONET layer and it is responsible for transmitting the bits to the physical medium. The section layer is responsible for generating the proper STS-N frames which are to be transmitted across the physical medium. It deals with issues such as proper framing, error monitoring, section maintenance, and orderwire.
The line layer ensures reliable transport of the payload and overhead generated by the path layer. It provides synchronization and multiplexing for multiple paths. It modifies overhead bits relating to quality control. The path layer is SONET's highest level layer. It takes data to be transmitted and transforms them into signals required by the line layer, and adds or modifies the path overhead bits for performance monitoring and protection switching.[20][21]
SONET/SDH network management protocols
[edit]This section may be too technical for most readers to understand. (November 2010) |
Overall functionality
[edit]Network management systems are used to configure and monitor SDH and SONET equipment either locally or remotely.
The systems consist of three essential parts, covered later in more detail:
- Software running on a network management system terminal, e.g. workstation, dumb terminal or laptop housed in an exchange/central office.
- Transport of network management data between the network management system terminal and the SONET/SDH equipment, e.g. using TL1/Q3 protocols.
- Transport of network management data between SDH/SONET equipment using dedicated embedded data communication channels (DCCs) within the section and line overhead.
The main functions of network management thereby include:
- Network and network-element provisioning
- In order to allocate bandwidth throughout a network, each network element must be configured. Although this can be done locally, through a craft interface, it is normally done through a network management system (sitting at a higher layer) that, in turn, operates through the SONET/SDH network management network.
- Software upgrade
- Network-element software upgrades are done mostly through the SONET/SDH management network in modern equipment.
- Performance management
- Network elements have a very large set of standards for performance management. The performance-management criteria allow not only monitoring the health of individual network elements, but isolating and identifying most network defects or outages. Higher-layer network monitoring and management software allows the proper filtering and troubleshooting of network-wide performance management, so that defects and outages can be quickly identified and resolved.
Consider the three parts defined above:
Network management system terminal
[edit]- Local Craft interface
- Local "craftspersons" (telephone network engineers) can access a SDH/SONET network element on a "craft port" and issue commands through a dumb terminal or terminal emulation program running on a laptop. This interface can also be attached to a console server, allowing for remote out-of-band management and logging.
- Network management system (sitting at a higher layer)
This will often consist of software running on a Workstation covering a number of SDH/SONET network elements
TL1/Q3 Protocols
[edit]- TL1
SONET equipment is often managed with the TL1 protocol. TL1 is a telecom language for managing and reconfiguring SONET network elements. The command language used by a SONET network element, such as TL1, must be carried by other management protocols, such as SNMP, CORBA, or XML.
- Q3
SDH has been mainly managed using the Q3 interface protocol suite defined in ITU recommendations Q.811 and Q.812. With the convergence of SONET and SDH on switching matrix and network elements architecture, newer implementations have also offered TL1.[22]
Most SONET NEs have a limited number of management interfaces defined:
- TL1 Electrical interface
- The electrical interface, often a 50-ohm coaxial cable, sends SONET TL1 commands from a local management network physically housed in the central office where the SONET network element is located. This is for local management of that network element and, possibly, remote management of other SONET network elements.
Dedicated embedded data communication channels (DCCs)
[edit]- SONET and SDH have dedicated data communication channels (DCCs) within the section and line overhead for management traffic. Generally, section overhead (regenerator section in SDH) is used. According to ITU-T G.7712, there are three modes used for management:[23]
To handle all of the possible management channels and signals, most modern network elements contain a router for the network commands and underlying (data) protocols.
Equipment
[edit]With advances in SONET and SDH chipsets, the traditional categories of network elements are no longer distinct. Nevertheless, as network architectures have remained relatively constant, even newer equipment (including multi-service provisioning platforms) can be examined in light of the architectures they will support. Thus, there is value in viewing new, as well as traditional, equipment in terms of the older categories.
Regenerator
[edit]Traditional regenerators terminate the section overhead, but not the line or path. Regenerators extend long-haul routes in a way similar to most regenerators, by converting an optical signal that has already traveled a long distance into electrical format and then retransmitting a regenerated high-power signal.
Since the late 1990s, regenerators have been largely replaced by optical amplifiers. Also, some of the functionality of regenerators has been absorbed by the transponders of wavelength-division multiplexing systems.
STS multiplexer and demultiplexer
[edit]STS multiplexer and demultiplexer provide the interface between an electrical tributary network and the optical network.
Add-drop multiplexer
[edit]Add-drop multiplexers (ADMs) are the most common type of network elements. Traditional ADMs were designed to support one of the network architectures, though new generation systems can often support several architectures, sometimes simultaneously. ADMs traditionally have a high-speed side (where the full line rate signal is supported), and a low-speed side, which can consist of electrical as well as optical interfaces. The low-speed side takes in low-speed signals, which are multiplexed by the network element and sent out from the high-speed side, or vice versa.
Digital cross connect system
[edit]Recent digital cross connect systems (DCSs or DXCs) support numerous high-speed signals, and allow for cross-connection of DS1s, DS3s and even STS-3s/12c and so on, from any input to any output. Advanced DCSs can support numerous subtending rings simultaneously.
Network architectures
[edit]SONET and SDH have a limited number of architectures defined. These architectures allow for efficient bandwidth usage as well as protection, i.e. the ability to transmit traffic even when part of the network has failed, and are fundamental to the worldwide deployment of SONET and SDH for moving digital traffic. Every SDH/SONET connection on the optical physical layer uses two optical fibers, regardless of the transmission speed.
Linear Automatic Protection Switching
[edit]Linear Automatic Protection Switching (APS), also known as 1+1, involves four fibers: two working fibers (one in each direction), and two protection fibers. Switching is based on the line state, and may be unidirectional (with each direction switching independently), or bidirectional (where the network elements at each end negotiate so that both directions are generally carried on the same pair of fibers).
Unidirectional path-switched ring
[edit]In unidirectional path-switched rings (UPSRs), two redundant (path-level) copies of protected traffic are sent in either direction around a ring. A selector at the egress node determines which copy has the highest quality, and uses that copy, thus coping if one copy deteriorates due to a broken fiber or other failure.
UPSRs tend to sit nearer to the edge of a network, and as such are sometimes called collector rings. Because the same data is sent around the ring in both directions, the total capacity of a UPSR is equal to the line rate N of the OC-N ring.[24] For example, in an OC-3 ring with 3 STS-1s used to transport 3 DS-3s from ingress node A to the egress node D, 100 percent of the ring bandwidth (N=3) would be consumed by nodes A and D. Any other nodes on the ring could only act as pass-through nodes. The SDH equivalent of UPSR is subnetwork connection protection (SNCP); SNCP does not impose a ring topology, but may also be used in mesh topologies.
Bidirectional line-switched ring
[edit]Bidirectional line-switched ring (BLSR) comes in two varieties: two-fiber BLSR and four-fiber BLSR. BLSRs switch at the line layer. Unlike UPSR, BLSR does not send redundant copies from ingress to egress. Rather, the ring nodes adjacent to the failure reroute the traffic "the long way" around the ring on the protection fibers. BLSRs trade cost and complexity for bandwidth efficiency, as well as the ability to support "extra traffic" that can be pre-empted when a protection switching event occurs. In four-fiber ring, either single node failures, or multiple line failures can be supported, since a failure or maintenance action on one line causes the protection fiber connecting two nodes to be used rather than looping it around the ring.
BLSRs can operate within a metropolitan region or, often, will move traffic between municipalities. Because a BLSR does not send redundant copies from ingress to egress, the total bandwidth that a BLSR can support is not limited to the line rate N of the OC-N ring, and can actually be larger than N depending upon the traffic pattern on the ring.[25]
In the best case, all traffic is between adjacent nodes. The worst case is when all traffic on the ring egresses from a single node, i.e., the BLSR is serving as a collector ring. In this case, the bandwidth that the ring can support is equal to the line rate N of the OC-N ring. This is why BLSRs are seldom, if ever, deployed in collector rings, but often deployed in inter-office rings. The SDH equivalent of BLSR is called Multiplex Section-Shared Protection Ring (MS-SPRING).
Synchronization
[edit]Clock sources used for synchronization in telecommunications networks are rated by quality, commonly called a stratum.[26] Typically, a network element uses the highest quality stratum available to it, which can be determined by monitoring the synchronization status messages (SSM) of selected clock sources.
Synchronization sources available to a network element are:[citation needed]
- Local external timing
- This is generated by an atomic cesium clock or a satellite-derived clock by a device in the same central office as the network element. The interface is often a DS1, with sync-status messages supplied by the clock and placed into the DS1 overhead.
- Line-derived timing
- A network element can choose (or be configured) to derive its timing from the line-level, by monitoring the S1 sync-status bytes to ensure quality.
- Holdover
- As a last resort, in the absence of higher quality timing, a network element can go into a holdover mode until higher-quality external timing becomes available again. In this mode, the network element uses its own timing circuits as a reference.
Timing loops
[edit]A timing loop occurs when network elements in a network are each deriving their timing from other network elements, without any of them being a "master" timing source. This network loop will eventually see its own timing "float away" from any external networks, causing mysterious bit errors—and ultimately, in the worst cases, massive loss of traffic. The source of these kinds of errors can be hard to diagnose.[27] In general, a network that has been properly configured should never find itself in a timing loop, but some classes of silent failures could nevertheless cause this issue.
Next-generation SONET/SDH
[edit]SONET/SDH development was originally driven by the need to transport multiple PDH signals—like DS1, E1, DS3, and E3—along with other groups of multiplexed 64 kbit/s pulse-code modulated voice traffic. The ability to transport ATM traffic was another early application. In order to support large ATM bandwidths, concatenation was developed, whereby smaller multiplexing containers (e.g., STS-1) are inversely multiplexed to build up a larger container (e.g., STS-3c) to support large data-oriented pipes.
One problem with traditional concatenation, however, is inflexibility. Depending on the data and voice traffic mix that must be carried, there can be a large amount of unused bandwidth left over, due to the fixed sizes of concatenated containers. For example, fitting a 100 Mbit/s Fast Ethernet connection inside a 155 Mbit/s STS-3c container leads to considerable waste. More important is the need for all intermediate network elements to support newly introduced concatenation sizes. This problem was overcome with the introduction of Virtual Concatenation.
Virtual concatenation (VCAT) allows for a more arbitrary assembly of lower-order multiplexing containers, building larger containers of fairly arbitrary size (e.g., 100 Mbit/s) without the need for intermediate network elements to support this particular form of concatenation. Virtual concatenation leverages the X.86 or Generic Framing Procedure (GFP) protocols in order to map payloads of arbitrary bandwidth into the virtually concatenated container.
The Link Capacity Adjustment Scheme (LCAS) allows for dynamically changing the bandwidth via dynamic virtual concatenation, multiplexing containers based on the short-term bandwidth needs in the network.
The set of next-generation SONET/SDH protocols that enable Ethernet transport is referred to as Ethernet over SONET/SDH (EoS).
End of life and retirement
[edit]SONET/SDH was used by internet access providers for large customers, and is no longer competitive in the supply of private circuits. Development has stagnated for the last decade (2020) and both suppliers of equipment and operators of SONET/SDH networks are migrating to other technologies such as OTN and wide area Ethernet.
British Telecom has recently (March 2020) closed down their KiloStream and Mega Stream products which were the last large scale uses of the BT SDH. BT has also ceased new connections to their SDH network which indicates withdrawal of services soon.[28][29][30]
See also
[edit]Notes
[edit]References
[edit]- ^ a b c Horak, Ray (2007). Telecommunications and Data Communications Handbook. Wiley-Interscience. p. 476. ISBN 978-0-470-04141-3.
- ^ a b ITU-T Rec. G.707/Y.1322, Network node interface for the synchronous digital hierarchy (SDH)., Geneva: International Telecommunication Union, January 2007, retrieved 3 November 2010
- ^ ITU-T Rec. G.783, Characteristics of synchronous digital hierarchy (SDH) equipment functional blocks., Geneva: International Telecommunication Union, March 2006, retrieved 3 November 2010
- ^ ITU-T Rec. G.784, Management aspects of the synchronous digital hierarchy (SDH) transport network element., Geneva: International Telecommunication Union, March 2008, retrieved 3 November 2010
- ^ ITU-T Rec. G.803, Architecture of transport networks based on the synchronous digital hierarchy (SDH)., Geneva: International Telecommunication Union, March 2000, retrieved 3 November 2010
- ^ a b "SONET/SDH Technical Summary". TechFest. TechFest.com. 2002. Archived from the original on 27 January 1999. Retrieved 13 November 2010.
- ^ Telcordia GR-253-CORE, Synchronous Optical Network (SONET) Transport Systems: Common Generic Criteria (October 2009). Issue 5.
- ^ a b ANSI T1.105.07-1996 (R2005), Synchronous Optical Network (SONET) – Sub-STS-1 Interface Rates and Formats Specification., New York: American National Standards Institute, 1996, archived from the original on 6 March 2012
- ^ "Forward error correction in optical networks" (PDF). Conexant Systems, Inc. Archived from the original (PDF) on 10 December 2014. Retrieved 10 December 2014.
- ^ "Synchronous Digital Hierarchy (SDH) Graphical Overview". Cisco. San Jose, California: Cisco indiA Systems. 1 October 2006. Retrieved 14 November 2010.
- ^ "Synchronous Optical Network (SONET)". Web ProForums. International Engineering Consortium. 2007. Archived from the original on 7 April 2008. Retrieved 21 April 2007.
- ^ "OC 768 Internet Connection". GCG. Global Communications Group. 2009. Archived from the original on 20 September 2010. Retrieved 14 November 2010.
- ^ DWDM Network Technology
- ^ IEEE Std 802.3bv-2017
- ^ Tozer, Edwin Paul J. (2004). "1.8.11 Synchronous Digital Hierarchy (SDH)". Broadcast Engineer's Reference Book. Focal Press. p. 97. ISBN 978-0-240-51908-1.
- ^ Elbert, Bruce R. (2008). Introduction to Satellite Communication. Artech House space applications series (3rd ed.). Artech House. p. 73. ISBN 978-1-59693-210-4.
- ^ Tyson, Jeff. "How OSI Works" HowStuffWorks.com. <http://computer.howstuffworks.com/osi.htm> 2 December 2011.
- ^ Black, Uyless D. Emerging Communications Technologies. Englewood Cliffs, NJ: PTR Prentice Hall, 1994. 298-99. Print.
- ^ Hassan, Rosilah, James Irvine, and Ian Glover. "Design and Analysis of Virtual Bus Transport Using Synchronous Digital Hierarchy/Synchronous Optical Networking." Journal of Computer Science 4.12 (2008): 1003-011. Print.
- ^ "SONET: How Does SONET Work?" Capybara.Org. Web. 2 December 2011. <[1]>.
- ^ "Introduction to SONET." Networking - Computer and Wireless Networking Basics - Home Networks Tutorials. Web. 2 December 2011. <http://compnetworking.about.com/od/hardwarenetworkgear/l/aa092800a.htm Archived 20 June 2016 at the Wayback Machine>.
- ^ "Framework for the Integrated Management of Hybrid Circuit/Packet Networks". www.ietf.org. 2003. Retrieved 15 June 2023.
- ^ ITU-T Rec. G.7712/Y.1703, Architecture and Specification of Data Communication Network., Geneva: International Telecommunication Union, 30 March 2007
- ^ "Understanding SONET UPSRs". SONET Homepage. Retrieved 14 November 2010.
- ^ "Understanding SONET BLSRs". SONET Homepage. Retrieved 14 November 2010.
- ^ Matthew Gast (August 2001). "Chapter 5: Timing, Clocking, and Synchronization in the T-carrier System". T1: A Survival Guide. "O'Reilly Media, Inc.". ISBN 0-596-00127-4. Archived from the original on 18 August 2001. Retrieved 28 September 2012.
- ^ "Why is a timing loop so bad, and why is it so difficult to fix?". Optical Timing: Frequently Asked Questions. Cisco Systems. 2 December 2005. Retrieved 28 September 2012.
- ^ KiloStream Retirement
- ^ SDH to OTN Migration
- ^ "MegaStream Withdrawal". Archived from the original on 5 July 2020. Retrieved 4 July 2020.
External links
[edit]- Understanding SONET/SDH
- The Queen's University of Belfast SDH/SONET Primer Archived 20 September 2005 at the Wayback Machine
- SDH Pocket Handbook from Acterna/JDSU
- SONET Pocket Handbook from Acterna/JDSU
- The Sonet Homepage
- SONET Interoperability Form (SIF)
- Network Connection Speeds Reference
- Next-generation SDH: the future looks bright[dead link]
- The Future of SONET/SDH (pdf)
- Telcordia GR-253-CORE, SONET Transport Systems: Common Generic Criteria
- Telcordia GR-499-CORE, Transport Systems Generic Requirements (TSGR): Common Requirements
- ANSI T1.105: SONET - Basic Description including Multiplex Structure, Rates and Formats
- ANSI T1.119/ATIS PP 0900119.01.2006: SONET - Operations, Administration, Maintenance, and Provisioning (OAM&P) - Communications
- ITU-T recommendation G.707: Network Node Interface for the Synchronous Digital Hierarchy (SDH)
- ITU-T recommendation G.783: Characteristics of synchronous digital hierarchy (SDH) equipment functional blocks
- ITU-T recommendation G.803: Architecture of Transport Networks Based on the Synchronous Digital Hierarchy (SDH)
Synchronous optical networking
View on GrokipediaIntroduction and History
Development and Standardization
Synchronous optical networking originated in the mid-1980s as part of efforts by Bell Communications Research (Bellcore, now Telcordia Technologies) to upgrade T1 carrier systems in North America following the 1984 breakup of the Bell System. Bellcore proposed the SONET framework in February 1985 to the ANSI T1X1 subcommittee to standardize optical interfaces for multi-vendor interoperability in fiber optic networks, addressing the limitations of plesiochronous digital hierarchy (PDH) systems.[4][5] Standardization efforts advanced rapidly, with the American National Standards Institute (ANSI) approving T1.105 in August 1988, which defined SONET's optical carrier rates and frame formats for North American digital hierarchies. Concurrently, the International Telecommunication Union - Telecommunication Standardization Sector (ITU-T), then known as CCITT, initiated work in 1986 and published Recommendation G.707 in November 1988, establishing the Synchronous Digital Hierarchy (SDH) as a global counterpart with aligned bit rates but adapted for international hierarchies like E1. Bellcore's generic requirements, documented in GR-253, further refined SONET specifications, influencing equipment design.[4][6] Key players included Bellcore as the primary developer for SONET, the ANSI T1 committee for North American standards, and ITU-T for SDH's international scope, with contributions from carriers like AT&T and MCI to ensure compatibility. While SONET focused on North American framing (e.g., STS-1 at 51.84 Mbit/s), SDH used STM-1 at the same rate but with global adaptations, leading to defined mappings for interoperability.[7][4] The first SONET field trials occurred in 1989, followed by successful multi-vendor midfiber meets in 1990, paving the way for initial commercial deployments in the early 1990s within North American backbone networks. By the mid-1990s, both SONET and SDH saw widespread adoption globally for high-capacity transport. Standardization efforts culminated in convergence by the early 2000s, with ITU-T recommendations incorporating SONET mappings into SDH frameworks, enabling seamless international operations.[4][7]Purpose and Key Features
Synchronous optical networking (SONET), along with its international counterpart synchronous digital hierarchy (SDH), was developed to provide a standardized framework for the reliable, synchronous transport of multiple digital signals over optical fiber at high speeds.[2] This technology enables the multiplexing and transmission of voice, data, and video services in telecommunications networks, supporting rates from the base Synchronous Transport Signal level 1 (STS-1) at 51.84 Mbps up to higher levels such as OC-768 at approximately 40 Gbps historically.[1] By synchronizing all network elements to a common clock traceable to a primary reference source with accuracy of ±1 in 10^11, SONET/SDH ensures precise timing across the transport path, facilitating efficient signal integration without the delays associated with asynchronous methods.[8] Key features of SONET/SDH include synchronous multiplexing, which uses byte-interleaved techniques to combine lower-rate signals into higher-rate frames, allowing scalable bandwidth allocation through basic building blocks like STS-1 for SONET and virtual container 3 (VC-3) for SDH.[1] Embedded overhead bytes—divided into section, line, and path categories—provide comprehensive network management capabilities, including operations, administration, maintenance, and provisioning (OAM&P), error monitoring, and fault detection.[2] Additionally, automatic protection switching (APS) enables rapid fault restoration, typically within 50 milliseconds, using dedicated signaling bytes like K1 and K2 to switch traffic to backup paths in ring or linear topologies.[8] This architecture supports flexible configurations, such as concatenation for contiguous bandwidth (e.g., STS-3c), enhancing adaptability to diverse traffic requirements.[1] Compared to plesiochronous systems, SONET/SDH offers advantages such as reduced jitter and wander through its fully synchronous design and pointer mechanisms, which adjust for phase differences without bit stuffing.[8] This results in more stable signal delivery and simplifies the add/drop multiplexing of individual channels at intermediate nodes, improving overall network efficiency and multivendor interoperability.[1] These benefits make SONET/SDH particularly suited for backbone networks and telecom carrier interconnects, where high-capacity, resilient transport is essential for long-haul and metropolitan applications.[2]Comparison to Predecessor Technologies
Differences from PDH
Synchronous optical networking, or SONET/SDH, represents a significant advancement over the plesiochronous digital hierarchy (PDH), which suffered from inherent limitations due to its asynchronous nature. In PDH systems, each multiplexing stage operates with clocks that are nominally at the same rate but allow slight variations (plesiochronous operation), leading to timing discrepancies that require bit stuffing—also known as positive or negative justification—to pad or align data streams for synchronization. This bit stuffing complicates signal processing and reduces efficiency, as extra bits are inserted without carrying useful information. Additionally, PDH employs fixed hierarchies, such as the North American DS1 (1.544 Mbps) and DS3 (44.736 Mbps) levels or the European E1 (2.048 Mbps) and E3 (34.368 Mbps) levels, defined by ITU-T Recommendation G.702, which limit flexibility in combining different rates. Multiplexing and demultiplexing in PDH are cumbersome, often requiring multiple stages where accessing a lower-rate tributary necessitates fully disassembling the entire high-rate stream, increasing latency and equipment complexity.[9] SONET/SDH addresses these issues through fully synchronous operation, where all network elements share a common clock reference, enabling byte-oriented framing without the need for bit stuffing.[10] Instead of bit-level adjustments, SONET/SDH uses pointer-based justification in its transport overhead, allowing flexible mapping of payloads into virtual containers that accommodate minor timing differences between client signals and the synchronous frame rate via pointer adjustments.[9] This results in more efficient bandwidth utilization and simpler multiplexing, as signals are organized into a unified hierarchy starting from STS-1 (51.84 Mbps) in SONET and STM-1 (155.52 Mbps) in SDH, with STM-1 equivalent to three STS-1 signals, and scaling synchronously without justification overhead.[10] The byte-synchronous structure, with fixed frames of 9 rows by 90 columns for STS-1 (scaling to 90N columns for STS-N), repeating every 125 μs, separates overhead from payload clearly, facilitating robust network management and performance monitoring across all levels, unlike the limited capabilities in PDH above 8 Mbps.[9] A key operational contrast is in add/drop functionality: while PDH requires demultiplexing the complete aggregate stream to extract or insert individual channels, SONET/SDH employs virtual tributaries (VTs in SONET or virtual containers in SDH) that enable direct access and manipulation of lower-rate signals within the higher-rate frame using add/drop multiplexers (ADMs), without disassembling the entire signal. This pointer-driven approach minimizes processing delays and supports dynamic reconfiguration, enhancing efficiency in ring or mesh topologies. The migration from PDH to SONET/SDH was driven by the explosive growth in telecommunications demand during the 1980s, fueled by the telecom boom and the advent of optical fiber technologies, which exposed PDH's scalability limits—capped around 140 Mbps—and lack of interoperability among carriers. Standardization efforts by ANSI (for SONET in 1988) and ITU-T (for SDH in 1989–1990) responded to these needs, providing a flexible, high-capacity framework that supported the rising bandwidth requirements for voice, data, and emerging services.[10]Transition from Asynchronous Systems
Asynchronous transmission systems, including the Plesiochronous Digital Hierarchy (PDH), Asynchronous Transfer Mode (ATM), and Frame Relay, dominated telecommunications infrastructure in the latter half of the 20th century but suffered from inherent limitations that hindered scalability and efficiency. PDH networks, which aggregated lower-speed signals like T1 or E1 lines through hierarchical bit interleaving, required constant rate justification via bit stuffing to compensate for slight clock differences between plesiochronous elements, complicating synchronization across long-haul links and increasing the risk of timing slips or errors.[7][11] ATM and Frame Relay, as cell- and frame-based protocols respectively, operated with variable bit rates and independent timing, exacerbating synchronization challenges in extended networks where accumulating jitter could degrade performance for time-sensitive applications like voice and video. These systems' asynchronous nature made them ill-suited for the emerging demands of integrated broadband services, as multiplexing and demultiplexing often necessitated expensive, multi-stage equipment to access individual channels.[7] Synchronous Optical Networking (SONET) and Synchronous Digital Hierarchy (SDH) addressed these shortcomings by introducing a unified synchronous transport framework, serving as a critical bridge in the evolution toward modern telecom architectures. Standardized by ANSI in 1988 for SONET and by ITU-T in 1989 for SDH, these technologies enabled seamless integration of voice, data, and video through byte-synchronous multiplexing and pointer-based payload mapping, which eliminated bit stuffing and allowed direct access to low-rate tributaries without full demultiplexing.[12][13] This synchronous approach provided transparent bit-rate transport for asynchronous payloads, such as early IP packets over ATM or Frame Relay, supporting the explosive growth of data traffic in the 1990s while maintaining precise end-to-end timing for circuit-based services.[11] By standardizing optical interfaces and overhead for network management, SONET/SDH reduced operational complexity and costs compared to PDH's ad hoc hierarchies, fostering vendor interoperability and rapid fault protection in milliseconds.[7] In the 1990s, widespread deployments exemplified the shift, with telecom carriers replacing PDH-based inter-office and long-haul trunks to meet surging bandwidth needs from digital services. For instance, post-1984 divestiture of AT&T, U.S. regional Bell operating companies accelerated SONET rollouts to multiplex multiple T1 lines efficiently into OC-3 (155 Mbps) rings, achieving cost savings through simplified add-drop operations and enabling backbone capacities up to OC-48 (2.5 Gbps).[14] In Europe, SDH deployments by operators like BT and Deutsche Telekom similarly supplanted E1 hierarchies in metropolitan and national networks, driven by ITU-T standards that facilitated global compatibility.[12] Coexistence strategies during this period involved embedding PDH signals as virtual tributaries within SONET/SDH frames, allowing hybrid networks where legacy equipment remained operational while new fiber spans were provisioned, thus minimizing service disruptions.[11] These migrations, often completed in phases over 5-10 years, transformed core networks into scalable platforms that underpinned the internet's expansion. The transition, however, presented significant challenges, particularly the high costs associated with deploying optical fiber infrastructure and adapting operational practices. Laying fiber optic cables required substantial capital outlays for excavation, splicing, and terminal equipment, with estimates in the early 1990s placing inter-city link costs at millions of dollars per mile due to terrain and regulatory hurdles.[15] Moreover, shifting to synchronous operations demanded extensive retraining for technicians and engineers, as PDH's plesiochronous model gave way to SDH's rigid clock synchronization and overhead monitoring, increasing the learning curve for fault isolation and provisioning. Despite these barriers, the long-term efficiencies in bandwidth utilization and maintenance justified the investments, solidifying SONET/SDH as the foundation for high-capacity optical transport.[7]Protocol Fundamentals
Overview of SONET/SDH Protocol
Synchronous Optical Networking (SONET) and Synchronous Digital Hierarchy (SDH) form a layered protocol architecture within the physical layer of the OSI model, comprising four primary layers: photonic (or physical), section, line, and path. The photonic layer handles the transmission of optical signals over fiber optic media, including modulation, scrambling, and basic signal regeneration without interpreting the frame content. The section layer manages short spans between adjacent network elements, such as regenerators, by formatting frames, performing electrical-to-optical conversion, and providing basic error monitoring via section overhead. The line layer oversees multiplexing of multiple Synchronous Transport Signals (STS) or Administrative Units (AU) into higher-rate signals, synchronizing them, and adding line overhead for functions like error performance monitoring and automatic protection switching between line-terminating equipment. The path layer ensures end-to-end transport of client payloads from source to destination, mapping signals into the synchronous payload envelope (SPE), and incorporating path overhead for end-to-end signaling, pointer adjustments, and error monitoring between path-terminating elements. These layers collectively enable reliable, synchronous transport across optical networks, with SONET defined by ANSI standards such as T1.105 and SDH by ITU-T Recommendation G.707.[16][2][17] The mapping process integrates asynchronous client signals, such as DS3 or ATM cells, into SONET/SDH frames for transport. Lower-rate signals are first adapted into virtual tributaries (VT) or directly into the STS-1 SPE for higher rates like DS3, where the payload is byte-synchronously mapped to preserve timing while allowing pointer-based justification for rate differences. For ATM, cells are packed into the SPE with idle bytes or pointer adjustments to align with the synchronous frame structure, ensuring efficient bandwidth utilization without requiring client signal synchronization to the network clock. This adaptation occurs at the path layer, transforming diverse tributaries into a uniform synchronous stream suitable for multiplexing at higher layers.[18][1] Concatenation in SONET/SDH allows aggregation of multiple basic units, such as STS-1 or STM-1, to support higher-bandwidth payloads. Contiguous concatenation, denoted by a "c" suffix (e.g., STS-3c), treats the combined payload as a single undivided block, allocating the full envelope capacity without interleaving, which simplifies transport for services like uncompressed video or high-rate data streams. In contrast, interleaved or channelized concatenation multiplexes individual STS-1 signals separately, enabling independent routing and lower-rate tributaries within the aggregate frame, though it requires more complex demultiplexing at the receiver. This flexibility supports both broadband and legacy circuit applications.[19] Error handling in SONET/SDH relies primarily on Bit Interleaved Parity-8 (BIP-8) for detection across layers, with optional forward error correction (FEC) enhancements. BIP-8 computes an even parity over all bits in a monitored block (e.g., the entire STS frame for section layer via byte B1, SPE for line via B2, or path via B3), allowing receivers to count and report bit errors through remote error indication (REI) signals for performance monitoring and threshold-based alarms. Section and line layers use BIP-8 for span-specific integrity, while path layer applies it end-to-end for payload validation. FEC, though not core to basic SONET/SDH, can be provisioned in extended overhead for higher-rate links to correct single-bit errors, improving transmission reliability over long distances as per optional ITU-T G.709 integration.[20][21]Basic Transmission Units and Hierarchy
Synchronous optical networking (SONET) defines its fundamental transmission unit as the Synchronous Transport Signal level 1 (STS-1), which operates at a bit rate of 51.84 Mbps and serves as the basic building block for higher-rate signals.[1] This unit is specified in the ANSI T1.105 standard, which establishes the electrical format for SONET interfaces.[22] The STS-1 frame consists of 810 bytes transmitted every 125 microseconds, enabling synchronous transport of payloads while accommodating timing variations through pointer mechanisms.[2] The SONET hierarchy builds upon the STS-1 by multiplexing multiple STS-1 signals to form higher-level Synchronous Transport Signals, denoted as STS-N where N represents the number of interleaved STS-1 units. Common levels include STS-3 (three STS-1s), STS-12 (12 STS-1s), STS-24 (24 STS-1s), STS-48 (48 STS-1s), and STS-192 (192 STS-1s), all achieved through byte-synchronous interleaving.[1] In this multiplexing process, bytes from each constituent STS-1 are sequentially interleaved to maintain synchronization and simplify demultiplexing at the receiver.[3] The Synchronous Digital Hierarchy (SDH), the international counterpart to SONET, employs a parallel structure with the Synchronous Transport Module (STM-N) as its basic units, where STM-1 corresponds to the capacity of three STS-1s at 155.52 Mbps. To accommodate lower-rate tributaries within the SONET/SDH hierarchy, virtual containers (VCs) and virtual tributaries (VTs) are used for mapping asynchronous or lower-speed signals into the synchronous frame. In SONET, the VT1.5 structure maps a DS1 signal (1.544 Mbps) into a 27-byte by 9-row envelope within the STS-1 Synchronous Payload Envelope (SPE), allowing up to 24 VT1.5s or four VT2s (for DS2) per STS-1.[23] SDH equivalents include VC-3 for mapping E3 or DS3 rates and VC-4 for higher capacities within STM-1, as defined in ITU-T Recommendation G.707, which specifies the multiplexing of these containers into administrative units (AUs) for transport. These VCs ensure flexible accommodation of plesiochronous digital hierarchy (PDH) signals without requiring bit stuffing, unlike predecessor technologies.[3] Dynamic alignment of payloads within the frame is facilitated by payload pointers, which allow the SPE to float relative to the transport overhead to compensate for clock differences. In SONET, bytes H1 and H2 form the pointer word in the line overhead, indicating the offset (in bytes) from the pointer to the J1 byte, the first byte of the SPE path overhead.[1] Byte H3 supports negative pointer justification by carrying payload data during frequency downshifts, while the J1 byte enables path trace identification for maintenance.[2] In SDH, equivalent pointers (H1, H2, H3) are used within the administrative unit to align VC-3 or VC-4 payloads to the STM-N frame, ensuring robust synchronization across network elements.Frame Structure and Overhead
Framing Process
The framing process in Synchronous Optical Networking (SONET) and its international counterpart, Synchronous Digital Hierarchy (SDH), entails the systematic construction of transport frames to encapsulate client signals within a synchronous structure. At the core of this process is the assembly of the basic STS-1 frame in SONET (equivalent to the STM-1 in SDH), which comprises 90 columns of 9 bytes each, yielding 810 bytes per frame. These frames are generated and transmitted at precise intervals of 125 microseconds to maintain the synchronous timing essential for multiplexing higher-order signals. This structure ensures byte-oriented alignment across the network, facilitating efficient add-drop and cross-connection operations at intermediate nodes.[24] Payload mapping follows frame assembly, adapting diverse client signals into the Synchronous Payload Envelope (SPE) while accommodating rate mismatches between the client and the transport layer. For asynchronous clients, such as plesiochronous digital hierarchy (PDH) signals like DS1 or DS3, the mapping procedure inserts fixed and stuffing bytes to justify the lower-speed data into the fixed-rate SPE, preventing buffer overflows or underflows during transport. In contrast, for synchronous clients with minor frequency deviations from the network clock, pointer mechanisms enable dynamic adjustments by inserting or removing justification bytes, allowing the payload start position to shift within the frame envelope to track these differences without disrupting continuity. These techniques ensure robust signal integrity across varying clock domains.[24] To mitigate direct current (DC) wander and provide sufficient transitions for clock recovery at the receiver, the fully assembled frame—excluding designated unscrambled bytes—is subjected to bit-oriented scrambling. This employs a frame-synchronous scrambler governed by the polynomial , with an initial seed value of 1111111, applied across the payload and the majority of the overhead to produce a pseudo-random bit sequence. Scrambling occurs after payload insertion and pointer processing but before serialization, enhancing transmission reliability over optical media. At the receiving end, demultiplexing commences with frame alignment, achieved by pattern matching on the unscrambled framing bytes A1 and A2, which delineate the 810-byte boundary and enable byte synchronization for subsequent overhead extraction and payload recovery.[24][25]SDH/SONET Frame Composition
The Synchronous Optical Networking (SONET) frame, specifically the basic Synchronous Transport Signal level 1 (STS-1), consists of a rectangular structure measuring 90 columns by 9 rows, totaling 810 bytes transmitted every 125 microseconds at a bit rate of 51.84 Mbps.[26] This frame is divided into two primary sections: the transport overhead occupying the first three columns (27 bytes across the 9 rows) and the Synchronous Payload Envelope (SPE) encompassing the remaining 87 columns (783 bytes).[26] The transport overhead includes section and line overhead bytes for network management, while the SPE carries the actual user payload along with path overhead.[26] The SPE provides flexibility in payload placement, as it is not fixed to a specific position within the frame but "floats" across frames to accommodate timing variations between client signals and the synchronous frame rate.[26] This positioning is dynamically indicated by pointers located in the line overhead, which specify the offset of the first octet of the SPE from the pointer's location.[26] Within the SPE, the path overhead includes the J1 trace byte, a designated area for carrying a user-configurable message to identify the path for traceability and verification purposes.[26] In contrast, the Synchronous Digital Hierarchy (SDH) equivalent, the Synchronous Transport Module level 1 (STM-1), features a frame of 270 columns by 9 rows, totaling 2,430 bytes at 155.52 Mbps, which aligns with three interleaved STS-1 frames in SONET (often denoted as STS-3).[27] The STM-1 frame similarly allocates the first nine columns to section overhead (combining regenerator section overhead in rows 1-3 and multiplex section overhead in rows 5-9), with the remaining 261 columns dedicated to the payload area, structured as an Administrative Unit type 4 (AU-4) virtual container.[27] Like the SONET SPE, the SDH payload floats within the frame, with its position defined by an Administrative Unit pointer in row 4, columns 1-9; the J1 byte resides in the path overhead of the virtual container for path identification.[27] These structures, defined in ANSI T1.105 for SONET and ITU-T G.707 for SDH, ensure compatibility while adapting to regional standards, with SDH's larger base frame facilitating higher initial multiplexing efficiency.[26][27]Transport and Path Overhead Details
In Synchronous Optical Networking (SONET), the transport overhead is divided into section overhead and line overhead, which facilitate error monitoring, synchronization, and management across different network segments.[1] Section overhead, processed by section-terminating equipment such as regenerators, consists of nine bytes per STS-1 frame and includes framing, tracing, and error-checking functions. These bytes are located in the first three columns of the transport overhead rows.[1] The section overhead bytes are as follows:- A1 and A2 (framing bytes): These fixed-pattern bytes (A1 = 0xF6, A2 = 0x28) mark the start of the STS-1 frame and aid in synchronization and alignment.[1]
- J0 (section trace byte): For the first STS-1 in an STS-N, this byte carries a section trace identifier to verify the source of the section; in higher STS-N signals, it is reserved for growth.[1]
- B1 (bit-interleaved parity-8, BIP-8): This byte provides error monitoring over the regenerator section by computing even parity across all bits in the previous frame (excluding the B1 byte itself, before scrambling).[1]
- E1 (orderwire byte): Used for a 64 kb/s voice channel to enable communication between section-terminating equipment, such as regenerators.[1]
- F1 (user channel byte): A 64 kb/s channel available for user-defined purposes, such as data transfer between section equipment.[1]
- D1, D2, D3 (data communication channel, DCC, bytes): These form a 192 kb/s channel for operations, administration, maintenance, and provisioning (OAM&P) messaging between section elements.[1]
- H1, H2, and H3 (pointer bytes): H1 and H2 indicate the offset of the synchronous payload envelope (SPE) from the start of the payload, allowing dynamic alignment; H1 bits 7-4 and H2 bits 7-1 form the pointer value, while H3 supports payload shift actions for frequency justification.[1]
- K1 and K2 (automatic protection switching, APS, bytes): These bytes manage protection switching modes, channel numbers, and architecture, with K2 also conveying line remote error indication and remote defect indication.[1]
- J1 (path trace byte): A 64-byte cyclic string that identifies the path's origin, ensuring correct connection verification at the path termination.[1]
- B3 (path BIP-8 byte): Monitors bit errors in the SPE by applying even parity over all bits in the previous SPE (excluding B3, before scrambling).[1]
- C2 (signal label byte): Indicates the type of payload within the SPE, such as ATM or Ethernet mapping, and signals payload defects if set to a specific pattern.[1]
- G1 (path status byte): Provides path remote error indication and path remote defect indication, feeding back performance data to the path originator.[1]
- F2 (path user channel byte): A 64 kb/s channel for user communication between path originator and terminator, often used for maintenance data.[1]
Data Rates and Multiplexing
Standardized Data Rates
Synchronous Optical Networking (SONET) defines a hierarchy of standardized transmission rates through its Synchronous Transport Signal (STS-N) levels, where N represents the number of basic STS-1 units multiplexed together. The fundamental STS-1 rate is 51.84 Mbps, as specified in the American National Standards Institute (ANSI) standard T1.105. Higher rates are achieved by synchronous multiplexing: for instance, STS-3 operates at 155.52 Mbps (3 × 51.84 Mbps), STS-12 at 622.08 Mbps (12 × 51.84 Mbps), and STS-192 at 9.95328 Gbps (192 × 51.84 Mbps). These electrical STS-N signals correspond to optical carrier (OC-N) levels with identical bit rates, such as OC-1 at 51.84 Mbps and OC-192 at 9.95328 Gbps, facilitating transmission over fiber optic media. The Synchronous Digital Hierarchy (SDH), standardized by the International Telecommunication Union Telecommunication Standardization Sector (ITU-T) in Recommendation G.707, employs a similar structure but aligns its basic module to the STM-1 rate of 155.52 Mbps to accommodate international hierarchies. An STM-0 level exists at 51.84 Mbps for lower-rate applications, though it is less commonly deployed. Higher SDH rates include STM-4 at 622.08 Mbps (4 × 155.52 Mbps) and STM-64 at 9.95328 Gbps (64 × 155.52 Mbps). SONET and SDH rates are interoperable, with STS-3/STS-12/STS-192 directly mapping to STM-1/STM-4/STM-64, respectively, enabling global compatibility despite regional differences in base units. Each SONET/SDH frame allocates a portion of its capacity to overhead for management and synchronization, leaving the remainder for payload. For STS-1, the line rate of 51.84 Mbps includes a payload envelope of 50.112 Mbps, yielding an overhead of 1.728 Mbps; this results in a payload efficiency of approximately 96.7% at the transport level. However, when mapping legacy plesiochronous digital hierarchy (PDH) signals, the effective payload fraction drops to around 87% due to additional mapping overhead. For example, an STS-1 payload can accommodate one DS3 signal at 44.736 Mbps or 28 DS1 (T1) signals at 1.544 Mbps each, totaling 43.232 Mbps for the DS1 case after stuffing and framing adjustments.| SONET Level | Line Rate (Mbps) | SDH Equivalent | Typical Payload Capacity Example |
|---|---|---|---|
| STS-1/OC-1 | 51.84 | STM-0 | 1 DS3 (44.736 Mbps) or 28 DS1 (1.544 Mbps each) |
| STS-3/OC-3 | 155.52 | STM-1 | 3 DS3 or 84 DS1 |
| STS-12/OC-12 | 622.08 | STM-4 | 12 DS3 or 336 DS1 |
| STS-192/OC-192 | 9953.28 | STM-64 | 192 DS3 or 5376 DS1 |
Relationship to Ethernet and Other Standards
Synchronous Optical Networking (SONET) and Synchronous Digital Hierarchy (SDH) provide a standardized transport mechanism for integrating Ethernet traffic, particularly in metropolitan and core networks during the early 2000s. The IEEE 802.3ae-2002 standard defines the 10 Gigabit Ethernet (10GbE) WAN Physical Layer (PHY), known as 10GBASE-W, which maps Ethernet frames directly to the SONET STS-192c or SDH VC-4-64c payload at a line rate of 9.95328 Gbit/s. This mapping is facilitated by the WAN Interface Sublayer (WIS) in Clause 50 of the standard, which encapsulates the 10GBASE-R Physical Coding Sublayer (PCS) output—operating at 10.3125 Gbit/s—into SONET/SDH-compatible frames, enabling seamless interoperability with existing optical infrastructure. To enhance efficiency in transporting variable-length Ethernet frames over the fixed-rate SONET/SDH structure, the Generic Framing Procedure (GFP) was developed as specified in ITU-T Recommendation G.7041. GFP provides a protocol-independent adaptation layer that maps Ethernet Protocol Data Units (PDUs) into the SONET/SDH Virtual Container (VC) or Synchronous Transport Signal (STS) payload with minimal overhead, supporting both frame-mapped (GFP-F) and transparent (GFP-T) modes for Ethernet. This procedure addresses bandwidth mismatches by allowing asynchronous client signals like Ethernet to be efficiently encapsulated, reducing idle bytes compared to earlier methods such as PPP over SONET. Further flexibility for Ethernet services is achieved through virtual concatenation (VCAT), defined in ITU-T G.707, which enables the inverse multiplexing of lower-rate SONET/SDH containers (e.g., STS-1 or VC-3) to form higher-bandwidth virtual tributaries tailored to Ethernet rates. Combined with the Link Capacity Adjustment Scheme (LCAS) in ITU-T G.7042, VCAT allows dynamic bandwidth allocation and hitless addition/removal of members, optimizing resource utilization for bursty Ethernet traffic in SONET/SDH networks. These mechanisms made SONET/SDH a viable transport layer for Ethernet in metro and core segments until the 2010s, when packet-based alternatives gained prominence.[29] As optical networks evolved, the Optical Transport Network (OTN) emerged as a successor to SONET/SDH, standardized in ITU-T G.709, offering enhanced management of high-capacity wavelengths and better support for diverse client signals including Ethernet. OTN builds on SONET/SDH concepts but introduces flexible mapping via Optical Data Units (ODUs) and forward error correction, facilitating the transition from TDM-centric to more packet-friendly architectures. SONET/SDH also integrates with Dense Wavelength Division Multiplexing (DWDM) systems to scale capacity, as outlined in ITU-T G.694.1 for spectral grids, allowing multiple SONET channels to coexist on separate wavelengths over a single fiber. This combination extends SONET's reach and density in long-haul applications without altering the base protocol.[30]Physical Layer Specifications
Optical Interfaces and Transmission
Synchronous optical networking (SONET) and synchronous digital hierarchy (SDH) define a range of optical carrier (OC-N) levels for SONET, starting from OC-1 at 51.84 Mbps, and synchronous transport module (STM-N) levels for SDH, starting from STM-1 at 155.52 Mbps, scaling up to OC-768/STM-256 at 39.813 Gbps, to support scalable fiber-optic transmission.[22] These interfaces primarily utilize single-mode fiber (SMF), such as Corning SMF-28 compliant with ITU-T G.652, operating at wavelengths of 1310 nm for shorter reaches and 1550 nm for longer distances due to lower attenuation in the latter window.[31] Transmission distances vary by interface category as specified in ITU-T G.957, with intra-office interfaces (I series) for distances up to 2 km at 1310 nm on SMF-28, limited by attenuation budgets of 0-7 dB, and short-reach interfaces (S series) achieving up to 15 km at 1310 nm with budgets of 0-12 dB, while intermediate-reach (L series) extends to 40-80 km at 1550 nm with budgets up to 20-30 dB. Ultra-long-haul applications, often incorporating optical amplification, support spans exceeding 3000 km, with individual amplified segments of 80-120 km, constrained by cumulative attenuation of approximately 0.35 dB/km at 1310 nm and 0.20 dB/km at 1550 nm on SMF-28. Chromatic dispersion further limits uncompensated distances, particularly at higher rates like OC-192/STM-64, where zero-dispersion near 1310 nm allows ~80 km but 17-20 ps/nm/km at 1550 nm restricts it to ~40 km without dispersion compensation. For dense wavelength-division multiplexing (DWDM) integration, SONET/SDH signals align with the ITU-T G.694.1 frequency grid, typically 100 GHz or 50 GHz channel spacing in the C-band (1528-1568 nm), enabling multiple wavelengths on a single fiber while managing dispersion limits through compensation techniques. Common connector types include SC and LC duplex for pluggable modules like SFPs, supporting typical transmit power levels of -10 to 0 dBm and receiver sensitivities of -20 to -30 dBm, depending on the rate and reach category.[32] Optical signals in these interfaces may necessitate periodic regeneration to maintain signal integrity over extended distances.Signal Encoding and Regeneration
In Synchronous Optical Networking (SONET) and Synchronous Digital Hierarchy (SDH), the physical layer employs Non-Return-to-Zero (NRZ) encoding as the primary line code for optical interfaces, where a logical '1' is represented by a light pulse and '0' by its absence, ensuring a simple binary transmission format compatible with laser modulation.[31] This NRZ scheme is directly applied without additional bipolar coding in the core SONET/SDH signal path, though legacy T1 (DS1) tributaries mapped into SONET may use Bipolar with 8-Zero Substitution (B8ZS) for their electrical interfaces to maintain DC balance and error detection prior to multiplexing. To prevent long strings of identical bits that could impair clock recovery, the entire frame—excluding the fixed framing bytes—is scrambled using a frame-synchronous scrambler with the polynomial , applied via modulo-2 addition, which randomizes the signal while allowing deterministic descrambling at the receiver.[31] Signal regeneration in SONET/SDH occurs at intervals typically every 50-80 km, depending on fiber type, attenuation, and dispersion, to counteract optical power loss and waveform distortion over distance.[2] Standard regeneration employs 3R processing—reamplification to boost signal power, reshaping to restore pulse integrity, and retiming to recover and synchronize the clock—performed at regenerator sections to maintain bit error rates below . In contrast, 2R regeneration (reamplification and reshaping only, without retiming) may be used in shorter spans or amplified systems to reduce complexity, though it risks accumulating timing errors over multiple hops. The section trace byte (J0) in the section overhead facilitates loopback testing by carrying a user-defined identifier (1, 16, or 64 bytes) that verifies the connection between transmitter and receiver, enabling fault isolation during maintenance without disrupting traffic. Clock recovery in SONET/SDH relies on phase-locked loop (PLL) circuits that extract timing from framing pattern transitions and data transitions in the scrambled NRZ signal, ensuring bit-level synchronization across the network.[33] These PLLs must adhere to strict jitter specifications, with maximum output jitter generation limited to less than 0.1 unit intervals (UI) peak-to-peak for frequencies above 20 kHz, to prevent cumulative phase errors that could degrade downstream performance.[6] Error correction in SONET/SDH primarily uses basic parity checks embedded in the overhead, such as Bit Interleaved Parity-8 (BIP-8) in section (B1), line (B2), and path (B3) bytes, which provide error monitoring and detection but not correction. Forward error correction (FEC) is optional and can be implemented using G.709-like schemes in enhanced overhead bytes (e.g., MSOH for SDH), adding Reed-Solomon coding to correct burst errors and extend transmission reach, though it increases overhead by up to 7% and is not part of the core SONET/SDH specification.Network Equipment
Regenerators and Repeaters
In Synchronous Optical Networking (SONET) and Synchronous Digital Hierarchy (SDH) systems, regenerators serve to amplify and regenerate optical signals, countering attenuation, dispersion, and noise accumulation over long fiber spans. These devices are deployed at regular intervals along fiber spans to maintain signal integrity without full termination of the transport stream, with distances depending on fiber type, signal rate, and environmental factors. By restoring the signal's amplitude, shape, and timing—known as 3R regeneration (reamplification, reshaping, retiming)—regenerators enable reliable transmission across continental distances.[34] Two primary types of regenerators are employed in SONET/SDH networks: optical amplifiers and electrical regenerators. Optical amplifiers, such as Erbium-Doped Fiber Amplifiers (EDFAs), operate at the 1550 nm wavelength band, where fiber attenuation is minimal, providing purely optical amplification without electrical conversion to extend spans beyond traditional limits.[35] EDFAs perform 1R or 2R regeneration by boosting power and optionally reshaping the signal, effectively replacing older OEO regenerators and reducing latency.[36] In contrast, electrical regenerators use optical-electrical-optical (OEO) conversion, fully demodulating the signal to the electrical domain for retiming and error correction before re-modulation, which is essential for combating severe degradation but introduces higher complexity and cost.[37] Regenerators process the section overhead (SOH in SDH or section layer in SONET) to handle framing, error monitoring, and data communication channel functions between adjacent network elements, while transparently passing the line overhead, payload, and path overhead.[38] The regenerator derives its clock from the incoming signal, replaces section overhead bytes such as the Bit Interleaved Parity (B1) for error detection and the Section Trace (J0) for connectivity verification, and retransmits the frame.[8] If a fault is detected, such as excessive bit errors, the regenerator may insert an Alarm Indication Signal (AIS) into the section overhead to alert downstream elements, preventing error propagation.[1] Placement of regenerators occurs in-line between multiplexers or add-drop sites, often at span boundaries to minimize latency, with mid-span meet configurations ensuring interoperability across multi-vendor equipment by standardizing optical interfaces at OC-N/STM-N levels.[1] This setup allows seamless signal handoff without proprietary adaptations, supporting the standardized fiber-to-fiber connectivity defined in ANSI T1.105 and ITU-T G.707 recommendations.[8]Multiplexers and Cross-Connects
In Synchronous Optical Networking (SONET), multiplexers serve as key components for aggregating lower-rate digital signals into higher-rate Synchronous Transport Signals (STS-N). These devices employ byte-interleaved multiplexing to combine N STS-1 signals (each at 51.84 Mbps) into an STS-N frame, enabling efficient transport over optical fibers without requiring bit stuffing due to the synchronous nature of the signals.[1][8] Multiplexers are distinguished by their handling of signal granularity: wideband multiplexers process full STS-N frames for high-capacity aggregation, such as combining multiple STS-1s into OC-3 (155.52 Mbps) or higher rates, while narrowband multiplexers focus on tributary-level mapping, incorporating Virtual Tributaries (VTs) like VT1.5 for DS1 (1.544 Mbps) signals into the Synchronous Payload Envelope (SPE). This distinction allows wideband units to manage broadband traffic efficiently at central offices, whereas narrowband units support finer-grained grooming of voice and data tributaries.[1][8] Digital cross-connect systems (DCS) extend multiplexing functionality by providing switching capabilities for grooming and rerouting lower-rate signals within SONET networks, minimizing the need for complete demultiplexing of OC-N carriers. DCS facilitate the consolidation of subrate traffic, such as mapping multiple DS1s into available VTs or STS-1s, to optimize bandwidth utilization and support service provisioning. These systems operate on non-blocking switch matrices, typically implemented as time-slot interchangers or space-division fabrics, ensuring any input port can connect to any output without contention under normal loads. Configurations are established through network management interfaces, allowing dynamic reconfiguration for traffic engineering.[39][1] SONET DCS are classified by the granularity of switching: access or narrowband DCS groom at the DS1 (or finer DS0) level, handling individual channels up to 1.5 Mbps for detailed voice/data segregation; wideband DCS switch at the VT or DS1/DS3 level (1.5–45 Mbps), ideal for hub-based grooming of T1 lines without full frame disassembly; and broadband DCS operate at the STS-1 or OC-N level (51.84 Mbps to multiple Gbps), enabling high-capacity cross-connections for video and aggregated data services. This hierarchy aligns with the SONET multiplexing structure defined in ANSI T1.105 and ITU-T G.707 standards.[39][1][8] In the 1990s, commercial SONET DCS implementations featured switching fabrics with capacities up to 10 inputs by 10 outputs at 10 Gbps (approximating OC-192 rates), supporting scalable deployments in regional networks as per Telcordia GR-2996 generic requirements. These systems played a pivotal role in early SONET deployments by enabling flexible traffic management and rapid restoration.[39]Add-Drop Multiplexers
Add-drop multiplexers (ADMs) in Synchronous Optical Networking (SONET) are specialized devices that enable the efficient insertion and extraction of lower-rate tributary signals, such as VT1.5 at 1.728 Mb/s carrying DS1 signals, from a higher-rate optical carrier like OC-N without requiring the demultiplexing of the entire stream. This design leverages single-stage multiplexing to groom and pass through unaffected traffic, minimizing processing overhead and supporting applications like rural signal consolidation or drop-and-repeat services for telephony and cable TV. Additionally, ADMs incorporate loop-back mechanisms at various levels (e.g., line, path, or VT) to facilitate fault isolation and protection switching, allowing signals to be looped back locally or remotely for testing and redundancy verification.[1][40] ADM architectures vary between bidirectional and unidirectional configurations to suit different network topologies, with bidirectional designs supporting two-way traffic flow for enhanced efficiency in ring-based setups, while unidirectional variants handle one-directional streams for simpler linear deployments. In dense wavelength division multiplexing (DWDM) environments integrated with SONET, optical add-drop multiplexers (OADMs) extend this capability to the wavelength level, using components like acousto-optic tunable filters (AOTF) on lithium niobate substrates to selectively add or drop specific wavelengths (e.g., 32 channels at 10 Gb/s with 0.8 nm spacing) without optoelectronic conversion of the full multiplex. These OADMs support fixed or reconfigurable (ROADM) variants, evolving toward colorless, directionless, and contentionless designs for greater flexibility.[41][42] The primary benefits of ADMs lie in their ability to reduce latency and operational costs in linear and ring networks by avoiding full signal disassembly, thereby lowering equipment requirements and enabling efficient bandwidth utilization through wavelength reuse and self-healing features. They are particularly typical in metropolitan ring configurations, where they facilitate scalable access to high-capacity OC-N signals (e.g., OC-48 at 2.488 Gb/s) while supporting rapid provisioning of services like ATM or IP overlays. In ring topologies, ADMs enhance survivability with sub-60 ms restoration times.[41][43] The evolution of ADMs transitioned from electrical-based systems in the late 1980s to photonic implementations in the 2000s, incorporating WDM for transparent optical transport and higher bit rates beyond 10 Gb/s, while maintaining backward compatibility with legacy SONET equipment. This shift, driven by advancements in dynamic OADMs and ring protection schemes like bidirectional line-switched rings (BLSR), improved scalability and cost-effectiveness for metro and core networks.[43][42]Network Management and Protocols
Overall Management Framework
The management of Synchronous Optical Networking (SONET) and Synchronous Digital Hierarchy (SDH) networks follows the Telecommunications Management Network (TMN) model established by the ITU-T, which provides a standardized architectural framework for overseeing transport network operations across diverse equipment and vendors. This model emphasizes interoperability and scalability, integrating management functions to support the provisioning, monitoring, and maintenance of high-capacity optical transmission systems. TMN's layered approach ensures that management activities are distributed efficiently, from individual devices to the entire network domain, while adhering to principles of openness and modularity. Central to the TMN framework are the FCAPS management layers—Fault, Configuration, Accounting, Performance, and Security—which collectively address key operational needs in SONET/SDH environments. Fault management involves detecting, isolating, and resolving network anomalies, such as signal degradations or equipment failures, to minimize downtime. Configuration management handles the setup and modification of network resources, including path and section allocations. Accounting tracks resource utilization for billing and resource planning, while Performance management monitors metrics like bit error rates and availability to ensure service quality. Security management protects against unauthorized access and safeguards data integrity across the optical infrastructure. These FCAPS functions are mapped onto TMN's functional blocks, enabling a unified approach that aligns with the OSI management framework for comprehensive network control. The hierarchical elements of the framework include Element Management Systems (EMS), which focus on single or grouped network elements like multiplexers and regenerators, performing localized tasks such as software upgrades and basic fault isolation. In contrast, Network Management Systems (NMS) operate at a higher level to manage end-to-end connectivity, aggregating data from multiple EMS instances for global oversight. Key functions encompass circuit provisioning to establish virtual tributaries or paths dynamically, performance monitoring of parameters like Severely Errored Seconds (SES) to quantify error impacts on transmission quality, and alarm correlation to analyze event patterns across elements for root-cause diagnosis.[44] This structure leverages overhead channels in the SONET/SDH frame for embedding management data, facilitating real-time oversight without disrupting payload traffic. ITU-T Recommendation M.3100 specifies the generic network information model underpinning these interfaces, defining object-oriented representations for managed resources to ensure consistent data exchange between EMS, NMS, and higher-level systems.[45] By standardizing these elements, the framework supports multivendor interoperability and evolves with advancements in optical networking, maintaining reliability in carrier-grade deployments.TL1 and Q3 Protocols
Transaction Language 1 (TL1) is a standardized, ASCII-based messaging protocol developed for managing SONET network elements and transport surveillance functions. Defined in Telcordia Generic Requirements GR-833-CORE, TL1 enables communication between operations systems (OS) and network elements (NE) through a series of input commands and autonomous output messages. It supports cross-vendor interoperability and is particularly prevalent in North American SONET deployments for tasks such as equipment configuration, fault isolation, and performance monitoring.[46][47] TL1 messages follow a structured format consisting of a verb, modifiers, parameters, and terminators, with addressing achieved via a Target Identifier (TID) for the NE and Access Identifier (AID) for specific resources. Input commands initiate actions or retrieve data, such as theRTRV-EQPT::TID:SLOT-1: command, which retrieves equipment status for a specific slot in the NE. Autonomous messages, generated unsolicited by the NE, report events like alarms; for instance, a Loss of Signal (LOS) alarm might be reported as REPT-EQPT::TID:SLOT-1:AL-LOS;, alerting the OS to transmission failures. Security and access control are enforced through TID/AID validation and optional security parameters in message headers.[48][49]
Circuit provisioning exemplifies TL1's operational utility, using commands like ENT-CRS-1::TID:::SRCVT=VT15-1-1-1,DSTVT=VT15-2-1-1;, which establishes a virtual tributary cross-connection between source and destination paths. Additional examples include alarm retrieval via RTRV-ALM-ALL:::; to list all active faults across the NE, supporting proactive network maintenance. These commands ensure reliable, transaction-oriented interactions, with each message transaction confirmed by acknowledgments or denial responses to maintain session integrity.[48][49]
In contrast, the Q3 protocol provides an object-oriented management interface based on the Common Management Information Protocol (CMIP) within the Telecommunications Management Network (TMN) framework. Specified in ITU-T Recommendations Q.811 for lower-layer protocol profiles and Q.812 for upper-layer profiles, Q3 facilitates hierarchical network management using an OSI-compliant stack, including ACSE, CMIP, and transport layers. It models SONET/SDH resources as managed objects, enabling operations like create, delete, set, and get attributes for elements such as multiplexers and cross-connects. While Q3 supports global interoperability in SDH environments, it is less adopted in North America compared to TL1 due to the latter's simpler ASCII syntax and entrenched use in legacy SONET systems.[50]
Q3 operations mirror TL1's input/output paradigm but employ confirmed/unconfirmed CMIP services for actions like alarm reporting and configuration. For example, an LOS event would trigger a managed object attribute change notification via CMIP's M-EVENT-REPORT primitive, addressed to specific TMN management domains. Security relies on OSI authentication mechanisms, such as access control lists tied to distinguished names, ensuring secure multi-vendor interactions in international SDH networks. Overall, both protocols underpin SONET/SDH management by providing robust, standardized messaging, though TL1's procedural style contrasts with Q3's declarative, object-centric approach.
