Application Based Charging

Description

Application Based Charging (ABC) is a sophisticated charging framework defined in 3GPP specifications that enables mobile network operators to implement granular, application-aware charging policies. Unlike traditional volume-based or time-based charging models, ABC allows operators to identify specific applications or categories of applications (such as video streaming, social media, gaming, or enterprise applications) and apply distinct charging rules to each. This capability is implemented within the Policy and Charging Control (PCC) architecture, where the Policy and Charging Rules Function (PCRF) or Policy Control Function (PCF) plays a central role in determining and enforcing application-specific charging policies based on real-time network conditions and subscriber profiles.

The technical implementation of ABC relies on deep packet inspection (DPI) capabilities, typically deployed in the Traffic Detection Function (TDF) or as an integrated feature within the Packet Gateway (PGW) or User Plane Function (UPF). These components analyze packet headers and payloads to identify applications using various techniques including port-based detection, signature matching, behavioral analysis, and machine learning algorithms. Once an application is identified, the system maps it to specific charging rules defined in the operator's policy database. The charging rules may specify different tariff rates, quota allocations, or spending limits based on the application type, time of day, network congestion levels, or subscriber tier.

Within the charging architecture, ABC interfaces with the Online Charging System (OCS) for real-time credit control and the Offline Charging System (OFCS) for post-processing of charging data records (CDRs). When a subscriber initiates a data session, the PCRF/PCF retrieves the subscriber's profile from the Subscription Profile Repository (SPR) or Unified Data Repository (UDR), which includes ABC-specific policies. As the user accesses different applications, the TDF or equivalent detection function identifies the applications and reports them to the PCRF/PCF, which then instructs the charging systems to apply the appropriate charging rules. This dynamic, application-aware charging enables operators to offer innovative service plans such as 'social media bundles,' 'video streaming passes,' or 'gaming packages' where specific applications receive preferential charging treatment.

The implementation of ABC requires careful consideration of privacy regulations and network performance. Since DPI involves examining packet contents, operators must implement appropriate privacy safeguards and obtain necessary user consents where required by local regulations. Additionally, the processing overhead of application detection must be balanced against network performance requirements, with optimizations such as cached detection results and flow-based rather than packet-based analysis. ABC represents a significant evolution from simple data volume charging to intelligent, service-aware monetization that aligns with how subscribers actually use mobile data services in the modern application-centric internet ecosystem.

Purpose & Motivation

Application Based Charging was developed to address the limitations of traditional charging models in the face of rapidly evolving mobile data usage patterns. Prior to ABC, most operators relied primarily on volume-based or time-based charging, which treated all data traffic equally regardless of the application generating it. This approach failed to capture the varying value that different applications provide to subscribers and the different network resource requirements of various services. For example, video streaming consumes significantly more bandwidth than messaging applications, yet under volume-based charging, both would be billed identically per megabyte. ABC enables operators to implement more nuanced charging that reflects both the cost to deliver different services and the perceived value to subscribers.

The creation of ABC was motivated by several business and technical factors. From a business perspective, operators needed more sophisticated monetization tools to compete with over-the-top (OTT) service providers and to create differentiated service offerings. By enabling application-specific charging, operators could partner with content providers for 'sponsored data' arrangements, create targeted service bundles, and implement 'zero-rating' for specific applications. Technically, the proliferation of smartphones and mobile applications created a need for charging systems that could recognize and categorize thousands of different applications in real-time. This required advancements in deep packet inspection technology and integration with the evolving Policy and Charging Control architecture in 3GPP networks.

ABC also addresses the challenge of network congestion management by enabling application-aware policies that can prioritize or deprioritize certain types of traffic based on both technical requirements and commercial considerations. For instance, an operator might choose to apply more favorable charging to delay-tolerant applications during peak congestion periods while maintaining standard rates for real-time services. This flexibility allows operators to better manage network resources while offering subscribers more choice and transparency in how they are charged for different types of data usage. The introduction of ABC in Release 12 represented a significant step toward more intelligent, service-aware network monetization in the 4G/LTE era, with continued evolution through subsequent releases to support 5G use cases and network architectures.

Key Features

• Application identification through deep packet inspection (DPI) techniques
• Integration with Policy and Charging Control (PCC) architecture for dynamic policy enforcement
• Support for both online and offline charging scenarios
• Granular charging rules based on application type, category, or specific service
• Real-time charging capability with interface to Online Charging System (OCS)
• Flexible policy definitions supporting time-based, volume-based, and event-based charging triggers

Evolution Across Releases

Defining Specifications