TMMBR

Temporary Maximum Media Stream Bit Rate Request

Protocol →
Introduced in Rel-8 Also in: Services

TMMBR is an RTCP feedback message used to request a peer to temporarily limit its maximum sending bit rate for a specific media stream, enabling congestion control in real-time services like VoIP.

Category
Protocol
Introduced
Rel-8
Where
Core Network › Evolved Packet Core
Also touches
1 segments
Specifications
8 specs
TMMBR Description Purpose Related Classification Detected Changes Specifications

Description

The Temporary Maximum Media Stream Bit Rate Request (TMMBR) is a specific feedback message defined within the RTP Control Protocol (RTCP) framework, standardized by the IETF and adopted by 3GPP for IP Multimedia Subsystem (IMS) and Packet-Switched Streaming (PSS) services. It operates as part of the Audio-Visual Profile with Feedback (AVPF), which extends RTCP to provide more timely feedback. The primary mechanism involves a receiver analyzing the incoming media stream, detecting network congestion or limitations in its own processing capabilities, and generating a TMMBR packet. This packet is sent to the sender (the media source) and contains two key pieces of information: a unique identifier for the media stream (SSRC) and the requested maximum bit rate limit, expressed in kilobits per second.

Upon receiving a TMMBR, the sender is expected to adjust its encoding parameters or traffic shaping to ensure its transmission bit rate does not exceed the requested limit. This adjustment is 'temporary,' meaning the limit can be updated with subsequent TMMBR messages as network conditions change. The protocol includes rules for handling multiple TMMBR requests from different receivers for the same stream, typically requiring the sender to adhere to the most restrictive (lowest) bit rate limit among the active requests. This ensures the media flow does not overwhelm the most constrained participant in the session.

Architecturally, TMMBR is implemented within the media plane endpoints (e.g., User Equipment, media servers) and is transported over UDP alongside the RTP media streams. Its role is integral to the Quality of Experience (QoE) management in real-time services, working in concert with other RTCP feedback messages like Temporary Maximum Media Stream Bit Rate Notification (TMMBN) to acknowledge limits, and Receiver Estimated Maximum Bitrate (REMB). It provides a direct, session-level control mechanism that complements lower-layer transport protocols like TCP congestion control, which is unsuitable for real-time media due to retransmission delays.

Purpose & Motivation

TMMBR was created to address the critical need for dynamic bit rate adaptation in real-time multimedia communications over packet-switched networks, which are inherently variable in terms of available bandwidth and latency. Prior to such feedback mechanisms, applications often used static bit rates or simplistic probing, which could lead to persistent congestion, packet loss, and degraded audio/video quality when network conditions deteriorated. The 'temporary' and request-based nature of TMMBR provides a finer-grained, receiver-driven control compared to sender-only estimation or network-layer Quality of Service (QoS) markings alone.

Its development was motivated by the growth of IMS and mobile video services in 3GPP Release 8, where efficient use of the radio interface and core network resources became paramount. TMMBR allows a receiving endpoint, which may be on a congested cell edge or have limited processing power, to proactively signal its constraints to the far-end sender. This solves the problem of a media source unknowingly transmitting at a rate that the receiver or an intermediate network path cannot sustain, thereby preventing buffer overflows, reducing jitter, and minimizing packet discard. It enables more graceful degradation of media quality during congestion.

Classification

Part ofRTCP
Related approachesTMMBN

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (9 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Studied in Rel-8, normative work from Rel-16.

Rel-16 2 changes

In Release 16, the TMMBR function was updated to support the IMS Data Channel through the addition of a corresponding Media Feature Tag. This change aligns with the IETF reference update for the Data Channel media, integrating the control of telepresence media streams as defined by the IETF CLUE framework.

  • Adding Media Feature Tag for IMS Data Channel TS 26.114CR0499
  • IETF Reference Update for Data Channel Media TS 26.114CR0510
Rel-17 1 change

In Release 17, the TMMBR function was updated as part of the ITT4RT features, which introduced new control capabilities for the MRFC to manage media stream resources on the MRFP. These enhancements specifically included the ability for the MRFC to request the MRFP to stop playing tones or announcements upon DTMF detection, integrating TMMBR-related stream control with user interaction. This allowed for more dynamic media bit rate and playback management within services like audio announcements and recording.

  • Change Request on ITT4RT features TS 26.114CR0519
Rel-18 4 changes

In Release 18, no specific new changes were introduced for the TMMBR function itself, as the provided Change Request titles and grounding context exclusively detail updates for other RTCP and streaming mechanisms, such as distinguishing bootstrap data channels and RTCP-APP redundancy for Processing Information. The technical material describes general MRFC control of media streams but contains no mention of enhancements to the TMMBR procedure from this release. Therefore, Release 18 did not include novel updates to the TMMBR function compared to the previous release.

  • Mechanism to distinguish two bootstrap data channels with the same stream ID value (Rel-18) TS 26.114CR0560
  • RTCP-APP Redundancy Request for Processing Information (PI) TS 26.114CR0566
  • [ITT4RT] IANA registration of RTCP feedback for Viewport TS 26.114CR0549
  • Correction of RTCP Viewport feedback format value TS 26.114CR0577
Rel-19 2 changes

In Release 19, the TMMBR function was enhanced to support IMS restoration procedures after PCRF/PCF failure. This was achieved by adding a new RTCP RR packets trigger procedure. This addition allows the system to use existing RTCP mechanisms to aid in service restoration following a core network policy function failure.

  • Add RTCP RR packets trigger procedure to support IMS restoration procedures after PCRF/PCF failure TS 23.334CR0186
  • Add RTCP RR packets trigger procedure to support IMS restoration procedures after PCRF/PCF failure TS 29.334CR0419

Explore further

Broader topics and technologies where TMMBR plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 23.333 vj00 MRFC-MRFP Mp Interface Requirements Rel-19
TS 23.334 vj00 IMS-ALG to IMS-AGW Interface (Iq) Stage 2 Rel-19
TS 26.114 vj10 IMS Multimedia Telephony Media Handling Rel-19
TR 26.919 vj00 Study on 5G Conversational Media Handling Rel-19
TS 29.162 vj00 IMS-IP Network Interworking Rel-19
TS 29.238 vj00 H.248 Profile for IBCF-TrGW Interface Rel-19
TS 29.333 vj00 MRFC-MRFP Mp Interface Protocol Rel-19
TS 29.334 vj00 IMS-ALG to IMS-AGW Interface Protocol Rel-19