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
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (3 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 18, the ADAES (Application Data Analytics Enablement Services) function was formally introduced, establishing its service-based interface (SAdae) and its role in the SEAL architecture. It specifically gained new analytics functionalities for VAL performance analytics on tethered UEs and for DN Energy Analytics per DNN/DNAI. Furthermore, the release defined ADAES's interaction with AIMLE servers via the AIML-X reference point to support ML-enabled analytics and detailed procedures for subscribing to data producers and ADAEC for analytics events.
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.
| Specification | Title | Release |
|---|---|---|
| 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 |