Description
The 5G Repository is a conceptual and architectural element in the 5G System that hosts subscription data for 5G User Equipment (UEs). It is referenced in 3GPP study and technical report specifications such as TS 23.732 and TS 23.973, which examine data storage, data management and related architectural aspects of the 5G core. In the concrete 5G Core (5GC) architecture defined in TS 23.501, this repository role is realised primarily by the Unified Data Repository (UDR), which stores subscription data, policy data and structured data for exposure, and by the Unified Data Management (UDM) function that fronts this data toward other network functions.
The repository is a data-layer entity rather than a signalling entity. It does not participate directly in NAS or RRC procedures; instead, it is accessed by control-plane network functions through service-based interfaces. The UDM uses the Nudr interface to read and write subscriber data in the UDR, while the PCF uses Nudr to access policy-related subscription information. Application Functions and other consumers may access data through the UDM's Nudm services or through the Network Exposure Function (NEF). This separation of data storage from data processing follows the control and user plane separation (CUPS) philosophy and enables a stateless, cloud-native core network.
Subscription data held in the repository includes permanent subscriber identifiers (SUPI), authentication credentials and subscription information, access and mobility subscription data, session management subscription data (including per-slice and per-DNN information), SMS subscription data, and policy data such as the subscriber's QoS and charging profiles. The repository also stores structured data for exposure, including event monitoring subscriptions and background data transfer policies. Because this data is centralised, multiple network functions can access a consistent view of subscriber state, which is essential for mobility, session management and policy enforcement.
The repository is designed to be highly available and scalable, typically deployed as a distributed database or as a set of UDR instances partitioned by data type or subscriber range. Data consistency is maintained through the UDM's role as the single point of authority for subscription data modification. When a subscriber's data changes — for example, due to a subscription update or a policy change — the UDM notifies the relevant consumers (such as AMF or SMF) so that they can update their local contexts. This event-based notification model is a hallmark of the 5G service-based architecture.
The 5G Repository concept also underpins network slicing, because slice-specific subscription data (allowed S-NSSAIs, slice-specific QoS) must be stored and retrieved per subscriber. It supports the separation of concerns between data storage, data management and data exposure, and it enables operators to build a unified subscriber data layer that serves 5G, 4G (via interworking) and fixed-mobile convergence scenarios. The definition of the term has remained unchanged from Rel-16 through Rel-19, reflecting the stability of the underlying data architecture.
Purpose & Motivation
The 5G Repository exists to provide a centralised, consistent and scalable store for subscriber-related data in the 5G core network. In earlier generations, subscriber data was tightly coupled to specific network elements — for example, the HSS in EPC combined data storage with authentication and mobility management functions. This monolithic design made it difficult to scale data storage independently, to share data across multiple functions, and to support the service-based architecture that 5G introduced.
By separating the data layer (the repository) from the data management and exposure functions (UDM, PCF, NEF), 5G enables a stateless core network in which control-plane functions can be instantiated, scaled and replaced without losing subscriber state. This is essential for cloud-native deployments, network slicing and multi-vendor environments. It also allows a single repository to serve multiple purposes — subscription data, policy data and exposure data — reducing duplication and inconsistency.
The repository concept was motivated by the need to support new 5G capabilities such as network slicing, where slice-specific subscription data must be stored and retrieved efficiently, and by the need for standardised data access interfaces (Nudr) that allow different vendors' network functions to interoperate. It also supports regulatory and operational requirements for data retention, auditing and exposure to third parties through the NEF. The study work captured in TS 23.732 and TS 23.973 explored further enhancements to data storage and management, confirming the repository as a foundational element of the 5G data architecture.
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 5G Repository, 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 |