Diameter Base Protocol Accounting

Description

Diameter Base Protocol Accounting (DBPA) is an integral part of the Diameter protocol suite, specifically defined for accounting operations in 3GPP networks. It operates as an application on top of the Diameter base protocol (RFC 6733), leveraging its peer-to-peer architecture, reliable transport over TCP or SCTP, and built-in security features like TLS and IPsec. DBPA defines the specific Diameter commands, Attribute-Value Pairs (AVPs), and session state machines necessary to collect and report usage data from network elements such as the P-GW, S-GW, or MME to charging functions like the Online Charging System (OCS) or Offline Charging System (OFCS).

The protocol works through a request-and-answer model using specific Accounting-Request (ACR) and Accounting-Answer (ACA) command codes. A network element acting as a Diameter client initiates an accounting session by sending an ACR message, which contains critical AVPs like the Session-Id, Accounting-Record-Type (START, INTERIM, STOP, EVENT), and numerous service-specific AVPs detailing the resource usage (e.g., data volume, duration, QoS parameters). The receiving accounting server (e.g., a Charging Data Function or CDF) processes the request, correlates it with the correct subscriber session, and returns an ACA message to acknowledge receipt. This allows for real-time (online) or batch (offline) reporting of events.

Key architectural components include the accounting session state, maintained via the Accounting-Record-Type and Session-Id, which allows for correlation of multiple interim updates for a single service session. DBPA supports both event-based accounting (for immediate, one-time charges) and session-based accounting (for continuous services like a data session). The protocol's design ensures failover and failback capabilities through the Diameter peer discovery and routing mechanisms, guaranteeing that accounting data is not lost even if a primary server fails. Its role is critical in the Charging Trigger Function (CTF) architecture, where it serves as the standardized northbound interface for transporting Charging Data Records (CDRs) or credit control events.

DBPA's extensibility is a major feature; while 3GPP specifications like 32.299 define a core set of AVPs for telecom services, vendors and other standards bodies can define new, vendor-specific AVPs to carry additional information. This makes DBPA adaptable beyond its initial 3GPP scope. Furthermore, its integration with the broader Diameter infrastructure—including relay, proxy, and redirect agents—enables scalable and manageable accounting across large, distributed networks, forming the backbone of modern policy and charging architectures.

Purpose & Motivation

DBPA was created to address the limitations of its predecessor, the RADIUS accounting protocol, which was not designed for the complex, high-reliability requirements of 3GPP mobile networks. RADIUS suffered from scalability constraints, a lack of inherent security (relying on hop-by-hop shared secrets), and limited support for the sophisticated session-based and event-based charging models required for IP-based mobile services like IMS and mobile broadband. The transition to all-IP core networks in 3GPP Release 5 and beyond necessitated a more robust, flexible, and secure protocol for transporting billing-related data.

The primary problem DBPA solves is providing a standardized, carrier-grade mechanism for network elements to report usage information reliably and securely to centralized charging systems. This enables accurate billing for diverse services—from voice calls and SMS to data sessions and IMS multimedia services—based on detailed resource consumption. Its creation was motivated by the need for real-time charging capabilities to support prepaid services and sophisticated rating models, which were difficult to implement reliably with earlier protocols. By being part of the Diameter suite, DBPA also ensures seamless integration with the parallel Diameter Credit-Control Application (DCCA) used for online charging, creating a unified protocol ecosystem for policy and charging control.

Key Features

• Standardized command set (ACR/ACA) for accounting operations
• Support for session-based and event-based accounting record types
• Reliable transport over TCP/SCTP with failover support
• Extensible AVP (Attribute-Value Pair) structure for carrying usage data
• Integration with Diameter base protocol security (TLS, IPsec)
• Correlation of accounting records via Session-Id and accounting session state

Evolution Across Releases

Defining Specifications