Update Notification Acknowledgment

Description

The Update Notification Acknowledgment (UPA) is a specific Diameter Answer message defined in the 3GPP S6a (for LTE/EPC) and S6d (for GTP-based SGSN to HSS) interface specifications. It is the direct response to the Update Notification Request (UPR) command. The S6a/S6d interface is used for authentication, authorization, and mobility management between the Mobility Management Entity (MME) or Serving GPRS Support Node (SGSN) and the Home Subscriber Server (HSS). The UPR/UPA dialog is a critical mechanism for the HSS to proactively notify the MME/SGSN about changes in a subscriber's profile or status stored in the HSS.

Technically, the UPA is a Diameter message with the Command-Code set to 316 (Update-Notification) and the 'R' bit cleared in the Command Flags field, indicating it is an Answer. It is sent from the MME or SGSN back to the HSS. The primary function of the UPA is to inform the HSS that the MME/SGSN has successfully received and processed the corresponding UPR. The UPA message carries a Result-Code AVP (Attribute-Value Pair) which indicates the outcome of the processing. A successful acknowledgment would use a Result-Code like DIAMETER_SUCCESS (2001).

The UPA message may also contain other relevant AVPs. For instance, if the UPR requested the MME to send user data, the UPA could include the requested data in specific AVPs. The exchange ensures synchronization between the HSS (the master database) and the serving node (MME/SGSN) regarding subscriber information. This is crucial for enforcing changes like updated QoS profiles, subscribed Access Point Names (APNs), or barring status in real-time, without waiting for the next periodic update or attach procedure. The reliable delivery of the UPA confirms to the HSS that the serving node is now applying the updated subscriber parameters, maintaining consistent service delivery across the network.

Purpose & Motivation

The UPA exists as part of a reliable notification protocol to keep subscriber data synchronized between the central repository (HSS) and the distributed network nodes (MME/SGSN) that enforce policies and manage sessions. It solves the problem of stale or inconsistent subscriber data in the serving node, which could lead to service issues, incorrect charging, or security vulnerabilities. Before such mechanisms, updating a subscriber's profile often required the subscriber to re-attach to the network or relied on infrequent synchronization, which was inefficient and slow.

Introduced in the context of the Evolved Packet Core (EPC) and Diameter-based interfaces (Release 11 for S6a refinement), the UPR/UPA procedure provides a push model for data updates. The motivation was to support dynamic policy changes and real-time service modifications. For example, an operator could instantly disable a lost device (via IMSI detach) or upgrade a user's service plan, and the HSS could immediately notify the serving MME, which would acknowledge with a UPA. This ensures network responsiveness and enables advanced, real-time subscriber management features, improving both operational efficiency and customer experience.

Key Features

• Diameter Answer message (Command-Code 316) on the S6a/S6d interface.
• Sent by MME or SGSN to acknowledge receipt and processing of an Update Notification Request (UPR).
• Contains a Result-Code AVP indicating success or failure of the update.
• Enables reliable synchronization of subscriber data between HSS and serving node.
• Supports real-time enforcement of subscriber profile changes (e.g., QoS, APN, barring).
• Part of a proactive notification mechanism initiated by the HSS.

Evolution Across Releases

Defining Specifications