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

Glossary term · Protocol

Bad traffic frame

Bad Traffic Frame

Protocol →

Bad traffic frame is a speech or data frame flagged by the radio subsystem as corrupted or unreliable, which triggers error concealment or retransmission mechanisms.

Introduced
Rel-8
Where
Radio Access Network
Specifications
3 specs
Bad traffic frame Description Purpose Neighbours Specifications

Description

The bad traffic frame concept is defined in 3GPP specifications for speech and data transmission over radio interfaces, particularly in TS 46.031, TS 46.041, and TS 46.081. It is used in the context of the radio subsystem, which includes the base station and user equipment, to indicate the quality of received frames. A traffic frame is a unit of speech or user data that is transmitted over the radio link. When the radio subsystem detects that a frame is corrupted or likely to be erroneous, it flags the frame with either a Bad Frame Indication (BFI) or an Unreliable Frame Indication (UFI).

The BFI is set to '1' when the frame is considered bad, meaning that the radio subsystem has detected errors or the frame failed a CRC check. The UFI is set to '1' when the frame is deemed unreliable but not necessarily completely corrupted; this may occur when the frame's quality is below a certain threshold but the CRC passes. These indications are passed to upper layers, such as the speech codec, which can then apply error concealment techniques to mitigate the impact of the bad frame on audio quality.

In speech communication, error concealment may involve extrapolating parameters from previous good frames, muting, or repeating the last good frame. The goal is to minimize audible artifacts and maintain intelligible speech. In data communication, a bad frame may trigger retransmission at the RLC or HARQ layer, depending on the radio bearer configuration and QoS requirements.

The bad traffic frame mechanism is closely related to the radio link control (RLC) and medium access control (MAC) layers, which handle error detection and retransmission. The physical layer performs channel decoding and CRC checks; if the CRC fails, the frame is marked as bad. The MAC layer may perform HARQ retransmissions, and if the frame still fails, it may be passed to the RLC layer for further retransmission or to the application layer with the bad frame indication.

In 3GPP specifications, the bad traffic frame is often discussed in the context of the Adaptive Multi-Rate (AMR) speech codec and other speech codecs, where the frame quality indication is used to control codec mode adaptation and error concealment. The specifications define how the BFI and UFI are generated, transmitted, and used by the receiver.

The bad traffic frame concept is applicable to both circuit-switched and packet-switched voice services. In VoLTE and VoNR, similar mechanisms exist, although the specific terminology may differ; the underlying principle of indicating frame quality to upper layers remains. The term is also relevant to other real-time services such as video telephony, where frame errors can cause visual artifacts.

Overall, the bad traffic frame is a crucial concept for ensuring robust and high-quality real-time communication over error-prone radio channels. It enables the receiver to take appropriate actions to maintain service quality.

Purpose & Motivation

The bad traffic frame concept exists to provide a standardized way for the radio subsystem to inform upper layers about the reliability of received frames. In wireless communications, radio channels are subject to noise, interference, and fading, which can cause bit errors and corrupted frames. Without an indication of frame quality, upper layers would not know whether to trust the received data, potentially leading to poor audio quality or data corruption.

Historically, early digital cellular systems such as GSM introduced frame quality indicators to support speech codecs and error concealment. The BFI and UFI were defined to allow the speech decoder to apply concealment techniques when frames are bad or unreliable. This significantly improved voice quality in adverse radio conditions.

As networks evolved to support data services and packet-switched voice, the need for frame quality indications persisted. In LTE and 5G, similar mechanisms are used at different layers (e.g., HARQ, RLC, and PDCP), but the principle of flagging bad frames remains. The bad traffic frame concept therefore addresses the fundamental problem of error handling in real-time communication, ensuring that the receiver can adapt and maintain acceptable service quality.

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-8 Initial

Initial introduction of the bad traffic frame term in 3GPP specifications. The definition establishes the concept of a traffic frame flagged with BFI=1 or UFI=1 by the radio subsystem. It supports speech and data error handling.

The definition text remains unchanged. The term continues to be used in the same context without modification.

The definition text remains unchanged. The term is carried over without modification.

The definition text remains unchanged. The term is carried over without modification.

The definition text remains unchanged. The term is carried over without modification.

The definition text remains unchanged. The term is carried over without modification.

The definition text remains unchanged. The term is carried over without modification.

The definition text remains unchanged. The term is carried over without modification.

The definition text remains unchanged. The term is carried over without modification.

The definition text changed by removing the line break after 'BFI= "1"' and adjusting punctuation, resulting in a single-line phrasing: 'traffic frame flagged BFI= "1" (Bad Frame Indication) or with UFI= "1" (Unreliable Frame Indication) by the Radio Subsystem.' The semantic meaning remains identical; only formatting was adjusted.

The definition text remains unchanged from the Rel-17 single-line phrasing. No modification is observed.

The definition text reverts to the two-line format with a line break after 'BFI= "1"'. This is a formatting change only; the meaning remains the same.

Defining Specifications

3GPP specifications that define or reference Bad traffic frame, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 46.031 vj00 GSM Full Rate Speech DTX Operation Rel-19 read
TS 46.041 vj00 GSM Half Rate Speech DTX Operation Rel-19 read
TS 46.081 vj00 GSM Enhanced Full Rate DTX Operation Rel-19 read