SGC

Service Gap Control

Services →
Introduced in Rel-15

SGC is a NAS-level mechanism that manages periodic service gaps for UEs to perform inter-frequency or inter-RAT measurements, optimizing mobility and power efficiency while maintaining an active session.

Category
Services
Introduced
Rel-15
Where
Core Network › 5G Core
Specifications
2 specs
SGC Description Purpose Related Classification Detected Changes Specifications

Description

Service Gap Control (SGC) is a Non-Access Stratum (NAS) functionality introduced in 5G and evolved in later releases to enable User Equipment (UE) to temporarily interrupt an active data session for measurement purposes. It operates by defining a 'service gap'—a configured time window during which the network refrains from scheduling user data, allowing the UE to tune its radio away from the serving cell to scan other frequencies or radio access technologies (RATs). The SGC parameters, including gap duration, periodicity, and validity, are negotiated between the UE and the core network via NAS signaling, specifically defined in specifications 24.301 (EPS NAS) and 24.501 (5GS NAS).

Architecturally, SGC involves coordination between the UE and the Access and Mobility Management Function (AMF) in 5GC, or the MME in EPS. The UE requests a service gap pattern based on its capabilities and needs, such as inter-frequency or inter-RAT measurements for cell reselection or handover preparation. The network evaluates the request against policy and resource availability, then approves or modifies the pattern via a NAS message like the SERVICE GAP CONTROL message. During active gaps, the UE's RRC connection may be maintained, but user plane data transmission is halted, ensuring the session is preserved.

How it works: Once a service gap is activated, the UE uses the gap intervals to perform measurements on target cells, which could be on different NR bands, LTE carriers, or even non-3GPP networks. The network suspends downlink data scheduling and buffers any incoming packets, resuming transmission after the gap ends. This mechanism is distinct from traditional measurement gaps in RRC, as SGC operates at the NAS layer, providing more flexibility and longer durations suitable for background tasks like network scanning for edge computing or power saving.

Key components include the SERVICE GAP TIMER, which defines the gap length, and the SERVICE GAP PERIOD, which sets the recurrence interval. The UE reports gap utilization and measurement results to the network, enabling optimized mobility decisions. SGC enhances efficiency by allowing measurements without establishing new RRC connections or causing session drops, crucial for always-on services and battery-constrained devices.

Purpose & Motivation

SGC was created to address limitations in existing measurement gap mechanisms, which were primarily RRC-controlled and often insufficient for extensive inter-RAT or background scanning. In earlier releases, UEs relied on configured measurement gaps that were short and frequent, potentially disrupting latency-sensitive services and lacking NAS-level coordination. SGC solves this by introducing a NAS-based, negotiable service interruption, allowing for longer, tailored gaps that align with UE capabilities and network policies.

Historically, as networks evolved toward 5G and multi-RAT deployments (e.g., NR-LTE coexistence), UEs needed efficient ways to discover and measure alternative cells without degrading the user experience. SGC, introduced in Release 15 with 5G, provides this by enabling scheduled pauses in service, facilitating smooth mobility preparation and network discovery. It is particularly useful for power-saving modes and edge computing scenarios where UEs may need to periodically scan for local services.

The motivation stems from the need to balance service continuity with measurement requirements. By allowing controlled gaps, SGC reduces signaling overhead and battery consumption compared to frequent RRC reconfigurations. It supports advanced features like network slicing and non-terrestrial networks, where measurement intervals may vary significantly. Ultimately, SGC enhances overall system performance by enabling proactive mobility and resource optimization.

Classification

Part ofNAS
Related approachesAMF

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-15 8 changes

In Release 15, the Service Gap Control (SGC) function was newly introduced to allow the network to control how frequently UEs can transition from EMM-IDLE to EMM-CONNECTED mode. The core mechanism involves the network providing a service gap timer (T3447) to supporting UEs within ATTACH ACCEPT and TRACKING AREA UPDATE ACCEPT messages, which the UE must store. The release also defined specific UE behaviors, such as handling attach requests without a PDN connection and managing mobile-originated signaling while the timer is running, along with procedures for UEs that do not support the feature.

  • Introduction of Service Gap Control; basics and feature negotiation TS 24.301CR2982
  • Service Gap Control feature; non supporting UEs TS 24.301CR2983
  • Service Gap Control; UE behaviour service gap timer is running TS 24.301CR2984
  • Service Gap Control feature cleanup and corrections TS 24.301CR3010
  • Service Gap Control, attach without PDN connection for supporting UEs TS 24.301CR3036
  • MO signaling and data with service gap control timer running in connected mode TS 24.301CR3142

+ 2 more changes

Rel-16 23 changes

In Release 16, the Service Gap Control (SGC) function was extended from EPS to 5GS, introducing its activation and enforcement within the 5G Core network and the UE. Key enhancements included detailed procedures for SGC timer handling during intersystem change, interactions with power-saving modes like PSM and MICO, and specific rules for rejecting Mobile Originated services, such as SMS or LPP payloads, when the timer is running. The release also defined mechanisms for updating the timer via a UE Configuration Update procedure and clarified UE behavior for sending MO data while connected during an active service gap period.

  • Service Gap control in 5GS, general description TS 24.501CR0974
  • Service Gap control in 5GS, activation with IE and indication flag TS 24.501CR0975
  • Service Gap control in 5GS, enforcement in UE TS 24.501CR0977
  • Service Gap control in 5GS, enforcement in AMF TS 24.501CR0978
  • Service Gap control in 5GS, new time value via UCU procedure TS 24.501CR0979
  • Service Gap control in 5GS, reject of UL NAS Transport message TS 24.501CR1222

+ 17 more changes

Rel-18 1 change

In Release 18, the updates for Service Gap Control (SGC) primarily involved corrections and clarifications to existing functionality, as indicated by the Change Request title "Service gap control correction." The provided grounding context details the established SGC procedures from earlier releases, such as the network including the T3447 timer value in ATTACH ACCEPT and TRACKING AREA UPDATE ACCEPT messages when active, and the UE's behavior when the timer is running. Therefore, the Release 18 changes focused on refining these pre-defined mechanisms for controlling how frequently UEs transition from EMM-IDLE to EMM-CONNECTED mode.

  • Service gap control correction TS 24.501CR4497

Explore further

Broader topics and technologies where SGC plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 24.301 vj60 NAS protocol for Evolved Packet System Rel-19
TS 24.501 vj50 5G NAS Protocols Specification Rel-19
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.