Description
Traffic mode, as defined in 3GPP specifications 34.124, 36.124, and 38.124, describes the operational state of a User Equipment (UE) when it is powered on and has successfully established a Radio Resource Control (RRC) connection with the network. This state is distinct from idle mode, where the UE is switched on but has no active RRC connection and is only monitoring paging channels. In traffic mode, the UE has an active signaling connection and can transmit and receive user data, making it the state in which all active communication services—voice calls, data sessions, and multimedia streaming—take place.
The concept of traffic mode is fundamental to the Radio Resource Control (RRC) protocol, which governs the establishment, maintenance, and release of connections between the UE and the radio access network (e.g., UTRAN, E-UTRAN, or NG-RAN). When a UE transitions from idle mode to traffic mode, it performs an RRC connection establishment procedure, which involves random access, signaling radio bearer setup, and security activation. Once in traffic mode, the UE is assigned a Cell Radio Network Temporary Identifier (C-RNTI) and can be scheduled on shared or dedicated physical channels for data transmission.
In traffic mode, the network maintains context information for the UE, including its identity, security parameters, radio bearer configuration, and mobility state. This allows the network to efficiently manage radio resources, perform handovers, and deliver data with low latency. The UE in traffic mode continuously monitors control channels for scheduling grants, paging indicators, and system information updates. Depending on the radio access technology, traffic mode may be further subdivided into states such as CELL_DCH, CELL_FACH, CELL_PCH, and URA_PCH in UTRAN, or RRC_CONNECTED with various sub-states in E-UTRAN and NR.
The specifications that define traffic mode—34.124, 36.124, and 38.124—are part of the 3GPP TS 34-series and 36/38-series, which address UE conformance testing and radio access network performance requirements. These specifications ensure that UEs correctly implement the state transitions and behaviors associated with traffic mode, including measurement reporting, handover execution, and connection release. The consistent definition across these specifications ensures interoperability across different radio access technologies and vendor equipment.
Traffic mode is closely linked to the concept of quality of service (QoS), as the network must allocate sufficient radio resources to satisfy the QoS requirements of the active bearers. The transition between idle mode and traffic mode is a critical aspect of network performance, affecting call setup latency, signaling load, and battery consumption. Understanding traffic mode is essential for engineers designing RRC protocols, optimizing network capacity, and developing power-saving features such as Discontinuous Reception (DRX) and Connected Mode DRX (CDRX).
Purpose & Motivation
The traffic mode concept exists to clearly define the operational state in which a UE can actively exchange user data with the network. This distinction is crucial for radio resource management, as the network must allocate dedicated resources and maintain context information for UEs in traffic mode, whereas idle-mode UEs require minimal network resources. By standardizing this state across different radio access technologies, 3GPP ensures that UEs and networks from different vendors can interoperate seamlessly, and that performance requirements can be consistently specified and tested.
The primary problem that the traffic mode definition addresses is the need for a well-defined state machine for UE operation, enabling efficient transitions between idle and active states. Without a clear definition of traffic mode, network operators would struggle to manage radio resources, and UEs would not know when to expect scheduling grants or paging messages. The concept also enables power-saving mechanisms, as UEs in traffic mode can be configured with DRX cycles to reduce battery consumption while maintaining connectivity.
Historically, the traffic mode concept has evolved alongside the RRC protocol itself. In early UMTS releases, traffic mode was associated with dedicated channel states (CELL_DCH), but later releases introduced additional states like CELL_FACH and CELL_PCH to optimize for bursty data traffic. In LTE and NR, the RRC_CONNECTED state encompasses traffic mode with additional features like carrier aggregation and dual connectivity. The definition of traffic mode has remained stable across releases, reflecting its fundamental role in the RRC state machine.
What changed in its specifications
The latest release-to-release comparison of specifications that define Traffic mode. Each summary describes the whole specification, not only this term.
Rel-13 brings only minor changes to TS 34.124: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TS 34.124 →Rel-13 brings only minor changes to TS 36.124: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TS 36.124 →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 Traffic mode, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 34.124 vj00 | EMC Requirements for 3G UTRA Terminals | Rel-19 read |
| TS 36.124 vj00 | EMC for E-UTRA User Equipment | Rel-19 read |
| TS 38.124 vj00 | NR UE EMC Requirements | Rel-19 read |