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

Glossary term · Core Network

UDM

Unified Data Management

Core Network →

UDM is the core network function that manages subscriber data, identities, and authentication credentials, serving as the central repository for user profiles in the 5G Service-Based Architecture.

Introduced
Rel-15
Where
Core Network › 5G Core
Specifications
61 specs
Also in
Security, Services
UDM Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The Unified Data Management (UDM) function is a critical component of the 5G Core Network (5GC) based on the Service-Based Architecture (SBA). It serves as the centralized repository and management point for subscriber-related data. The UDM is responsible for storing and managing long-term subscription information, including user identities, security credentials, service profiles, and policy-related data. It interacts with other network functions through standardized service-based interfaces, primarily using HTTP/2 with JSON or CBOR encoding. The UDM's primary roles include authentication credential processing, user identification handling, access authorization, and subscription data management.

Architecturally, the UDM is a software-based network function that can be deployed in cloud environments. It often works in conjunction with the Unified Data Repository (UDR), which provides the actual persistent storage for the subscriber data. The UDM contains the application logic to process and manage this data, while the UDR acts as the database. Key internal components include the Authentication Credential Repository and Processing Function (ARPF), which stores long-term keys and runs authentication algorithms, and subscription data management logic. The UDM exposes its capabilities as services to other NFs, such as Nudm_UEAuthentication for authentication, Nudm_SubscriberDataManagement for subscription data, and Nudm_EventExposure for monitoring subscriber events.

How it works: When a user equipment (UE) attempts to register with the 5G network, the Access and Mobility Management Function (AMF) contacts the UDM. The UDM's ARPF generates authentication vectors (using the 5G Authentication and Key Agreement (5G-AKA) or EAP-AKA' procedures) and provides them to the AMF via the AUSF. For session establishment, the Session Management Function (SMF) retrieves the user's subscription data and policy profile from the UDM to determine allowed services, QoS parameters, and charging rules. The UDM also manages the binding between the user's permanent subscription identifier (SUPI) and the temporary identifier (SUCI) used for privacy, and it tracks the serving AMF for each subscriber to route signaling messages correctly.

Its role is central to network security, service personalization, and mobility management. By centralizing subscriber data, the UDM enables consistent policy enforcement across the network, supports seamless mobility and session continuity, and provides a single point of truth for user profiles. This is essential for advanced 5G features like network slicing, where the UDM provides the slice selection subscription information. Furthermore, its service-based design allows for flexible integration, scalability, and support for new services, forming the foundation for subscriber management in the 5G era.

Purpose & Motivation

The UDM was created to address the limitations of legacy subscriber data management in pre-5G networks, which was fragmented across different network elements. In 4G EPC, functions like the Home Subscriber Server (HSS) managed user profiles and authentication, but the architecture was node-based and less flexible. The proliferation of diverse 5G services, IoT, and network slicing demanded a more agile, scalable, and unified approach to data management.

The primary problem the UDM solves is the centralization and standardization of subscriber data handling. It consolidates functions previously spread across the HSS, Home Location Register (HLR), and other entities into a single, cloud-native network function. This unification simplifies operations, reduces data duplication, and provides a consistent view of the subscriber to all other core network functions. Its creation was motivated by the shift to the Service-Based Architecture (SBA), which requires network functions to expose capabilities as reusable services.

Historically, the UDM evolved from the HSS/HLR concepts but with a fundamental architectural redesign. It enables dynamic subscription management, real-time policy updates, and efficient support for massive numbers of IoT devices. By separating the application logic (UDM) from storage (UDR), it allows independent scaling and leverages modern cloud and software-defined networking principles. This addresses the need for a more programmable, automated, and service-aware core network capable of supporting the wide array of use cases envisioned for 5G and beyond.

What changed in its specifications

The latest release-to-release comparison of specifications that define UDM. Each summary describes the whole specification, not only this term.

TS 23.237Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 23.237: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 23.237 →
TS 23.292Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 23.292: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 23.292 →

Architecture

Where it sits in the network

Evolution Lineage

Technology family

