Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Core Network

SMF

Session Management Function

Core Network →

SMF is the 5G core control network function that establishes and controls PDU sessions, selects user plane functions, and allocates IP addresses and policies.

Introduced
Rel-15
Where
Core Network › 5G Core
Specifications
87 specs
Also in
Services, Management
SMF Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

Session Management Function is a core control-plane network function in the 5G System that is responsible for the establishment, modification, and release of PDU sessions. It is the main session-management entity in the 5G core architecture, separating session control from mobility management, which is handled by the AMF, and from user-plane forwarding, which is handled by the UPF. The SMF plays a central role in assigning IP connectivity, selecting user-plane anchors, applying policy and charging rules, and coordinating lawful intercept. For every PDU session, the SMF maintains the session context and the rules that define how the UE traffic is identified, routed, treated, and reported. When a UE requests a PDU session, the AMF selects an appropriate SMF based on the requested Data Network Name, Single Network Slice Selection Assistance Information, subscriber profile, network topology, and policy. The SMF then interacts with the Unified Data Management to obtain subscription data, with the Policy Control Function to obtain session and policy rules, and with charging or billing systems to apply charging methods. It allocates an IP address or other session identifier for the UE, selects one or more UPFs, and establishes N4 sessions with them. Through N4, the SMF configures packet detection rules, forwarding rules, QoS enforcement rules, usage reporting rules, and other user-plane behaviors. These rules tell the UPF how to classify traffic, apply QoS, enforce policies, and forward packets to the data network or to other UPFs. The SMF also manages session continuity and mobility. Depending on the Session and Service Continuity mode, the SMF may keep the same UPF anchor, relocate the anchor, or use multiple anchors to support edge computing, roaming, or service-specific requirements. During handover, the SMF may update user-plane paths, adjust QoS, and coordinate with the AMF and RAN. For roaming, the SMF may interact with a peer SMF in the visited network, exchanging session parameters and policy information. For non-3GPP access, the SMF participates in session establishment through the AMF and can apply the same session-control principles as for 3GPP access. It can also support event exposure, allowing authorized network functions or applications to receive notifications about session state changes or charging events. Key SMF responsibilities include UE IP address allocation, DNN and S-NSSAI handling, UPF selection and control, PCC rule enforcement, charging, lawful intercept, roaming, and session context management. The SMF may store session state locally or use a data repository such as a Unified Data Repository, depending on deployment architecture. It may also interact with network analytics functions to optimize session placement, QoS, and resource usage. Because the SMF is a service-based control function, it can be instantiated, scaled, and orchestrated independently of the AMF and UPF, which supports cloud-native 5G core deployments. In the overall 5G architecture, the SMF is essential for turning subscriber requests into working data sessions. It provides the control logic that connects radio access, mobility management, policy, charging, and user-plane forwarding. Without the SMF, the network would lack a centralized point for session lifecycle management and would have difficulty supporting diverse services, network slicing, edge computing, and roaming. Its role is to make session management modular, programmable, and scalable, which is one of the defining advances of the 5G core compared with earlier packet-core architectures.

Purpose & Motivation

SMF exists because 5G requires a modular, scalable, and programmable approach to session management. In earlier packet-core architectures, functions such as GGSN or P-GW combined session control, user-plane anchoring, policy enforcement, charging, and mobility-related tasks in relatively monolithic nodes. This made it difficult to support diverse service types, network slicing, edge computing, and cloud-native deployment models. The SMF separates session management from mobility management and user-plane forwarding, allowing each function to evolve and scale independently. The motivation for SMF is to provide a dedicated control point for PDU sessions while enabling flexible UPF selection, policy enforcement, and service exposure. It solves the need to establish sessions for different Data Network Names, slices, access types, and roaming scenarios without coupling the logic to a single user-plane node. It also supports dynamic session anchoring for edge services, lawful intercept, charging, and event exposure. By centralizing session rules and interactions with PCF, UDM, AMF, and UPF, the SMF helps operators deliver differentiated services with predictable control and manageable complexity.

What changed in its specifications

The latest release-to-release comparison of specifications that define SMF. Each summary describes the whole specification, not only this term.

TS 23.078Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 23.078: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 23.078 →
TS 23.380Rel-18 → Rel-19

