Current Bucket Level

Description

The Current Bucket Level (CBL) is a fundamental charging-related parameter defined within the 3GPP Base Station System (BSS) architecture, specifically managed by the Base Station Controller (BSC). It operates as a decrementing counter that tracks the volume of data (or sometimes duration for circuit-switched services) consumed by a mobile station (MS) for a specific charging context, such as a pre-paid data bucket. The CBL is measured in quantifiable units, typically kilobytes for packet data services, and its value represents the remaining allowance before a charging-related action, like service suspension or notification, must be triggered.

Architecturally, the CBL is maintained locally within the BSC for the duration of a data session or mobility management context. Its initial value is provided by the core network's Charging System, often via the Serving GPRS Support Node (SGSN) using the BSSGP (BSS GPRS Protocol) messages over the Gb interface. The BSC is responsible for decrementing the CBL in real-time based on the actual data volume transmitted to and from the mobile station. This real-time accounting is a critical function that enables accurate pre-paid charging and immediate service control without constant signaling to the core network for every data packet.

The CBL's role is central to the enforcement of charging policies. As data flows, the BSC continuously monitors the CBL. When the CBL reaches a configurable threshold (often zero or a low-water mark), the BSC must take action as instructed by the core network. This typically involves sending a notification to the SGSN (a 'Bucket Empty' indication) or directly restricting the user's data flow. The SGSN can then interact with the online charging system (OCS) to refill the bucket or apply policy decisions. This mechanism ensures that pre-paid subscribers cannot incur charges beyond their credit limit and allows for near-instantaneous service control, which is a regulatory requirement in many markets.

Key components interacting with the CBL include the BSC (which hosts and manages the counter), the SGSN (which provides initial values and receives notifications), and the underlying GPRS tunneling and radio resource management protocols that facilitate the data transfer being measured. The CBL is a cornerstone of the Advice of Charge (AoC) and immediate service termination capabilities mandated for pre-paid services, making it an essential element for commercial mobile network operations, particularly in markets with high pre-paid subscriber penetration.

Purpose & Motivation

The CBL was introduced to address the critical commercial need for reliable and real-time charging control in mobile networks, especially for pre-paid subscription models. Prior to its standardization, implementing pre-paid services, particularly for data, was challenging and often relied on less accurate, batch-oriented post-processing or proprietary solutions that could lead to revenue leakage or poor customer experience due to delayed service suspension. The CBL provides a standardized, network-based mechanism for precise, session-aware resource accounting directly at the point of resource consumption (the BSC).

Its creation was motivated by the growth of GPRS and EDGE data services in 3GPP Release 8 and beyond, where data usage could quickly consume a user's credit. Operators required a way to enforce spending limits in real-time to protect their revenue and give customers control over their expenditure. The CBL solves this by delegating the granular, high-frequency task of measuring usage to the BSC, which handles the radio resources, while the core network retains overall policy control. This distributed architecture balances signaling load and enables swift action.

The technology addresses the limitation of not having a standardized, real-time counter within the radio access network dedicated to charging. It enables complex tariff models, such as volume-based data bundles, and is fundamental for compliance with telecommunications regulations concerning consumer protection and transparent billing. By providing a clear, decrementing measure of remaining resources, it forms the technical basis for notifications like 'data limit approaching' alerts, enhancing the user experience for pre-paid services.

Key Features

• Real-time decrementing counter for data volume or call duration
• Managed locally by the Base Station Controller (BSC) for low-latency control
• Initial value and policies provisioned by the core network (SGSN/Charging System)
• Triggers notifications (e.g., Bucket Empty) to the core network upon threshold breach
• Enables immediate service suspension or limitation to prevent overspending
• Fundamental for pre-paid charging and Advice of Charge (AoC) functionality

Evolution Across Releases

Defining Specifications