Description
The Analytical Data Repository Function (ADRF) is a standardized network function introduced in 3GPP Release 17 as part of the 5G architecture's management and orchestration framework. It serves as a centralized data storage and management entity specifically designed to support network analytics functions. The ADRF operates by collecting, aggregating, and persistently storing various types of network data, including performance measurements, configuration data, subscriber information, and service usage patterns. This data is then made available to authorized analytics consumers through standardized northbound interfaces, primarily supporting the Network Data Analytics Function (NWDAF) and the Management Data Analytics Function (MDAF).
Architecturally, the ADRF is implemented as a standalone network function with well-defined service-based interfaces (SBIs) that follow the 3GPP's service-based architecture principles. It exposes services such as Nnrf_NFManagement, Nnrf_NFDiscovery, and specific data management services defined in the 29.5xx series specifications. The ADRF's internal architecture typically includes data ingestion modules, storage management layers, data processing engines, and policy enforcement components. It supports various data storage technologies and can handle both structured and unstructured data formats, with mechanisms for data lifecycle management including retention policies, archiving, and data purging.
In operation, the ADRF receives data from multiple sources including network functions (NFs), operations support systems (OSS), and external data providers. It applies data validation, normalization, and enrichment processes before storage. The function implements sophisticated data organization schemes including time-series databases, key-value stores, and relational databases to optimize different query patterns. Security is paramount, with the ADRF implementing access control policies, data encryption at rest and in transit, and audit logging for all data access operations. It also supports data anonymization and pseudonymization to protect subscriber privacy while maintaining analytical utility.
The ADRF plays a critical role in enabling data-driven network operations by providing a single source of truth for analytics data. It eliminates data silos that previously existed across different network domains and management systems. By standardizing data formats and access methods, the ADRF reduces integration complexity for analytics applications and enables more sophisticated cross-domain analytics. Its scalable architecture supports the massive data volumes generated by 5G networks while maintaining performance for real-time and near-real-time analytics use cases.
Purpose & Motivation
The ADRF was created to address the growing need for centralized, standardized data management in 5G networks, particularly to support advanced analytics and artificial intelligence/machine learning (AI/ML) applications. Prior to its introduction, network analytics functions had to collect data from disparate sources using proprietary interfaces and formats, leading to integration challenges, data inconsistencies, and limited scalability. This fragmented approach hindered the development of comprehensive network analytics and automated optimization capabilities that are essential for 5G's promised network automation and intelligence.
Historically, network operators managed analytics data through multiple siloed systems including performance management systems, fault management systems, and various operational databases. Each analytics application required custom integration with these data sources, resulting in high development costs, maintenance overhead, and delayed time-to-market for new analytics services. The lack of standardized data models and interfaces also made it difficult to correlate data across different network domains or to implement consistent data governance and security policies.
The ADRF solves these problems by providing a unified, standards-based approach to analytics data management. It enables network operators to implement consistent data collection, storage, and access policies across their entire network infrastructure. By decoupling data storage from analytics processing, the ADRF allows analytics functions to focus on their core analytical tasks rather than data management complexities. This architectural separation also enables more efficient resource utilization, as multiple analytics functions can share the same data repository rather than each maintaining duplicate copies of data. The ADRF's standardized interfaces facilitate ecosystem development, allowing third-party analytics applications to integrate more easily with operator networks.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (143 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, the Analytical Data Repository Function (ADRF) was newly introduced as a logical function within the 5G network data analytics architecture. It is defined alongside the NWDAF, DCCF, and other network functions, with its service-based interface designated as Nadrf. The specification clarifies that the ADRF's functionalities can also be hosted by an NWDAF instance.
In Release 16, the ADRF (Analytics Data Repository Function) was formally introduced as a logical function, separate from but potentially hosted within an NWDAF, for storing analytics data. The specification defined its service-based interface, called Nadrf, and clarified its architectural relationship with other functions like the DCCF within the network data analytics framework. These changes provided the foundational standardization for the ADRF's role in the 5G analytics architecture.
- Use of NWDAF analytics for decision of MICO mode parameters TS 23.501CR0837
- NEF service for NWDAF analytics TS 23.501CR0964
- CR for TS 23.501 Clarifications NWDAF Discovery and Selection TS 23.501CR0987
- CR for TS 23.501 Clarifications NWDAF Discovery and Selection TS 23.501CR1258
- Consistency on Definitions related to NWDAF TS 23.501CR1787
- Corrections to NWDAF discovery and selection TS 23.501CR1992
+ 9 more changes
In Release 17, the ADRF (Analytics Data Repository Function) was formally introduced as a new functional entity with its own service-based interface, Nadrf. The release specified new procedures for the ADRF, including support for the removal of stored analytics and data according to a provided specification and the capability to carry an ADRF ID within the Nmfaf_3daDataManagement_Configure service operation.
- Network Slice restriction based on NWDAF analytics TS 23.501CR2567
- NWDAF discovery and selection TS 23.501CR2575
- NWDAF Discovery TS 23.501CR2577
- Extensions of NWDAF services TS 23.501CR2584
- NWDAF discovery and selection based on provided ML models TS 23.501CR2585
- UP path selection enhancement based on analytics info provided by NWDAF TS 23.501CR2586
+ 43 more changes
In Release 18, the ADRF (Analytics Data Repository Function) saw enhancements to its discovery and selection procedures, specifically to account for Machine Learning (ML) model management capabilities and to support NWDAFs engaged in Federated Learning. The update also expanded ADRF services, including enhancements to the Nnwdaf_MLModelProvision API to support ML model retrieval with ADRF, and introduced user consent management improvements for NWDAF analytics subscriptions and data management.
- Discovery and Selection of the NWDAF Supporting Federated Learning in 5GC TS 23.501CR3772
- NWDAF discovery principle enhancements for enhanced model sharing TS 23.501CR3783
- Considering ML model management capability during ADRF discovery and selection TS 23.501CR3929
- Discovery and selection of NWDAF with FL support - Resolve EN TS 23.501CR4070
- Update NEF to support NWDAF-assisted application detection TS 23.501CR4105
- Extension of NWDAF registration information to reflect new accuracy checking capability TS 23.501CR3764
+ 46 more changes
In Release 19, the ADRF was enhanced to become a formal consumer of key NWDAF services, specifically the Nnwdaf_EventsSubscription and Nnwdaf_AnalyticsInfo services, as well as the Nnwdaf_DataManagement_Fetch service. This release also introduced explicit support for the ADRF's identifier and its storage handling information within analytics subscriptions. Furthermore, new procedures were defined to support the storage of NWDAF analytics data directly in the ADRF via notifications.
- VFL support during the discovery of NWDAF, NEF, and AF instances TS 23.501CR5630
- NWDAF model provision for AI positioning TS 23.501CR5635
- NWDAF discovery and selection parameters TS 23.501CR5978
- Adding ADRF as a consumer of Nnwdaf_EventsSubscription and Nnwdaf_AnalyticsInfo Services TS 29.520CR0969
- Clarifications and miscellaneous corrections on NWDAF services TS 29.520CR0984
- Support of ADRF ID and storage handling information in Analytics subscription TS 29.520CR1134
+ 19 more changes
Explore further
Broader topics and technologies where ADRF plays a role.
Defining Specifications
3GPP specifications that define or reference ADRF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.501 vk00 | 5G System Architecture Stage 2 | Rel-20 |
| TS 23.700 vk00 | XR Services Application Enablement Layer | Rel-20 |
| TS 29.520 vj40 | 5G Network Data Analytics Services Stage 3 | Rel-19 |
| TS 29.552 vj40 | 5G Network Data Analytics Signalling Flows | Rel-19 |
| TS 29.574 vj40 | 5G Data Collection Coordination Services Stage 3 | Rel-19 |
| TS 29.575 vj40 | 5G Analytics Data Repository Services Stage 3 | Rel-19 |
| TS 29.576 vj40 | 5G Messaging Framework Adaptor Services Stage 3 | Rel-19 |