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

Glossary term · Core Network

Session Continuity

Session Continuity

Core Network →

Session Continuity is the continuity of a PDU Session, preserving the session's IPv4, IPv6, or IPv4v6 IP address for its lifetime and supporting seamless mobility and service continuity in 5G.

Introduced
Rel-14
Where
Core Network › 5G Core
Specifications
3 specs
Session Continuity Description Purpose What changed Neighbours Detected Changes Specifications

Description

Session Continuity in 3GPP refers to the ability to maintain a PDU (Packet Data Unit) Session without interruption, particularly ensuring that the IP address assigned to the UE remains unchanged for the lifetime of the session. This concept is defined in TS 23.501 (System Architecture for the 5G System) and was initially studied in TS 23.799 (Study on Architecture for Next Generation System). It is a core aspect of the 5G System architecture, enabling seamless mobility and service continuity for applications that require a stable IP address.

In 5G, a PDU Session is a logical connection between the UE and a Data Network (DN) that provides connectivity for user plane data. Each PDU Session is associated with an IP address (for IP-based PDU Sessions) and a set of QoS flows. Session continuity means that as the UE moves, the PDU Session remains active and the IP address does not change. This is achieved through mechanisms such as the Session Management Function (SMF) maintaining the session context and the User Plane Function (UPF) anchoring the session. When the UE moves, the SMF may select a new UPF or update the existing one to ensure continuity, but the IP address is preserved.

The 5G System supports different Session and Service Continuity (SSC) modes to cater to various application needs. SSC Mode 1 ensures that the IP address is preserved throughout the lifetime of the PDU Session, providing the highest level of continuity. SSC Mode 2 allows the network to release the PDU Session and assign a new IP address when the UE moves to a new area, which may be suitable for applications that can tolerate IP address changes. SSC Mode 3 allows the UE to establish a new PDU Session with a new IP address before releasing the old one, enabling make-before-break continuity. These modes allow operators to balance continuity requirements with network efficiency.

Session continuity is crucial for applications such as voice over IP (VoIP), video streaming, and mission-critical communications, where an IP address change could disrupt the service. It also supports mobility across different access technologies (e.g., 3GPP and non-3GPP) and across different network slices. The 5G core network functions, particularly the SMF and UPF, work together to maintain session continuity by managing session contexts, IP address allocation, and user plane paths. The concept also extends to interworking with 4G, where session continuity may be maintained during handovers between 4G and 5G.

Overall, Session Continuity is a fundamental capability of the 5G System that ensures a seamless user experience by preserving IP addresses and maintaining active sessions as the UE moves. It is a key differentiator from previous generations and is essential for the diverse set of services expected in 5G.

Purpose & Motivation

Session Continuity exists to address the need for uninterrupted service as users move across different areas and access technologies. In earlier generations, such as 3G and 4G, session continuity was primarily handled through mechanisms like GTP tunnels and anchor points, but the concept was not as explicitly defined or flexible as in 5G. With the advent of 5G and the diverse range of applications (e.g., IoT, URLLC, eMBB), the requirement for maintaining IP address stability became more critical, especially for applications that cannot tolerate IP address changes.

The 5G System introduced the concept of SSC modes to provide flexibility. Some applications, like mission-critical push-to-talk, require that the IP address remains constant to avoid session disruption. Others, like web browsing, can tolerate IP address changes and may benefit from more efficient network resource usage. By defining SSC modes, 3GPP allows operators to tailor session continuity to the needs of different services, optimizing network resources while meeting application requirements.

Historically, session continuity was often tied to the concept of an anchor point (e.g., PGW in 4G). In 5G, the architecture decouples the control plane and user plane, and the SMF can dynamically manage UPF selection to maintain continuity. This evolution reflects the need for a more flexible and scalable approach to mobility management. The definition of Session Continuity in 3GPP specifications has evolved from a general concept in Rel-14 to a more precise definition in Rel-15, specifying the IP address preservation for IPv4, IPv6, and IPv4v6 PDU Sessions. This precision ensures consistent implementation across vendors and supports interoperability.

What changed in its specifications

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

TS 23.501Rel-18 → Rel-19

Rel-19 added MPQUIC steering to multi-access PDU sessions, XR and media handling, and an Energy Information Function. It also added Local Offloading Management for edge computing, Vertical Federated Learning for AI/ML, and Ambient IoT text.

Full comparison in TS 23.501 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-16 1 change
  • Delivery of SMF waiting time to AF for session continuity TS 23.501CR1768

Defining Specifications

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

SpecificationTitleRelease
TS 23.501 vk30 5G System Architecture Rel-20 read
TR 23.799 ve00 Study on Next Generation System Architecture Rel-14 read
TS 33.819 vg10 5GS Security for Vertical & LAN Services Rel-16 read