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

Glossary term · Management

UCMF

UE radio Capability Management Function

Management →

UCMF is a core network function that centrally stores, manages, and provides UE radio capabilities to eliminate redundant signaling and improve efficiency.

Introduced
Rel-16
Where
Core Network › 5G Core
Specifications
7 specs
UCMF Description Purpose What changed Neighbours Detected Changes Specifications

Description

The UE radio Capability Management Function (UCMF) is a pivotal component within the 5G Core (5GC) network architecture, specifically designed to manage UE radio capability information. It operates as a centralized repository and processing entity for the Radio Capability ID (RCID) and the associated UE radio capability information. The primary architectural role of the UCMF is to interact with other Network Functions (NFs) like the Access and Mobility Management Function (AMF) via service-based interfaces, primarily Nucmf. When a UE attaches to the network, the AMF may not have the full details of the UE's radio capabilities. Instead, it may only possess a UE Radio Capability ID. The AMF can then invoke the Nucmf_Get service operation on the UCMF, providing this RCID. The UCMF responds with the complete UE radio capability information corresponding to that ID, which the AMF can then forward to the Radio Access Network (RAN) for optimal radio resource configuration.

How the UCMF works involves a lifecycle management process for capability data. It can receive UE radio capability information from the AMF (e.g., when a new UE type connects) and generate a new, unique RCID for it. This RCID is a compact identifier that can be stored in the UE's Universal Subscriber Identity Module (USIM) or in the 5GC's Unified Data Management (UDM) function, associated with the subscriber's profile. In subsequent network attachments, the UE or the UDM can provide this RCID, allowing the network to retrieve the full capabilities from the UCMF without the UE needing to transmit the large capability payload over the air repeatedly. This mechanism is crucial for bandwidth-constrained devices and for reducing signaling overhead.

The UCMF's role extends beyond simple storage; it ensures consistency and validity of capability data across the network. It may validate incoming capability information, manage versioning, and handle the mapping between different RCIDs and their corresponding data sets. By decoupling the voluminous radio capability information from routine signaling procedures, the UCMF enables more efficient mobility management, faster connection setup, and scalable support for massive Machine-Type Communication (mMTC) scenarios where a vast number of diverse IoT devices with specific radio profiles connect to the network. Its design is a cornerstone for the service-based architecture of 5GC, promoting network function reusability and streamlined operations.

Purpose & Motivation

The UCMF was created to solve significant inefficiencies in how UE radio capabilities were handled in previous generations like 4G LTE. In legacy systems, a UE often had to transmit its complete set of radio capabilities—which could be a large data block—during initial attachment or handover procedures. This process consumed valuable radio resources, increased signaling latency, and drained device battery life, problems exacerbated by the growing diversity and quantity of IoT devices with specialized capabilities.

The motivation for UCMF in 3GPP Release 16 was directly tied to the 5G design principles of efficiency and scalability for heterogeneous devices. The previous approach did not scale well for massive IoT deployments and constrained devices. By introducing a centralized management function, the network can assign a lightweight Radio Capability ID (RCID) to a UE's capability set. This ID, rather than the full data, is used in most signaling, drastically reducing overhead. It also allows for network-side updates and management of capability information, which is essential for introducing support for new radio features or for devices that may have their capabilities updated remotely.

Furthermore, UCMF addresses the problem of 'capability signaling storms' that could occur during network recovery or mass device wake-ups. It provides a deterministic and efficient method for the RAN to obtain necessary configuration data, enabling optimized radio performance and resource allocation from the very start of a connection. Its creation was a strategic enhancement to the 5GC architecture, aligning with the goals of network automation, reduced operational complexity, and enhanced support for the 5G use case triangle: enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC).

What changed in its specifications

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

TS 23.401Rel-18 → Rel-19

Rel-19 adds Disaster Roaming in EPS, which covers disaster-roaming procedures and attach, tracking area update and mobility signalling. It also adds Time Reference Information Distribution Indication to subscription data and the MME-to-eNB path, along with Store and Forward Satellite operation text.

Full comparison in TS 23.401 →
TS 23.501Rel-18 → Rel-19

Rel-19 added MPQUIC steering to multi-access PDU sessions, XR and media handling, and an Energy Information Function. It also added Local Offloading Management for edge computing, Vertical Federated Learning for AI/ML, and Ambient IoT text.

Full comparison in TS 23.501 →

Architecture

Where it sits in the network

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (11 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-16 7 changes
  • Introduction of RACS: UCMF services TS 23.501CR1037
  • UCMF provisioning procedures TS 23.682CR0457
  • Correction on UCMF event notification for PLMN assigned ID(s) TS 23.401CR3593
  • Resolution of Editor's Note on UCMF-AMF interaction TS 23.501CR1592
  • UCMF provisioning correction TS 23.501CR2106
  • On UCMF discovery TS 23.501CR2116

+ 1 more changes

Rel-17 1 change
Rel-19 3 changes
  • Clarification on UCMF instance TS 23.401CR3936
  • UCMF discovery in case of Indirect Network Service (INS) deployment-23.501. TS 23.501CR6121
  • Clarification on UCMF instance TS 23.501CR6421

Defining Specifications

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

SpecificationTitleRelease
TS 23.401 vk10 Evolved Packet System Architecture Rel-20 read
TS 23.501 vk30 5G System Architecture Rel-20 read
TS 23.682 vj30 Architecture for MTC and SCEF Enhancements Rel-19 read
TS 29.518 vk10 AMF Service Based Interface Rel-20 read
TS 29.673 vk00 3GPP TS 29673 vk00: Nucmf Service Based Interface Rel-20 read
TS 29.674 vj00 UE Radio Capability Management Protocol (URCMP) Rel-19 read
TS 29.675 vj20 Nucmf Service Based Interface Protocol Rel-19 read