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

Glossary term · Core Network

SM

Session Management

Core Network →

SM is a core network function responsible for establishing, maintaining, modifying, and terminating user data sessions, including IP address allocation and QoS enforcement.

Introduced
R99
Where
Services › IMS
Specifications
39 specs
Also in
Core Network, User Equipment
SM Description Purpose What changed Neighbours Detected Changes Specifications

Description

Session Management (SM) is a fundamental control-plane function within the 3GPP network architecture, executed by the Session Management Function (SMF) in 5G Core (5GC) and historically by the SGSN and GGSN in the GPRS core network. Its primary role is to manage the lifecycle of a user's data session, which provides IP connectivity to external data networks (DNs). In 5G, this session is termed a Protocol Data Unit (PDU) Session, while in earlier systems like GPRS and EPS, it was known as a Packet Data Protocol (PDP) Context.

The SM process begins with a session establishment request from the User Equipment (UE). The SMF/SGSN authenticates the request, interacts with the Policy Control Function (PCF) or Policy and Charging Rules Function (PCRF) to obtain policy and charging rules, and selects a User Plane Function (UPF) or Gateway (GW) to anchor the session. It allocates an IP address to the UE, establishes the necessary tunnels (e.g., GTP tunnels between the RAN, UPF, and DN), and configures the required Quality of Service (QoS) parameters for the data flows. Throughout the session's lifetime, SM handles modifications triggered by events like handovers, changes in subscriber status, or network-initiated QoS updates, ensuring seamless connectivity.

Key components involved in SM include the SMF (in 5GC), the AMF (Access and Mobility Management Function) which forwards session requests, the PCF for policy control, the UPF for user-plane packet routing and forwarding, and the UDM (Unified Data Management) for subscriber data. The function also manages session continuity during mobility events, supports multiple concurrent sessions per UE, and interfaces with charging systems. It is defined by a rich set of procedures in technical specifications, covering every aspect from initial provisioning to graceful release.

Purpose & Motivation

Session Management was created to provide a standardized, scalable mechanism for establishing and maintaining packet-switched data connections for mobile users. Prior to its introduction in 3GPP Release 99, mobile networks were primarily circuit-switched, designed for voice. The emergence of mobile internet necessitated a packet-oriented core network capable of managing dynamic, IP-based sessions with varying quality requirements.

SM solves the problem of providing controlled, billable IP connectivity in a mobile environment. It enables the network to manage resources efficiently, applying policies based on user subscription, service type, and network conditions. Without SM, the network would be unable to differentiate between data sessions, enforce QoS, support mobility, or implement charging—essential for commercial data services. Its evolution from PDP Context management in GPRS to PDU Session management in 5G reflects the increasing demands for flexibility, network slicing support, and cloud-native architectures.

What changed in its specifications

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

TR 21.905Rel-17 → Rel-18

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

Full comparison in TR 21.905 →
TS 22.142Rel-8 → Rel-9

Rel-9 added VAS4SMS, independent VAS-SMS provisioning, limited message forwarding, and auto-reply loop prevention.

Full comparison in TS 22.142 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-15 1 change
  • Alignments with NAS 5GS Session Management TS 29.502CR0047
Rel-16 1 change
  • Support of BDT reference Id within Session Management data TS 29.519CR0149
Rel-17 1 change
  • User location included in session management messages TS 29.502CR0453

Defining Specifications

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

SpecificationTitleRelease
TS 21.810 v300 Multi-mode UE Issues - Categories, principles and procedures R99 read
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TR 21.910 v300 Multi-mode UE Operation Principles R99 read
TS 22.142 vj00 Value-added Services for SMS Requirements Rel-19 read
TR 22.942 vj00 SMS Value-Added Services Requirements Rel-19 read
TR 22.944 vj00 UE Functionality Split Scenarios and Requirements Rel-19 read
TS 23.039 v500 SMSC to SME Interface Protocols Rel-5 read
TS 23.040 vk00 SMS Technical Realization for GSM/UMTS/EPS/5GS Rel-20 read
TS 23.048 v590 Secured Packets Structure for SMS and UICC Management Rel-5 read
TS 23.060 vj00 GPRS Stage 2 Service Description Rel-19 read
TS 23.078 vj00 CAMEL Phase 4 Stage 2 Specification Rel-19 read
TS 23.204 vj10 SMS over generic IP access; Stage 2 Rel-19 read
TS 23.437 vk40 Spatial Anchors and Mapping for Metaverse Rel-20 read
TS 23.540 vk00 5G Service-Based SMS Architecture Rel-20 read
TS 23.824 va00 IP-SM-GW enhancements for CPM-SMS Interworking Rel-10 read
TS 23.840 v710 SMS Inter-PLMN Architecture Analysis Rel-7 read
TS 24.007 vk00 Layer 3 Architecture for GSM/UMTS/EPS/5GS Rel-20 read
TS 24.065 v310 GPRS Subnetwork Dependent Convergence Protocol R99 read
TS 24.237 vj00 IMS Service Continuity Protocol Details Rel-19 read
TS 24.305 vj00 Selective Disabling of 3GPP UE Capabilities Rel-19 read
TS 29.078 vj00 CAMEL Phase 4 CAP Specification Rel-19 read
TS 29.311 vj00 Service Level Interworking for Messaging Rel-19 read
TS 29.338 vj30 Diameter protocols for SMS in MME/5GS Rel-19 read
TS 29.437 vk10 SEAL Spatial Anchor and Map APIs Rel-20 read
TS 29.502 vk10 5G SMF Service Based Interface Stage 3 Rel-20 read
TS 29.518 vk10 AMF Service Based Interface Rel-20 read
TS 29.519 vk10 5G UDR Policy and Application Data Services Rel-20 read
TS 29.541 vk00 NEF South-Bound Interfaces for NIDD and SMS Rel-20 read
TS 29.549 vk10 SEAL Service APIs Rel-20 read
TS 29.577 vk00 IP-SM-GW and SMS Router SBI Stage 3 Rel-20 read
TS 29.579 vk00 3GPP TS 29579 vk00: SMS-IWMSC Service Based Interface Rel-20 read
TS 31.115 vj00 Secured Packet Structure for UICC Applications Rel-19 read
TS 31.121 vj00 UICC Application Test Specification Rel-19 read
TS 31.829 vd00 ISIM Conformance Requirements Technical Report Rel-13 read
TS 32.899 vf10 5G Charging Architecture Study Rel-15 read
TS 33.434 vj00 Security aspects of SEAL for verticals Rel-19 read
TS 38.401 vj30 NG-RAN Architecture Description Rel-19 read
TR 43.901 vj00 Generic Access to A/Gb Interface Feasibility Study Rel-19 read
TS 44.065 vj00 GPRS SNDCP Specification Rel-19 read