Core network elements and functions · Core Network

  1. Phase 1 AuC, EIR, GMSC, HLR, IWF, MSC, VLR
  2. Phase 2 SMS-GMSC, SMS-IWMSC
  3. R96 GGSN, SGSN
  4. R99 3G-SGSN, GLR, IM-GSN, IM-MSC
  5. Rel-4 CS-MGW, GMSC Server, MSC Server
  6. Rel-5 HSS, SLF
  7. Rel-6 3GPP AAA Server
  8. Rel-7 PCEF, PCRF
  9. Rel-8 ANDSF, BBERF, ePDG, MME, PGW, SGW
  10. Rel-9 HLR-FE, HSS-FE, UDR
  11. Rel-10 L-GW
  12. Rel-11 TDF
  13. Rel-14 PGW-C, PGW-U, SGW-C, SGW-U, TDF-C, TDF-U
  14. Rel-15 AMF, AUSF, PCF, SMF, SMF+PGW-C, UDM, UPF
  • UDM counterpart in another generation: HSS
    “During the TAU or Attach procedure the HSS+UDM cancels any AMF registration associated with the 3GPP access” 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 sources

Documented changes in 6 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.

Rel-15 introduced

UDM is specified for the first time in Rel-15: Nudm services (SDM, UECM, UEAuthentication) returning subscription data, registering serving AMFs, and handling SUCI de-concealment via SIDF.

  • “the UDM may be stateless and stores information externally in the UDR.” TS 29.503 v15.10.0
  • “The UDM stores the associated Access Type together with the serving AMF and does not remove the AMF identity” TS 23.502 v15.17.0
  • “the UDM shall invoke SIDF if a SUCI is received. SIDF shall de-conceal SUCI to gain SUPI” TS 33.501 v15.20.0
Rel-16 1 CR

In Rel-16 the UDM gained new behaviour: it returns more subscription data types (LCS, V2X, enhanced coverage restriction, shared data), supports group ID discovery, and interacts with the AUSF for SoR and UPU protection.

  • “On success, the UDM responds with "200 OK", the message body containing the UE's subscribed V2X data as relevant for the requesting NF service consumer.” TS 29.503 v16.18.0
  • “After the UDM is informed that the UE has been successfully (re-)authenticated, the UDM shall store the AUSF instance which reported the successful authentication.” TS 33.501 v16.20.0
  • UDM Discovery by Internal Group ID TS 23.501CR1737
Rel-17 specification text

In Rel-17 the UDM gained new behaviour: it returns ProSe, 5MBS and User Consent subscription data, handles disaster roaming subscription data, and uses AF-specific information for GPSI translation.

  • “the UDM responds with "200 OK" with the message body containing the UE's ProSe Data as relevant for the requesting NF service consumer.” TS 29.503 v17.22.0
  • “The UDM provides the subscription data for a Disaster Roaming service to the AMF based on the local policy and/or the local configuration” TS 23.502 v17.15.0
  • “the UDM shall take the provided AF specific information into account to determine the GPSI (i.e. External Identifier) to be returned for the UE.” TS 29.503 v17.22.0
Rel-18 specification text

In Rel-18 UDM gained new behaviour: it returns new subscription data types (Time Synchronization, LCS, Ranging/Sidelink, A2X), uses AF-specific info for GPSI translation, and can trigger primary authentication on its own policy.

  • “the UDM shall take the provided AF specific information into account to determine the GPSI to be returned for the UE.” TS 29.503 v18.13.0
  • “the UDM responds with "200 OK", the message body containing the UE's subscribed A2X data as relevant for the requesting NF service consumer.” TS 29.503 v18.13.0
  • “The UDM may be pre-configured with an operator authentication policy in order to determine when to trigger a primary authentication procedure.” TS 33.501 v18.12.0
Rel-19 1 CR

In Rel-19 UDM gained new behaviour: multiple SUPI/GPSI identifier translation, AF-specific GPSI selection, MPS for Messaging priority handling, and storing generated AF-specific UE identifiers in UDR.

  • “the UDM shall take the provided AF specific information into account to determine the GPSI to be returned for each UE in the supi-list” TS 29.503 v19.7.0
  • “the UDM shall set the SBI-Message-Priority header with a value appropriate for MPS and shall treat the response with priority” TS 29.503 v19.7.0
  • Support for Multiple SUPI to GPSI Conversion in UDM TS 29.503CR1305
Rel-20 2 CRs

