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
Phase 1
Where
Services › IMS
Specifications
39 specs
Also in
Core Network, User Equipment
SM Description Purpose What changed Family 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 →

Technology family

NAS mobility and session protocols · User Equipment › Protocol Layers (NAS)

  1. Phase 1 CC, MM, SM
  2. R97 GMM
  3. R98 CTS-MM
  4. Rel-8 EMM, ESM
  5. Rel-15 5GMM, 5GSM
  • SM counterpart in another generation: ESM
    “LV-E and TLV-E are used by for example, 5GS Mobility Management (5GMM), 5GS Session Management (5GSM), EPS Mobility Management (EMM), EPS Session Management (ESM), GPRS Mobility Management (GMM) and GPRS Session Management (SM).” TS 24.007
  • SM used together with GMM
    “The GPRS Mobility Management (GMM) sublayer provides services to the Session Management (SM) entity, Supplementary Service (SS) entity and the Short Message Service Support (GSMS) entity for message transfer.” TS 24.007

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 14 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.

Phase 1 introduced

Introduced in Phase 1 (release dating of the term; no individual change cited).

R99 specification text

The GMM/SM protocol is specified for the first time in 23.060 v3h0, with SM supporting PDP context activation, modification and deactivation for GPRS and UMTS.

  • “SM supports PDP context activation and PDP context deactivation, as described in subclause "PDP Context Activation, Modification, Deactivation, and Preservation Functions".” TS 23.060 v3.17.0
  • “This protocol supports mobility management functionality such as GPRS attach, GPRS detach, security, routeing area update, location update, PDP context activation, and PDP context deactivation” TS 23.060 v3.17.0
Rel-7 specification text

Session Management procedures in 23.060 gained added text restricting how they apply and a QoS management aspect during Session Management procedures, including MS-only secondary PDP context requests.

  • “When 'MS_only' the MS shall request any additional PDP contexts for the PDP Address/APN pair through the Secondary PDP Context Activation Procedure.” TS 23.060 v7.11.0
  • “Session Management procedures described in clause 9.2 apply with the following restrictions:” TS 23.060 v7.11.0
Rel-10 specification text

Rel-10 adds APN based Session Management congestion control: the SGSN can reject SM requests with a back-off timer per APN and the MS must defer SM procedures while it runs.

  • “The SGSN may reject the Session Management (SM) requests from the MS (e.g. Activate PDP Context, Secondary PDP Context and Modify PDP Context Requests)” TS 23.060 v10.14.0
  • “The MS shall support a separate Session Management back-off timer for every APN that the MS may activate.” TS 23.060 v10.14.0
  • “the MS shall stop the Session Management back-off timer associated with this APN and respond to the SGSN.” TS 23.060 v10.14.0
Rel-11 1 CR

SM back-off timer congestion control was extended: it can be sent in Deactivate PDP Context Request, applies per APN for low access priority requests, and AC11-15 and emergency access are exempt while the timer runs.

  • “The SGSN may deactivate PDP contexts belonging to a congested APN by sending the Deactivate PDP Context Request message to the MS with a Session Management back-off timer.” TS 23.060 v11.12.0
  • “The MS is allowed to initiate the Session Management procedures when it is accessing the network with AC11‑15 or for emergency services” TS 23.060 v11.12.0
  • Network Provided Location Information Retrieval via Session Management Procedures TS 23.060CR1613
Rel-12 1 CR

A Session Management back-off timer was added for UEs in Single-Connection mode, changing how SM behaves for such UEs.

  • Session Management back-off timer for UE in Single-Connection mode TS 29.273CR0379
Rel-13 specification text

Rel-13 adds group-specific and APN-and-group-specific NAS level congestion control for Session Management signalling, letting the SGSN reject SM requests or deactivate PDP contexts with an SM back-off timer.

  • “The SGSN may reject the Session Management (SM) requests from the MS belonging to this particular group” TS 23.060 v13.8.0
  • “The SGSN may deactivate PDP contexts from the MSs, belonging to this particular group and attaching to this particular APN” TS 23.060 v13.8.0
Rel-14 specification text

