Description
The User Plane Node Management Information Container (UMIC) is a concept and data structure defined within the 5G core network architecture, specifically related to the Packet Forwarding Control Protocol (PFCP) which is used for communication between the Control Plane Function (CPF) – such as the Session Management Function (SMF) – and the User Plane Function (UPF). The UMIC is not a standalone protocol but a container or information element that can be included within certain PFCP messages. Its primary purpose is to transport management and operational information about the state of the UPF to the controlling CPF.
Architecturally, the UMIC is generated by the UPF. It encapsulates various types of management information that reflect the UPF's current operational status. This information can include metrics related to load (e.g., CPU utilization, memory usage, packet processing rate), overload control indicators (signaling that the UPF is approaching or in an overloaded state), and other node-specific management data. The UPF includes this UMIC in PFCP messages sent to the SMF, such as in PFCP Session Modification Response messages or potentially in PFCP Association Update messages. Upon receiving a message containing a UMIC, the SMF parses the container to extract the management information.
The role of the UMIC is to provide the control plane with real-time or near-real-time visibility into the health and capacity of user plane nodes. This enables several advanced network management functions. For example, an SMF receiving a UMIC indicating high load on a particular UPF can make informed decisions for new sessions, potentially selecting a different, less-loaded UPF for session establishment (load balancing). If the UMIC signals an overload condition, the SMF can trigger overload control procedures, such as rejecting new session requests or gracefully redirecting traffic. The UMIC facilitates a closed-loop management system where the control plane can dynamically adapt its decisions based on the actual state of the user plane resources, moving beyond static configuration. This is a key enabler for network automation, elasticity, and efficient resource utilization in cloud-native 5G core networks.
Purpose & Motivation
UMIC was introduced in 5G Release 17 to address the need for enhanced and dynamic management of the disaggregated user plane. In previous architectures and early 5G releases, control plane decisions (like UPF selection) were often based on static configuration (e.g., Network Repository Function (NRF) profiles) or simple policies. There was no standardized, in-band mechanism for a UPF to proactively report its dynamic load or overload status to the SMF during active PFCP sessions. This limitation could lead to sub-optimal load distribution, where an SMF might continue assigning sessions to an overloaded UPF because it lacked real-time information.
The creation of UMIC solves this problem by defining a standardized container to carry this vital management information within the existing PFCP signaling channel. This allows for immediate and context-aware reactions from the control plane. The motivation stems from the cloud-native principles of 5G, where UPFs are expected to be software instances scaled elastically. To automate scaling and traffic steering, the control plane requires fine-grained feedback from the user plane. UMIC provides this feedback loop, enabling more intelligent load balancing, proactive overload avoidance, and improved overall network resilience and quality of service. It represents an evolution towards self-optimizing networks where the core network functions can autonomously adapt to changing load conditions.
Classification
Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (3 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-17, normative work from Rel-18.
In Release 18, clarifications and corrections were made to the User Plane Node Management Information Container (UMIC) function, specifically regarding subscription procedures and the standardization of its terminology. The enhancements define that UMIC data, containing user plane node management messages, is transferred between the SMF and UPF within the TSC Management Information IE using PFCP session modification procedures. This provides a clearer framework for the SMF to forward or the UPF to report this container, integrating it with existing port management mechanisms for NW-TT operations.
Explore further
Broader topics and technologies where UMIC plays a role.
Defining Specifications
3GPP specifications that define or reference UMIC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 29.244 vj40 | PFCP Specification for Control/User Plane Separation | Rel-19 |
| TS 29.512 vj40 | 5G Session Management Policy Control Service | Rel-19 |
| TS 29.513 vj40 | 5G PCC Signalling Flows & QoS Mapping | Rel-19 |
| TS 29.514 vj40 | 5G System; Policy Authorization Service; Stage 3 | Rel-19 |