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

Glossary term · Identifier

Mapped Cell ID

Mapped Cell Identifier

Identifier →

Mapped Cell ID is a Non-Terrestrial Network identifier that identifies a fixed geographical area rather than a moving satellite beam, allowing the network to present a stable cell identity to UEs as satellite beams sweep across Earth.

Introduced
Rel-17
Where
Radio Access Network › NG-RAN (5G)
Specifications
2 specs
Mapped Cell ID Description Purpose What changed Neighbours Detected Changes Specifications

Description

The Mapped Cell ID is an identifier concept introduced in 3GPP Release 17 specifically for Non-Terrestrial Networks (NTN), where access is provided by satellites (LEO, MEO, GEO) or high-altitude platforms rather than fixed terrestrial base stations. In terrestrial networks, a physical cell identity (PCI) and the associated cell are tied to a fixed antenna location, so a UE moving across the ground naturally changes serving cells as it moves. In NTN, the situation is inverted: the satellite moves rapidly (LEO satellites orbit the Earth in roughly 90 minutes), so a beam footprint sweeps across the ground, and a stationary UE would otherwise observe frequent, unnecessary cell changes even though it has not moved. The Mapped Cell ID resolves this by decoupling the identity presented to the UE from the moving physical beam.

The core idea is that the Mapped Cell ID corresponds to a fixed geographical area on the Earth's surface. As a satellite beam moves, the network maps the current physical beam/cell to the Mapped Cell ID associated with the geographic region currently covered. From the UE's perspective, the cell identity remains stable while the UE stays within the same geographical area, even though the physical radio resources serving it are changing. This mapping is maintained by the network (satellite payload and/or ground segment) and is transparent to the UE in the sense that the UE simply sees a consistent cell identity.

Architecturally, the Mapped Cell ID is defined in the RAN specifications TS 36.300 (E-UTRAN overall description) and TS 38.300 (NR overall description), which contain the NTN-specific additions. The mapping function sits with the gNB/eNB functionality hosted on the satellite or distributed between the satellite and the ground-based NTN gateway. When the beam footprint moves, the network updates which Mapped Cell ID applies to the beam, and mobility procedures (measurements, reselection, handover) can be anchored to the geographical area rather than to the transient beam.

The primary benefit is a dramatic reduction in unnecessary mobility signalling. Without a stable mapped identity, a stationary UE under a moving LEO beam would trigger repeated cell reselections or handovers, wasting radio resources, draining UE battery, and generating signalling load on the core network. By presenting a fixed geographical cell identity, the network can keep the UE anchored to a logical cell while the physical layer handles beam switching internally. This also simplifies tracking area and paging design, because the geographical mapping aligns logical cell boundaries with fixed regions.

Mapped Cell ID works alongside other NTN-specific concepts such as the moving beam, the satellite ephemeris (used by the UE to predict beam movement), and timing advance pre-compensation for the large propagation delays. It is one of the foundational enablers that make direct satellite access to 5G devices practical, and it carried forward into Rel-18 and Rel-19 as NTN was enhanced for coverage, mobility, and regulatory scenarios.

Purpose & Motivation

Terrestrial cellular design assumes that cells are fixed to the ground and that a UE's cell changes because the UE moves. NTN breaks this assumption: LEO satellites travel at roughly 7.5 km/s, so their beams sweep across the Earth's surface and a stationary UE would be handed over between beams every few tens of seconds. This creates excessive measurement reporting, handover signalling, paging churn, and battery drain, and it complicates core-network mobility and tracking-area management.

The Mapped Cell ID was created to restore a stable, geography-anchored identity in a network whose radio topology is inherently mobile. By mapping the moving physical beam to a fixed geographical area identifier, the standard allows the network to hide beam dynamics from higher layers and from the UE's mobility state machine. This preserves the familiar cellular model — a cell is a place — while the physical layer performs beam steering and switching underneath.

This concept was motivated by the commercial push to connect unmodified or minimally modified 5G devices directly to satellites (direct-to-device NTN), where simplicity at the UE and minimal signalling are essential. It also supports regulatory and emergency-service requirements that depend on knowing a device's geographical serving area. The Mapped Cell ID therefore exists to reconcile the physics of satellite constellations with the architectural conventions of 3GPP networks.

What changed in its specifications

The latest release-to-release comparison of specifications that define Mapped Cell ID. 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 38.300Rel-18 → Rel-19

Rel-19 adds multi-hop L2 UE-to-Network relay for NR sidelink as the largest item. It also adds low-power wake-up signal and receiver (LP-WUS/WUR) text, on-demand SSB and SIB1 for network energy savings, and sub-band full duplex for TDD carriers.

Full comparison in TS 38.300 →

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 IoT NTN about constructing the Mapped Cell ID TS 36.300CR1376

Defining Specifications

3GPP specifications that define or reference Mapped Cell ID, 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 38.300 vj40 NR and NG-RAN Overall Description Rel-19 read