MTCH

MBMS point-to-multipoint Traffic Channel

Radio Access Network →
Introduced in Rel-2 Also in: Services, User Equipment

MTCH is a downlink logical channel in 3GPP systems used exclusively for MBMS to deliver user data traffic from the network to multiple UEs simultaneously within a specific service area.

Category
Radio Access Network
Introduced
Rel-2
Where
Radio Access Network › NG-RAN (5G)
Also touches
2 segments
Specifications
26 specs
MTCH Description Purpose Related Classification Detected Changes Specifications

Description

The MBMS point-to-multipoint Traffic Channel (MTCH) is a unidirectional, downlink logical channel defined within the 3GPP radio interface protocol architecture for Multimedia Broadcast Multicast Service (MBMS). It operates at the Medium Access Control (MAC) layer and is dedicated to carrying the actual user plane data of an MBMS service, such as video streams, file downloads, or audio broadcasts, from the network to a group of user equipments (UEs). The MTCH is mapped to transport channels, specifically the Multicast Channel (MCH) in LTE and the Forward Access Channel (FACH) in UMTS, which are then mapped to physical resources. How it works is intrinsically linked to the MBMS session. When an MBMS session starts, the network configures the necessary radio bearers. The MTCH is associated with a specific Temporary Mobile Group Identity (TMGI) and MBMS Service Area. Data packets for the service are processed by the Packet Data Convergence Protocol (PDCP) and Radio Link Control (RLC) layers, which may apply header compression and segmentation. At the MAC layer, these packets are scheduled onto the MTCH logical channel. In a given cell, all MTCHs for different services are multiplexed onto the same MCH transport channel. UEs interested in receiving a service monitor the MCCH (MBMS Control Channel) for scheduling information, which tells them when and on which subframes the MTCH for their desired service will be transmitted. They then tune in to receive the data broadcast, enabling efficient spectrum usage as a single transmission serves all interested UEs in the coverage area. Its role is fundamental to the point-to-multipoint nature of MBMS, providing the pipe for the content delivery that distinguishes it from unicast traffic channels like the DTCH.

Purpose & Motivation

The MTCH was created to fulfill the need for an efficient, standardized mechanism to deliver identical content to many users simultaneously over a cellular radio interface, a capability not supported by traditional point-to-point (unicast) channels. Before MBMS and the MTCH, delivering popular content like live TV or software updates to a mass audience required establishing individual unicast bearers for each user, which rapidly consumes radio resources and core network bandwidth as the audience grows. This approach is neither scalable nor spectrum-efficient. The MTCH, as part of the broader MBMS framework, solves this problem by enabling true broadcast/multicast at the radio level. It allows a single transmission from the network to be received by an unlimited number of UEs within the coverage area, dramatically improving spectral efficiency for group communication services. Its creation was motivated by the desire to enable mobile TV, live event streaming, public warning systems, and group data delivery (like vehicular software updates) over cellular networks, turning them into a broadcast-capable platform. The MTCH provides the dedicated, service-specific data path that makes these applications feasible.

Classification

Part ofMCH
Specific typesSC-MTCH
Related approachesMCCH

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-17 1 change

In Release 17, a correction was made to the description of the `mtch-neighbourCell` field within the specifications for the MTCH function. This change ensured the technical documentation accurately reflected the intended use and meaning of this specific field related to MBMS neighbor cell information.

  • Correction to mtch-neighbourCell field description TS 38.331CR4015

Explore further

Broader topics and technologies where MTCH plays a role.

Defining Specifications

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

SpecificationTitleRelease
TR 21.905 vj00 3GPP Technical Terms and Definitions Rel-19
TS 23.468 vj00 Group Communication System Enablers for LTE Rel-19
TS 23.768 vc10 Group Communication System Enablers for LTE Rel-12
TS 25.102 vj00 UTRA TDD RF Characteristics Rel-19
TS 25.301 vj00 UE-UTRAN Radio Interface Protocol Architecture Rel-19
TS 25.302 vj00 UTRA Physical Layer Services Rel-19
TS 25.304 vj00 UTRA Idle Mode Procedures Specification Rel-19
TS 25.321 vj00 MAC Protocol Specification for UTRAN Rel-19
TS 25.322 vj00 RLC Protocol Specification Rel-19
TS 25.331 vj00 UTRAN RRC Protocol Specification Rel-19
TS 25.346 vj00 MBMS in UTRA Technical Specification Rel-19
TS 25.401 vj00 UTRAN Overall Architecture Rel-19
TS 25.402 vj00 UTRAN Synchronisation Mechanisms Rel-19
TR 25.912 vj00 Evolved UTRA and UTRAN Technical Report Rel-19
TS 36.300 vj00 E-UTRAN Radio Interface Protocol Architecture Overview Rel-19
TS 36.302 vj00 E-UTRA Physical Layer Services Rel-19
TS 36.304 vj00 UE Idle Mode Procedures in E-UTRA Rel-19
TS 36.322 vj00 E-UTRA Radio Link Control Protocol Specification Rel-19
TR 36.976 vj00 LTE-based 5G Terrestrial Broadcast Overview Rel-19
TS 38.300 vj00 NG-RAN Overall Description Rel-19
TS 38.304 vj00 UE RRC_IDLE and RRC_INACTIVE Procedures Rel-19
TS 38.321 vj00 NR MAC Protocol Specification Rel-19
TS 38.322 vj00 NR Radio Link Control (RLC) Protocol Rel-19
TS 38.323 vj00 Packet Data Convergence Protocol (PDCP) Rel-19
TS 38.331 vj00 NR Radio Resource Control (RRC) Protocol Specification Rel-19
TS 38.523 vj20 5G NR UE Conformance Testing: Idle/Inactive Rel-19
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.