URRP-MME

User Reachability Request Parameter for MME

Core Network →
Introduced in Rel-8

URRP-MME is a parameter in the 4G Evolved Packet Core that an SGW uses to request an MME to page an idle UE and initiate its reconnection for downlink data delivery.

Category
Core Network
Introduced
Rel-8
Where
Core Network › Evolved Packet Core
Specifications
2 specs
URRP-MME Description Purpose Related Classification Detected Changes Specifications

Description

The User Reachability Request Parameter for MME (URRP-MME) is a signaling element used in the 4G Evolved Packet Core (EPC) on the S11 interface between the Serving Gateway (SGW) and the Mobility Management Entity (MME). Its purpose is to allow the SGW to request the MME to execute procedures to make a UE reachable when the SGW receives downlink data for an EPS bearer of a UE that is in ECM-IDLE state. The SGW, which buffers the downlink packets, includes the URRP-MME within a Downlink Data Notification (DDN) message sent to the MME.

Upon receiving the DDN with URRP-MME, the MME initiates the network-triggered service request procedure. This involves the MME first sending a Paging message to all eNodeBs within the UE's registered Tracking Area(s) to locate the UE. Once the UE responds with a Service Request, the MME coordinates with the eNodeB and SGW to re-activate the EPS bearers, transitioning the UE back to ECM-CONNECTED state and establishing the S1-U user plane tunnel. The MME then sends a Downlink Data Notification Acknowledge to the SGW, which can then forward the buffered data. The parameter may also carry information such as the EPS Bearer ID for which data is waiting, allowing the MME to prioritize certain bearers.

Architecturally, URRP-MME is a critical component of the EPC's power-saving and mobility management design. It enables the network to maintain IP session continuity while allowing UEs to enter a battery-efficient idle state. The SGW acts as the mobility anchor and data path trigger, while the MME handles the actual paging and signaling connection management. This clear functional split is a hallmark of EPC design. The procedure ensures that paging is only performed when necessary (i.e., when downlink data arrives), optimizing radio and core network signaling resources. The mechanism is also used for other network-initiated procedures, such as request for PDN connectivity or bearer modification initiated by the PCRF.

Purpose & Motivation

URRP-MME was defined in the initial LTE/EPC specifications (Release 8) to solve the fundamental problem of delivering downlink data to a mobile UE that is in a power-saving idle state. Prior cellular systems had similar concepts, but LTE's flat IP architecture and strict separation between the user plane (SGW) and control plane (MME) required a standardized, efficient signaling mechanism between them. The URRP-MME formalizes this trigger within the DDN message.

It addresses the limitation of not having a persistent user plane connection to an idle UE. Without this mechanism, the network would either need to keep UEs always connected (wasting battery and radio resources) or would be unable to deliver data, breaking always-on IP connectivity. The URRP-MME enables the 'always reachable' paradigm for IP services, which was crucial for the adoption of LTE for smartphone applications relying on push notifications (email, messaging, etc.).

Furthermore, it provides a controlled gateway for network-initiated actions. Beyond simple data arrival, the URRP-MME mechanism allows the core network (via PCRF or other entities) to trigger the MME to bring a UE to connected state for policy-driven reasons, such as establishing a dedicated bearer for a new service. This solved the problem of how the network could proactively manage UE bearer resources based on external service requests or changing subscription profiles, enabling advanced QoS and charging models in LTE.

Classification

Part ofMME
Related approachesSGW

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (17 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Studied in Rel-8, normative work from Rel-15.

Rel-15 10 changes

In Release 15, the URRP-MME function was enhanced to allow the MME to provide a "Homogenous Support of IMS Voice over PS Sessions" indication to the HSS upon request. This indication, provided per Tracking Area list along with the last radio contact time and current RAT type, helps the HSS avoid unnecessary reachability queries. Additionally, clarifications were made for UE reachability monitoring event handling over the S6a/S6d interface.

  • Additional parameters for NB-IoT UE Uu operation optimisation TS 23.401CR3350
  • Handling of multiple CP parameter sets TS 23.401CR3286
  • Modify Bearer Request during TAU TS 23.401CR3353
  • Alignment with CT WG1 for handling of Connection Resume Requests at Service Gap TS 23.401CR3413
  • MME request for UE Radio Capabilities TS 23.401CR3440
  • UE CIoT capability in RRC Connection Establishment request for TAU TS 23.401CR3356

+ 4 more changes

Rel-16 5 changes

In Release 16, the URRP-MME function was enhanced to include a **Subscriber RRM Group as an additional parameter to the SPID/RFSP Index**, providing the E-UTRAN with more granular information for applying UE-specific radio resource management strategies. Furthermore, the parameters within the **Create Session Request procedure were aligned with the definitions in TS 29.274** to ensure consistency across the core network interfaces. These updates provided additional tools for network-controlled RRM and improved signalling alignment.

  • Subscriber RRM Group as additional parameter to SPID/RFSP TS 23.401CR3499
  • Aligning Create Session Request parameters with 29.274 TS 23.401CR3524
  • SMS transmission in Communication pattern parameters TS 23.401CR3552
  • Subscription parameter for NR-U access restriction TS 23.401CR3586
  • Subscribed PC5 QoS Parameters for NR V2X TS 29.272CR0817
Rel-17 1 change

In Release 17, the URRP-MME function was updated with a terminology alignment, specifically the removal of "Leaving" from the "Leaving/Release Request indication." This change clarifies the parameter used by the MME when reporting on user reachability, such as in a Monitoring Report message, ensuring consistency in the network's reachability management procedures for a UE in ECM-IDLE or ECM-CONNECTED state.

  • Terminology alignment: Removal of Leaving from the Leaving/Release Request indication TS 23.401CR3637
Rel-18 1 change

In Release 18, the URRP-MME function was enhanced to include a "Reachability Cause" parameter for immediate reports. This addition allows the MME to provide specific context, such as the reason for a reachability event, when sending a Monitoring Report message to the address indicated in a related Monitoring Request. This improves the granularity of reachability information provided by the network.

  • Reachability Cause in immediate reports TS 29.272CR0844

Explore further

Broader topics and technologies where URRP-MME plays a role.

Defining Specifications

3GPP specifications that define or reference URRP-MME, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.401 vj50 Evolved Packet System (EPS) Stage 2 Description Rel-19
TS 29.272 vj40 Diameter Interfaces for MME/SGSN Rel-19