Data Link Connection Identifier

Description

The Data Link Connection Identifier (DLCI) is a key field within the header of a data link layer frame. Its primary function is to identify the logical Data Link Connection to which a transmitted frame belongs. In 3GPP systems, this concept is prominently used in protocols like the Link Access Protocol on the Dm channel (LAPDm) for the GSM radio interface and in certain core network signaling transport protocols. The DLCI allows a single physical resource (e.g., a timeslot or a signaling link) to carry frames for multiple independent logical connections simultaneously, a process known as multiplexing.

Technically, the DLCI value is assigned during the establishment of the Data Link Connection. In LAPDm (specified in TS 44.006), the address field of the frame contains the DLCI, which typically consists of a Service Access Point Identifier (SAPI) and, in some formats, a Terminal Endpoint Identifier (TEI). The SAPI identifies the type of service or layer 3 entity (e.g., call control, mobility management, SMS) using the connection, while the TEI identifies a specific terminal (like a mobile station) on a multipoint link. Together, they form a complete address for the logical link.

When a network entity receives a frame, it examines the DLCI in the address field to determine which logical connection the frame is associated with. The frame is then passed to the corresponding data link layer entity for processing, which involves checking sequence numbers, performing error detection, and ultimately delivering the contained information to the correct Layer 3 protocol entity (e.g., MM, CC, GMM). This mechanism is crucial for efficient resource usage, as it avoids the need for dedicated physical channels for each type of signaling or data flow. The management of DLCI values, their assignment, and the mapping to higher layers are central to the data link layer's operation in legacy GSM/GPRS networks.

Purpose & Motivation

The DLCI was created to solve the problem of efficiently supporting multiple concurrent communication streams over a single, often scarce, physical transmission resource, particularly the radio channel in cellular networks. Without such an identifier, the network would be unable to distinguish between frames carrying different types of information (e.g., a call setup signal versus a mobility update) destined for different logical endpoints, leading to confusion and incorrect processing.

Its development was motivated by the ISDN Q.921 (LAPD) standard, which used a DLCI for multiplexing multiple logical links on the D-channel. 3GPP adapted this for the mobile-specific LAPDm protocol. The primary problem it addresses is resource optimization; instead of allocating separate physical channels for each service (which would be incredibly wasteful, especially on the air interface), a single channel can be shared by time-multiplexing frames tagged with different DLCIs.

Furthermore, it provides a clear addressing mechanism at Layer 2, enabling the demultiplexing function at the receiver. This allows the network and the mobile station to maintain several parallel logical connections for different purposes—such as one for voice call control, another for SMS, and another for packet data session management—all over the same physical radio link. This architectural elegance and efficiency were fundamental to the service richness of GSM beyond simple voice telephony.

Key Features

• Uniquely identifies a logical Data Link Connection within the scope of a physical link or interface.
• Enables multiplexing of multiple independent logical channels over a single physical transmission path.
• Part of the frame address field, often comprising sub-fields like SAPI and TEI for service and endpoint identification.
• Used by the receiver to route an incoming frame to the correct data link layer entity and subsequently to the proper Layer 3 protocol.
• Values are assigned during connection establishment procedures.
• Essential for the operation of layer 2 protocols like LAPDm in GSM.

Evolution Across Releases

Defining Specifications