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.
Key Features
- Standardized Information Element within the PFCP protocol on the N4 interface
- Carries port management instructions from SMF to UPF
- Supports configuration of port status (administratively up/down) and parameters
- Essential for managing Ethernet-type PDU sessions and associated MAC addresses
- Enables explicit control of user plane ports for services like fixed-mobile convergence
- Facilitates interoperability in multi-vendor 5G Core deployments involving Ethernet user plane
Evolution Across Releases
Introduced the Port Management Information Container as part of the enhanced PFCP protocol to support explicit port management for Ethernet PDU session types and other advanced user plane scenarios. Defined its structure and usage within N4 session modification procedures, enabling the SMF to control UPF port states and configurations.
Defining Specifications
| Specification | Title |
|---|---|
| TS 29.244 | 3GPP TS 29.244 |
| TS 29.512 | 3GPP TS 29.512 |
| TS 29.513 | 3GPP TS 29.513 |
| TS 29.514 | 3GPP TS 29.514 |