URPP-SGSN

User Reachability Request Parameter for SGSN

Core Network
Introduced in Rel-9
URPP-SGSN is a specific parameter used in the GTP-C (GPRS Tunnelling Protocol - Control plane) signaling between a Serving GPRS Support Node (SGSN) and a Gateway GPRS Support Node (GGSN) or Packet Data Network Gateway (PGW) in 2G/3G/4G networks. It indicates the SGSN's request for the GGSN/PGW to provide notifications about the UE's reachability status (e.g., when it becomes reachable after being unreachable), enabling efficient downlink data delivery and paging optimization.

Description

The User Reachability Request Parameter for SGSN (URPP-SGSN) is a detailed information element within the GPRS Tunnelling Protocol for the control plane (GTP-C), specified in 3GPP TS 29.272 (Evolved Packet System; Mobility Management Entity and Serving GPRS Support Node related interfaces). It is used in the communication between the Serving GPRS Support Node (SGSN) – which manages mobility and session for UEs in 2G (GERAN) and 3G (UTRAN) access – and the Gateway GPRS Support Node (GGSN) in GPRS/UMTS cores, or the Packet Data Network Gateway (PGW) in the Evolved Packet Core (EPC). Its primary function is to convey the SGSN's request regarding how it wishes to be informed about changes in the User Equipment's (UE) reachability status from the gateway's perspective.

Operationally, the URPP-SGSN is included in GTP-C messages like Create Session Request, Modify Bearer Request, or specific Context Request/Response messages. The parameter contains flags that specify the SGSN's preferences. A key flag is the 'Request for UE Reachability Notification'. When this flag is set, it instructs the GGSN/PGW to monitor for the UE transitioning from an unreachable state (e.g., due to power-off, out-of-coverage, or extended idle timers) back to a reachable state. If such a transition is detected by the gateway (often because it receives downlink data for a UE it had marked as unreachable), the GGSN/PGW will then send a Downlink Data Notification (DDN) message to the SGSN, even if it might not have done so otherwise. This triggers the SGSN to initiate paging procedures to locate and establish a connection with the UE.

This mechanism is a crucial part of network efficiency and power saving for UEs. Without URPP-SGSN, a GGSN/PGW might silently discard downlink data packets for a UE it believes is unreachable, or it might aggressively send DDN messages that lead to unnecessary paging and signaling load. By allowing the SGSN to explicitly request notifications only when needed, the network optimizes the trade-off between ensuring timely data delivery and conserving radio and core network signaling resources. The SGSN's decision to set the flag is based on its local policy, subscriber profile, and the nature of the activated Packet Data Protocol (PDP) context or PDN connection.

Purpose & Motivation

The URPP-SGSN parameter was introduced to address inefficiencies in downlink data handling and paging for mobile devices, particularly as networks evolved to support always-on IP connectivity and diverse data services. In early GPRS releases, the mechanisms for notifying the SGSN about pending downlink data were less refined, potentially leading to either missed data (if the gateway gave up too easily) or excessive, battery-draining paging (if the gateway was too aggressive). The problem was especially relevant for smartphones and M2M devices with intermittent connectivity or long sleep cycles.

URPP-SGSN solves this by putting control in the hands of the SGSN, which has more direct knowledge of the UE's radio state and mobility patterns. It allows the SGSN to tailor the gateway's behavior on a per-session basis. For example, for a background synchronization service, the SGSN might not request reachability notifications, accepting that data can be delayed. In contrast, for a real-time messaging service, it would request notifications to ensure prompt delivery. This granular control optimizes network resource usage (reducing unnecessary paging signaling) and improves the user experience by ensuring timely delivery for important data flows while allowing less critical flows to be handled in a more network- and battery-efficient manner. Its specification in TS 29.272, starting from Release 9, was part of the broader EPC standardization that refined the interactions between the SGSN (for legacy access) and the new PGW entity.

Key Features

  • GTP-C information element defined in TS 29.272 for SGSN-to-GGSN/PGW signaling
  • Contains flags to request UE reachability status notifications from the gateway
  • Enables optimized triggering of Downlink Data Notification (DDN) messages
  • Allows SGSN to control paging behavior based on per-session/service policies
  • Reduces unnecessary core and radio network signaling for unreachable UEs
  • Supports efficient downlink data delivery for always-on PDN connections

Evolution Across Releases

Rel-9 Initial

Initial specification of the URPP-SGSN parameter within TS 29.272 as part of the Evolved Packet Core (EPC) enhancements. It was defined to optimize the interaction between the SGSN (for 2G/3G access) and the new Packet Data Network Gateway (PGW), providing the SGSN with control over reachability notifications for UEs attached via legacy radio access.

Clarifications and potential bug fixes to the URPP-SGSN handling procedures within GTP-C signaling. Ensured consistent interpretation and implementation of the parameter flags between SGSN and PGW/GGSN nodes from different vendors.

Continued maintenance and potential enhancements related to inter-RAT mobility scenarios involving SGSN and MME. The URPP-SGSN parameter's role was reaffirmed in procedures for handovers between 2G/3G and 4G LTE access.

Further refinements in the context of network optimizations for Machine-Type Communication (MTC). The use of URPP-SGSN could be aligned with new MTC features for extended idle modes and efficient handling of small data transmissions from IoT devices.

Defining Specifications

SpecificationTitle
TS 29.272 3GPP TS 29.272