Rel-19 added IMS disaster prevention and restoration enhancements to TS 23.380, including detection of EPC/5GC NF failures, restoration of IMS sessions, and PCRF/PCF bypass procedures.

Full comparison in TS 23.380 →

Architecture

Where it sits in the network

Evolution Lineage

Technology family

Core network elements and functions · Core Network

  1. Phase 1 AuC, EIR, GMSC, HLR, IWF, MSC, VLR
  2. Phase 2 SMS-GMSC, SMS-IWMSC
  3. R96 GGSN, SGSN
  4. R99 3G-SGSN, GLR, IM-GSN, IM-MSC
  5. Rel-4 CS-MGW, GMSC Server, MSC Server
  6. Rel-5 HSS, SLF
  7. Rel-6 3GPP AAA Server
  8. Rel-7 PCEF, PCRF
  9. Rel-8 ANDSF, BBERF, ePDG, MME, PGW, SGW
  10. Rel-9 HLR-FE, HSS-FE, UDR
  11. Rel-10 L-GW
  12. Rel-11 TDF
  13. Rel-14 PGW-C, PGW-U, SGW-C, SGW-U, TDF-C, TDF-U
  14. Rel-15 AMF, AUSF, PCF, SMF, SMF+PGW-C, UDM, UPF
  • SMF counterpart in another generation: PGW (not stated verbatim in the specifications)

Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.

Release Timeline

Detected Changes Across Releases

verified against 3GPP sources

Documented changes in 6 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.

Rel-15 introduced

The SMF is specified for the first time in Rel-15, covering PDU session establishment and release, UPF selection and control over N4, policy interaction with the PCF, and the Nsmf services.

  • “SMF may support PDU Sessions for LADN where the access to a DN is only available in a specific LADN service area.” TS 23.501 v15.13.0
  • “The SMF is responsible for the enforcement of session management related policy decisions from the PCF” TS 29.512 v15.18.0
  • “The SMF sends N4 Session Release Request (N4 Session ID) message to the UPF(s) of the PDU Session.” TS 23.502 v15.17.0
Rel-16 specification text

SMF gained new Rel-16 behaviour: handling Extended Buffering, IPUPS control of UPFs, secondary authentication at PDU session establishment, and enforcing MA PDU Session ATSSS policy decisions.

  • “The SMF determines whether Extended Buffering applies based on local policy and the capability of the SMF (for SMF-based buffering) or the capability of the UPF” TS 23.502 v16.19.0
  • “The UPFs supporting the IPUPS functionality in VPLMN and HPLMN are controlled by the V-SMF and the H-SMF of that PDU Session respectively.” TS 23.501 v16.20.0
  • “If the SMF supports the "ATSSS" feature defined in subclause 5.8, the SMF shall within the SmPolicyContextData data structure include the ATSSS capability” TS 29.512 v16.23.0
Rel-17 1 CR

SMF behaviour was extended in Rel-17, e.g. NSACF-based slice admission control for PDU session counts, EAS/edge computing traffic routing and late notification, and NWDAF analytics use for UP path and DNAI selection.

  • “The SMF anchoring the PDU session sends Nnsacf_NSAC_NumOfPDUsUpdate_Request message to the NSACF.” TS 23.502 v17.15.0
  • “SMF may also take decision to apply traffic routing (by using UL Classifier functionality or IPv6 multi-homing) in EAS Discovery with EASDF procedure” TS 23.501 v17.15.0
  • NWDAF assisted DNAI and UPF selection at SMF TS 23.501CR2938
Rel-18 specification text

SMF behaviour was extended in Rel-18, e.g. it uses Namf_MT_EnableUEReachability for Suspend-mode PDU sessions and includes NSAC admission mode when invoking the NSACF for VPLMN roaming.

  • “the SMF uses Namf_MT_EnableUEReachability service operation if there is neither N1 SM container nor N2 SM information to be delivered by SMF” TS 23.502 v18.14.0
  • “the SMF provides in the Request the additional NSAC admission mode parameter, i.e. VPLMN with HPLMN assistance NSAC admission mode” TS 23.502 v18.14.0
  • “the SMF shall subscribe to the AoI reporting event with the AoI defined by the S-NSSAI” TS 29.502 v18.12.0
Rel-19 1 CR