UDM behaviour was extended in Rel-20: it supports Indirect Network Sharing (incl. Disaster Condition), provides allowed MAC addresses in SM subscription data, and applies MPS priority treatment for messaging.

  • “When "disaster-roaming-ind" is set to true and "hosting-plmn-id" is present, UDM can determine the case of Indirect Network Sharing for Disaster Condition” TS 29.503 v20.1.0
  • UDM support for Indirect Network Sharing TS 29.503CR1554
  • Priority treatment by the UDM for MPS for Messaging TS 29.503CR1576

Defining Specifications

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

SpecificationTitleRelease
TS 23.237 vj00 IMS Service Continuity (ISC) Stage 2 Rel-19 read
TS 23.292 vj00 IMS Centralized Services (ICS) Architecture Rel-19 read
TS 23.380 vk00 IMS Restoration Procedures Rel-20 read
TS 23.501 vk30 5G System Architecture Rel-20 read
TS 23.540 vk00 5G Service-Based SMS Architecture Rel-20 read
TS 23.700 vk10 AI/ML Application Layer Support Phase 2 Rel-20 read
TR 23.732 vg00 User Data Interworking, Coexistence, Migration Study Rel-16 read
TR 23.758 vh00 Study on Edge Application Architecture Rel-17 read
TR 23.973 vj00 Separate HSS/UDM Deployment Scenarios & Solutions Rel-19 read
TS 24.229 vk10 IMS SIP/SDP Call Control Protocol Rel-20 read
TS 24.501 vk10 5GS NAS Protocol Specification Rel-20 read
TR 26.919 vj00 Study on 5G Conversational Media Handling Rel-19 read
TS 26.942 vk00 Sustainable Media Metrics and Architectural Impacts for 5G Rel-20 read
TS 28.540 vk40 5G Network Resource Model (NRM) Stage 1 Rel-20 read
TS 28.561 vk20 Network Digital Twin Management Rel-20 read
TS 28.802 vf00 Management Study for 5G Network Architecture Rel-15 read
TR 28.833 vi01 Technical Report on 5G LAN-type Service Management Rel-18 read
TR 28.837 vi00 Technical Report on Trace/MDT Management Rel-18 read
TR 28.840 vi10 Technical Report Rel-18 read
TS 29.165 vk00 Inter-IMS Network-to-Network Interface (II-NNI) Rel-20 read
TS 29.337 vj00 Diameter T4 Interface for MTC Device Triggering 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.507 vk10 Access and Mobility Policy Control Rel-20 read
TS 29.508 vk10 Session Management Event Exposure Service 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.518 vk10 AMF Service Based Interface Rel-20 read
TS 29.520 vk10 5G NWDAF Services Rel-20 read
TS 29.523 vk10 Policy Control Event Exposure Service Rel-20 read
TS 29.524 vk00 5GC to NAS Cause Mapping Specification Rel-20 read
TS 29.525 vk10 UE Policy Control Service Rel-20 read
TS 29.544 vk00 Nspaf Service Based Interface for 5G System Rel-20 read
TS 29.550 vk00 Nsoraf Service Based Interface for SOR-AF Rel-20 read
TS 29.552 vk10 5G Network Data Analytics Procedures Rel-20 read
TS 29.563 vk00 Nhss Services for 5G SBA Stage 3 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
TR 29.829 vh10 SMS Service-Based Interfaces for 5G Core Rel-17 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.255 vk30 5G Data Connectivity Converged Charging Rel-20 read
TS 32.256 vk10 5G Connection and Mobility Charging Rel-20 read
TS 32.899 vf10 5G Charging Architecture Study Rel-15 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.515 vk00 5G SMF Security Assurance Specification Rel-20 read
TS 33.529 vj10 SCAS for SMSF Security Assurance Rel-19 read
TS 33.535 vj00 5G AKMA: Authentication and Key Management for Apps Rel-19 read
TS 33.545 vk10 NR Femto Security Architecture Rel-20 read
TS 33.701 vj00 Study on mitigations against bidding down attacks Rel-19 read
TR 33.739 vi10 Study on security enhancement of support for Rel-18 read
TS 33.749 vj00 Study on security aspects of edge computing enhancement Rel-19 read
TS 33.835 vg10 Study on authentication and key management for apps Rel-16 read
TS 33.836 vg10 Security Study for Advanced V2X Services Rel-16 read
TR 33.847 vh10 5G Proximity Services Security Study Rel-17 read
TS 35.234 vj00 MILENAGE-256 Algorithm Set Specification Rel-19 read
TS 38.300 vj40 NR and NG-RAN Overall Description Rel-19 read