Description
In FLO, the physical layer is configured dynamically per call rather than being tied to a fixed set of predefined transport formats. The notion of an 'active' transport channel is needed to precisely describe when a given transport channel is actually carrying user or signalling data during a given Transmission Time Interval (TTI), as opposed to being configured but idle.
According to the original Release 8 definition, a transport channel is active during a TTI if it carries an RLC/MAC block. The RLC/MAC block is the fundamental unit of data exchanged between the RLC and MAC layers in GERAN, encapsulating either user data or control signalling. By tying the definition of 'active' to the presence of an RLC/MAC block in a TTI, the specification provides an unambiguous, observable criterion that can be used by both the network and the mobile station when reasoning about multiplexing, power control, and resource allocation behaviour in FLO.
The definition matters because FLO allows multiple transport channels to be multiplexed onto the same physical resources, and the scheduler must decide, TTI by TTI, which transport channels are actually carrying data. Knowing which channels are active is essential for computing the correct transport format combination, for determining the appropriate coding and puncturing, and for ensuring that the receiver can correctly decode the multiplexed stream. The concept also underpins procedures related to discontinuous transmission and the handling of idle periods on a configured channel.
In Release 17 the wording was revised so that a transport channel is active during a TTI if it carries a transport block rather than an RLC/MAC block. This change aligns the GERAN terminology with the more generic 3GPP concept of a transport block, which is the unit of data passed between the MAC layer and the physical layer in the wider 3GPP system (notably in UTRAN and E-UTRAN). The underlying semantics remain the same: a channel is active when it is actually conveying a unit of data during the TTI. The revised wording simply modernises the terminology and improves consistency across 3GPP specifications.
The term is documented in specifications 44.118 (Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol for GERAN), 44.160 (General Packet Radio Service; Mobile Station - Base Station System interface; RLC/MAC protocol), and 45.902 (Flexible Layer One). Together these specifications define the FLO architecture, the RLC/MAC procedures, and the RRC signalling that configure and control transport channels, making the Active Transport Channel definition a small but necessary piece of the overall GERAN FLO picture.
Purpose & Motivation
The Active Transport Channel concept exists to give a precise, testable meaning to the phrase 'a transport channel is active' within GERAN Flexible Layer One. FLO was introduced to overcome the rigidity of earlier GERAN configurations, where the set of transport formats and the mapping to physical resources were largely fixed at call setup. With FLO, the network can reconfigure the physical layer dynamically, and multiple transport channels can share resources. In such a dynamic environment, engineers and protocol procedures need a clear criterion for deciding whether a configured channel is actually transmitting data in a given TTI, because that decision affects multiplexing, coding, power control, and receiver processing.
Before FLO, GERAN transport channels were associated with relatively static configurations, and the question of whether a channel was 'active' was less central because the mapping of logical channels to physical resources was more predictable. The introduction of flexible multiplexing made it necessary to define activity explicitly, so that both the network scheduler and the mobile station could agree on which channels contribute data to a given TTI. Tying activity to the presence of an RLC/MAC block (and later a transport block) provides an objective, observable condition rather than a matter of interpretation.
The Release 17 rewording to 'transport block' reflects the ongoing harmonisation of 3GPP terminology across radio access technologies. By adopting the generic transport block concept, the definition becomes consistent with the way UTRAN and E-UTRAN describe the interface between MAC and the physical layer, reducing confusion for engineers working across multiple RATs and improving the coherence of the 3GPP specification set as a whole.
What changed in its specifications
The latest release-to-release comparison of specifications that define Active Transport Channel. Each summary describes the whole specification, not only this term.
Generic Access to A/Gb Interface defines MS actions for radio bearer mapping, transport format set and combination handling, and transport channel deletion; adds IEs for mapping, interleaving, mode, and transport channel identity.
Full comparison in TS 44.118 →Reduced PS service interruption in Dual Transfer Mode. Added MAC-DTM channel mapping rules and an SRB2 condition for PDTCH or CDCH usage.
Full comparison in TS 44.160 →Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Defining Specifications
3GPP specifications that define or reference Active Transport Channel, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 44.118 vg00 | Radio Resource Control (RRC) Protocol for Iu Mode | Rel-16 read |
| TS 44.160 vg00 | GERAN Iu Mode RLC/MAC Protocol Specification | Rel-16 read |
| TR 45.902 vj00 | Flexible Layer One (FLO) for GERAN | Rel-19 read |