Description
The User plane node Management Service (UMS) is a specific management service defined in the 3GPP Management and Orchestration (MANO) framework. It falls under the umbrella of Network Resource Management (NRM) services and is dedicated to the lifecycle management of network functions that handle user data traffic, known as user plane nodes. The primary managed entity for UMS in 5G systems is the User Plane Function (UPF), but the concept applies to analogous user plane entities in previous generations, such as the Serving Gateway (SGW) and Packet Data Network Gateway (PGW) user plane in Evolved Packet Core (EPC).
Architecturally, UMS is typically realized as a set of capabilities within a Network Management System (NMS) or Element Management System (EMS). It exposes northbound interfaces, often based on 3GPP-defined information models using UML, to higher-level orchestration systems (like a Network Function Virtualization Orchestrator - NFVO) or to an integrated OSS. The service implements the standard FCAPS management areas: Fault Management (for alarm surveillance and fault recovery), Configuration Management (for provisioning and updating UPF parameters), Accounting Management (for collecting usage data), Performance Management (for gathering KPIs and metrics), and Security Management (for access control and security logging).
Operationally, UMS works by maintaining a managed object instance that represents each user plane node under its control. Through the Itf-N reference point or other management interfaces, it can receive commands from an operator or orchestrator to instantiate, configure, scale, or terminate a UPF. It continuously collects performance measurement data (e.g., throughput, packet delay, packet loss) and fault indications from the node. This data is then correlated, analyzed, and presented, enabling automated or manual actions to ensure user plane service quality and network efficiency. In a virtualized environment, UMS interacts with the Virtualized Infrastructure Manager (VIM) for the allocation of underlying compute and storage resources for the UPF.
Purpose & Motivation
The UMS was created to provide a standardized, abstracted, and automated method for managing the critical user plane components of mobile networks. As networks evolved towards all-IP architectures and later cloud-native, software-based deployments, the user plane nodes became more dynamic and numerous. Traditional, vendor-proprietary element management approaches were inefficient for multi-vendor networks and incapable of supporting rapid, automated lifecycle operations required for network slicing and on-demand service creation.
Its specification addresses the need for a common management service model that separates the management intent (e.g., 'ensure latency below 10ms for slice X') from the vendor-specific implementation details of a UPF. By defining UMS, 3GPP enables interoperability between management systems from different vendors and allows for centralized orchestration to treat user plane functions as manageable, composable resources. This is particularly vital for 5G, where the UPF can be deployed in a distributed fashion (e.g., at the edge) and its configuration (e.g., PDU Session anchors, traffic steering rules) must be dynamically adjusted based on user mobility and service requirements.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (22 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-4, normative work from Rel-16.
In Release 16, the UMS function was enhanced to specifically support Time-Sensitive Networking (TSN) bridge management by splitting Ethernet port management information into port-specific and bridge-specific information. This included updates to the definitions for Ethernet port management messages and the introduction of procedures for transferring this management information between a TSN AF and the DS-TT at the UE, as well as corrections to the NW-TT-initiated Ethernet port management procedure.
- Correction of the abnormal case in NW-TT-initiated Ethernet port management procedure TS 24.539CR0001
- Introduction of Bridge management information TS 24.539CR0004
- Updating definitions for Ethernet port management messages TS 24.539CR0005
- Spliting port management information into port- and bridge-specific information TS 24.539CR0007
- Correct the ETHERNET PORT MANAGEMENT NOTIFY ACK message name TS 24.539CR0008
- Bridge management information correction TS 24.539CR0012
+ 1 more changes
In Release 17, the UMS function introduced new capabilities for managing user plane nodes and their Ethernet ports, including selective read, set, and subscribe/notify operations for their parameters. It added specific management parameters such as `txPropagationDelayDeltaThreshold`, `TSN time domain number`, `AdminCycleTimeExtension`, and `PSFPAdminCycleTimeExtension`. Furthermore, the release defined new service cause values for reporting when a port or user plane node parameter becomes unavailable and resolved issues related to the length of parameter values.
- Correction on DS-TT/NW-TT Ethernet port and replacement of bridge with user plane node (24.519 CR) TS 24.539CR0027
- Clarification of applicability of port and user plane node management parameters TS 24.539CR0002
- Introducing new service cause values for port/user plane node parameter unavailable TS 24.539CR0003
- Enabling selective read, set and subscribe/notify of port and user plane node parameters TS 24.539CR0008
- Resolve the issue on length of port/user plane node parameter value TS 24.539CR0001
- Addition of txPropagationDelayDeltaThreshold and TSN time domain number to port management information TS 24.539CR0009
+ 2 more changes
In Release 18, the UMS (User plane node Management Service) introduced corrections and clarifications to its procedures, specifically for the user plane node update result and the port management procedure. These enhancements were made in conjunction with improvements to management functions for Time-Sensitive Networking (TSN) and Deterministic Networking (DetNet) port management information. The updates focused on refining the associated information elements and procedural outcomes for managing user plane nodes and ports.
- Correction to TSN AF-requested port management TS 24.539CR0017
- Correction to TSN AF-requested port management TS 24.539CR0021
- Correction to port management procedure and User plane node management procedure TS 24.539CR0037
- Correction to port update result and user plane node update result TS 24.539CR0034
- Correction to user plane node update result IE TS 24.539CR0036
- Corrections to the port management information for DetNet TS 24.539CR0040
In Release 19, the UMS (User plane node Management Service) function introduced a correction to the network-requested port management procedure to ensure its proper completion. This update also refined the associated status reporting for the User plane node itself.
- Correction to network-requested port management procedure completion and User plane node status TS 24.539CR0047
Explore further
Broader topics and technologies where UMS plays a role.
Defining Specifications
3GPP specifications that define or reference UMS, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj00 | 3GPP Technical Terms and Definitions | Rel-19 |
| TS 24.539 vj30 | NW-TT Protocol Aspects | Rel-19 |