Data Volume

Description

Data Volume (DV) is a fundamental measurement parameter in 3GPP systems, denoting the aggregate amount of user plane data exchanged. It is measured in octets (bytes) and is counted separately for uplink (from UE to network) and downlink (from network to UE) directions. The context for DV measurement is precisely defined: it can be associated with a specific Protocol Data Unit (PDU) Session, a dedicated QoS Flow within a session, a service data flow (SDF) identified by packet filters, or even an entire subscriber. The counting is performed by network functions that handle user plane traffic, primarily the User Plane Function (UPF) in the 5G Core and the Gateway GPRS Support Node (GGSN)/Packet Gateway (PGW) in the EPC.

The technical process involves the counting node inspecting packets as they are forwarded. For each packet matching a defined measurement context (e.g., belonging to a specific PDU Session and QoS Flow), the node increments the appropriate DV counter by the number of octets in the packet payload (excluding layer-specific headers like GTP-U, UDP/IP). These counters are typically maintained in real-time. The DV information is then utilized in several ways. For charging, the SMF (or PGW-C in EPC) may request reports from the UPF (or PGW-U) containing the DV used, which is then formatted into Charging Data Records (CDRs) for offline charging or used for online credit control. For policy control, the Policy Control Function (PCF) can set usage monitoring thresholds; when the DV reaches a threshold, the SMF is notified to potentially trigger policy actions like slowing down data rates.

DV reporting can be event-triggered (e.g., at session termination, upon reaching a quota) or periodic. The granularity of DV measurement is a key aspect of network management. It enables volume-based charging tiers, fair usage policies, and detailed analytics on network traffic patterns. In advanced deployments, DV can also be correlated with slice-specific usage for network slicing billing and capacity planning.

Purpose & Motivation

The concept of Data Volume has been integral since packet-switched services were introduced, but its formalization and granular application evolved with the need for sophisticated service differentiation and monetization. Early GPRS/UMTS networks used DV primarily for simple bulk charging. However, with the advent of flat-rate data plans, streaming services, and IoT, operators required finer-grained visibility and control over data usage.

DV as a standardized metric, particularly emphasized from 3GPP Release 16 onwards in contexts like enhanced coverage and UAV support, addresses the need for accurate, context-aware usage accounting. It solves the problem of how to charge for diverse services (e.g., charging differently for mission-critical IoT data vs. mobile broadband) and how to enforce fair usage policies without simply blocking access. By tying DV to specific QoS Flows or network slices, it enables the business models for 5G, such as network-as-a-service, where billing can be based on the volume of guaranteed-bit-rate traffic. It provides the quantitative basis for the policy and charging control (PCC) architecture.

Key Features

• Measured in octets, with separate counters for uplink and downlink directions.
• Counted within specific contexts: per PDU Session, per QoS Flow, per SDF, or per UE.
• Primary measurement point is the user plane gateway (UPF in 5GC, PGW-U in EPC).
• Feeds into Charging Data Records (CDR) for offline charging and online credit control.
• Integrates with Policy and Charging Control (PCC) for usage monitoring and policy enforcement.
• Supports event-triggered and periodic reporting to control plane functions (SMF, PCF).

Evolution Across Releases

Defining Specifications