Service Continuity

Description

Service Continuity is a fundamental concept in 3GPP networks that ensures an uninterrupted user experience for active services when a User Equipment (UE) undergoes changes in its access network. This includes changes in radio access technology (RAT), such as handover between 2G, 3G, 4G, and 5G, as well as changes between circuit-switched (CS) and packet-switched (PS) domains. The goal is to maintain the service (e.g., an ongoing voice call, video stream, or data session) without perceptible interruption to the user.

Service continuity is achieved through various mechanisms, including handover procedures, session management, and mobility management. In the context of voice services, Single Radio Voice Call Continuity (SRVCC) enables a voice call to be transferred from LTE (VoLTE) to 3G/2G CS networks when the UE moves out of LTE coverage. Similarly, Reverse SRVCC (rSRVCC) allows calls to move from CS to PS. For data services, session continuity is maintained through IP address preservation and bearer management across different access technologies.

The 3GPP specifications define service continuity requirements in documents such as TS 22.278 (Service requirements for the Evolved Packet System) and TS 23.501 (System Architecture for the 5G System). These specifications outline the procedures for handover, session transfer, and interworking between different access networks. Key network elements involved include the Mobility Management Entity (MME), Serving Gateway (SGW), Packet Data Network Gateway (PGW), and the Access and Mobility Management Function (AMF) in 5G.

In 5G, service continuity is further enhanced with features like dual connectivity, where the UE maintains simultaneous connections to multiple cells, and network slicing, which allows tailored continuity guarantees for different services. The concept has evolved from simple CS handovers in early releases to complex, multi-access, multi-service continuity in modern networks.

Service continuity is critical for user satisfaction and is a key performance indicator for operators. It enables seamless mobility, supports real-time services, and ensures that users can move freely without dropping calls or losing data sessions. As networks become more heterogeneous, service continuity mechanisms continue to evolve to handle new challenges such as ultra-reliable low-latency communications (URLLC) and massive machine-type communications (mMTC).

Purpose & Motivation

Service Continuity exists to address the fundamental need for uninterrupted service delivery as users move across different networks and access technologies. In early mobile networks, a change in radio access technology or domain (e.g., from 3G to 2G) would often result in dropped calls or interrupted data sessions, leading to poor user experience. Service Continuity mechanisms were developed to ensure that active services remain seamless during such transitions.

The primary motivation is to provide a consistent user experience akin to that of fixed-line networks, where a call is not dropped when the user moves. This is particularly important for voice services, which are real-time and sensitive to interruptions. As networks evolved to include multiple RATs (2G, 3G, 4G, 5G) and domains (CS, PS), the complexity of maintaining continuity increased, necessitating standardized procedures.

Service Continuity also enables operators to leverage their existing infrastructure while migrating to new technologies. For example, SRVCC allows operators to provide VoLTE services in LTE coverage and fall back to 3G/2G CS networks when LTE coverage is unavailable, ensuring voice service continuity without requiring ubiquitous LTE coverage. This gradual migration strategy is cost-effective and user-friendly.

Furthermore, Service Continuity is essential for supporting emerging use cases such as mission-critical communications, where interruptions can have severe consequences. It is a key enabler for the 5G vision of a seamlessly connected society, where users expect ubiquitous and uninterrupted connectivity.