Application Data Analytics Enablement Client

Description

The Application Data Analytics Enablement Client (ADAEC) is a standardized client function defined within the 3GPP architecture, specifically designed to operate on the User Equipment (UE). It acts as the endpoint for application data analytics collection within the 5G system and beyond. The ADAEC is responsible for interfacing with applications running on the UE, gathering relevant analytics data as defined by analytics subscriptions or configurations provided by the network, and reporting this data to the Application Data Analytics Enablement Server (ADAES) located in the network. Its operation is governed by policies and instructions received from the ADAES, ensuring that data collection is privacy-compliant, resource-efficient, and aligned with the analytics requirements of authorized entities.

Architecturally, the ADAEC is part of the Application Data Analytics Enablement framework, which includes the ADAES in the network. The ADAEC communicates with the ADAES over the Nadae interface, as specified in 3GPP TS 24.559. This interface supports procedures for analytics subscription, configuration delivery, and analytics reporting. The ADAEC's key internal components include a policy enforcement function to interpret and apply data collection policies from the ADAES, a data collection engine that interfaces with the UE's application programming interfaces (APIs) or operating system to gather specified metrics (e.g., application latency, throughput, error rates, user interaction events), and a reporting function that formats and transmits the collected data to the server.

How it works involves a subscription-based model. An analytics consumer (e.g., a network operator, third-party application provider) requests specific analytics through the ADAES. The ADAES then provisions the corresponding analytics subscription to the target ADAEC(s) in UEs. The subscription includes the analytics type, collection parameters, reporting conditions (e.g., event-triggered, periodic), and any data filtering or aggregation rules. The ADAEC, upon receiving the configuration, initiates monitoring of the specified applications and metrics. It processes the raw data locally as per the instructions—which may involve filtering, aggregation, or deriving Key Performance Indicators (KPIs)—and then sends analytics reports to the ADAES when the reporting conditions are met. This client-server model offloads some processing to the edge (the UE), reducing network overhead for raw data transmission.

Its role in the network is pivotal for enabling closed-loop automation and enhanced Quality of Experience (QoE) management. By providing granular, application-specific data from the end-user device, the ADAEC feeds the network's analytics and AI/ML engines with crucial input. This data can be used for numerous purposes: diagnosing application performance issues, optimizing radio and core network parameters for specific services (like video streaming or gaming), enabling network exposure of application context to authorized third parties, and supporting new business models around service-level agreements (SLAs) and experience-level agreements (ELAs). The ADAEC, therefore, transforms the UE from a passive endpoint into an active source of intelligence for the network.

Purpose & Motivation

The ADAEC was created to address the growing need for granular, application-aware insights in mobile networks, which traditional network-centric performance counters cannot fully provide. Prior to its standardization, application performance monitoring was often achieved through non-standardized, proprietary solutions—such as deep packet inspection (DPI) in the network or SDKs embedded in applications—which raised privacy concerns, were inefficient, and lacked interoperability. DPI struggles with encrypted traffic and provides only a network-side view, missing the true user-perceived experience on the device. Proprietary SDKs create fragmentation and increase application development complexity. The ADAEC standardizes a device-centric, privacy-aware, and application-friendly method for collecting analytics.

The primary problem it solves is the lack of a standardized, efficient, and secure mechanism to collect high-value analytics data directly from the application layer on the UE. This data is essential for operators and service providers to understand and optimize the true end-to-end Quality of Experience (QoE) for users. The motivation for its creation in Release 18 stems from the evolution towards 5G-Advanced and the increasing importance of vertical services (e.g., XR, cloud gaming, industrial IoT), which have stringent and diverse performance requirements. Optimizing networks for these services requires detailed knowledge of application behavior and user interaction, which the ADAEC enables.

Furthermore, ADAEC addresses limitations in previous 3GPP analytics frameworks, like those defined for Minimization of Drive Tests (MDT) or Quality of Experience (QoE) measurement collection, which were more focused on radio conditions or specific media streaming. ADAEC provides a more generic, flexible, and application-centric framework. It is designed with privacy-by-design principles, as the UE client operates under explicit user consent and network policies, giving users more control over what data is shared compared to opaque network probing techniques. Its creation was motivated by the industry's shift towards data-driven network automation, AI/ML-based optimization, and the need to support new business models where application performance is a key differentiator.

Key Features

• Standardized client-server interface (Nadae) for application analytics data collection
• Policy-driven data collection and reporting configurable from the network (ADAES)
• Support for various analytics types including application performance, user experience, and device context
• Local processing capabilities on the UE for data filtering, aggregation, and KPI derivation
• Privacy enforcement through user consent mechanisms and subscription-based data access
• Event-triggered and periodic reporting modes for flexible data delivery

Evolution Across Releases

Defining Specifications