Hi,
The Truth About “Handover” in Telecom — What It Really Means
There is a massive misconception in the industry about the term handover. Many engineers casually apply it to any mobility event, but that is technically wrong.
Let’s set the record straight.
1. Handover is a Voice‑Continuity Concept — Not a Data Concept
The term handover exists because of voice calls, not data sessions.
Why?
A voice call:
-
is real‑time
-
is stateful
-
has strict latency requirements
-
cannot tolerate interruption
-
must maintain an unbroken RTP stream
If the radio link drops even briefly, the call drops.
Therefore, the network must perform a seamless, controlled transfer of the call from one cell or RAT to another.
This is what handover means.
2. Data Sessions Do NOT Need Handover
Data is packet‑switched, meaning:
So the network does not need to perform a seamless transfer.
Data mobility is handled by:
-
cell reselection (idle mode)
-
RRC handover (connected mode, but only radio-level)
-
TAU / RAU
-
GTP tunnel relocation
-
PDU session anchor mobility
These are mobility procedures, not handover in the voice sense.
This is why we call it a Packet‑Switched (PS) network — interruptions are acceptable.
3. Legacy (2G/3G) Handover Was Purely About Voice
In GSM/UMTS days, handover was defined by voice domain boundaries:
-
Intra‑BSC handover
-
Inter‑BSC handover
-
Intra‑MSC handover
-
Inter‑MSC handover
All of these existed to keep a circuit‑switched voice call alive while the UE moved.
Data (GPRS/EDGE/UMTS PS) did not require seamless continuity.
4. 4G Changed Everything — Voice Became Packet‑Based
When LTE arrived:
-
the network became data‑anchored
-
initial attach was to the packet core (EPC)
-
voice moved to IMS over data tunnels
-
fallback to 3G was used when IMS was unavailable
This created a challenge:
-
3G voice was CS‑anchored
-
4G voice was PS‑anchored
Moving a live call between these two worlds required a new mechanism.
5. SRVCC Was Invented to Bridge 3G ↔ 4G Voice
SRVCC (Single Radio Voice Call Continuity) was created to allow:
-
VoLTE → 3G CS voice
-
3G CS voice → VoLTE
It was needed because:
SRVCC ensured the call moved seamlessly, preserving the SIP dialog and RTP stream.
This was the dominant mobility method until 3G shutdown.
6. 5G SA Simplified Voice Mobility Again
In 5G SA:
-
everything is packet‑switched
-
IMS voice works over 5G NR, 4G LTE, or Wi‑Fi
-
the core network doesn’t care which access the UE uses
Voice continuity between:
-
5G ↔ 4G
-
5G ↔ Wi‑Fi
-
4G ↔ Wi‑Fi
is handled by IMS Access Transfer (ATCF/ATGW), not by radio handover.
The RAN only handles radio mobility.
The IMS handles voice continuity.
7. Idle Mode “Handover” Does Not Exist
People often say “idle mode handover,” but this is incorrect.
In idle mode:
-
the UE is not in RRC_CONNECTED
-
there is no bearer to transfer
-
the UE performs cell reselection, not handover
-
the network does not control mobility
Correct term: Idle Mode Mobility, not handover.
8. Final Summary
Handover = Seamless continuity of a live voice call
Data sessions do not need handover
Idle mode has no handover — only cell reselection
Legacy handover was CS‑voice anchored
LTE introduced IMS voice and SRVCC for 3G ↔ 4G
5G SA unified everything under packet‑switched voice
RAN handles radio mobility; IMS handles voice continuity