RPLMN

Registered Public Land Mobile Network

Mobility →
Introduced in Rel-4

RPLMN is the Public Land Mobile Network where a User Equipment is currently registered and authorized to receive cellular services.

Category
Mobility
Introduced
Rel-4
Where
Radio Access Network › NG-RAN (5G)
Specifications
5 specs
RPLMN Description Purpose Related Classification Detected Changes Specifications

Description

The Registered Public Land Mobile Network (RPLMN) is a core identifier within 3GPP mobility management protocols. It represents the specific Public Land Mobile Network (identified by a Mobile Country Code and Mobile Network Code - MCC-MNC) where a User Equipment (UE) has successfully performed a registration procedure and is currently considered 'attached' or 'registered'. This registration grants the UE authorization to access that network's services, including voice, data, and supplementary services. The RPLMN is stored in the UE's non-volatile memory and in the network's subscriber database (e.g., HSS/UDM). It is a key parameter used by the UE and the network to manage the UE's state and service continuity.

Architecturally, the RPLMN is central to the network selection and reselection processes defined in the Non-Access Stratum (NAS) protocols. When a UE is powered on or loses coverage, it searches for available PLMNs. The selection algorithm prioritizes the RPLMN if it is available, as this is the network the UE is already subscribed to for service. The concept is integral across 3GPP generations, from GSM/GPRS (where it might be referred to in the context of the Location Area) through UMTS and LTE, to 5G. In 5G, the RPLMN is maintained as part of the UE's 5G Mobility Management (5GMM) context and is crucial for initial registration and mobility registration updates.

How it works involves a multi-step interaction between the UE and the core network. Upon successful authentication and registration with a network, that network's PLMN ID becomes the UE's RPLMN. The network confirms this registration in its core network entities. The UE will then periodically or upon specific triggers (like movement) report its location to this RPLMN. If the UE moves out of the RPLMN's coverage area, it may register with a new PLMN (which then becomes the new RPLMN) if a roaming agreement exists, or it may attempt to re-select the RPLMN when it returns to coverage. The RPLMN is distinct from but related to the Equivalent PLMN (EPLMN) list, which contains networks considered equivalent to the RPLMN for cell reselection and handover purposes, facilitating seamless mobility.

Purpose & Motivation

The RPLMN concept was created to provide a clear, unambiguous reference point for a mobile device's 'home' or currently active network within a global ecosystem of multiple, independent operator networks. It solves the fundamental problem of network identity and service authorization in a roaming environment. Before such standardized concepts, managing subscriber mobility across different operator domains would be chaotic and insecure.

Historically, as cellular networks evolved from single-operator deployments to national and international roaming consortia, a mechanism was needed to track where a subscriber was registered and which network was responsible for providing and billing for services at any given time. The RPLMN provides this anchor. It addresses the limitation of simply detecting a radio signal by tying service access to a formal registration and subscription relationship. It enables features like roaming (by allowing a visited PLMN to know the subscriber's home PLMN for billing and service profile retrieval), prioritized network selection (always try to use your registered network first), and efficient mobility management (the network knows which set of cells and tracking areas are associated with a given RPLMN). Its persistence in the UE's memory allows for faster service recovery after power cycles or temporary loss of signal.

Classification

Part ofPLMN
Related approachesEPLMNVPLMN

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-19 1 change

In Release 19, a specific enhancement was introduced to handle the ECRATU list when the Registered PLMN (RPLMN) is not part of the Equivalent PLMN (EPLMN) set. This change addresses the scenario where the UE, which has successfully performed location registration on the RPLMN, must manage the ECRATU list appropriately during mobility. The update ensures proper NAS procedure behavior when roaming outside the registered area defined for the RPLMN.

  • ECRATU list handling when RPLMN is not part of EPLMN TS 24.501CR6781

Explore further

Broader topics and technologies where RPLMN plays a role.

Defining Specifications

3GPP specifications that define or reference RPLMN, 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 24.501 vj50 5G NAS Protocols Specification Rel-19
TS 36.331 vj00 LTE RRC Protocol Specification Rel-19
TS 37.320 vj00 Minimization of Drive Tests (MDT) Overview Rel-19
TS 38.331 vj00 NR Radio Resource Control (RRC) Protocol Specification 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.