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

Glossary term · QoS

Spending limit

Spending Limit

QoS →

Spending limit is the maximum usage amount of a policy counter, such as monetary, volume, or duration, that a subscriber is permitted to consume within a policy and charging control system.

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

Description

A spending limit is a fundamental concept in 3GPP policy and charging control (PCC) architecture. It represents the maximum usage of a policy counter that a subscriber is allowed to consume before the network takes action, such as blocking further usage or applying different QoS. Policy counters are maintained in the Online Charging System (OCS) or, in 5G, the Charging Function (CHF), and can be based on various metrics including monetary units, data volume, or time duration. The spending limit itself is a threshold value that, when reached, triggers a notification to the Policy and Charging Rules Function (PCRF) or Policy Control Function (PCF), which then enforces the appropriate policy decision.

The concept was introduced in 3GPP Release 11 as part of the Sy reference point between the PCRF and OCS. The Sy interface allows the PCRF to request and receive spending limit reports from the OCS, enabling real-time policy decisions based on the subscriber's remaining balance or usage quota. This integration is crucial for operators to offer tiered services, prepaid plans, and fair usage policies. For example, a subscriber on a prepaid plan may have a monetary spending limit; once the balance is exhausted, the PCRF can instruct the PCEF to block data traffic or redirect to a top-up portal.

In the 5G System (5GS), the architecture evolves with the PCF interacting with the CHF via the N28 interface (or Sy in interworking scenarios). The spending limit concept remains similar, but the CHF manages policy counters and provides spending limit reports to the PCF. The PCF then enforces policies through the SMF (Session Management Function) and UPF (User Plane Function). This enables dynamic policy control based on real-time charging information, supporting diverse 5G use cases such as network slicing, where each slice may have its own spending limits.

The spending limit mechanism operates through a series of interactions: the PCRF/PCF subscribes to policy counter status notifications from the OCS/CHF; the OCS/CHF monitors usage and, when a threshold is reached, sends a spending limit report; the PCRF/PCF then evaluates the report and may modify the PCC rules, such as changing QoS parameters or blocking the service. This closed-loop control ensures that subscribers do not exceed their allowed usage, preventing revenue loss and enhancing user experience by avoiding unexpected charges.

Key components involved include the policy counter, which tracks usage; the spending limit, which defines the threshold; and the spending limit report, which communicates status changes. The spending limit can be expressed in various units, and multiple policy counters can be active simultaneously, each with its own limit. This flexibility allows operators to implement complex charging schemes, such as combined volume and time limits, or tiered pricing based on usage buckets. The spending limit is thus a cornerstone of modern policy and charging control, enabling personalized and dynamic service offerings.

Purpose & Motivation

The spending limit concept was introduced to address the need for real-time policy control based on a subscriber's usage and balance. Before its introduction, policy decisions were largely static and based on subscription profiles, without dynamic interaction with charging systems. This led to challenges such as bill shock for postpaid users and inability to enforce prepaid limits in real-time. The spending limit mechanism enables operators to dynamically adjust policies based on the subscriber's remaining quota, ensuring that services are delivered according to the purchased plan and preventing unauthorized usage.

Historically, the separation between policy control and charging functions meant that policy decisions could not easily incorporate real-time charging information. The Sy reference point, introduced in Release 11, bridged this gap by allowing the PCRF to query the OCS for spending limit reports. This integration enabled operators to offer innovative services like zero-rated applications, where usage does not count towards the spending limit, or sponsored data, where a third party pays for the data. It also facilitated fair usage policies by allowing the network to throttle or block users who exceed their limits.

In 5G, the spending limit concept continues to evolve with the PCF and CHF interaction, supporting new business models such as network slicing and edge computing. The ability to enforce spending limits per slice or per application ensures that resources are allocated efficiently and that subscribers are charged appropriately. The spending limit thus remains a vital tool for operators to manage revenue, enforce policies, and deliver a positive user experience.

What changed in its specifications

The latest release-to-release comparison of specifications that define Spending limit. 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 (6 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-15 2 changes
  • Selection of the CHF for charging and spending limit control for the PDU session TS 23.503CR0150
  • Clarification of "intermediate spending limit report retrieval" usage TS 29.594CR0011
Rel-16 2 changes
  • Correction to spending limit subscribe and unsubscribe procedures TS 29.594CR0056
  • Correction to Intermediate spending limit report retrieval TS 29.594CR0064
Rel-18 2 changes
  • Clarification on Spending Limit Control Service TS 29.594CR0105
  • Corrections for spending limit information stored in UDR TS 23.503CR1252

Defining Specifications

3GPP specifications that define or reference Spending limit, 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