Block Header

Description

The Block Header (BH) is a fundamental component of the protocol data units defined in 3GPP TS 43.064, which specifies the overall description of the General Packet Radio Service (GPRS) and Enhanced Data rates for GSM Evolution (EDGE) Radio Access Network (GERAN) for the Gb interface. It operates within the Base Station System GPRS Protocol (BSSGP) layer, which manages the flow of data and signaling between the Serving GPRS Support Node (SGSN) and the Base Station Controller (BSC). The BH is prepended to user data or signaling messages to form a complete BSSGP Protocol Data Unit (PDU), enabling the network to process and route information correctly.

Structurally, the Block Header contains several critical fields that govern the handling of the subsequent data block. Key components include the Block Type, which identifies the nature of the PDU (e.g., data or signaling), and the Block Length, which specifies the total size of the BSSGP PDU. Other fields may include identifiers for the Network Service Entity (NSE) and the Base Station System Virtual Connection (BVC), which are essential for routing the block to the correct logical connection within the Gb interface. The header ensures that each block is delivered to the appropriate processing entity within the BSS or core network.

In operation, when an SGSN needs to send a packet to a Mobile Station (MS) via the BSC, it encapsulates the packet within a BSSGP PDU, starting with the Block Header. The BSC uses the information in the BH to determine how to process the block—for instance, whether it should be forwarded to a specific cell or if it requires special handling for quality of service (QoS). Similarly, uplink data from the MS follows the reverse path, with the BSC adding the appropriate BH before transmitting the block to the SGSN. This mechanism supports various GPRS/EDGE services, including SMS over GPRS, by providing a standardized way to manage block-oriented communication.

The role of the Block Header is crucial for maintaining the integrity and efficiency of data transfer across the Gb interface. It facilitates functions such as flow control, by allowing the network to manage the rate of data blocks, and error handling, by enabling the identification and retransmission of corrupted blocks. Furthermore, the BH's design supports the multiplexing of multiple logical connections over a single physical link, optimizing resource usage in the radio access network. Its consistent application across 3GPP releases ensures backward compatibility and smooth evolution of GERAN technologies.

Purpose & Motivation

The Block Header was introduced to address the need for a structured and reliable method of transmitting data blocks in GPRS and EDGE networks. Prior to its standardization, early mobile data services lacked a unified protocol for bearer-independent messaging, leading to potential interoperability issues between network equipment from different vendors. The BH, as part of the BSSGP layer, provided a common framework for encapsulating user data and control information, enabling seamless communication between the core network and the radio access network.

Historically, the development of GPRS required a packet-switched complement to the circuit-switched GSM network. This necessitated new protocols to handle packet routing, flow control, and resource management over the Gb interface connecting the SGSN and BSC. The Block Header emerged as a key element of this protocol suite, solving the problem of how to efficiently package and identify data blocks without relying on the underlying transport network specifics. It allowed for the separation of concerns, where the BH handles logical routing and control, while lower layers manage physical transmission.

The creation of the BH was motivated by the limitations of earlier data transmission methods, which were often tightly coupled to specific bearers or lacked the flexibility needed for evolving packet services. By providing a bearer-independent header structure, it facilitated the introduction of advanced services like SMS over GPRS and paved the way for enhanced data rates with EDGE. Its design ensured that network elements could correctly process blocks regardless of the radio technology or core network evolution, supporting the long-term scalability and reliability of 2G/3G mobile data networks.

Key Features

• Standardized structure for BSSGP Protocol Data Units
• Contains Block Type for data/signaling discrimination
• Includes Block Length for PDU size specification
• Supports routing via Network Service Entity (NSE) and Base Station System Virtual Connection (BVC) identifiers
• Enables flow control and error handling mechanisms
• Facilitates multiplexing of logical connections over the Gb interface

Evolution Across Releases

Defining Specifications