High Level Data Link Control

Description

High Level Data Link Control (HDLC) is a foundational data link layer protocol, standardized by ISO as ISO/IEC 13239, which has been adopted within 3GPP specifications for framing and reliable data transfer. It operates at Layer 2 of the OSI model and is a bit-oriented, synchronous protocol. Its primary function is to ensure the reliable transmission of data frames between network nodes over a physical link. HDLC defines a structured frame format consisting of flag sequences for delimitation, address fields for identifying stations, control fields for managing frame types and sequencing, an information field for payload, and a frame check sequence (FCS) for error detection using cyclic redundancy check (CRC). The protocol supports multiple operational modes, including Normal Response Mode (NRM), Asynchronous Response Mode (ARM), and Asynchronous Balanced Mode (ABM), which define the roles of primary and secondary stations in managing link control and data flow.

Within the 3GPP architecture, HDLC is specified for use over various interfaces, particularly in the core network and for certain Radio Access Network (RAN) signaling links. For instance, in UMTS, it is used for the Iub interface between the Radio Network Controller (RNC) and Node B, as well as for some signaling transport in the core network. The protocol provides essential data link services such as connection establishment and termination, frame sequencing and acknowledgment, error detection and recovery through retransmission, and flow control to prevent receiver overload. It ensures data transparency through bit stuffing, where a '0' bit is inserted after five consecutive '1' bits in the data field to prevent confusion with flag sequences.

HDLC's role in 3GPP networks is to offer a robust, standardized method for point-to-point and multipoint communications, forming a reliable sublayer for higher-layer protocols. While newer technologies and protocols like IP-based transport and PPP have become more prevalent, HDLC remains a critical component in legacy systems and specific interface definitions. Its implementation in 3GPP specs ensures interoperability and reliable data transfer for control signaling and user data in earlier network generations, providing a stable foundation for network operations.

Purpose & Motivation

HDLC was created to provide a standardized, reliable data link layer protocol for synchronous serial communication, addressing the need for error-free data transmission over telecommunications links. Prior to its standardization, proprietary and less robust link layer protocols led to interoperability issues and unreliable data transfer. HDLC solved these problems by offering a comprehensive framework for frame structure, error control, and flow management, which became a model for many subsequent data link protocols.

In the context of 3GPP, HDLC was adopted to ensure reliable signaling and data transport across various network interfaces, particularly in GSM and UMTS networks. It provided a proven, stable protocol for the data link layer, enabling the dependable exchange of control messages and user data between network elements like RNCs and Node Bs. Its inclusion in 3GPP specifications supported the goal of creating interoperable, robust mobile networks by leveraging an internationally recognized standard for link-level communications.

The motivation for using HDLC in 3GPP stemmed from its maturity, widespread industry adoption, and ability to handle the stringent reliability requirements of telecommunications networks. It addressed limitations of earlier, simpler protocols by incorporating advanced features like sliding window flow control and robust error detection, which were essential for maintaining network integrity and performance in the evolving mobile ecosystem.

Key Features

• Bit-oriented synchronous framing with flag delimiters
• Support for multiple operational modes (NRM, ARM, ABM)
• Error detection using Frame Check Sequence (FCS) with CRC
• Flow control and sequence numbering for reliable transfer
• Data transparency through zero bit insertion (bit stuffing)
• Connection-oriented and connectionless communication support

Evolution Across Releases

Defining Specifications