Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Core Network

EPS UDR

EPS User Data Repository

Core Network →

EPS UDR is a logical entity in the 5G core network, defined in 3GPP TS 23.335, that stores subscription and policy data for EPS (4G) users and enables unified data management across access technologies.

Introduced
Rel-16
Where
Core Network › 5G Core
Specifications
2 specs
EPS UDR Description Purpose Neighbours Specifications

Description

The EPS User Data Repository (EPS UDR) is a term used in 3GPP specifications to identify the User Data Repository (UDR) as defined in TS 23.335, clause 4.2.3. The UDR is a functional element within the 5G Service-Based Architecture (SBA) that serves as a consolidated repository for user-related data, including subscription data, policy data, and application-specific data. The EPS UDR specifically refers to the instance or partition of the UDR that stores data related to Evolved Packet System (EPS) subscribers, i.e., users accessing the network via LTE or other 4G access technologies.

In the 5G core network architecture, the UDR is part of the Unified Data Management (UDM) and Policy Control Function (PCF) ecosystem. It provides a standardized interface (Nudr) for other network functions to store and retrieve data. The UDR can be deployed as a standalone database or as part of a larger data layer. The EPS UDR is essentially a data set within the UDR that contains EPS-specific subscription information, such as EPS bearer QoS profiles, APN configurations, and mobility restrictions. This allows the 5G core to serve EPS users seamlessly, even when they are not yet migrated to 5G standalone.

The concept of EPS UDR emerged in Release 16 as part of the broader effort to converge core network data management across generations. Prior to this, 4G networks used the Home Subscriber Server (HSS) and Subscription Profile Repository (SPR) as separate entities. The 5G core introduced the UDM and UDR to unify data storage, but interworking with EPS required a way to represent EPS subscription data within the 5G data framework. The EPS UDR serves this purpose by providing a standardized data model and interface for EPS-related data, enabling the UDM to act as a front-end for both 5G and 4G subscribers.

From an architectural standpoint, the EPS UDR is accessed by the UDM and PCF via the Nudr service-based interface. The UDM uses the EPS UDR to retrieve authentication vectors, subscription profiles, and access restrictions for EPS users. The PCF uses it to obtain policy data for EPS sessions. The data model for the EPS UDR is defined in TS 23.335, which specifies the structure of the data (e.g., subscription data, policy data, exposure data) and the operations that can be performed on it. The EPS UDR is thus a key enabler for unified data management, allowing operators to maintain a single data repository for both 4G and 5G subscribers.

In Releases 17, 18, and 19, the definition of EPS UDR remained unchanged, indicating that the initial specification was stable and sufficient. The term continues to be used in the context of 5G core interworking with EPS, and it is expected to remain relevant as long as EPS networks coexist with 5G. The EPS UDR is a testament to 3GPP's commitment to convergence and backward compatibility, ensuring that the transition to 5G does not require a complete overhaul of subscriber data management.

Purpose & Motivation

The EPS UDR exists to solve the problem of managing subscription data for EPS users within the 5G core network architecture. In the evolution from 4G to 5G, 3GPP introduced a new data management framework based on the UDM and UDR, which replaced the HSS and SPR of 4G. However, during the transition period, networks must support both 4G and 5G subscribers. The EPS UDR provides a standardized way to store EPS-specific data within the UDR, allowing the 5G core to serve EPS users without requiring a separate HSS.

Prior to the introduction of the EPS UDR, EPS subscription data was stored in the HSS, which was a monolithic entity with its own data model and interfaces. The 5G core's UDR is designed to be more flexible and service-based, supporting multiple data types and access technologies. The EPS UDR bridges the gap by defining how EPS data is represented in the UDR, enabling the UDM to act as a unified front-end for both 5G and 4G subscribers. This simplifies network operations, reduces data duplication, and enables seamless interworking between 4G and 5G.

The motivation also includes supporting network slicing and policy control. By consolidating data in the UDR, operators can apply consistent policies across access technologies and slices. The EPS UDR ensures that EPS users benefit from the same advanced data management capabilities as 5G users, such as improved scalability, redundancy, and exposure to third-party applications.

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.

Rel-16 Initial

Initial definition of EPS UDR as the term to identify the User Data Repository for EPS data, as specified in TS 23.335 clause 4.2.3.

The definition of EPS UDR carried over unchanged from Rel-16.

The definition of EPS UDR carried over unchanged from Rel-17.

The definition of EPS UDR carried over unchanged from Rel-18.

Defining Specifications

3GPP specifications that define or reference EPS UDR, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
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