In Rel-19 the SMF gained new behaviour: selecting a MoQ-capable PSA UPF, requesting the MoQ relay address over N4, marking End of Data Burst/Time to Next Burst, and rejecting modifications for unavailable non-3GPP device identifiers.

  • “SMF shall select a PSA UPF that supports MoQ relay functionality, if possible (e.g. using NRF for this selection)” TS 23.502 v19.9.0
  • “If the SMF decides to enable End of Data Burst and/or Time to Next Burst marking by PSA UPF” TS 23.502 v19.9.0
  • N6 delay measurement triggered by SMF TS 23.501CR6024
Rel-20 1 CR

SMF gained new Rel-20 behaviour: determining continuation or fallback of UE-Satellite-UE communication, configuring UPFs for abnormal traffic mitigation, and reporting satellite backhaul category to the PCF.

  • “the SMF determines whether to continue or to fallback the UE-Satellite-UE communication when serving satellite changes” TS 23.501 v20.3.0
  • “The SMF may use related UPF configuration on a PDU session level (using N4 rules) or on node level” TS 23.501 v20.3.0
  • PFCP per Node procedure for SMF to trigger mitigation actions towards UPF on non-PDU session level for abnormal use plane traffic handling TS 23.502CR5637

Defining Specifications

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

SpecificationTitleRelease
TS 22.822 vg00 Satellite Access in 5G Study Rel-16 read
TS 23.078 vj00 CAMEL Phase 4 Stage 2 Specification Rel-19 read
TS 23.380 vk00 IMS Restoration Procedures Rel-20 read
TS 23.501 vk30 5G System Architecture Rel-20 read
TS 23.527 vk00 5G Restoration Procedures for N4 Interface Rel-20 read
TS 23.558 vk30 Enabling Edge Applications Rel-20 read
TS 23.700 vk10 AI/ML Application Layer Support Phase 2 Rel-20 read
TS 24.501 vk10 5GS NAS Protocol Specification Rel-20 read
TS 24.890 vg00 5G NAS Protocol for 5GS Stage 3 Rel-16 read
TS 26.802 vk00 5G Media Streaming Multicast Enhancements Rel-20 read
TR 26.803 vh00 5G Media Streaming Extensions for Edge Processing Rel-17 read
TS 26.804 vk10 5G Media Delivery Architecture Extensions Rel-20 read
TR 26.806 vi00 Technical Report on Smartly Tethering AR Glasses Rel-18 read
TS 26.891 vg00 Media Distribution Services in 5G System Rel-16 read
TR 26.919 vj00 Study on 5G Conversational Media Handling Rel-19 read
TS 26.942 vk00 Sustainable Media Metrics and Architectural Impacts for 5G Rel-20 read
TS 28.561 vk20 Network Digital Twin Management Rel-20 read
TS 28.801 vf10 Management and Orchestration of Network Slicing Rel-15 read
TS 28.802 vf00 Management Study for 5G Network Architecture Rel-15 read
TR 28.816 vh00 Charging for 5G Cellular IoT Rel-17 read
TR 28.833 vi01 Technical Report on 5G LAN-type Service Management Rel-18 read
TR 28.840 vi10 Technical Report Rel-18 read
TR 28.843 vi10 Technical Report on Charging Aspects for Vertical Scenarios Rel-18 read
TS 28.874 vj10 Study on Management Aspects of NTN Phase 2 Rel-19 read
TS 29.061 vk10 Packet Domain Interworking Requirements Rel-20 read
TS 29.078 vj00 CAMEL Phase 4 CAP Specification Rel-19 read
TS 29.214 vk00 Rx Interface for Policy and Charging Control Rel-20 read
TS 29.244 vk10 PFCP for Control and User Plane Separation Rel-20 read
TS 29.502 vk10 5G SMF Service Based Interface Stage 3 Rel-20 read
TS 29.503 vk10 UDM Service Based Interface Rel-20 read
TS 29.505 vk00 UDR Services for Subscription Data Rel-20 read
TS 29.507 vk10 Access and Mobility Policy Control Rel-20 read
TS 29.508 vk10 Session Management Event Exposure Service Rel-20 read
TS 29.512 vk10 Session Management Policy Control Service Stage 3 Rel-20 read
TS 29.513 vk10 5G PCC Signalling Flows Rel-20 read
TS 29.514 vk10 Policy Authorization Service Rel-20 read
TS 29.518 vk10 AMF Service Based Interface Rel-20 read
TS 29.520 vk10 5G NWDAF Services Rel-20 read
TS 29.521 vk10 Binding Support Management Service Rel-20 read
TS 29.523 vk10 Policy Control Event Exposure Service Rel-20 read
TS 29.524 vk00 5GC to NAS Cause Mapping Specification Rel-20 read
TS 29.525 vk10 UE Policy Control Service Rel-20 read
TS 29.532 vk00 Nmbsmf Service Based Interface Specification Rel-20 read
TS 29.534 vk00 5G Access and Mobility Policy Authorization Rel-20 read
TS 29.536 vk10 Nnsacf Network Slice Admission Control Rel-20 read
TS 29.541 vk00 NEF South-Bound Interfaces for NIDD and SMS Rel-20 read
TS 29.542 vk00 Nsmf NIDD Service API (TS 29.542) Rel-20 read
TS 29.551 vk00 3GPP TS 29551 vk00: PFD Management Service Specification Rel-20 read
TS 29.552 vk10 5G Network Data Analytics Procedures Rel-20 read
TS 29.558 vk00 Edge Application Enablement APIs Rel-20 read
TS 29.561 vk10 5G Network Interworking Procedures Rel-20 read
TS 29.564 vk10 Nupf Service Based Interface Rel-20 read
TS 29.574 vk10 DCCF Service Based Interface Rel-20 read
TS 29.575 vk10 ADRF Service Based Interface Rel-20 read
TS 29.576 vk10 MFAF Service Based Interface Rel-20 read
TS 29.585 vj00 TSN Interworking Protocol for 5G System Rel-19 read
TS 29.591 vk10 NEF Southbound Services Rel-20 read
TR 29.820 vh00 Study on PFCP Best Practice Rel-17 read
TS 29.866 vj00 IMS Disaster Prevention & Restoration Enhancement Rel-19 read
TS 29.867 vk00 IMS Resiliency Enhancement Study Rel-20 read
TS 29.889 vj10 Study on UPF data collection for AI/ML Rel-19 read
TS 29.890 vg00 CT3 5G System Technical Report Rel-16 read
TS 32.240 vk10 3GPP Charging Architecture and Principles Rel-20 read
TS 32.255 vk30 5G Data Connectivity Converged Charging Rel-20 read
TS 32.260 vk10 IMS Charging Management Rel-20 read
TS 32.279 vj00 5G MBS Session Converged Charging Rel-19 read
TS 32.290 vk00 5G Charging Service-Based Architecture Rel-20 read
TS 32.291 vk10 5G Charging Service-Based Interface Rel-20 read
TS 32.298 vk10 Charging Data Record Specification Rel-20 read
TR 32.847 vi00 Technical Report Rel-18 read
TS 32.872 vk00 Roaming Charging Reliability Enhancement Rel-20 read
TS 32.899 vf10 5G Charging Architecture Study Rel-15 read
TS 33.108 vj00 LI Handover Interface Specification Rel-19 read
TS 33.127 vj80 Lawful Interception Architecture Rel-19 read
TS 33.501 vk30 5G Security Architecture Rel-20 read
TS 33.511 vk10 5G gNB Security Assurance Specification Rel-20 read
TS 33.513 vk20 UPF Security Assurance Specification Rel-20 read
TS 33.515 vk00 5G SMF Security Assurance Specification Rel-20 read
TS 33.727 vj00 Lawful Interception with End-to-End Encryption in 5G Rel-19 read
TR 33.739 vi10 Study on security enhancement of support for Rel-18 read
TS 33.749 vj00 Study on security aspects of edge computing enhancement Rel-19 read
TS 33.794 vj10 Study on Zero Trust Security Enablers for 5G Rel-19 read
TS 33.929 3GPP TR 33.929 Rel-15 read
TS 38.300 vj40 NR and NG-RAN Overall Description Rel-19 read
TS 38.401 vj30 NG-RAN Architecture Description Rel-19 read
TS 38.410 vj20 NG-RAN; NG General Aspects and Principles Rel-19 read
TS 38.413 vj40 NG Application Protocol (NGAP) Specification Rel-19 read