ADAES

Application Data Analytics Enablement Services

Services →
Introduced in Rel-18

ADAES is a 3GPP framework that enables network exposure of analytics to applications, allowing Application Functions to request and receive data analytics to facilitate smarter application behavior and optimization.

Category
Services
Introduced
Rel-18
Where
Services
Specifications
6 specs
ADAES Description Purpose Related Classification Detected Changes Specifications

Description

Application Data Analytics Enablement Services (ADAES) is a standardized framework within the 5G Core network architecture that provides a mechanism for authorized Application Functions (AFs) to request and receive data analytics derived from network data. It acts as an intermediary service layer, exposing network analytics capabilities to external applications in a secure and controlled manner. The primary architectural components include the ADAES Provider, which is a logical function typically co-located with or part of the Network Data Analytics Function (NWDAF) or other analytics producers, and the ADAES Consumer, which is the AF requesting the analytics. The service is exposed via standardized service-based interfaces, primarily Nadaes (ADAES Services) as defined in 3GPP TS 29.549.

The ADAES framework operates by defining a set of service operations that allow an AF (the consumer) to subscribe to, request, or be notified about specific analytics information. The analytics requests are highly customizable; an AF can specify the type of analytics (e.g., load level analytics, UE mobility analytics, QoS sustainability analytics), the target of the analytics (e.g., a specific group of UEs, a geographical area, a network slice), and the required reporting characteristics (e.g., periodic, event-triggered, immediate). The ADAES Provider processes these requests, potentially aggregating and analyzing raw data from various network functions like the Access and Mobility Management Function (AMF), Session Management Function (SMF), and Policy Control Function (PCF), before returning the processed analytics results to the AF.

Key to ADAES is its role in decoupling the analytics production from consumption. It standardizes the data models and procedures for analytics exchange, ensuring interoperability between different vendor implementations of network analytics and diverse third-party applications. The analytics provided can range from network performance metrics and user equipment (UE) behavior patterns to predictions about future network conditions. This enables AFs to make intelligent, data-driven decisions, such as adjusting application bitrates based on predicted network congestion or triggering specific actions for UE groups exhibiting certain mobility patterns.

From a procedural perspective, the interaction typically involves subscription and notification. An AF subscribes to an analytics event by sending a Nadaes_AnalyticsSubscription_Create request to the ADAES Provider. The subscription includes the analytics filter criteria and a callback URI for notifications. The ADAES Provider then monitors the network for the specified conditions. When the analytics event occurs or when a periodic report is due, the provider generates an analytics report and sends it via a Nadaes_AnalyticsSubscription_Notify message to the AF's callback URI. This asynchronous, event-driven model is efficient and scalable. ADAES also supports direct request-response interactions for on-demand analytics queries without a subscription.

Purpose & Motivation

ADAES was created to address the growing need for applications to be network-aware and contextually intelligent. Prior to its standardization, applications had limited, proprietary, or non-existent means to access rich analytics derived from the mobile network core. This lack of standardized exposure hindered the development of advanced services that could dynamically adapt to network conditions, user mobility, and service quality in real-time. The motivation stems from the 5G vision of enabling vertical industries and innovative use cases—such as enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC)—which require deep integration between applications and network capabilities.

The framework solves the problem of siloed network intelligence. Without ADAES, valuable insights generated within the network (e.g., by the NWDAF) remained trapped within the operator's domain. ADAES provides a secure, policy-controlled, and standardized gateway for exposing these insights. This allows third-party application developers and enterprise AFs to build services that proactively respond to network events, optimize resource usage, and personalize user experiences. For example, a video streaming service can reduce video quality preemptively upon receiving an analytics forecast of cell congestion, or an IoT platform can reroute traffic based on UE mobility predictions.

