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.
What changed in its specifications
The latest release-to-release comparison of specifications that define ADRF. Each summary describes the whole specification, not only this term.
Rel-19 added MPQUIC steering to multi-access PDU sessions, XR and media handling, and an Energy Information Function. It also added Local Offloading Management for edge computing, Vertical Federated Learning for AI/ML, and Ambient IoT text.
Full comparison in TS 23.501 →Rel-19 adds Vertical Federated Learning training and inference APIs to TS 29.520, along with signalling storm, QoS/policy, and roaming analytics subscriptions. It also extends NWDAF ML model provisioning, event subscription fields, and 308 Permanent Redirect responses.
Full comparison in TS 29.520 →Technology family
Network exposure and analytics · Core Network
- Rel-11 SCS/AS
- Rel-13 IWK-SCEF, SCEF
- Rel-15 CAPIF, NEF, NWDAF
- Rel-16 SCEF+NEF
- Rel-17 ADRF, AnLF, DCCF, L-NEF, MDAF, MFAF, MTLF
- Rel-18 RE-NWDAF
- ADRF used together with DCCF
“Based on the NF request or configuration on the DCCF, the DCCF may determine the ADRF and interact directly or indirectly with the ADRF to request or store data or analytics.” TS 23.288
- ADRF used together with NWDAF
“The functionalities provided by DCCF and/or ADRF can also be hosted by an NWDAF.” TS 23.501
Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.
Release Timeline
Detected Changes Across Releases
verified against 3GPP sourcesDocumented changes in 4 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.
ADRF and its Nadrf_DataManagement services (storage, retrieval, subscription, removal) are specified for the first time, including stored-data handling, DCCF/MFAF/NWDAF interactions and the Nadrf API.
- “The ADRF stores data received in an Nadrf_DataManagement_StorageRequest sent directly from an NF” TS 23.288 v17.12.0
- “Upon the reception of an HTTP POST request with "{apiRoot}/nadrf-datamanagement/<apiVersion>/data-store-records" as Resource URI” TS 29.575 v17.7.0
- New ADRF NF Registration and Discovery TS 29.510CR0562
In Rel-18 the ADRF gained ML model storage/retrieval, DataSetTag-based data storage, a Storage Approach with deletion alerts, and new Nadrf service operations and API resources.
- “The ADRF may store, provide or delete ML Model(s) based on the Nadrf_MLModelManagement service received from NWDAF.” TS 23.288 v18.13.0
- “If indicated by the Storage Approach, the ADRF sends a notification alerting the DCCF or NWDAF that data are about to be deleted.” TS 23.288 v18.13.0
- ML Model storage and retrieval via ADRF TS 23.288CR0641
ADRF behaviour was extended in Rel-19: it can store analytics and ML models for LMF-based AI/ML positioning, store NWDAF analytics via notifications, and gains ML model storage/retrieval and feature-negotiation changes.
- “is used by consumers (NWDAF containing MTLF, NWDAF containing AnLF or LMF) to retrieve ML Models from an ADRF.” TS 23.288 v19.8.0
- NWDAF Analytics Storage in ADRF via Notifications TS 29.552CR0131
- “If the subscription is for runtime analytics (i.e. the "histAnaTimePeriod" attribute is absent) then the NWDAF shall store the notifications in this ADRF.” TS 29.520 v19.8.0
Rel-20 adds ADRF-related management information and measurements: hosting ADRF information in NWDAFFunction and new measurements for ADRF storage services, and extends ML model ADRF information to the Ue_Positioning feature.
- Add hosting ADRF information to NWDAFFunction TS 28.541CR1713
- Add new measurements related to ADRF storage services when NWDAF hosting ADRF TS 28.552CR0747
- “if the "ModelProvisionExt" or "Ue_Positioning" feature is supported, the ADRF (Set) information of the ML Model” TS 29.520 v20.1.0
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 vk30 | 5G System Architecture | Rel-20 read |
| TS 23.700 vk10 | AI/ML Application Layer Support Phase 2 | Rel-20 read |
| TS 29.520 vk10 | 5G NWDAF Services | Rel-20 read |
| TS 29.552 vk10 | 5G Network Data Analytics Procedures | Rel-20 read |
| TS 29.574 vk10 | DCCF Service Based Interface | Rel-20 read |
| TS 29.575 vk10 | ADRF Service Based Interface | Rel-20 read |
| TS 29.576 vk10 | MFAF Service Based Interface | Rel-20 read |