Application Characteristics

Description

Application Characteristics (AC) are a set of standardized attributes defined within the 3GPP specifications to profile the behavior and requirements of applications using the mobile network. These characteristics serve as a critical input for network functions, particularly within the Policy and Charging Control (PCC) architecture, to determine how application traffic should be treated. The AC parameters describe aspects such as the application's traffic pattern (e.g., real-time, streaming, interactive, background), its tolerance to delay and jitter, its required bandwidth, and its expected data volume. By classifying applications based on these characteristics, the network can map the traffic to appropriate QoS Class Identifiers (QCIs) or 5G QoS Identifiers (5QIs), ensuring the application receives the necessary network resources and performance guarantees.

The core mechanism involves the Application Function (AF), such as a P-CSCF for IMS services or a third-party application server, providing the AC information to the Policy Control Function (PCF) via the Rx (in 4G) or N5 (in 5G) interface. This communication typically occurs during the establishment of a service data flow. The PCF, which is the central brain for policy decisions, uses the received AC along with subscriber information, subscription data, and network conditions to formulate dynamic PCC rules. These rules are then enforced by the Policy and Charging Enforcement Function (PCEF) in the Gateway (e.g., PGW, UPF) to apply the correct QoS, perform gating (allow/block traffic), and trigger appropriate charging actions. The AC thus acts as the application's 'declaration of needs' to the policy framework.

Key components in the AC ecosystem include the standardized parameter set itself, the AF that generates them, the PCF that consumes them for policy derivation, and the enforcement points (PCEF, SMF/UPF). The parameters are often aligned with broader service requirements defined in other specifications, ensuring consistency. For example, characteristics for a Voice over LTE (VoLTE) call would indicate a stringent real-time conversational profile, leading to the allocation of a Guaranteed Bit Rate (GBR) bearer with a low-latency QCI. This systematic profiling prevents network resources from being over-provisioned for simple background data or under-provisioned for critical services, striking a balance between application performance and network efficiency.

In 5G systems, the concept evolves with enhanced granularity and support for network slicing. AC information can influence the selection of a specific network slice instance tailored for an application's needs. The Service-Based Architecture (SBA) of 5G Core facilitates more dynamic and granular exchange of AC data between network functions like the Network Exposure Function (NEF), PCF, and Application Function. This allows for more sophisticated traffic steering, edge computing service invocation, and differentiated charging based on the precise application context. Ultimately, AC provides the semantic link between the application layer's intent and the transport network's capability, enabling intelligent, automated, and optimized end-to-end service delivery across 3GPP systems.

Purpose & Motivation

The primary purpose of defining Application Characteristics (AC) is to bridge the gap between application-layer requirements and network-layer resource management. Before standardized AC, networks treated most IP traffic uniformly with 'best-effort' delivery, which was insufficient for the diverse quality needs of emerging services like VoIP, video streaming, and online gaming. This one-size-fits-all approach led to poor user experience for latency-sensitive applications and inefficient use of network capacity. The introduction of AC, as part of the broader PCC framework from 3GPP Release 5 onwards, was motivated by the need to enable Quality of Service (QoS) differentiation and dynamic policy control based on the specific type of application being used.

Historically, early mobile data services like GPRS offered limited QoS mechanisms based on static subscriber profiles, lacking real-time awareness of the active application. The evolution towards All-IP networks and IMS-based services demanded a more dynamic and granular system. AC solves this by allowing the application itself, or a proxy aware of its needs, to explicitly signal its behavioral profile to the policy control system. This empowers operators to move from simple volume-based charging to sophisticated service-aware charging models and to guarantee performance for premium services, creating new revenue streams and improving customer satisfaction.

Furthermore, AC addresses the challenge of network efficiency. By accurately characterizing application traffic, the network can avoid over-allocating precious radio and transport resources to non-critical data flows. It enables intelligent traffic management, such as throttling background updates during congestion while preserving the quality of a live video call. In the context of 5G and network slicing, AC provides the essential criteria for automating slice selection and configuration, ensuring that each application is hosted on a slice with the appropriate performance characteristics. Thus, AC exists as a foundational enabler for the service-aware, efficient, and monetizable mobile broadband networks defined by 3GPP.

Key Features

• Standardized parameter set for application behavior profiling
• Input for dynamic Policy and Charging Control (PCC) rule generation
• Enables mapping of application traffic to specific QoS classes (QCIs/5QIs)
• Facilitates service-aware charging and gating control
• Supports network slice selection and service requirements in 5G
• Exchanged via standardized interfaces (e.g., Rx, N5) between AF and PCF

Evolution Across Releases

Defining Specifications