Update Notification

Description

The Update Notification (UPN) is a specific GTPv2-C (GPRS Tunnelling Protocol version 2 for Control plane) message defined in 3GPP TS 29.275. It operates on the S5 interface (within the same PLMN) or S8 interface (between PLMNs) connecting the Serving Gateway (SGW) and the Packet Data Network Gateway (PGW) in the Evolved Packet Core (EPC). The primary function of the UPN message is to inform the PGW about a change in the SGW's state or configuration that is relevant to the management of active PDN connections and EPS bearers. This is a critical mechanism for maintaining session continuity and ensuring the PGW has an accurate view of the network topology for packet routing.

When an event occurs that necessitates an update, such as an SGW change during an inter-SGW handover, the SGW constructs and sends a UPN message to the PGW. This message contains Information Elements (IEs) that specify the nature of the change. Key IEs include the Cause, which indicates the reason for the notification (e.g., SGW change due to UE mobility), and the SGW's F-TEID (Fully Qualified Tunnel Endpoint Identifier) for the control plane, which the PGW must use for subsequent signaling. Upon receiving the UPN, the PGW processes the information, updates its internal context for the affected UE(s), and responds with an Update Notification Acknowledge (UPA) message. This handshake ensures both nodes are synchronized.

The UPN mechanism is integral to mobility management, particularly in scenarios like Tracking Area Updates (TAU) or handovers that trigger an SGW relocation. It allows the PGW, which is the anchor point for the UE's IP session, to be promptly informed of the new SGW serving the UE. This enables the PGW to correctly route downlink data packets through the new GTP-U tunnel established with the new SGW. Furthermore, UPN can be used for other administrative or recovery purposes, such as notifying the PGW of an SGW restart, allowing the PGW to take appropriate actions like re-establishing bearers or clearing stale contexts.

Purpose & Motivation

The Update Notification (UPN) was introduced to address the need for reliable state synchronization between the SGW and PGW in the EPC architecture. Prior to its formal definition, mechanisms for informing the anchor gateway (PGW) of changes in the intermediate gateway (SGW) were less standardized or relied on implicit triggers, which could lead to session disruptions or suboptimal routing during mobility events. The creation of a dedicated GTPv2-C message provided a clear, reliable, and mandatory procedure for this critical update.

The core problem it solves is ensuring the PGW maintains an accurate and timely mapping between a UE's IP address (anchored at the PGW) and the current GTP-U tunnel endpoint (the SGW) for downlink traffic delivery. Without an explicit notification like UPN, a PGW might continue sending packets to a previous SGW after a handover, causing packet loss. The UPN protocol ensures seamless handovers and service continuity, which are fundamental requirements for mobile broadband services. Its introduction in Release 11 was part of the broader effort to solidify and optimize the EPC signaling procedures for LTE networks.