Description
The Service Management Function (SMF) is a critical control plane network function within the 5G Core (5GC) architecture, defined by 3GPP. It is responsible for the comprehensive management of Protocol Data Unit (PDU) sessions, which are the logical connections providing user equipment (UE) with connectivity to a data network (DN), such as the internet or an operator service. The SMF interacts with numerous other network functions to perform its duties. During session establishment, the SMF receives session management requests from the Access and Mobility Management Function (AMF). It selects a User Plane Function (UPF) to serve as the data path anchor, allocates an IP address to the UE (acting as a DHCP server or via interaction with an external DHCP server), and establishes the necessary tunnels (e.g., N3, N9 interfaces) between the Radio Access Network (RAN), UPF, and data network. The SMF is also responsible for policy enforcement and QoS control. It interfaces with the Policy Control Function (PCF) to obtain policy rules and then configures the UPF to enforce these rules, such as applying gating, bandwidth limits, and charging triggers. Furthermore, the SMF manages charging data collection by interacting with the Charging Function (CHF). It generates usage reports and forwards them for offline or online charging. The SMF also handles session modification procedures triggered by network policies, user requests, or mobility events (like handovers), ensuring seamless service continuity. It plays a key role in network slicing by being aware of the slice instance and ensuring the PDU session adheres to the specific slice's characteristics and isolation requirements. Its functionality is exposed via service-based interfaces, primarily Nsmf, allowing other authorized NFs to invoke its services.
Purpose & Motivation
The SMF was created as part of the new 5G Core (5GC) service-based architecture (SBA) to address the limitations of the legacy Evolved Packet Core (EPC). In EPC, session management was tightly coupled within the MME (for control plane) and the Serving Gateway (SGW) and PDN Gateway (PGW) for user plane and policy. This monolithic architecture lacked flexibility, scalability, and hindered rapid service innovation. The SMF's purpose is to disaggregate session management into a dedicated, software-based control plane function. This separation allows for independent scaling, more granular policy control, and efficient support for diverse 5G use cases like enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine Type Communications (mMTC). By centralizing PDU session state, the SMF simplifies mobility management, enables advanced features like simultaneous connectivity to multiple data networks, and provides a single point for applying session-specific policies. Its creation was motivated by the need for a cloud-native, agile core network that could dynamically orchestrate connectivity tailored to specific application requirements, which is fundamental to realizing the full potential of 5G, including network slicing and edge computing.
Key Features
- Centralized management and control of PDU session lifecycle (establishment, modification, release)
- IP address allocation and management for UE (IPv4, IPv6, or both)
- Selection and control of User Plane Function (UPF) instances for data forwarding
- Enforcement of session and service-related policies received from the PCF
- QoS flow management and control, including authorization and enforcement of QoS parameters
- Charging data collection and interaction with the Charging Function (CHF)
Evolution Across Releases
Introduced as a foundational network function in the first 5G System (5GS) specification. Defined its core responsibilities: PDU session establishment/modification/release, UPF selection and control, IP address management, policy enforcement, and charging interactions. Established the service-based interface (Nsmf) and reference point interfaces (e.g., N4 to UPF, N7 to PCF).
Enhanced support for network slicing, including improved slice-specific SMF selection and operation. Introduced enhancements for non-public networks (NPNs) and integration with LAN-type services. Added support for ATSSS (Access Traffic Steering, Switching and Splitting) for simultaneous access over 3GPP and non-3GPP access.
Further refined support for edge computing, including enhanced coordination with Local Area Data Network (LADN) and edge application server discovery. Introduced enhancements for QoS monitoring and support for time-sensitive communication. Improved procedures for service continuity during SMF relocation events.
Ongoing evolution focusing on integration with AI/ML for network automation, enhanced support for extended reality (XR) traffic with specific QoS handling, and further refinements for network slicing and service exposure. Work on energy efficiency and reduced capability devices.
Defining Specifications
| Specification | Title |
|---|---|
| TS 22.822 | 3GPP TS 22.822 |
| TS 23.078 | 3GPP TS 23.078 |
| TS 23.380 | 3GPP TS 23.380 |
| TS 23.501 | 3GPP TS 23.501 |
| TS 23.527 | 3GPP TS 23.527 |
| TS 23.558 | 3GPP TS 23.558 |
| TS 23.700 | 3GPP TS 23.700 |
| TS 24.501 | 3GPP TS 24.501 |
| TS 24.890 | 3GPP TS 24.890 |
| TS 26.802 | 3GPP TS 26.802 |
| TS 26.803 | 3GPP TS 26.803 |
| TS 26.804 | 3GPP TS 26.804 |
| TS 26.806 | 3GPP TS 26.806 |
| TS 26.891 | 3GPP TS 26.891 |
| TS 26.919 | 3GPP TS 26.919 |
| TS 26.942 | 3GPP TS 26.942 |
| TS 28.801 | 3GPP TS 28.801 |
| TS 28.802 | 3GPP TS 28.802 |
| TS 28.816 | 3GPP TS 28.816 |
| TS 28.833 | 3GPP TS 28.833 |
| TS 28.840 | 3GPP TS 28.840 |
| TS 28.843 | 3GPP TS 28.843 |
| TS 28.874 | 3GPP TS 28.874 |
| TS 29.061 | 3GPP TS 29.061 |
| TS 29.078 | 3GPP TS 29.078 |
| TS 29.214 | 3GPP TS 29.214 |
| TS 29.244 | 3GPP TS 29.244 |
| TS 29.502 | 3GPP TS 29.502 |
| TS 29.503 | 3GPP TS 29.503 |
| TS 29.505 | 3GPP TS 29.505 |
| TS 29.507 | 3GPP TS 29.507 |
| TS 29.508 | 3GPP TS 29.508 |
| TS 29.512 | 3GPP TS 29.512 |
| TS 29.513 | 3GPP TS 29.513 |
| TS 29.514 | 3GPP TS 29.514 |
| TS 29.518 | 3GPP TS 29.518 |
| TS 29.520 | 3GPP TS 29.520 |
| TS 29.521 | 3GPP TS 29.521 |
| TS 29.523 | 3GPP TS 29.523 |
| TS 29.524 | 3GPP TS 29.524 |
| TS 29.525 | 3GPP TS 29.525 |
| TS 29.532 | 3GPP TS 29.532 |
| TS 29.534 | 3GPP TS 29.534 |
| TS 29.536 | 3GPP TS 29.536 |
| TS 29.541 | 3GPP TS 29.541 |
| TS 29.542 | 3GPP TS 29.542 |
| TS 29.551 | 3GPP TS 29.551 |
| TS 29.552 | 3GPP TS 29.552 |
| TS 29.558 | 3GPP TS 29.558 |
| TS 29.561 | 3GPP TS 29.561 |
| TS 29.564 | 3GPP TS 29.564 |
| TS 29.574 | 3GPP TS 29.574 |
| TS 29.575 | 3GPP TS 29.575 |
| TS 29.576 | 3GPP TS 29.576 |
| TS 29.585 | 3GPP TS 29.585 |
| TS 29.591 | 3GPP TS 29.591 |
| TS 29.820 | 3GPP TS 29.820 |
| TS 29.866 | 3GPP TS 29.866 |
| TS 29.889 | 3GPP TS 29.889 |
| TS 29.890 | 3GPP TS 29.890 |
| TS 32.240 | 3GPP TR 32.240 |
| TS 32.255 | 3GPP TR 32.255 |
| TS 32.260 | 3GPP TR 32.260 |
| TS 32.279 | 3GPP TR 32.279 |
| TS 32.290 | 3GPP TR 32.290 |
| TS 32.291 | 3GPP TR 32.291 |
| TS 32.298 | 3GPP TR 32.298 |
| TS 32.847 | 3GPP TR 32.847 |
| TS 32.899 | 3GPP TR 32.899 |
| TS 33.108 | 3GPP TR 33.108 |
| TS 33.127 | 3GPP TR 33.127 |
| TS 33.501 | 3GPP TR 33.501 |
| TS 33.511 | 3GPP TR 33.511 |
| TS 33.515 | 3GPP TR 33.515 |
| TS 33.739 | 3GPP TR 33.739 |
| TS 33.749 | 3GPP TR 33.749 |
| TS 33.794 | 3GPP TR 33.794 |
| TS 38.300 | 3GPP TR 38.300 |
| TS 38.401 | 3GPP TR 38.401 |
| TS 38.410 | 3GPP TR 38.410 |
| TS 38.413 | 3GPP TR 38.413 |