Application layer - Analytical Data Repository Function

Description

The Application layer - Analytical Data Repository Function (A-ADRF) is a logical function defined within the 3GPP service-based architecture for network data analytics. It operates at the application layer, separate from the user plane and control plane, and is designed as a centralized or distributed repository that stores structured analytical data. This data can include network performance metrics, user equipment (UE) behavior patterns, service usage statistics, and other information generated by various network functions (NFs) and external application functions (AFs). The A-ADRF exposes northbound APIs, primarily specified in 3GPP TS 29.549, allowing authorized consumers like the Network Data Analytics Function (NWDAF), other A-ADRFs, or third-party analytics applications to store, retrieve, query, and subscribe to data updates in a standardized manner.

Architecturally, the A-ADRF interfaces with data producers and consumers via service-based interfaces (SBIs) within the 5G core network. It is part of the broader data analytics framework that includes functions like the NWDAF for analytics generation and the ADRF (a core network function) for storing raw or processed data. The A-ADRF distinguishes itself by focusing on application-layer data, which may be more abstract or service-oriented compared to network-layer data. Key components include data ingestion modules that handle incoming data streams via APIs, a storage backend that could leverage databases or data lakes, data management capabilities for lifecycle control (e.g., retention policies, anonymization), and query processing engines to support complex analytical requests. It supports various data formats and schemas as defined in 3GPP specifications, ensuring interoperability.

In operation, the A-ADRF works by receiving data from producers—such as an NWDAF that has generated analytics insights or an AF providing application-specific metrics—through standardized HTTP-based RESTful APIs. It stores this data persistently, applying any required data processing like aggregation, filtering, or formatting. Consumers can then access the data on-demand via query interfaces or set up subscriptions for real-time notifications when new data matching certain criteria is available. This enables use cases like training machine learning models for network optimization, where historical data from the A-ADRF is fed into AI workflows. The A-ADRF also supports data federation, allowing multiple A-ADRFs to exchange data, which is crucial for large-scale or cross-domain analytics scenarios. Its role is to decouple data storage from analytics processing, promoting reusability, scalability, and efficient data management in 5G and future networks.

Purpose & Motivation

The A-ADRF was created to address the increasing complexity and data-intensive nature of modern mobile networks, particularly with the rollout of 5G and the vision for 6G. Prior to its introduction, analytical data in 3GPP systems was often handled in an ad-hoc manner, with analytics functions like the NWDAF storing data internally or relying on non-standardized repositories. This led to challenges in data sharing, interoperability, and scalability, as different network functions and external applications could not easily access or contribute to a common data pool. The lack of a standardized repository hindered the development of advanced analytics, AI/ML applications, and automated network management, which require large, diverse datasets for training and inference.

Historically, 3GPP began enhancing data analytics capabilities with the introduction of the NWDAF in Release 15, which focused on generating analytics. However, as networks evolved towards greater intelligence and automation, the need for a dedicated, scalable data storage function became apparent. The A-ADRF, introduced in Release 18, solves this by providing a unified, application-layer repository that separates data storage from analytics logic. This aligns with industry trends toward data-driven operations and supports use cases like network slicing optimization, predictive maintenance, and quality of experience (QoE) enhancement. By standardizing interfaces and data models, it enables ecosystem innovation, allowing vendors and operators to build compatible analytics solutions without proprietary lock-in.

The motivation for the A-ADRF also stems from the limitations of previous approaches, where data silos and non-standard interfaces made it difficult to perform cross-domain analytics or integrate third-party AI tools. For example, without the A-ADRF, an operator might struggle to correlate application-layer data from Over-the-Top (OTT) services with network performance data for end-to-end service assurance. The A-ADRF addresses this by offering a flexible repository that can store diverse data types, support federation across domains, and provide secure, controlled access. This facilitates the realization of 3GPP's vision for an automated, intelligent network that leverages data to improve efficiency, user experience, and service innovation.

Key Features

• Standardized RESTful APIs for data ingestion and consumption (based on 3GPP TS 29.549)
• Support for persistent storage of structured analytical data from network and application sources
• Data lifecycle management including retention policies and anonymization capabilities
• Subscription and notification mechanisms for real-time data updates
• Query interfaces enabling complex data retrieval for analytics and AI/ML workflows
• Federation capabilities allowing data exchange between multiple A-ADRFs across domains

Evolution Across Releases

Defining Specifications