Description
The Unified Data Repository (UDR) is a critical component within the 5G Core (5GC) Service-Based Architecture (SBA), defined by 3GPP. It acts as a centralized, standardized data storage entity for structured data, decoupling data storage from application logic. The UDR stores various data profiles, including Subscription Data (used by the Unified Data Management, UDM), Policy Data (used by the Policy Control Function, PCF), Application Data (used by Network Exposure Function, NEF), and Structured Data for Network Slicing. Architecturally, the UDR exposes a northbound service-based interface (Nudr) using HTTP/2 and JSON, allowing other Network Functions (NFs) like UDM, PCF, and NEF to access and manage data via standardized API operations such as Nudr_DM (Data Management) and Nudr_DR (Data Repository).
Internally, the UDR organizes data into Data Sets, which are collections of data of a specific type for a given user or service. For example, subscription data for a user is stored in a specific data set. The UDR ensures data consistency, integrity, and availability. It supports operations like Create, Read, Update, Delete, and Query (CRUDQ) on these data sets. The repository is designed to be highly scalable and reliable, often implemented with distributed database technologies to handle the massive data volumes and low-latency access requirements of 5G networks. Its role is purely for storage and retrieval; the application logic (e.g., authentication decisions by UDM) resides in the consumer NFs.
The UDR's implementation enables a clear separation between data storage and data usage logic, which is a key principle of the 5GC SBA. This separation allows for independent scalability of storage and processing functions, simplifies upgrades, and fosters innovation. For instance, the UDM can focus on subscription management logic while relying on the UDR for persistent storage. The UDR also supports network slicing by storing slice-specific subscription and policy data, allowing different slices to have isolated or shared data sets as needed. Furthermore, it facilitates data exposure to authorized third-party applications via the NEF, enabling new service paradigms.
Purpose & Motivation
The UDR was created to address the data fragmentation and siloed storage issues present in previous mobile network generations like 4G EPC. In EPC, data was often stored in dedicated, function-specific repositories (e.g., HSS for subscription, SPR for policy), leading to duplication, inconsistency, and complex integration. The 5G vision required a more agile, cloud-native, and service-oriented core network to support diverse use cases from enhanced mobile broadband to massive IoT and ultra-reliable low-latency communications.
The UDR solves these problems by providing a unified, centralized repository for all structured data in the 5GC. This consolidation eliminates data redundancy, ensures a single source of truth, and simplifies data management operations. It directly supports the 5GC's Service-Based Architecture by offering a standardized data storage service that any authorized network function can consume via APIs. This design is essential for enabling network slicing, as each slice can have its dedicated data profiles stored and managed within the same UDR infrastructure, ensuring isolation and efficient resource utilization. The UDR thus future-proofs the network for data-driven services and flexible service deployment.
What changed in its specifications
The latest release-to-release comparison of specifications that define UDR. Each summary describes the whole specification, not only this term.
NB-IoT/eMTC support for Non-Terrestrial Networks: adds QCI characteristic for satellite access, note on GEO/LEO delays, and PCRF policy control for satellite PDN connections.
Full comparison in TS 23.203 →Rel-19 adds Enhanced Mission Critical Architecture changes, including location reporting trigger cancel and override indication. It also adds location reporting and location information request procedures for mission critical clients on non-3GPP devices behind a UE or 5G-RG.
Full comparison in TS 23.280 →Architecture
Where it sits in the network
- Mobile Network → 5G Core → UDR (Shared Data Environment)
Evolution Lineage
- Evolved from: HSS (4G→5G)
- Network evolution overview →
Technology family
Core network elements and functions · Core Network
- Phase 1 AuC, EIR, GMSC, HLR, IWF, MSC, VLR
- Phase 2 SMS-GMSC, SMS-IWMSC
- R96 GGSN, SGSN
- R99 3G-SGSN, GLR, IM-GSN, IM-MSC
- Rel-4 CS-MGW, GMSC Server, MSC Server
- Rel-5 HSS, SLF
- Rel-6 3GPP AAA Server
- Rel-7 PCEF, PCRF
- Rel-8 ANDSF, BBERF, ePDG, MME, PGW, SGW
- Rel-9 HLR-FE, HSS-FE, UDR
- Rel-10 L-GW
- Rel-11 TDF
- Rel-14 PGW-C, PGW-U, SGW-C, SGW-U, TDF-C, TDF-U
- Rel-15 AMF, AUSF, PCF, SMF, SMF+PGW-C, UDM, UPF
- UDR used together with HSS-FE
“UDR provides a unique reference point to one or more Applications Front Ends, such as: one or more HSS/HLR/AuC-FEs, and one or more AS- FEs.” TS 23.335
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 7 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.
Introduced in Rel-9 (release dating of the term; no individual change cited).
The UDR and its Nudr_DataRepository service are specified for the first time, with stage 3 APIs for policy, application and exposure data and the UDR's role in 5GC procedures.
- “The Unified Data Repository (UDR) provides the Unified Data Repository service. This service provides a repository for policy data, application data and exposure data.” TS 29.519 v15.13.0
- “The present specification provides the stage 3 definition for the usage of the Unified Data Repository service (Nudr_DataRepository) of 5G System” TS 29.519 v15.13.0
- “UDR stores the provisioned data as part of the subscription data and responds with Nudr_DM_Update Response message.” TS 23.502 v15.17.0
In Rel-16 the UDR gained new functionality: NF Group ID mapping service, subscription segmentation, storage of applied BDT policy data, and extra Nudr consumers such as NRF.
- “This service allows NF service consumers to retrieve, NfGroupId data stored in the UDR.” TS 29.504 v16.14.0
- Adding UDR NF Group ID association functionality TS 23.501CR1384
- “The Nudr interface is used by the network functions (i.e. UDM, PCF, NEF and NRF) to access a particular set of the data stored in the UDR.” TS 29.504 v16.14.0
In Rel-17 the UDR gained new behaviour: restoration notifications to consumers after data loss, storage of non-subscriber data, and new query handling and application data models.
- “The DataRestorationNotification service operation is used for the UDR to send notfications on UDR restoration event to one or a set of NFs” TS 29.504 v17.21.0
- UDR storing of non-subscriber related data TS 23.501CR3650
- “the UDR shall identify the identity of the NF service consumer via the NF instance ID” TS 29.504 v17.21.0
In Rel-18 the UDR gained new stored data and behaviour, including DNAI-EAS mapping data, PDTQ policy data, policy counter storage and new query parameters and features such as GMEC and ImmediateReport.
- New PDTQ related UDR PolicyData subset TS 29.510CR0870
- DNAI-EAS Mappings data subset in the UDR TS 29.504CR0241
- “The UDR shall return only Individual Influence Data resource(s) that match one of the provided internal group IDs” TS 29.519 v18.11.0
UDR gained new roles and behaviour in Rel-19: storing non-3GPP device identifier information, supporting Ambient IoT data, additional Nudr consumers (ADM), data-loss and migration handling, and expanded query filtering.
- “PCF retrieves, if not already available, Non-3GPP Device Identifier Information for the corresponding Non-3GPP Device Identifier from the UDR by invoking Nudr_DM_Query” TS 23.502 v19.9.0
- “The known NF Service Consumers are the UDM, PCF, NEF and ADM.” TS 29.504 v19.8.0
- Update UDR description for Ambient IoT TS 23.501CR6409
UDR's role changed in Rel-20: it stores energy-related BDT/PDTQ information from the H-PCF, PDTQ storage in UDR became optional, ESI was added to the UDR Data Management service, and ADM became a UDR consumer.
- “The H-PCF may store the PDTQ Reference ID together with the new PDTQ policy and the relevant AF provided information” TS 23.502 v20.3.0
- Adding ESI in the UDR Data Management service TS 23.502CR5780
- “the NF service consumer (e.g. UDM, PCF, NEF or ADM) sends a request to the UDR to subscribe to data change notifications” TS 29.504 v20.1.0
Defining Specifications
3GPP specifications that define or reference UDR, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 22.985 vj00 | 3GPP User Data Convergence (UDC) concept | Rel-19 read |
| TS 23.203 vk10 | Policy and Charging Control Architecture | Rel-20 read |
| TS 23.280 vk51 | Mission Critical Services Architecture | Rel-20 read |
| TS 23.335 vj00 | User Data Convergence (UDC) Procedures | Rel-19 read |
| TS 23.501 vk30 | 5G System Architecture | Rel-20 read |
| TS 23.845 va00 | UDC Evolution Study | Rel-10 read |
| TS 23.862 vc00 | Operator-DAP Interworking Architecture | Rel-12 read |
| TS 26.804 vk10 | 5G Media Delivery Architecture Extensions | Rel-20 read |
| TS 26.891 vg00 | Media Distribution Services in 5G System | Rel-16 read |
| TR 26.919 vj00 | Study on 5G Conversational Media Handling | Rel-19 read |
| TS 28.540 vk40 | 5G Network Resource Model (NRM) Stage 1 | Rel-20 read |
| TR 28.840 vi10 | Technical Report | Rel-18 read |
| TS 29.201 vj00 | RESTful Rx Interface for AF-PC Communication | Rel-19 read |
| TS 29.212 vk00 | Diameter-Based PCC Reference Points | Rel-20 read |
| TS 29.213 vj30 | PCC Procedures and Flows | Rel-19 read |
| TS 29.214 vk00 | Rx Interface for Policy and Charging Control | Rel-20 read |
| TS 29.215 vj00 | S9 Reference Point Stage 3 Specification | Rel-19 read |
| TS 29.335 vj00 | Ud Interface Protocol for UDC (Stage 3) | Rel-19 read |
| TS 29.503 vk10 | UDM Service Based Interface | Rel-20 read |
| TS 29.504 vk10 | Nudr Unified Data Repository Services | Rel-20 read |
| TS 29.505 vk00 | UDR Services for Subscription Data | Rel-20 read |
| TS 29.512 vk10 | Session Management Policy Control Service Stage 3 | Rel-20 read |
| TS 29.513 vk10 | 5G PCC Signalling Flows | Rel-20 read |
| TS 29.514 vk10 | Policy Authorization Service | Rel-20 read |
| TS 29.519 vk10 | 5G UDR Policy and Application Data Services | Rel-20 read |
| TS 29.521 vk10 | Binding Support Management Service | Rel-20 read |
| TS 29.522 vk10 | NEF Northbound Interface | Rel-20 read |
| TS 29.523 vk10 | Policy Control Event Exposure Service | Rel-20 read |
| TS 29.525 vk10 | UE Policy Control Service | Rel-20 read |
| TS 29.543 vk10 | Data Transfer Policy Control Services | Rel-20 read |
| TS 29.554 vk10 | BDT Policy Control Service | Rel-20 read |
| TS 29.562 vk10 | HSS Nhss Services for IMS and GBA | Rel-20 read |
| TS 29.563 vk00 | Nhss Services for 5G SBA Stage 3 | Rel-20 read |
| TS 29.808 vg00 | Study on Nudsf Service Based Interface | Rel-16 read |
| TS 29.817 vc10 | Study on XML-based Rx interface for PCC | Rel-12 read |
| TS 29.866 vj00 | IMS Disaster Prevention & Restoration Enhancement | Rel-19 read |
| TS 29.890 vg00 | CT3 5G System Technical Report | Rel-16 read |
| TS 32.181 vj00 | User Data Convergence Management Framework | Rel-19 read |
| TS 32.182 vj00 | UDC Common Baseline Information Model (CBIM) | Rel-19 read |
| TS 32.255 vk30 | 5G Data Connectivity Converged Charging | Rel-20 read |
| TS 32.256 vk10 | 5G Connection and Mobility Charging | Rel-20 read |
| TS 32.808 v800 | Common Profile Storage Framework for User Data | Rel-8 read |
| TS 32.843 vd00 | Inter-PLMN Online Charging for Roaming | Rel-13 read |
| TR 32.901 vj00 | UDC Application Data Models Study | Rel-19 read |
| TS 33.127 vj80 | Lawful Interception Architecture | Rel-19 read |
| TS 33.501 vk30 | 5G Security Architecture | Rel-20 read |
| TS 33.514 vk20 | UDM Security Assurance Specification | Rel-20 read |
| TS 33.530 vj00 | Security Assurance for Unified Data Repository | Rel-19 read |