Description
An MBSFN Area Reserved Cell is a cell located within an MBSFN Area that does not participate in the MBSFN transmission. While the majority of cells in an MBSFN Area are coordinated to transmit the same MBSFN signal simultaneously, reserved cells are excluded from this coordinated transmission. They are still geographically within the area's footprint, but for operational or technical reasons they do not contribute to the single-frequency-network broadcast. This concept is defined in TS 36.300 and managed through the network management specifications TS 32.421, 32.422, and 32.442.
The primary constraint on a reserved cell is that it may be allowed to transmit for other services (e.g., normal unicast LTE traffic) but only at restricted power on the resource elements allocated for MBSFN transmission. This restriction is essential because the MBSFN transmission relies on constructive combination of signals from contributing cells. If a reserved cell transmitted at normal power on the same time-frequency resources, it would create harmful interference to UEs receiving the MBSFN transmission in neighboring cells, degrading the single-frequency-network gain. By limiting its transmit power on those resources, the reserved cell minimizes interference while still being able to serve its own unicast traffic on other resources.
Reserved cells are used in several practical scenarios. An operator may designate a cell as reserved when it cannot be synchronized with the MBSFN Synchronization Area, when its antenna configuration or propagation characteristics would not contribute usefully, or when local traffic demands make unicast service more valuable than MBSFN participation. Reserved cells also provide flexibility during network planning and deployment, allowing an operator to roll out MBSFN coverage incrementally or to exclude problematic cells without redesigning the entire area.
From the UE perspective, reserved cells are transparent in the sense that the UE does not need to know which cells are reserved; it simply receives the MBSFN transmission from contributing cells. However, the network management system must accurately configure the reserved cell list so that the MBSFN coordination and interference management work correctly. The management specifications define how reserved cells are configured and how their restricted-power behavior on MBSFN resources is enforced.
The MBSFN Area Reserved Cell concept is important for the operational viability of MBSFN. It gives operators a tool to handle cells that cannot or should not participate in coordinated broadcast, while protecting the quality of the MBSFN transmission for the rest of the area. It reflects the practical reality that real networks have heterogeneous cells and that coordination must accommodate exceptions without sacrificing the benefits of single-frequency-network operation.
Purpose & Motivation
The MBSFN Area Reserved Cell concept exists to handle exceptions in MBSFN coordination without compromising the single-frequency-network transmission. MBSFN relies on all cells in an area transmitting the same signal simultaneously so that signals combine constructively at the UE. However, not every cell within an area's geographic footprint can or should participate: some may lack synchronization, have unsuitable antenna configurations, or need to prioritize local unicast traffic.
Without a reserved-cell mechanism, such cells would either have to be excluded from the area entirely (complicating area planning) or would transmit on MBSFN resources and cause interference, destroying the MBSFN gain. The reserved cell concept solves this by allowing cells to remain within the area but not contribute to the transmission, while restricting their power on MBSFN resources to protect neighboring MBSFN reception.
This provides operational flexibility for incremental deployment, network planning, and interference management. It addressed the limitation that MBSFN areas had to be perfectly homogeneous, and it remains a practical tool for operators managing real-world heterogeneity in LTE broadcast deployments.
What changed in its specifications
The latest release-to-release comparison of specifications that define MBSFN Area Reserved Cell. Each summary describes the whole specification, not only this term.
Rel-19 adds RRC report collection to TS 32.421 for NG-RAN, covering RLF, RCEF, RA, SHR, SPR and MHI reports. It also introduces new clauses, definitions and requirements for subscriber and equipment trace and QoE collection management.
Full comparison in TS 32.421 →C-MDT for non-split and split RAN architectures, RRC reporting trace sessions, trace failure notification, and new parameters.
Full comparison in TS 32.422 →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.
The definition in the available wording refers to 3GPP TS 36.300, indicating that the reserved cell concept was already established in the LTE architecture specification. The term was maintained as a reference to the architectural definition rather than restated in full.
The definition was expanded from a short reference to TS 36.300 into a full textual description: a cell within an MBSFN Area that does not contribute to the MBSFN transmission, may transmit other services but at restricted power on resources allocated for MBSFN transmission.
The available definition wording is too short to reliably compare with the previous release, so the specific change cannot be assessed from the quoted text. The term reverted to a reference to TS 36.300 (with a different reference number), but the substantive change cannot be determined from the available wording.
Defining Specifications
3GPP specifications that define or reference MBSFN Area Reserved Cell, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 32.421 vj40 | Subscriber & Equipment Trace Concepts & Requirements | Rel-19 read |
| TS 32.422 vk30 | Trace, MDT and UE Measurement Control | Rel-20 read |
| TS 32.442 vj00 | Trace Management IRP: Information Service | Rel-19 read |
| TS 36.300 vj20 | E-UTRAN Radio Interface Protocol Architecture | Rel-19 read |