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

Glossary term · Radio Access Network

MBMS/Unicast-mixed cell

MBMS/Unicast-Mixed Cell

Radio Access Network →

MBMS/Unicast-mixed cell is a cell that supports both unicast and MBMS broadcast/multicast transmissions simultaneously, allowing bidirectional and broadcast services to share the same radio resources in LTE.

Introduced
Rel-14
Where
Radio Access Network › E-UTRAN (LTE)
Specifications
2 specs
MBMS/Unicast-mixed cell Description Purpose What changed Neighbours Specifications

Description

An MBMS/Unicast-mixed cell is a radio cell that supports both unicast transmissions (normal bidirectional user traffic) and MBMS point-to-multipoint transmissions within the same coverage area. It is defined in the E-UTRAN specifications 36.300 (overall architecture) and 36.304 (UE procedures in idle mode), and it is the counterpart to the MBMS-dedicated cell. In practice, the mixed cell is the dominant deployment model because it allows an operator to offer broadcast services without dedicating an entire cell (and its spectrum) to broadcast-only operation.

In a mixed cell, radio resources are shared between unicast and MBMS traffic. For MBSFN operation, the cell reserves specific subframes (MBSFN subframes) for multicast/broadcast transmission, while the remaining subframes carry unicast traffic. The eNodeB schedules both traffic types, and the UE must be capable of receiving both. For single-cell point-to-multipoint (SC-PTM) operation, the same physical resources are dynamically shared, with the eNodeB scheduling PTM transmissions on a per-subframe basis alongside unicast. This flexibility is the key advantage of the mixed cell: broadcast capacity can be adjusted according to demand rather than being statically provisioned.

From the UE perspective, a mixed cell simplifies mobility and service continuity. A UE camped on a mixed cell can receive MBMS content and also initiate or receive unicast services without changing cells. This avoids the reselection complexity inherent in dedicated cells, where a UE would have to move to another cell for bidirectional traffic. The UE procedures in 36.304 account for the cell's capability to support both traffic types when evaluating cell suitability and service availability.

The mixed cell model also has implications for interference and spectral efficiency. Because MBSFN subframes are transmitted synchronously across multiple cells in an MBSFN area, the UE can combine signals from neighbouring cells, turning inter-cell interference into useful signal energy. Unicast subframes, by contrast, are scheduled independently per cell. The eNodeB must therefore coordinate the allocation of MBSFN subframes across the MBSFN area while managing unicast scheduling within each cell. This coordination is a central design challenge of mixed-cell MBMS deployments.

The term was formally introduced in Release 14, although the underlying mixed-cell operation existed in earlier releases. Its introduction as a distinct defined term reflects the maturation of MBMS terminology and the need to clearly distinguish mixed cells from dedicated cells in specifications. In the 5G era, the analogous concept is the 5G MBS mixed cell, where multicast/broadcast services share gNB resources with unicast traffic.

Purpose & Motivation

The MBMS/Unicast-mixed cell exists to solve a fundamental deployment problem: how to offer broadcast and multicast services without sacrificing the spectrum and infrastructure needed for unicast traffic. Dedicated broadcast cells are expensive and inflexible, requiring separate coverage and offering no capacity for bidirectional services. The mixed cell allows operators to reuse existing unicast infrastructure for broadcast delivery, sharing radio resources dynamically and preserving investment.

Historically, early MBMS deployments in UMTS and LTE faced the challenge of integrating broadcast into networks designed primarily for unicast. The mixed-cell model emerged as the practical answer, and 3GPP specifications formalized it as the primary supported deployment option. By defining the mixed cell explicitly in Release 14, 3GPP provided a clear terminology for network planning, UE behaviour, and interoperability. The concept underpins the economics of MBMS: broadcast services become an incremental feature of an existing network rather than a separate overlay.

What changed in its specifications

The latest release-to-release comparison of specifications that define MBMS/Unicast-mixed cell. Each summary describes the whole specification, not only this term.

TS 36.300Rel-18 → Rel-19

Rel-19 added NTN IoT Phase 3 for LTE, covering regenerative payload S1 removal, Msg3 early data transmission, and ETWS/CMAS for NB-IoT NTN. It also added inter-RAT mobility from E-UTRAN terrestrial network to NR NTN, plus NR NTN feeder link switchover via handover.

Full comparison in TS 36.300 →
TS 36.304Rel-18 → Rel-19

Rel-19 adds NTN IoT Phase 3 for LTE to TS 36.304, changing sf-OperationMode and t-ModeSwitching, plus IoT NTN TDD support. Three further items are also added or changed in the same spec.

Full comparison in TS 36.304 →

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

Initial definition introduced: 'cell supporting both unicast and MBMS transmissions.' Formalized the mixed-cell concept as a distinct term alongside the MBMS-dedicated cell.

Definition carried over unchanged from Rel-14.

Definition carried over unchanged from Rel-14.

Definition carried over unchanged from Rel-14.

Definition carried over unchanged from Rel-14.

Definition carried over unchanged from Rel-14.

Defining Specifications

3GPP specifications that define or reference MBMS/Unicast-mixed cell, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 36.300 vj20 E-UTRAN Radio Interface Protocol Architecture Rel-19 read
TS 36.304 vj30 LTE UE Idle Mode Procedures Rel-19 read