Block period

Description

In 3GPP GERAN (GSM/EDGE Radio Access Network) specifications, a Block period is defined as a sequence of timeslots on a Single Block Packet Switched Channel (SBPSCH) or a Dual Block Packet Switched Channel (DBPSCH) used to convey one radio block. This concept is fundamental to the operation of packet data channels such as PDTCH (Packet Data Traffic Channel), PACCH (Packet Associated Control Channel), and various traffic channels. The block period determines how many timeslots are grouped together to form a single radio block, which is the basic unit of transmission in GERAN packet data.

The length of a block period depends on the channel type and the modulation/coding scheme. For PDTCH, PACCH, SACCH, SDCCH, TCH/AHS, and E-FACCH, the block period consists of 4 timeslots. For FACCH/H, it is 6 timeslots; for TCH/AFS and FACCH/F, it is 8 timeslots; and for (E-)TCH/F, it is 22 timeslots. These variations reflect the different burst structures and interleaving depths used for each channel to achieve the required robustness and latency. The block period is essential for scheduling and multiplexing, as it defines the time interval over which a radio block is transmitted and received.

The concept was introduced in Release 8, coinciding with the evolution of GERAN to support higher data rates through EDGE Evolution. It has been carried forward through all subsequent releases up to Release 19. In Release 17, the definition was simplified to "block period is the sequence of four timeslots on a PDCH used to convey one radio block," reflecting the predominant use of 4-timeslot block periods for packet data channels. This change aligned the definition with the most common configuration and removed references to specific channel types that were less relevant in later releases.

In practice, the block period is used by the network to schedule radio blocks on packet data channels. The scheduler allocates timeslots to mobile stations, and the block period defines the granularity of these allocations. For example, in a 4-timeslot block period, the network can assign one or more timeslots within the block period to a mobile station, and the mobile station transmits or receives its radio block within that period. This enables efficient statistical multiplexing of packet data traffic.

The block period also impacts latency and throughput. A shorter block period (e.g., 4 timeslots) allows more frequent scheduling opportunities, reducing latency, while a longer block period (e.g., 22 timeslots) provides greater robustness against errors but increases latency. The choice of block period is therefore a trade-off between reliability and delay, and it is configured based on the service requirements and channel conditions. The specifications 3GPP TS 44.060 and TS 44.160 define the procedures and formats for block periods in GERAN.

Purpose & Motivation

The Block period concept exists to provide a standardized timing structure for transmitting radio blocks over GERAN packet data channels. Before its formal definition, packet data transmissions used various ad-hoc groupings of timeslots, which led to interoperability issues and inefficient scheduling. By defining a block period as a specific sequence of timeslots, 3GPP enabled consistent mapping of radio blocks to physical resources, facilitating multi-vendor interoperability and efficient radio resource management.

The block period solves the problem of how to organize timeslots into units that can be independently scheduled and error-protected. Different channel types require different levels of error protection and interleaving, which is why the block period length varies. For instance, speech channels (TCH/AFS) use 8 timeslots to achieve sufficient interleaving depth for good voice quality, while packet data channels (PDTCH) use 4 timeslots to minimize latency. This flexibility allows GERAN to support a wide range of services with different QoS requirements.

Historically, the block period was introduced in Release 8 as part of the GERAN evolution to support higher data rates and improved spectral efficiency. The definition has remained largely stable, with a simplification in Release 17 to focus on the 4-timeslot block period used for packet data. This reflects the continued importance of packet data in GERAN and the need for a clear, concise definition for modern implementations.