Usage Reporting Rule

Description

The Usage Reporting Rule (URR) is a fundamental component of the 5G Policy Control Framework, defined within the PCF (Policy Control Function) and enforced by the SMF (Session Management Function). It is a policy rule that dictates when and how usage information for a specific Service Data Flow (SDF) or aggregate of SDFs is to be reported. The URR is provisioned by the PCF as part of a PCC (Policy and Charging Control) rule and is uniquely identified within a PDU (Packet Data Unit) session. The rule contains triggers that define the reporting events, which can be based on thresholds (e.g., uplink/downlink data volume, session duration), specific occurrences (e.g., start/stop of a service, location change), or a combination thereof.

When a URR is active, the SMF monitors the relevant traffic against the configured triggers. Upon a trigger event, the SMF generates a Usage Monitoring Report. This report contains detailed information such as the URR ID, the monitored volumes (potentially broken down by rating group or QoS Flow), the triggering event, and timestamps. The SMF then sends this report to the PCF, typically via the N7 reference point, using the Npcf_SMPolicyControl_Update service operation. The PCF uses this reported data for multiple purposes, including real-time policy decisions, charging correlation, and providing input to the CHF (Charging Function) for online or offline charging.

Architecturally, URRs operate within the SMF's policy enforcement and data collection modules. They are tightly integrated with QoS Flow management and packet detection rules. A single PDU session can have multiple URRs active simultaneously, each monitoring different aspects of the session—for instance, one URR could monitor total data volume for billing, while another monitors volume for a specific sponsored service. The granularity allows for sophisticated service differentiation. The reporting can be one-time (upon a single event) or recurring (e.g., reporting every 100MB of data consumed). The URR framework is extensible, allowing for new trigger types to be defined in later 3GPP releases to support emerging services like network slicing or edge computing.

Purpose & Motivation

The URR was introduced to address the limitations of static, session-level reporting in previous generations, which were insufficient for the dynamic and service-rich environment of 5G. In 4G EPC, usage reporting was often tied to bearer establishment and modification, lacking the granularity for on-demand, event-driven reporting required for new business models like sponsored data, QoS-on-demand, and real-time analytics. The URR provides a flexible, policy-driven mechanism that decouples reporting from session management events.

Its creation was motivated by the need for more intelligent policy control. Operators require fine-grained visibility into network usage to implement advanced charging schemes (e.g., time-of-day, application-specific), enforce fair usage policies, and provide service guarantees. The URR enables this by allowing the PCF to dynamically instruct the SMF on what usage to monitor and when to report it, based on subscriber profile, network conditions, or service logic. This flexibility is crucial for supporting Network Slicing, where different slices may have entirely different reporting requirements for isolation and billing.

Furthermore, URR facilitates the convergence of policy and charging. By providing detailed, trigger-based reports, it allows the PCF to make informed decisions that directly impact charging in the CHF. This solves the problem of delayed or batched usage data, enabling real-time spending limit controls, quota management, and immediate service downgrade or upgrade based on consumed resources, thereby enhancing the user experience and operator revenue assurance.