Description
The Spending-Limit-Answer (SLA) is a critical component of the 3GPP Online Charging System (OCS) architecture, operating within the Diameter-based Ro/Rf reference points. It is a direct response to the Spending-Limit-Request (SLR) message initiated by a network function like a Gateway GPRS Support Node (GGSN), Packet Data Network Gateway (PGW), or Session Management Function (SMF). The SLA carries the decision from the OCS regarding the amount of service units (e.g., data volume, time duration, monetary credit) a subscriber is permitted to consume. The message contains key Attribute-Value Pairs (AVPs) such as the Granted-Service-Unit AVP, which specifies the precise quota (e.g., 10 MB of data). It may also include the Validity-Time AVP, defining how long the quota is valid, and the Final-Unit-Indication AVP, which signals that the granted quota is the final one before service termination or redirection.
Architecturally, the SLA is part of the Diameter Credit-Control Application (DCCA) as defined in IETF RFC 4006, which 3GPP has adopted and extended. The OCS, upon receiving an SLR, performs subscriber balance checks, applies tariff rates, and potentially consults policy rules before formulating the SLA. The process is stateful, with the OCS maintaining a session context for each active credit-control session. The SLA is transported reliably over the Diameter protocol, ensuring the charging client in the network receives the authorization decision.
Its role is fundamental to real-time, event-based charging for data, voice, SMS, and IMS services. By providing a dynamic and immediate spending limit, the SLA enables prepaid services, spending-limit controls for postpaid accounts, and seamless service continuation through quota renewal cycles. The integrity and timeliness of the SLA are paramount for accurate revenue assurance and for providing subscribers with transparent, up-to-date information on their credit consumption.
Purpose & Motivation
The Spending-Limit-Answer exists to facilitate real-time credit authorization in telecommunications networks, a necessity for prepaid services and spending control. Prior to online charging, operators relied heavily on offline charging (post-event billing), which carried the risk of bad debt from subscribers exceeding their credit. The SLA, as part of the OCS framework, solves this by providing an immediate 'yes/no' and 'how much' decision before network resources are committed.
Its creation was motivated by the commercial need to offer innovative prepaid plans for emerging packet-switched services like GPRS and, later, 3G/4G/5G data. The traditional call-detail-record (CDR) based approach had too much latency between usage and billing, making it unsuitable for controlling data sessions that could consume large value quickly. The SLA mechanism allows operators to offer flexible, real-time tariffs and protect their revenue by enforcing hard limits on consumption.
Historically, its introduction in R99 coincided with the standardization of the CAMEL-based and later Diameter-based OCS. It addressed the limitation of passive billing by creating an interactive dialogue between the network and the charging system, transforming charging from a mere recording function into an active policy enforcement point for monetization.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific 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.
Explore further
Broader topics and technologies where SLA plays a role.
Defining Specifications
3GPP specifications that define or reference SLA, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj20 | 3GPP Terminology and Definitions | Rel-19 |
| TS 22.495 v1700 | NGN Requirements for IMS Services | Rel-7 |
| TS 22.519 vj00 | NGN Business Communication Requirements | Rel-19 |
| TR 22.980 vj00 | Network Composition Feasibility Study | Rel-19 |
| TS 23.107 vj00 | UMTS QoS Framework | Rel-19 |
| TS 23.207 vj00 | End-to-End QoS Framework for GPRS | Rel-19 |
| TS 23.435 vk00 | Network Slice Capability Enablement (NSCE) Architecture | Rel-20 |
| TS 23.700 vk10 | AI/ML Application Layer Support Phase 2 | Rel-20 |
| TR 23.758 vh00 | Study on Edge Application Architecture | Rel-17 |
| TS 24.525 vj00 | Business Trunking Architecture & Requirements | Rel-19 |
| TS 26.501 vj40 | 5G Media Streaming Architecture | Rel-19 |
| TS 26.804 vk00 | 5G Media Streaming Architecture Extensions | Rel-20 |
| TS 26.891 vg00 | Media Distribution Services in 5G System | Rel-16 |
| TS 26.942 vk00 | Sustainable Media Metrics and Architectural Impacts for 5G | Rel-20 |
| TS 28.530 vj00 | Network Slicing Concepts & Requirements | Rel-19 |
| TS 28.535 vj00 | Closed Control Loop Assurance Management | Rel-19 |
| TS 28.536 vj20 | Management services for communication service assurance | Rel-19 |
| TS 28.805 vg10 | Management of Communication Services in 5G | Rel-16 |
| TS 29.116 vj00 | REST-based protocol for xMB reference point | Rel-19 |
| TS 29.199 v1930 | Call Notification Web Service Specification | Rel-9 |
| TS 29.213 vj30 | PCC Procedures and Flows | Rel-19 |
| TS 29.219 vj00 | Sy Reference Point Stage 3 Specification | Rel-19 |
| TR 29.949 vj00 | VoLTE IMS Roaming Architecture & Procedures | Rel-19 |
| TS 32.101 vj00 | PLMN Management Principles and Requirements | Rel-19 |
| TS 32.102 vj00 | Telecom Management Physical Architecture Framework | Rel-19 |
| TS 32.141 vj00 | Subscription Management (SuM) Architecture | Rel-19 |
| TS 32.410 vj00 | 3GPP TS 32.410: Key Performance Indicators (KPI) | Rel-19 |
| TS 32.854 vb10 | FMC Federated Network Information Model | Rel-11 |
| TS 38.300 vj30 | NR and NG-RAN Overall Description | Rel-19 |
| TR 38.828 vg10 | CLI and RIM for NR | Rel-16 |
| TR 38.900 vf00 | Channel Model Study for >6 GHz | Rel-15 |
| TS 38.901 vj40 | Channel Model for 0.5-100 GHz | Rel-19 |