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

Glossary term · Radio Access Network

MTCH

MBMS point-to-multipoint Traffic Channel

Radio Access Network →

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.

Introduced
Rel-2
Where
Radio Access Network › UTRAN (3G)
Specifications
26 specs
Also in
Services, User Equipment
MTCH Description Purpose What changed Neighbours 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.

What changed in its specifications

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

TR 21.905Rel-17 → Rel-18

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

Full comparison in TR 21.905 →
TS 23.468Rel-18 → Rel-19

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

Full comparison in TS 23.468 →

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
  • Correction to mtch-neighbourCell field description TS 38.331CR4015

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 vj20 3GPP Terminology and Definitions Rel-19 read
TS 23.468 vj00 Group Communication System Enablers for LTE Rel-19 read
TS 23.768 vc10 Group Communication System Enablers for LTE Rel-12 read
TS 25.102 vj00 UTRA TDD RF Characteristics Rel-19 read
TS 25.301 vj00 UE-UTRAN Radio Interface Protocol Architecture Rel-19 read
TS 25.302 vj00 UTRA Physical Layer Services Rel-19 read
TS 25.304 vj10 UE Idle Mode Procedures Rel-19 read
TS 25.321 vj00 MAC Protocol Specification for UTRAN Rel-19 read
TS 25.322 vj00 RLC Protocol Specification Rel-19 read
TS 25.331 vj01 UTRAN Radio Resource Control Protocol Rel-19 read
TS 25.346 vj00 MBMS in UTRA Technical Specification Rel-19 read
TS 25.401 vj00 UTRAN Overall Architecture Rel-19 read
TS 25.402 vj00 UTRAN Synchronisation Mechanisms Rel-19 read
TR 25.912 vj00 Evolved UTRA and UTRAN Technical Report Rel-19 read
TS 36.300 vj20 E-UTRAN Radio Interface Protocol Architecture Rel-19 read
TS 36.302 vj00 E-UTRA Physical Layer Services Rel-19 read
TS 36.304 vj30 LTE UE Idle Mode Procedures Rel-19 read
TS 36.322 vj00 E-UTRA Radio Link Control Protocol Specification Rel-19 read
TR 36.976 vj00 LTE-based 5G Terrestrial Broadcast Overview Rel-19 read
TS 38.300 vj40 NR and NG-RAN Overall Description Rel-19 read
TS 38.304 vj30 NR UE Idle and Inactive State Procedures Rel-19 read
TS 38.321 vj40 NR MAC Protocol Specification Rel-19 read
TS 38.322 vj30 NR Radio Link Control (RLC) Protocol Specification Rel-19 read
TS 38.323 vj10 PDCP Protocol Specification Rel-19 read
TS 38.331 vj40 NR Radio Resource Control (RRC) Rel-19 read
TS 38.523 vj40 UE Conformance Specification for 5G NR Rel-19 read