Description
The 5G System Unified Data Repository (5GS UDR) is a core network function defined in 3GPP TS 23.501 (clause 4.2.5) that provides a centralized, converged repository for storing and retrieving subscription, policy, and application-related data in the 5G Service Based Architecture (SBA). Rather than each control-plane function maintaining its own siloed database, the UDR acts as the single authoritative data store that multiple Network Functions (NFs) query through standardized service-based interfaces.
Architecturally, the UDR sits behind the Unified Data Management (UDM), the Policy Control Function (PCF), the Network Exposure Function (NEF), and the Service Capability Exposure Function (SCEF) in interworking scenarios. Each of these consumers accesses the UDR through its own reference point: the UDM uses Nudr to store and retrieve subscription data, the PCF uses Nudr to manage policy and session management data, and the NEF uses Nudr to store structured data for exposure to third parties.
The data held by the UDR is organized into distinct data sets. Subscription data includes UE subscription information such as access and mobility subscription data, session management subscription data, and SMS subscription data. Policy data includes policy control subscription information and session management policy data used by the PCF. Structured data for exposure includes application-specific data that the NEF exposes to external application functions. Additionally, the UDR stores application data and, in later releases, data related to network analytics and slice-specific information. This partitioning allows each consumer NF to retrieve only the data set relevant to its function while sharing a common storage backend.
Operationally, the UDR supports the separation of control-plane logic from data storage, a key principle of the 5G SBA. When a UE registers, the AMF interacts with the UDM, which in turn retrieves and updates subscription data in the UDR. When a PDU session is established, the SMF obtains session management policy from the PCF, which reads and writes policy data in the UDR. This layered access ensures that data consistency is maintained centrally while the business logic remains distributed across NFs. The UDR can be deployed as a standalone NF or co-located with the UDM in a converged deployment, and it supports high availability through replication and load balancing across multiple UDR instances.
The 5GS UDR is fundamental to the convergence of access technologies in 5G. Because it stores data for both 3GPP and non-3GPP access, and serves both the UDM and PCF, it enables a unified subscriber data model that spans mobility management, session management, and policy control. This convergence reduces data duplication, simplifies consistency management, and provides a single point for lawful interception and data governance. The term was formally introduced in Release 16 specifications (TS 23.732, TS 23.973) to standardize the repository concept across the 5G core, and it has been carried forward unchanged through Releases 17, 18, and 19.
Purpose & Motivation
The 5GS UDR exists to solve the problem of fragmented and duplicated subscriber and policy data that plagued earlier generations of mobile core networks. In 4G EPC, the HSS maintained subscription data while the PCRF maintained policy data, and each element kept its own database with proprietary interfaces. This led to data inconsistency, complex synchronization, and difficulty in exposing data to third parties. The 5G SBA demanded a cleaner separation of concerns, where storage is decoupled from control logic and accessed through standardized, resource-oriented APIs.
By centralizing subscription, policy, and exposure data in a single repository, the UDR enables any authorized NF to retrieve consistent data through the Nudr interface, eliminating the need for point-to-point database replication between HSS-like and PCRF-like functions. It also supports the convergence of 3GPP and non-3GPP access by providing one data model for all access types, and it simplifies the introduction of new services because new data sets can be added to the repository without redesigning each consumer NF.
The UDR additionally underpins network exposure and third-party integration. The NEF relies on the UDR to store structured data that external application functions can query, enabling services such as device triggering and background data transfer. This design supports the broader 5G goal of programmable, service-oriented core networks where data is a first-class, standardized asset rather than a function-specific byproduct.
Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Defining Specifications
3GPP specifications that define or reference 5GS UDR, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 23.732 vg00 | User Data Interworking, Coexistence, Migration Study | Rel-16 read |
| TR 23.973 vj00 | Separate HSS/UDM Deployment Scenarios & Solutions | Rel-19 read |