SGSN session management back-off timer rejection no longer lists Modify PDP Context Requests among the SM requests that may be rejected, narrowing it to Activate and Secondary PDP Context.

  • “(e.g. Activate PDP Context, Secondary PDP Context and Modify PDP Context Requests) with a Session Management back-off timer.” TS 23.060 v14.8.0
  • “(e.g. Activate PDP Context, and Secondary PDP Context) with a Session Management back-off timer.” TS 23.060 v14.8.0
Rel-15 specification text

Session Management is specified for the first time in 5G System Rel-15: a dedicated clause 5.6 in TS 23.501, session management procedures in clause 4.3 of TS 23.502, SMF and Session Management Subscription data handling.

  • “Clause 4.3 defines the Session Management related procedures. It refers to clause 4.4 for the N4 interactions.” TS 23.502 v15.17.0
  • “The SMF updates the Session Management Subscription Data and acknowledges the UDM by returning an Ack with (SUPI).” TS 23.502 v15.17.0
  • “the UE shall not initiate any Session Management procedures for the congested DNN. The UE may initiate Session Management procedures for other DNNs.” TS 23.501 v15.13.0
Rel-16 2 CRs

Session Management procedures were extended in Rel-16: SM subscription data retrieval now includes serving PLMN ID and NID, SMF IP prefix allocation changed, and SM support was added for wireline 5G-RG/FN-RG access and MA PDU sessions.

  • “SMF retrieves the Session Management Subscription data using Nudm_SDM_Get (SUPI, Session Management Subscription data, selected DNN, S-NSSAI of the HPLMN, Serving PLMN ID, [NID])” TS 23.502 v16.19.0
  • Session Management of 5G-RG/FN-RG connection to 5GC in the Wireline ANs TS 23.501CR0962
  • Session Management Procedure for Control Plane CIoT 5GS Optimisation TS 23.502CR1002
Rel-17 1 CR

Session Management gained new Rel-17 behaviour: an SMF event exposing Session Management Congestion Control Experience per PDU Session, SMF use of that analytics for back-off timers, and SM subscription data extensions.

  • “the SMF may make use of Session Management Congestion Control Experience analytics provided by NWDAF” TS 23.501 v17.15.0
  • New SMF event for Session Management Congestion Control Experience TS 23.502CR2507
  • “ECS Address Configuration Information is provided to SMF as Session Management Subscription data.” TS 23.502 v17.15.0
Rel-18 1 CR

Session Management Subscription data and related SM procedures were extended in Rel-18, e.g. ECS Address Configuration Information provided to SMF/H-SMF as Session Management Subscription data and UE Policy Container forwarding via SMF+PGW-C.

  • “the ECS Address Configuration Information is provided to SMF as Session Management Subscription data.” TS 23.502 v18.14.0
  • “it forwards transparently the UE Policy Container to PCF for the PDU Session in the Npcf_SMPolicyControl_Update Request” TS 23.502 v18.14.0
  • Additional Shared DNN Config IDs in Session Management Subscription Data TS 29.503CR1107
Rel-19 2 CRs

Session Management subscription data handling was extended: UDM now stores AF-provided static IP address assignment parameters in Session Management Subscription data for the SMF, and CHF Group ID was added to SM subscription data.

  • “the UDM authorises the request and adds, updates or removes such static IP address/prefix in Session Management Subscription data for the UE” TS 23.502 v19.9.0
  • CHF Group ID in Access and Mobility, Session Management and SMS Management Subscription Data TS 23.502CR5485
  • Clarifications to Session Management aspects for handling Non-3GPP Device Identifiers TS 23.501CR6175
Rel-20 specification text

Session management behaviour changed in Rel-20: the H-SMF uses the hosting operator PLMN ID for charging and subscription retrieval, and SMF+PGW-C S-NSSAI handling for PDN connections in EPC was revised.

  • “the H-SMF may include that PLMN ID in charging data.” TS 23.502 v20.3.0
  • “may apply policy and charging control according to Indirect Network Sharing agreement with that hosting operator.” TS 23.502 v20.3.0

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-ME Interface Conformance Requirements 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