PMIC

Port Management Information Container

Core Network →
Introduced in Rel-16

PMIC is a data structure used in the 5G Core Network to convey port management information between the Session Management Function and User Plane Function for managing N4 session contexts.

Category
Core Network
Introduced
Rel-16
Where
Core Network › 5G Core
Specifications
4 specs
PMIC Description Purpose Related Classification Detected Changes Specifications

Description

The Port Management Information Container (PMIC) is a protocol data unit defined within the Packet Forwarding Control Protocol (PFCP) used on the N4 interface between the Session Management Function (SMF) and the User Plane Function (UPF) in the 5G Core. It is an Information Element (IE) carried within PFCP session modification or session establishment messages. The PMIC contains detailed information about the management of specific ports associated with a PDU session, particularly relevant for scenarios involving Ethernet-type PDU sessions or other data flows requiring explicit port control.

Architecturally, when the SMF needs to instruct the UPF to manage ports for a user plane connection—for example, to enable, disable, or configure parameters on a specific Ethernet port—it includes a PMIC within the relevant PFCP message. The container can specify the port number, the associated MAC address (for Ethernet), administrative status (up/down), and other port-specific attributes. The UPF, upon receiving this, applies the configuration to its user plane resources. This allows for granular control over the data forwarding environment at the UPF.

Its role is to enable the 5G Core to support services that require explicit layer 2 management, such as fixed-mobile convergence, industrial IoT with Ethernet backhaul, or network slicing with specific port-level isolation. The PMIC abstracts the port management details into a standardized container, ensuring interoperability between SMF and UPF from different vendors. It works in conjunction with other PFCP IEs that define packet detection rules, forwarding actions, and QoS enforcement to fully orchestrate the user plane path.

Purpose & Motivation

The PMIC was introduced to address the need for explicit port management within the 5G Core's user plane, a requirement that became prominent with the expansion of 5G to support non-IP PDU session types, particularly Ethernet. Previous mobile core architectures were primarily designed for IP-based traffic (GTP tunnels) where port management was implicit or handled at the IP layer. The support for Ethernet PDU sessions in 5G, driven by use cases like industrial automation and wireline convergence, required the ability to manage Ethernet switch ports within the UPF.

The problem it solves is the lack of a standardized mechanism for the control plane (SMF) to configure and manage physical or logical ports on the user plane function. Without the PMIC, managing Ethernet ports would require proprietary extensions, hindering multi-vendor interoperability and complicating service orchestration for fixed-access and enterprise scenarios.

Its creation was motivated by the 3GPP's work on supporting integrated access and backhaul (IAB), wireline-wireless convergence, and network slicing for vertical industries. These require the 5G system to act as a unified transport network capable of handling layer 2 protocols with the same level of programmability and control as traditional IP sessions. The PMIC provides this essential building block for port-level management within the standardized N4 protocol.

Classification

Part ofSMF
Related approachesPFCPUPF

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-16 3 changes

In Release 16, the PMIC function was introduced to enable the transparent relay of port-related management information between the TSN AF/TSCTSF and the NW-TT via the SMF and UPF. This release specified that the PMIC is transferred within the TSC Management Information IE using PFCP session procedures, such as the PFCP Session Modification Request and Response. Furthermore, it was clarified that a separate PMIC must be used for each port of an NW-TT and that these containers can be sent over any PFCP session associated with that NW-TT.

  • Correction to Port Management Information Container exchange TS 29.512CR0450
  • Correction to bridge information report and port management information container provisioning TS 29.514CR0200
  • PFCP session used to send PMIC and BMIC TS 29.244CR0490
Rel-18 1 change

In Release 18, a clarification was introduced for the subscription to User Plane Node Management Information Container (UMIC) and PMIC changes. The release specified that the SMF and UPF may send a Port Management Information Container (PMIC) for port management using PFCP session procedures associated with the relevant NW-TT, with a separate PMIC required for each port when managing multiple ports. Furthermore, it was detailed that these containers are transferred within the TSC Management Information IE during PFCP Session Modification or Report Request procedures.

  • Clarification to subscription to UMIC and PMIC changes TS 29.513CR0446

Explore further

Broader topics and technologies where PMIC plays a role.

Defining Specifications

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

SpecificationTitleRelease
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
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.