Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Services

SNA

Spending-Status-Notification-Answer

Services →

SNA is a Diameter protocol message sent from an Online Charging System (OCS) to a network function in response to a request, conveying credit control decisions like granting service units or denying a request.

Introduced
Rel-5
Where
Core Network › Evolved Packet Core
Specifications
9 specs
Also in
Radio Access Network
SNA Description Purpose What changed Neighbours Specifications

Description

The Spending-Status-Notification-Answer (SNA) is a critical Diameter command within the 3GPP Ro reference point, which is used for online credit control. It operates as part of the Diameter Credit-Control Application (DCCA) as defined in IETF RFC 4006, but with 3GPP-specific extensions and AVPs (Attribute-Value Pairs). This message is the response from the Online Charging System (OCS) to a network element acting as a Charging Trigger Function (CTF), such as a Policy and Charging Rules Function (PCRF) or an application server, which had previously sent a Spending-Status-Notification-Request (SNR).

The architecture involves the CTF detecting a service event that requires credit authorization (e.g., initiating a data session, an IMS voice call, or an application service). The CTF formulates an SNR message containing details like the subscriber's identity, requested service, and requested service units. This is sent to the OCS via the Ro interface. The OCS then processes this request: it queries the subscriber's account balance, applies relevant tariff and policy rules, and makes a credit control decision. The SNA message is the vessel for this decision. It contains a Result-Code AVP indicating success or failure (e.g., DIAMETER_SUCCESS, DIAMETER_CREDIT_LIMIT_REACHED) and, if successful, includes a Granted-Service-Unit AVP specifying the amount of quota (time, volume, or money) granted for the service.

How it works is inherently stateful. The OCS maintains a credit control session for the subscriber. The SNA message may instruct the CTF to continue the service, terminate it, or trigger a re-authorization after the granted units are consumed. It can also include AVPs for redirecting the subscriber to a top-up portal, indicating the validity time of the quota, or providing information about remaining balances. The SNA is thus the central mechanism for real-time, policy-driven service authorization and spending control in prepaid and hybrid billing scenarios, enabling services like data boost packs, spend limit controls, and real-time notifications.

Purpose & Motivation

The SNA message was created to fulfill the requirements of sophisticated Online Charging Systems (OCS) in 3GPP networks. Traditional offline charging (postpaid) could not support real-time prepaid services or spending controls. The SNA, as part of the Ro interface protocol, solves the problem of real-time authorization and quota management. It allows network operators to offer prepaid services for voice, SMS, and data with immediate control, preventing revenue leakage and enabling advanced features like fair usage policies and service differentiation.

Historically, before standardized online charging interfaces, vendors implemented proprietary protocols, leading to interoperability issues and stifling innovation. The standardization of the Ro interface and the SNA command in 3GPP Release 5 provided a uniform way for any network function (GGSN, P-CSCF, AS) to request and receive credit decisions from any compliant OCS. This addressed the limitations of fragmented, vendor-locked solutions. It motivated the creation of a vibrant ecosystem of charging systems and network elements, enabling complex service bundles, real-time balance checks, and seamless integration with IMS and later 5G service-based architectures. The SNA is a key enabler for the commercial models that define modern mobile services.

What changed in its specifications

The latest release-to-release comparison of specifications that define SNA. Each summary describes the whole specification, not only this term.

TS 23.009Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 23.009: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 23.009 →
TS 25.401Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 25.401: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 25.401 →

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-5 Initial

The Spending-Status-Notification-Answer was initially introduced as part of the Online Charging System (OCS) and the Ro reference point specification. It defined the basic Diameter-based protocol for real-time credit control, enabling network functions to query the OCS and receive authorized quotas for prepaid services in UMTS and IMS networks.

Defining Specifications

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

SpecificationTitleRelease
TS 23.009 vj00 Handover Procedures in PLMNs Rel-19 read
TS 23.700 vk10 AI/ML Application Layer Support Phase 2 Rel-20 read
TS 23.851 v610 Network Sharing Architecture for 3G Systems Rel-6 read
TS 25.401 vj00 UTRAN Overall Architecture Rel-19 read
TS 25.410 vj00 Iu Interface Introduction for UTRAN Rel-19 read
TS 25.413 vj00 Radio Access Network Application Part (RANAP) Rel-19 read
TS 25.423 vj00 UTRAN RNSAP Specification Rel-19 read
TS 29.213 vj30 PCC Procedures and Flows Rel-19 read
TS 29.219 vj00 Sy Reference Point Stage 3 Specification Rel-19 read