Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Radio Access Network

RAB sub-flows

Radio Access Bearer Sub-flows

Radio Access Network →

RAB sub-flows is the subdivision of a Radio Access Bearer in UTRAN into distinct data streams, each corresponding to a different NAS service with its own QoS characteristics like reliability class.

Introduced
Rel-4
Where
Radio Access Network › UTRAN (3G)
Specifications
2 specs
RAB sub-flows Description Purpose What changed Neighbours Specifications

Description

RAB sub-flows are a UTRAN-specific concept introduced in Release 4 that allows a single Radio Access Bearer to be realized through one or more sub-flows, each corresponding to a NAS (Non-Access Stratum) service data stream with distinct QoS characteristics. This mechanism enables multiplexing of multiple service data streams with different reliability requirements within a single RAB, providing efficient use of radio resources while maintaining service differentiation.

The concept is defined in 3GPP TS 25.401 (UTRAN overall description) and TS 25.415 (UTRAN Iu interface user plane protocols). A RAB, as defined in TR 21.905, is the service provided by the Access Stratum to the Non-Access Stratum for transferring user data between the UE and the core network. When a RAB supports multiple sub-flows, each sub-flow carries data with specific QoS attributes — for example, one sub-flow might carry conversational speech requiring high reliability and low delay, while another carries signaling or background data with different requirements.

The sub-flow concept is particularly relevant in the context of the Iu interface user plane protocol, where the frame protocol supports multiple sub-flows within a single bearer. Each sub-flow is identified by a sub-flow number (0 to N), and the frame protocol includes sub-flow-specific fields for sequence numbers, error detection, and rate control. This allows the receiving entity to process each sub-flow independently according to its QoS requirements.

In practical terms, RAB sub-flows are most commonly associated with AMR (Adaptive Multi-Rate) speech codecs, where the speech codec produces multiple bit streams — one for each AMR mode — with different error sensitivity. The most sensitive bits (Class A) are carried in one sub-flow with strong error protection, while less sensitive bits (Classes B and C) are carried in other sub-flows with progressively less protection. This unequal error protection (UEP) approach optimizes the use of radio resources while maintaining speech quality.

The sub-flow mechanism allows the UTRAN to apply different transport channel configurations to each sub-flow. For example, sub-flow 0 might use a transport channel with a low coding rate and CRC protection, while sub-flow 1 uses a higher coding rate without CRC. This flexibility enables the network to tailor error protection to the specific needs of each data stream.

While RAB sub-flows are primarily a UTRAN concept, the underlying principle of differentiating QoS within a bearer has influenced later architectures. In 5G NR, the QoS flow concept within a PDU session serves a similar purpose, though the implementation differs significantly. The RAB sub-flow concept remains an important reference for understanding the evolution of QoS differentiation in cellular networks.

Purpose & Motivation

RAB sub-flows were created to address a specific inefficiency in early UMTS networks: the need to carry multiple service data streams with different QoS requirements over a single radio access bearer without establishing separate RABs for each stream. Before this concept, each distinct QoS requirement would necessitate a separate RAB, consuming additional radio resources and signaling overhead.

The primary motivation was the introduction of AMR speech codecs in Release 4. AMR codecs produce multiple bit streams with different error sensitivities, and the most efficient way to transmit these is through unequal error protection. RAB sub-flows provided the mechanism to apply different transport formats and error protection levels to different portions of the codec output within a single RAB.

This approach solved the problem of how to efficiently multiplex multi-rate codec streams while maintaining the appropriate level of error protection for each. It also provided a general framework for carrying any set of service data streams with differing QoS characteristics within a single bearer, making it applicable beyond speech codecs to any service requiring intra-bearer QoS differentiation.

The concept was particularly important during the early UMTS deployment phase when radio resources were scarce and efficient multiplexing was critical. It allowed operators to maximize the number of simultaneous users while maintaining acceptable quality of service for real-time applications.

What changed in its specifications

The latest release-to-release comparison of specifications that define RAB sub-flows. Each summary describes the whole specification, not only this term.

TS 25.401Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 25.401: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 25.401 →
TS 25.415Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 25.415: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 25.415 →

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.

Rel-4 Initial

Initial definition introduced: 'Radio Access Bearer can be realised by UTRAN through several sub-flows. These sub-flows correspond to the NAS service data streams that have QoS characteristics that differ in a predefined manner within a RAB e.g. different reliability classes.' This established the foundational concept for intra-RAB QoS differentiation in UTRAN.

Definition text carried over unchanged from Rel-4.

Definition text carried over unchanged from Rel-4.

Definition text carried over unchanged from Rel-4.

Definition text was revised: 'RAB as defined in [9] is realised by UTRAN through one to several sub-flows. These sub-flows correspond to the NAS service data streams that have QoS characteristics that differ in a predefined manner within a RAB e.g. different reliability classes.' The key change was replacing 'several sub-flows' with 'one to several sub-flows,' clarifying that a RAB may be realized by a single sub-flow as well as multiple sub-flows. The reference citation was also changed from [9] to [9] with different formatting.

Definition text carried over from Rel-8 with the reference citation expanded to 'TR 21.905 [9]' for clarity.

Definition text carried over unchanged from Rel-9.

Definition text carried over unchanged from Rel-9.

Definition text carried over unchanged from Rel-9.

Definition text carried over unchanged from Rel-9.

Definition text carried over unchanged from Rel-9.

Definition text carried over unchanged from Rel-9.

Definition text carried over unchanged from Rel-9.

Definition text carried over unchanged from Rel-9, with formatting normalized to a single paragraph.

Definition text carried over unchanged from Rel-9.

Definition text carried over unchanged from Rel-9.

Defining Specifications

3GPP specifications that define or reference RAB sub-flows, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 25.401 vj00 UTRAN Overall Architecture Rel-19 read
TS 25.415 vj00 Iu Interface User Plane Protocol Rel-19 read