Description
Minimization of Service Interruption (MINT) is a collection of mechanisms standardized in 3GPP to reduce the time during which a User Equipment (UE) cannot send or receive user plane data during mobility procedures. Service interruption typically occurs during the execution of a handover, where the UE switches its connection from a source network node (e.g., gNB, eNB) to a target node. MINT techniques work by optimizing the handover preparation, execution, and re-establishment phases at both the Radio Access Network (RAN) and Core Network (CN) levels.
Architecturally, MINT involves enhancements in several network functions. In the RAN, it includes features like early handover preparation, where the source node initiates context fetching and resource reservation at the target node well before the actual handover command is sent to the UE. This is specified in RAN protocols (e.g., NGAP, XnAP). Another key technique is "Make-Before-Break" handover, particularly relevant in multi-connectivity scenarios like Dual Connectivity (DC) or Carrier Aggregation (CA), where the UE establishes a connection with the target cell while maintaining the link with the source cell, thereby eliminating the break period. The core network supports MINT through procedures like the "Handover without TAU/RAU" optimization for idle mode mobility and enhancements to the N26 interface for inter-CN mobility between 5GC and EPC.
From an operational perspective, MINT works by minimizing the sequential steps in a handover. For example, in a typical LTE-to-NR handover, the UE measurement reporting, target cell preparation, security key derivation, and path switch in the core network all contribute to delay. MINT procedures parallelize these tasks where possible. Key components involved are the Access and Mobility Management Function (AMF) for coordinating core network aspects, the source and target gNBs for RAN-level coordination, and the UE itself, which must support the enhanced RRC procedures. Its role is critical in 5G networks to meet the stringent requirements of Ultra-Reliable Low-Latency Communications (URLLC) and to ensure seamless experience for real-time services like voice (VoNR) and industrial automation during cell changes.
Purpose & Motivation
MINT was created to address the inherent service disruption that occurs during cellular handovers, which becomes particularly problematic for 5G use cases demanding high reliability and low latency, such as autonomous vehicles, remote surgery, and augmented reality. Traditional handover procedures, while reliable, involved a series of sequential signaling steps that could result in interruptions of hundreds of milliseconds, unacceptable for these new services. The limitations of previous approaches were their reactive nature and lack of coordination between RAN and CN during the critical handover execution phase.
The motivation for standardizing MINT in Release 17 and beyond stems from the 5G design principle of supporting diverse service requirements. Prior to MINT, enhancements like Data Forwarding during handover in LTE helped, but did not fully eliminate the interruption time, especially in inter-gNB or inter-system handovers. MINT provides a systematic framework to analyze and reduce every component of handover delay. It solves problems like prolonged interruption during inter-radio access technology (IRAT) handover between 4G and 5G, and during handovers in high-frequency bands (mmWave) where cells are smaller and handovers more frequent. By minimizing interruption, it ensures service continuity, which is a key performance indicator for network operators and a fundamental requirement for the commercial success of 5G-enabled critical applications.
Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (29 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 17, the MINT function was formally introduced to support disaster roaming, including the definition of a new registration type specifically for this scenario and a corresponding cause code. The updates also specified a UE MINT support indicator, provided clarifications on procedures like the UCU (UE Configuration Update) for MINT, and explicitly stated that S1 mode is not supported. Furthermore, the release included alignment and extensions for system information to enable the minimization of service interruption.
- Adding the functionality on MINT TS 23.501CR3019
- UE MINT support indicator TS 29.503CR0870
- MINT Updates TS 23.501CR3264
- Clarification on MINT TS 23.501CR3287
- Alignment on system information extensions for minimization of service interruption TS 23.501CR3407
- UCU procedure for MINT update TS 23.501CR3664
+ 3 more changes
In Release 18, the MINT function was enhanced by adding a pre-configured list of PLMNs, provided by the HPLMN, within the EFDRI (Disaster Roaming Information EF) for MINT-related parameters. Furthermore, corrections were made to the requirements for determining when a disaster condition has ended, specifically addressing an implementation collision from previous changes. These updates also included necessary corrections within the 24.501 specification to support the overall MINT functionality.
- MINT corrections in 24.501 TS 24.501CR6074
- Correction to requirements upon determining that a disaster condition has ended for MINT because of implementation collision of CR6074 and CR6162 TS 24.501CR6391
- Addition of pre-configured list of PLMNs, provided by HPLMN for MINT related parameters in EFDRI (Disaster roaming information EF). TS 31.102CR1001
In Release 19, the MINT (Minimization of Service Interruption) function was extended to support MINT-EPS, enabling 5G-capable UEs to minimize service interruption when roaming in EPS networks during disaster conditions. Key enhancements included the definition of specific abnormal case handling, TAU procedure updates, and timer handling for MINT-EPS operations. The release also provided clarifications on parameter storage for UEs supporting both MINT Phase 1 and Phase 2, and corrected the applicability of MINT procedures when a UE is already attached for disaster roaming services.
- General clause for MINT in EPS for 5G-only national roaming UEs TS 24.301CR4237
- Abnormal case handling for MINT-EPS TS 24.301CR4559
- EN removal for MINT-EPS TS 24.301CR4560
- TAU update in MINT-EPS TS 24.301CR4562
- Support of MINT-EPS TS 29.503CR1527
- Update of MINT clause for MINT-EPS handling TS 24.501CR7080
+ 11 more changes
Explore further
Broader topics and technologies where MINT plays a role.
Defining Specifications
3GPP specifications that define or reference MINT, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.401 vj50 | Evolved Packet System (EPS) Stage 2 Description | Rel-19 |
| TS 23.501 vk00 | 5G System Architecture Stage 2 | Rel-20 |
| TS 24.301 vj60 | NAS protocol for Evolved Packet System | Rel-19 |
| TS 24.501 vj50 | 5G NAS Protocols Specification | Rel-19 |
| TS 29.503 vj50 | UDM Service Based Interface Stage 3 | Rel-19 |
| TS 31.102 vj40 | USIM Application Specification | Rel-19 |
| TS 31.111 vj30 | USIM Application Toolkit (USAT) Specification | Rel-19 |