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

Glossary term · Protocol

5GSM

5G Session Management

Protocol →

5GSM is the protocol for managing PDU Session establishment, modification, and release between the UE and the SMF in 5G networks to enable services with specific QoS requirements.

Introduced
Rel-15
Where
Core Network › Evolved Packet Core
Specifications
4 specs
5GSM Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

5G Session Management (5GSM) is a control plane protocol defined within the 5G System (5GS) architecture. It operates between the User Equipment (UE) and the Session Management Function (SMF) to manage Packet Data Unit (PDU) Sessions, which are the fundamental connectivity service providing user plane connectivity between the UE and a specific Data Network (DN). The 5GSM protocol is carried within the Non-Access Stratum (NAS) signaling messages between the UE and the Access and Mobility Management Function (AMF), with the AMF transparently relaying 5GSM messages to and from the SMF. This separation of the session management signaling from the access and mobility management signaling (handled by the 5GMM protocol) is a key architectural principle of 5G, allowing for independent scaling and evolution of session and mobility management functions.

The primary function of 5GSM is to establish, modify, and release PDU Sessions. A PDU Session establishment procedure involves the UE sending a PDU Session Establishment Request to the network, which triggers the SMF to select a User Plane Function (UPF), establish the necessary N4 session with the UPF, and negotiate the required QoS parameters. The 5GSM protocol conveys critical information such as the PDU Session ID, the selected Data Network Name (DNN), the requested Single-Network Slice Selection Assistance Information (S-NSSAI), and the PDU Session Type (e.g., IPv4, IPv6, IPv4v6, Ethernet, or Unstructured). It also manages the activation, modification, and deactivation of QoS Flows within a PDU Session, mapping service data flows to specific QoS Flows with defined 5G QoS Identifier (5QI) values, Guaranteed Flow Bit Rate (GFBR), and Maximum Flow Bit Rate (MFBR).

Beyond basic session lifecycle management, 5GSM supports advanced features essential for 5G's service-based architecture. It enables the negotiation and management of Protocol Configuration Options (PCO), which allows the SMF to provide the UE with parameters like DNS server addresses. It also supports UE-requested PDU Session Modification procedures, allowing the UE to request changes to the session's characteristics, such as adding or removing a QoS Flow. Furthermore, 5GSM procedures are tightly integrated with network slicing; the S-NSSAI included in the 5GSM signaling ensures the PDU Session is established within the correct network slice instance, providing the intended service characteristics and isolation. The protocol also handles the release of PDU Sessions, either initiated by the UE or the network, ensuring proper cleanup of resources in the SMF, UPF, and UE.

Purpose & Motivation

5GSM was created as part of the new 5G Core (5GC) architecture to address the limitations of the Evolved Packet System (EPS) session management protocol used in 4G/LTE. In EPS, session and mobility management were more tightly coupled within a single protocol (ESM and EMM, respectively). The 5G design principle of service-based architecture and network function disaggregation necessitated a clean separation between the Access and Mobility Management Function (AMF) and the Session Management Function (SMF). 5GSM exists to provide a dedicated, efficient protocol for session management that can operate independently of the underlying access technology (3GPP access like NR or non-3GPP access like Wi-Fi) and can scale to support the massive diversity of 5G use cases.

The protocol solves the problem of managing complex, service-specific connectivity sessions with dynamic QoS requirements. Previous systems had more rigid QoS models. 5GSM is designed to support a wide array of PDU Session types (beyond just IP), including Ethernet and Unstructured types, which are critical for vertical industry applications and fixed-mobile convergence. It also provides the signaling foundation for network slicing, allowing a single UE to have multiple concurrent PDU Sessions, each potentially in a different network slice with entirely different performance and security characteristics. This was a significant evolution from the EPS bearer model, enabling true service-based connectivity.

Furthermore, 5GSM was motivated by the need for enhanced efficiency and flexibility. By separating session management signaling, the network can optimize the placement and scaling of the SMF independently from the AMF. The protocol supports UE-triggered session modification, giving applications more direct control over their network resources. It also simplifies the integration of non-3GPP access, as the same 5GSM protocol is used regardless of how the UE attaches to the 5GC, providing a unified session management experience. In essence, 5GSM is the enabling protocol that translates high-level service requests into specific, actionable user plane connectivity rules within the 5G network.

What changed in its specifications

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

TS 24.501Rel-18 → Rel-19

Rel-19 adds satellite NG-RAN access text, LP-WUS/WUR assistance and disabling, ATUC RAT utilization control, and network-controlled slice selection with S-NSSAI time validity to TS 24.501. It also adds ATSSS Phase 4 multi-access and 5G ProSe multi-hop relay support.

