Description
The Temporary Block Flow (TBF) is a core concept in the General Packet Radio Service (GPRS) and Enhanced Data rates for GSM Evolution (EDGE) radio access network. It represents a physical-layer connection used for the transfer of one or more Logical Link Control (LLC) Protocol Data Units (PDUs) in one direction (either uplink or downlink) between a Mobile Station (MS) and the network. A TBF is temporary, as its name implies, and is maintained only for the duration of the data transfer. It allocates radio resources on one or more Packet Data Channels (PDCHs), which are timeslots configured for packet data use.
The establishment of a TBF is initiated by the network for downlink transfer or by the MS for uplink transfer, triggered by the need to send data. The process involves a channel request (on the Random Access Channel, RACH, or Packet Random Access Channel, PRACH) and subsequent assignment messages (on the Access Grant Channel, AGCH, or Packet Associated Control Channel, PACCH). The assignment message specifies the PDCH(s) and the uplink state flag (USF) values for uplink TBFs, or the TFI (Temporary Flow Identity) for addressing blocks. The TBF uses the Radio Link Control/Medium Access Control (RLC/MAC) protocol. Data is segmented into RLC data blocks, which are transmitted within the allocated PDCH timeslots. Each block is identified by the TFI, allowing the receiver to reassemble the blocks belonging to the same TBF.
A key characteristic is its directionality: an MS can have one uplink TBF and one downlink TBF simultaneously, managed independently. Control for an active TBF, such as acknowledgments and resource control, is carried on the PACCH associated with the assigned PDCH. The TBF is released explicitly by a control message or implicitly by a timer expiry after the successful transfer of all data. This dynamic, on-demand allocation is what enables the efficient, shared use of radio resources for bursty packet data, contrasting with the permanent, circuit-switched connections used for voice.
Purpose & Motivation
The TBF was created to introduce efficient packet-switched data services into the originally circuit-switched GSM network. Before GPRS, GSM data services used a circuit-switched connection, tying up a full timeslot for the entire session duration, which was inefficient and expensive for intermittent, bursty data traffic like web browsing or email. The TBF mechanism solved this by allowing multiple users to share the same physical radio resources (timeslots) statistically.
It addressed the fundamental problem of resource allocation for unpredictable packet data. By establishing a connection only when there is data to send and releasing it immediately afterward, radio capacity could be reused rapidly among many users. This increased overall network capacity and reduced cost per bit. The TBF, along with the associated PDCH concept, was the enabling innovation that transformed GSM from a voice-only network into a platform for mobile internet access, forming the foundation for later 3G and 4G packet-switched architectures. Its design directly influenced later concepts like the Enhanced Dedicated Channel (E-DCH) in HSPA and the scheduling-based resource allocation in LTE and NR.
Classification
Evolution Across Releases
Introduced as a core component of the GPRS standard, defining the fundamental mechanism for packet data transfer over GSM networks. It specified the TBF establishment, data transfer using RLC/MAC blocks, and release procedures, enabling the first efficient packet-switched mobile data service.
Enhanced with EDGE (EGPRS) capabilities. Introduced new modulation and coding schemes (MCS) for higher data rates. The TBF mechanism was extended to support these enhanced RLC/MAC blocks, including incremental redundancy and link adaptation, significantly improving throughput and spectral efficiency within the TBF framework.
Further optimizations included features like Reduced Latency for packet data transfer, refining TBF establishment and release timers to decrease service delay. Enhancements to uplink TBF operation were also made to improve performance for interactive services.
Introduced Downlink Dual Carrier and later features, allowing a TBF to utilize two carriers simultaneously for a single user, effectively doubling the peak data rate. This required extensions to the TBF assignment and control signaling to manage resources across two frequency bands.
Explore further
Broader topics and technologies where TBF plays a role.
Defining Specifications
3GPP specifications that define or reference TBF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj00 | 3GPP Technical Terms and Definitions | Rel-19 |
| TR 23.979 vj00 | PoC over 3GPP Systems Architectural Requirements | Rel-19 |
| TS 26.804 vj10 | 5G Media Streaming Extensions Study | Rel-19 |
| TR 26.914 vj00 | Multimedia Telephony over IP Optimization | Rel-19 |
| TS 43.051 vj00 | GERAN Stage 2 Service Description | Rel-19 |
| TS 43.064 vj00 | GPRS Radio Interface Lower-Layer Functions | Rel-19 |
| TS 43.129 vj00 | PS Handover in GERAN A/Gb and GAN Modes | Rel-19 |
| TS 43.318 vj00 | Generic Access Network (GAN) Stage 2 | Rel-19 |
| TR 43.901 vj00 | Generic Access to A/Gb Interface Feasibility Study | Rel-19 |
| TR 43.902 vj00 | GAN Enhancements Feasibility Study | Rel-19 |
| TS 44.060 vj00 | GERAN RLC/MAC Protocol Specification | Rel-19 |
| TS 44.160 vg00 | GERAN Iu Mode RLC/MAC Protocol Specification | Rel-16 |
| TS 44.318 vj00 | Generic Access Network (GAN) Interface Procedures | Rel-19 |
| TR 45.902 vj00 | Flexible Layer One (FLO) for GERAN | Rel-19 |