Accounting Meter Record

Description

An Accounting Meter Record (AMR) is a specialized type of charging record defined in 3GPP specifications (32.240, 32.272) that contains one or more counters employed to register the usage of resources en masse. Unlike detailed Call Detail Records (CDRs) that capture per-event information, AMRs aggregate usage data over a period, providing a summary view of resource consumption. They are particularly useful for statistical analysis, capacity planning, and bulk billing where per-event granularity is not required or would be too voluminous.

The AMR includes simple event counters (e.g., number of attach requests, number of SMS messages) and/or cumulative call second counters (e.g., total voice minutes, total data volume). These counters are typically incremented by network elements as events occur, and the AMR is generated at the end of a measurement period (e.g., hourly, daily). The record structure is defined in 3GPP TS 32.272, which specifies the format and contents for accounting meter records. The AMR is usually generated by the Charging Trigger Function (CTF) within network elements such as the SMF, AMF, or UPF, and transferred to the Charging Gateway Function (CGF) or Billing Domain.

In the 3GPP charging architecture, AMRs are part of the offline charging mechanism. They are not used for real-time credit control but rather for post-paid billing and reporting. The AMR can be used to bill subscribers based on aggregate usage (e.g., a monthly data cap) or to settle inter-operator charges based on bulk traffic volumes. For example, in roaming, an AMR might summarize the total number of minutes or megabytes used by a subscriber in a VPLMN, which is then used for TAP3 file generation.

The AMR is distinct from other record types such as CDRs (which contain detailed session information) and Event Detail Records (EDRs, which capture individual events). AMRs are more compact and suitable for high-volume, low-granularity accounting. They are also used for network performance monitoring and KPI reporting, as they provide aggregated usage statistics that can be analyzed for trends and anomalies.

With the evolution to 5G, the concept of AMR continues to be relevant, though the charging architecture has shifted to a service-based interface (Nchf) and converged charging. The AMR may be generated by the Charging Function (CHF) or by network functions that support bulk reporting. The 3GPP specifications continue to define AMR formats for both 4G and 5G, ensuring backward compatibility and support for diverse business models.

Purpose & Motivation

The Accounting Meter Record was introduced in Rel-8 to address the need for efficient, aggregated accounting of resource usage in mobile networks. As networks grew in scale and complexity, generating detailed CDRs for every event became impractical and costly in terms of storage, processing, and transport. Operators needed a way to capture bulk usage statistics without the overhead of per-event records. The AMR solves this by providing a compact record that summarizes usage over a period, using counters.

This is particularly important for services with high transaction volumes, such as IoT, where millions of devices may generate small data transfers. Detailed CDRs for each transfer would overwhelm the charging system. AMRs allow operators to bill based on aggregate usage (e.g., total data volume per month) and to perform statistical analysis for network planning. They also support inter-operator settlements where bulk traffic volumes are exchanged, reducing the complexity of reconciliation.

The AMR also addresses the limitations of earlier charging systems that relied solely on CDRs. By introducing a standardized format for aggregated records, 3GPP enabled interoperability and automation in bulk accounting. This is essential for roaming and wholesale agreements, where operators need to exchange summary usage data efficiently. The AMR continues to be relevant in 5G for network slicing and massive IoT, where aggregated accounting is key to scalable operations.