Full comparison in TS 24.501 →
TS 29.214Rel-18 → Rel-19

Rel-19 adds IMS disaster prevention and restoration enhancements, including PCEF failure detection and a new PC-Session-Recovery-Status AVP. It also adds Multimedia Priority Service for Messaging support and satellite access charging with a Serving-Satellite-Identity AVP.

Full comparison in TS 29.214 →

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
  • 5GSM 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
  • 5GSM used together with 5GMM
    “the 5GSM entity provides services to the QoS flow control (QFC) entity and uses services of the 5GMM sublayer;” 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 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 5GSM protocol is specified for the first time in TS 24.501, providing procedures for handling 5GS PDU sessions and controlling user-plane resources, with 5GSM messages piggybacked in 5GMM transport messages.

  • “The 5GS session management (5GSM) protocol defined in the present document provides procedures for the handling of 5GS PDU sessions.” TS 24.501 v15.7.0
  • “A 5GS session management (5GSM) message is piggybacked in specific 5GS mobility management (5GMM) transport messages.” TS 24.501 v15.7.0
  • “The purpose of the 5GSM cause information element is to indicate the reason why a 5GSM request is rejected.” TS 24.501 v15.7.0
Rel-16 1 CR

In Rel-16, 5GSM behaviour changed: new 5GSM cause handling (#82 not applicable for non-3GPP access), back-off timer rules, and an exception to suspending 5GSM message transmission during service request.

  • “the UE and the AMF need not suspend the transmission of 5GSM messages related to other PDU session(s)” TS 24.501 v16.15.0
  • “Handling of 5GSM cause value #82 "maximum data rate per UE for user-plane integrity protection is too low" does not apply for non-3GPP access.” TS 24.501 v16.15.0
  • 5GSM cause value #29 semantic extension TS 24.501CR1124
Rel-17 1 CR

5GSM behaviour changed in Rel-17: UE suspends 5GSM messages during SOR, back-off timer rules for 5GSM cause #27 were clarified, and new 5GSM cause handling was added.

  • “the UE shall suspend the transmission of 5GSM messages after sending the REGISTRATION COMPLETE message” TS 24.501 v17.18.1
  • “If the network includes this back-off timer value for 5GSM cause value #27 "missing or unknown DNN"” TS 24.501 v17.18.1
  • Addition of 5GSM cause #37 TS 24.501CR2782
Rel-18 2 CRs

5GSM behaviour changed in Rel-18, e.g. 5GSM message transfer when outside the NS-AoS of an S-NSSAI, S-NSSAI location validity operation, and corrections to 5GSM state transitions and capability handling.

  • “If a UE is outside the NS-AoS of an S-NSSAI (see clause 4.6.2.10), the UE may initiate the UE-initiated NAS transport procedure” TS 24.501 v18.14.0
  • 5GSM operation for a UE with S-NSSAI location validity information TS 24.501CR5594
  • Correction in the 5GSM sublayer state transition in terms of the PDU SESSION MODIFICATION REJECT message including 5GSM cause value #43 TS 24.501CR5241
Rel-19 2 CRs

5GSM behaviour in TS 24.501 changed: restrictions on UE-requested 5GSM procedures outside the NS-AoS, 5GSM capability IE corrections, and 5GSM sublayer operation under CIoT congestion control.

  • “the UE shall not initiate for this PDU session any UE-requested 5GSM procedure except:” TS 24.501 v19.8.0
  • 5GSM sublayer operation upon receiving an indication that the CIoT user data was not forwarded due to congestion control TS 24.501CR6767
  • Correction on inclusion of 5GSM capability IE for PDU SESSION MODIFICATION REQUEST message TS 24.501CR6774
Rel-20 specification text

The E8PCPDEI-based extended 802.1Q PCP/DEI packet filter handling is extended to PDU session modification: the UE sets the bit in PDU SESSION MODIFICATION REQUEST and the SMF may include such filters in PDU SESSION MODIFICATION COMMAND.

  • “packet filter component type identifier set to extended 802.1Q C-TAG PCP/DEI packet filter component type or extended 802.1Q S-TAG PCP/DEI packet filter component type in the PDU SESSION MODIFICATION COMMAND message” TS 24.501 v20.1.0
  • “the UE shall set the E8PCPDEI bit to "Extended 802.1Q C-TAG/S-TAG PCP/DEI packet filter component type supported" in the 5GSM capability IE of the PDU SESSION MODIFICATION REQUEST message.” TS 24.501 v20.1.0

Defining Specifications

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

SpecificationTitleRelease
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 29.214 vk00 Rx Interface for Policy and Charging Control Rel-20 read
TS 38.508 vj31 5G NR UE ICS Proforma Rel-19 read