Historically, limited application programmability and a lack of open interfaces in earlier generations (4G/LTE) constrained such dynamic network-application synergy. The introduction of ADAES in 3GPP Release-18 is a direct response to these limitations, formalizing the 'enablement' of data analytics as a core network service. It aligns with the broader 3GPP architecture principle of network exposure, complementing other exposure services like the Network Exposure Function (NEF), but with a specific, dedicated focus on analytics data. This specialization ensures efficient, scalable, and tailored interactions for analytics consumption, which is distinct from general parameter provisioning or policy control exposure.

Classification

Part ofNWDAF
Specific typesADAEC
Related approachesNEF

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (91 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-17 2 changes

In Release 17, the ADAES function introduced a Network Slice Capability Enablement API, with subsequent modifications to its data type. This API enables the ADAE server to provide data analytics for VAL server or session performance specifically for a requested network slice or slice instance, as defined in the architecture for application data analytics enablement.

  • Resolution of the Editor’s note for Network slice capability Enablement API. TS 29.549CR0084
  • Modification of data type for Network slice capability Enablement API TS 29.549CR0094
Rel-18 45 changes

In Release 18, the ADAES function was expanded to introduce new analytics capabilities including UE-to-UE session performance analytics, edge load and transmission quality analytics, and slice-specific application performance analytics. It also added support for location accuracy performance analytics and service API analytics, while further defining data models and operations for slice usage pattern analytics. These enhancements built upon the existing framework for collecting data from diverse sources like OAM, 5GC, and UEs to serve vertical applications.

  • Obtaining edge load analytics information TS 24.558CR0053
  • UE-to-UE session performance analytics request TS 24.559CR0001
  • Supported features indication in UE-to-UE session performance analytics TS 24.559CR0002
  • Support of ADAES TS 29.549CR0158
  • VAL application performance API TS 29.549CR0184
  • Slice-specific application performance API TS 29.549CR0186

+ 39 more changes

Rel-19 41 changes

In Release 19, the ADAES function introduced new analytics capabilities including Collision Detection Analytics, Location-related UE Group Analytics, and support for Application Layer AI/ML Member capability analytics. It also expanded its scope to cover new scenarios such as UE RAT connectivity analytics for non-terrestrial access, VAL performance analytics for tethered UEs, and support for multi-device metaverse services. Furthermore, the release provided updates and enhancements to existing analytics for location accuracy, application performance, edge load, and slice usage patterns.

  • Edge computing preparation analytics TS 23.436CR0030
  • Support of Collision Detection Analytics TS 23.436CR0037
  • Support of Location-related UE Group Analytics TS 23.436CR0038
  • Support of Application Layer AI/ML Member capability Analytics TS 23.436CR0039
  • UE RAT connectivity analytics for non terrestrial access TS 23.436CR0040
  • Support for VAL performance analytics for tethered UEs TS 23.436CR0044

+ 35 more changes

Rel-20 3 changes

In Release 20, the ADAES function introduced support for monitoring Machine Learning-enabled analytics correctness and enabled sample alignment for VAL Servers in Vertical Federated Learning (VFL). These enhancements were built upon the existing architecture where ADAES can consume AIMLE services over the AIML-X interface for deriving ML-enabled analytics. Furthermore, the release included updates to the overall application enablement architecture to integrate these new capabilities.

  • Support monitoring ML-enabled analytics correctness TS 23.436CR0064
  • Sample Alignment Enablement for VAL Servers in VFL TS 23.482CR0062
  • Update application enablement architecture TS 23.482CR0069

Explore further

Broader topics and technologies where ADAES plays a role.

Defining Specifications

3GPP specifications that define or reference ADAES, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.436 vk00 ADAEnabler Functional Architecture and Information Flows Rel-20
TS 23.482 vk00 AIML Enablement Service Architecture Rel-20
TS 23.700 vk00 XR Services Application Enablement Layer Rel-20
TS 24.558 vj50 Edge Enabler APIs Stage 3 Rel-19
TS 24.559 vj41 Application Data Analytics Enablement Services Rel-19
TS 29.549 vj40 SEAL API Specification for Vertical Applications Rel-19