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

Glossary term · Mobility

FT

Fast BSS Transition

Mobility →

FT is a set of 3GPP protocols and procedures enabling rapid, secure transitions between Base Station Subsystems to minimize service interruption and support seamless mobility.

Introduced
Rel-8
Where
Management
Specifications
15 specs
Also in
Radio Access Network
FT Description Purpose What changed Neighbours Specifications

Description

Fast BSS Transition (FT) is a mobility management feature standardized by 3GPP to optimize handovers, particularly in scenarios involving non-3GPP access networks like Wi-Fi (as defined in the context of S2a mobility over trusted WLAN). The core objective is to reduce the latency and packet loss associated with a UE moving from one access point (AP) or base station to another. The FT procedures work by pre-establishing security and context information at the target AP *before* the UE physically disconnects from the serving AP. This is a proactive handover mechanism, as opposed to the traditional reactive break-before-make approach.

Architecturally, FT relies on key network entities defined in the 3GPP-WLAN interworking specifications, such as the Trusted WLAN Access Gateway (TWAG) and the AAA server. The procedure typically involves several key messages exchanged between the UE, the current AP (Current BSS), the target AP (Target BSS), and the central authentication server. A fundamental component is the use of key hierarchy derived from the initial authentication. The UE and the network can generate a Pairwise Master Key (PMK) or a Fast BSS Transition PMK (FT-PMK) that can be used to swiftly establish a secure connection with the target AP without needing a full EAP re-authentication, which is time-consuming.

The FT process can operate in different modes: Over-the-Air (where the UE communicates directly with the target AP), Over-the-DS (Distribution System, where messages are relayed through the current AP), and Fast Transition with Resource Request (where QoS resources are pre-reserved). The UE initiates the process by sending a reassociation request containing FT authentication material to the target AP. The target AP, having previously obtained or derived the necessary security context, can verify the UE and establish the link layer connection almost immediately. This entire handshake is designed to complete within tens of milliseconds, making it suitable for voice and other latency-sensitive applications. The extensive list of specifications (e.g., 24.502 for policy, 32.xxx for management) indicates FT's integration into broader network management, charging, and policy control frameworks.

Purpose & Motivation

Fast BSS Transition was created to address the critical problem of service disruption during handovers, especially for real-time applications. In traditional Wi-Fi networks, moving between access points required a full deauthentication/reauthentication and reassociation process, which could introduce interruptions of several hundred milliseconds—catastrophic for VoIP calls or live video streaming. FT solves this by decoupling the time-intensive authentication process from the actual physical transition event.

The historical motivation stems from the growing integration of Wi-Fi as a trusted access network within the 3GPP ecosystem (e.g., in ANDSF, Hotspot 2.0, and later 5G Access Traffic Steering, Switching and Splitting (ATSSS)). As operators began to rely on Wi-Fi for data offloading and seamless coverage, the need for carrier-grade mobility performance became paramount. FT addresses the limitations of the original IEEE 802.11 handover procedures, which were not designed with fast, secure, operator-controlled mobility in mind. By standardizing FT within the 3GPP framework, it ensures that handovers between Wi-Fi access points can meet the stringent latency and security requirements of mobile network operators, enabling true seamless mobility across heterogeneous networks.

What changed in its specifications

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

TS 24.502Rel-18 → Rel-19

Re-authentication procedures for mobility between access points on the same gateway, using FT to derive an FT key.

Full comparison in TS 24.502 →
TS 25.425Rel-11 → Rel-12

Adds two new 1-bit IEs for cell reselection indication and request received. Changes flag bit meanings in HS-DSCH and E-DCH frames.

Full comparison in TS 25.425 →

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-8 Initial

Introduced as part of the System Architecture Evolution (SAE) and trusted WLAN access integration. Initial architecture defined procedures for fast, secure transition between 802.11 access points, leveraging the 3GPP EAP-AKA' authentication framework and key hierarchy for context transfer.

Defining Specifications

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

SpecificationTitleRelease
TS 24.502 vk00 Non-3GPP Access Network Discovery and Selection Rel-20 read
TS 25.425 vj00 UTRAN Iur Interface User Plane Protocols Rel-19 read
TS 25.427 vj00 UTRAN Iub/Iur User Plane Protocols Rel-19 read
TS 25.435 vj00 UTRAN Iub Interface User Plane Protocols Rel-19 read
TS 32.332 vj00 Notification Log IRP Information Service Rel-19 read
TS 32.336 vj00 Notification Log IRP Solution Set Definitions Rel-19 read
TS 32.337 v900 Notification Log IRP SOAP Solution Set Rel-9 read
TS 32.341 vj00 File Transfer IRP Requirements Rel-19 read
TS 32.343 v900 File Transfer IRP CORBA Solution Set Rel-9 read
TS 32.345 v900 File Transfer IRP XML Definitions Rel-9 read
TS 32.346 vj00 File Transfer IRP Solution Set Definitions Rel-19 read
TS 32.371 vj00 Security Management Concept & Requirements Rel-19 read
TS 32.387 v910 Partial Suspension of Itf-N IRP SOAP Solution Set Rel-9 read
TS 32.411 vj00 PM IRP Requirements Rel-19 read
TS 32.572 vj00 HNB/HeNB Type 2 Interface Concepts & Requirements Rel-19 read