Description
Regionally Provided Service (RPS) is a concept in 3GPP that defines a service entitlement to only certain geographical part(s) of a Public Land Mobile Network (PLMN), as controlled by the network operator. This means that a subscriber may have access to a particular service only when located within a specific region of the network, and outside that region, the service may be denied or restricted. RPS is used to enable location-based service offerings, such as regional tariffs, localized content, or regulatory restrictions. It is defined in 3GPP TS 21.905 (Vocabulary) and TS 22.011 (Service accessibility).
The implementation of RPS involves the network operator configuring geographical zones within the PLMN. These zones can be defined by various means, such as tracking areas, cell identities, or geographical coordinates. When a UE attempts to access a service, the network checks the UE's current location against the service entitlement. If the UE is within an allowed region, the service is granted; otherwise, it is denied. This check can be performed by the core network nodes, such as the Mobility Management Entity (MME) or Access and Mobility Management Function (AMF), in conjunction with the Unified Data Management (UDM) or Home Subscriber Server (HSS), which store the subscriber's service profile including any regional restrictions.
RPS is particularly relevant for services that are subject to regional licensing or content rights. For example, a mobile TV service might only be available in certain countries or regions due to broadcasting rights. Similarly, an operator might offer a cheaper tariff for calls made within a specific home zone. RPS enables such offerings by providing a standardized mechanism to enforce geographical restrictions. It also supports emergency services, where the network may need to restrict certain services to specific areas during disasters or network congestion.
Architecturally, RPS relies on the network's ability to determine the UE's location and to enforce policies based on that location. This involves interactions between the access network (which provides cell or tracking area information), the core network (which manages mobility and session management), and the subscriber database (which holds service entitlements). The enforcement can be done at various levels, such as at the session management function (SMF) for data services or at the MME/AMF for mobility management. The network may also use additional location services (LCS) to obtain more precise location information if needed.
The concept of RPS has been present since Rel-4 and has remained largely unchanged in its definition, although the wording was slightly refined in Rel-19 to explicitly state 'Regionally Provided Service is defined as...'. This stability reflects the enduring need for regional service differentiation in mobile networks. As networks evolve towards 5G and beyond, RPS continues to be a valuable tool for operators to comply with regulations, manage content rights, and offer tailored services to different market segments.
Purpose & Motivation
Regionally Provided Service exists to allow network operators to offer services that are restricted to specific geographical areas. This is necessary for several reasons: regulatory compliance (e.g., lawful interception or emergency services may only be available in certain regions), content licensing (e.g., streaming services may have regional rights), and commercial differentiation (e.g., regional pricing plans). Without a standardized concept like RPS, operators would have to implement proprietary mechanisms, leading to interoperability issues and complexity.
Historically, the need for regional service control became apparent as mobile networks expanded and services became more diverse. In the early days of GSM, services were mostly nationwide, but as networks grew and new services emerged, the ability to restrict services to certain areas became important. The introduction of RPS in Rel-4 provided a formal definition and framework for such restrictions, enabling consistent implementation across vendors.
RPS solves the problem of enforcing geographical entitlements in a multi-vendor, multi-technology environment. It provides a clear definition that can be used in specifications and implementations, ensuring that different network elements interpret regional restrictions consistently. This is crucial for services that cross network boundaries or involve roaming, where the home network's entitlements must be enforced by the visited network. By standardizing the concept, 3GPP enables operators to offer innovative location-based services while maintaining interoperability and regulatory compliance.
What changed in its specifications
The latest release-to-release comparison of specifications that define Regionally Provided Service. Each summary describes the whole specification, not only this term.
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 →Rel-19 adds an optional Operator Controlled Lower Selection-priority PLMN Selector list, stored in USIM or ME, used during PLMN selection.
Full comparison in TS 22.011 →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.
Defining Specifications
3GPP specifications that define or reference Regionally Provided Service, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj20 | 3GPP Terminology and Definitions | Rel-19 read |
| TS 22.011 vl00 | Service Access and Roaming Procedures | Rel-21 read |