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

Glossary term · QoS

Spending limit report

Spending Limit Report

QoS →

Spending limit report is a notification containing the current policy counter status, generated from the OCS to the PCRF via the Sy reference point.

Introduced
Rel-11
Where
Core Network › 5G Core
Specifications
5 specs
Spending limit report Description Purpose What changed Neighbours Detected Changes Specifications

Description

A spending limit report is a notification message sent from the Online Charging System (OCS) to the Policy and Charging Rules Function (PCRF) in 4G networks, or from the Charging Function (CHF) to the Policy Control Function (PCF) in 5G networks. It contains the current status of one or more policy counters associated with a subscriber. The report is generated when a policy counter status changes, such as when a spending limit is reached or when the counter value crosses a threshold. This mechanism allows the PCRF/PCF to make informed policy decisions in real-time, such as modifying QoS, blocking services, or redirecting traffic.

The spending limit report is a key component of the Sy reference point (in 4G) and the N28 interface (in 5G). The PCRF/PCF subscribes to policy counter status notifications from the OCS/CHF, specifying the policy counters of interest and the conditions for reporting (e.g., threshold values). When the OCS/CHF detects a status change, it sends a spending limit report to the PCRF/PCF. The report includes information such as the policy counter identifier, its current status (e.g., active, inactive, or the remaining quota), and possibly the spending limit value. The PCRF/PCF then evaluates this information and may update the PCC rules accordingly.

The report can be triggered by various events: when the policy counter reaches a certain percentage of the spending limit, when it exceeds the limit, or when it is reset. This enables operators to implement tiered notifications, such as warning the subscriber when they are nearing their limit, and then taking action when the limit is exceeded. The spending limit report can also be used for other purposes, such as applying promotional offers or adjusting QoS based on usage patterns.

In terms of architecture, the spending limit report is part of the policy and charging control framework. The OCS/CHF maintains the policy counters and monitors usage in real-time. The PCRF/PCF acts as the policy decision point, enforcing rules through the PCEF (in 4G) or SMF/UPF (in 5G). The Sy/N28 interface provides the signaling between these entities, using protocols such as Diameter (for Sy) or HTTP/2 (for N28). The spending limit report is typically encoded as a Diameter AVP (Attribute-Value Pair) or a JSON object, depending on the interface.

The introduction of the spending limit report in Release 11 addressed the need for dynamic policy control based on charging information. Before this, policy decisions were static and could not react to real-time changes in subscriber balance. The spending limit report enables a closed-loop system where charging and policy functions interact seamlessly. This is particularly important for prepaid services, where the subscriber's balance must be checked before granting access, and for postpaid services with spending caps to prevent bill shock.

In 5G, the spending limit report continues to play a crucial role, but the architecture is more flexible. The PCF can subscribe to notifications from the CHF, and the report can include additional information such as the policy counter's validity time or the reason for the status change. The N28 interface supports both direct and indirect communication, allowing for scalability and redundancy. The spending limit report is thus a vital enabler for real-time policy and charging control in modern mobile networks.

Purpose & Motivation

The spending limit report was created to enable real-time communication between charging and policy functions, allowing operators to enforce dynamic policies based on a subscriber's current usage and balance. Prior to its introduction, policy decisions were based on static subscription data, which could not reflect real-time changes in usage or account balance. This led to inefficiencies such as delayed enforcement of spending limits, potential revenue loss, and poor user experience due to unexpected service interruptions or bill shock.

The spending limit report solves these problems by providing a standardized mechanism for the OCS/CHF to notify the PCRF/PCF when a policy counter status changes. This allows the PCRF/PCF to take immediate action, such as downgrading QoS, blocking access, or sending notifications to the subscriber. It also enables operators to offer more flexible services, such as allowing a grace period before blocking, or applying different policies based on the remaining quota.

Historically, the Sy reference point was introduced in Release 11 to support the spending limit report. It was later enhanced in 5G with the N28 interface, which uses a more modern protocol stack. The spending limit report has become a cornerstone of policy and charging control, supporting a wide range of services from prepaid voice to 5G data sessions. Its importance continues to grow as networks become more dynamic and personalized.

What changed in its specifications

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

TS 23.203Rel-16 → Rel-17

NB-IoT/eMTC support for Non-Terrestrial Networks: adds QCI characteristic for satellite access, note on GEO/LEO delays, and PCRF policy control for satellite PDN connections.

Full comparison in TS 23.203 →
TS 23.503Rel-18 → Rel-19

Rel-19 TS 23.503 adds Network Slice Replacement and Energy Saving Indicator reporting, Application Function influence on payload header handling, and Local Offloading Management Policy for edge computing. It also adds ATSSS Phase 4 multi-access steering (MPQUIC-E, ATSSS-LL), spending-limit policy for roaming, and PCF use of network analytics.

Full comparison in TS 23.503 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-15 1 change
  • Clarification of "intermediate spending limit report retrieval" usage TS 29.594CR0011
Rel-16 1 change
  • Correction to Intermediate spending limit report retrieval TS 29.594CR0064

Defining Specifications

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

SpecificationTitleRelease
TS 23.203 vk10 Policy and Charging Control Architecture Rel-20 read
TS 23.503 vk30 5G Policy and Charging Control Framework Rel-20 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
TS 29.594 vk00 5G Spending Limit Control Service (Nchf) Rel-20 read