Home / Call Flows / 5G / Idle Mode Mobility

5G Idle Mode Mobility Procedure Call Flow

call-flow 5G NR | Idle Mobility | Cell Reselection | Paging Reachability

5G Idle Mode Mobility is the UE-driven process that keeps a registered idle UE camped on the best suitable cell without maintaining an active RRC connection.

The practical engineering goal is not just reselection, but stable reachability, good paging behavior, and low signaling overhead.

Introduction

This page explains how the UE evaluates the serving cell, compares neighbors, reselects when needed, and triggers NAS mobility handling only when area boundaries require it.

In field troubleshooting, the strongest path is to inspect broadcast reselection rules, RF measurements, and whether paging still works after the move.

What Is Idle Mode Mobility in Simple Terms?

What starts the procedure: The UE in idle state sees a better cell or moves into a new area.
What the UE and network want to achieve: Keep the UE camped on the best suitable cell while preserving reachability and efficiency.
What success looks like: The UE reselects correctly and remains reachable for paging and later service.
What failure means: Camping becomes unstable, reachability breaks, or unnecessary NAS churn appears.

Why this procedure matters

Idle mobility problems create paging failures, battery drain, and unnecessary registration churn long before engineers notice obvious call or session failures.

Quick Fact Sheet

Procedure name	5G Idle Mode Mobility
Domain	5G NR idle-state mobility and cell reselection
Main trigger	UE in idle state detects a better cell or moves into a different registration area
Start state	UE is registered in 5GS and camped on an NR cell in RRC Idle
End state	UE camps on the best suitable cell and stays reachable for paging and later service
Main nodes	UE, serving cell, neighbor cells, gNB broadcast configuration, AMF for later registration update
Main protocols	RRC idle-state behavior, system information, NAS registration update when needed
Main success outcome	UE reselects correctly and remains reachable without unnecessary signaling or paging loss
Main failure outcome	UE camps on the wrong cell, reselects too often, misses paging, or triggers unnecessary registration churn
Most important messages	System information, measurement criteria, paging-related reachability, Mobility Registration Update if RA changes
Main specs	TS 38.304, TS 38.331, TS 23.502, TS 24.501

Preconditions

The UE is already registered in 5GS.
The UE is in RRC Idle and monitoring system information and paging.
Neighbor cells are detectable and have valid broadcast mobility configuration.
The network registration-area design is consistent with the expected mobility pattern.

Nodes and Interfaces

Nodes involved

Node	Role in this procedure
UE	Performs cell selection and reselection decisions locally based on measurements and broadcast rules.
Serving cell	Provides the idle-state system information and paging context the UE currently relies on.
Neighbor cells	Compete to become the better camping cell based on priority and measured quality.
gNB broadcast configuration	Defines the reselection thresholds, priorities, and paging reachability assumptions.
AMF	Becomes relevant when a change in registration area requires a mobility-related NAS update.

Interfaces used

Interface	Path	Role
NR-Uu	UE <-> serving and neighbor cells	Carries synchronization, system information reading, and paging reception in idle state.
Broadcast system information	Cell -> UE	Provides reselection priorities, thresholds, and access conditions.
N1 / NAS	UE <-> AMF	Used later if idle mobility leads to a Mobility Registration Update across registration areas.

End-to-End Call Flow

UE                Serving Cell            Neighbor Cells            AMF
|                     |                         |                    |
|-- measure serving ->|                         |                    |
|---------------- measure neighbors ----------->|                    |
|==== reselection decision and camping change =====================>|
|---------------- registration update if needed ------------------->|
|==== stable paging reachability on new camped cell ==============>|

Major Phases

Phase	What happens
1. Idle camping state	The UE is registered, camped, and waiting for paging or future service demand.
2. Measurement and evaluation	The UE compares serving and neighbor cell quality using idle-state rules.
3. Reselection decision	The UE chooses a better cell if the configured criteria say the move is worthwhile.
4. Registration-area impact check	The UE determines whether the new camping cell changes reachability or registration-area context.
5. Stable idle reachability	The UE remains camped on the best suitable cell and ready for paging or service restoration.

Step-by-Step Breakdown

The UE evaluates the serving cell while idle

Sender -> receiver: UE <-> serving cell

Message(s): System information reading and radio measurements

Purpose: Determine whether the current cell is still suitable for camping and paging reachability.

State or context change: The UE stays in idle mode and makes the first suitability judgment locally.

Note: Idle mode mobility is mainly a UE-driven decision process, so measurement interpretation is the first key checkpoint.

Neighbor cells are measured and compared

Sender -> receiver: UE <-> neighbor cells

Message(s): Idle-state measurement comparison

Purpose: Decide whether another cell offers a better idle mobility outcome.

State or context change: The UE weighs quality, priority, and suitability rules against the serving cell.

Note: A stronger signal alone is not enough. Priority, thresholds, and access conditions still matter.

The UE reselects the target idle cell

Sender -> receiver: UE -> target cell

Message(s): Cell reselection and camping transition

Purpose: Move idle camping to the better cell without connected-mode handover signaling.

State or context change: The target cell becomes the new camping cell for paging and future access.

Note: Reselection churn or ping-pong behavior usually means thresholds and priorities are not tuned well for the RF reality.

Registration-area impact is checked

Sender -> receiver: UE <-> AMF if needed

Message(s): Mobility Registration Update when registration area changed

Purpose: Keep the core network informed if the UE moved into a different registration or tracking context.

State or context change: Idle mobility becomes a NAS mobility event only when area boundaries require it.

Note: Do not confuse every reselection with a registration update. Many cell changes stay purely idle-state and local.

The UE remains reachable for paging and later service

Sender -> receiver: UE <-> new serving cell

Message(s): Paging monitoring and later service recovery readiness

Purpose: Maintain idle-mode efficiency while preserving network reachability.

State or context change: The UE finishes the idle mobility branch in a stable camping state.

Note: A reselected cell is only truly successful if paging and later service restoration still work well.

Important Messages in This Flow

Message	Protocol	Direction	Purpose in this procedure	What to inspect briefly
System information	RRC broadcast	Cell -> UE	Defines reselection behavior, thresholds, and suitability constraints.	Check priorities, thresholds, and barred-cell settings first.
Paging	RRC / NGAP	Network -> UE	Validates that the UE remained reachable after idle mobility.	Useful to prove the camping choice still supports service reachability.
Registration Update	NAS	UE -> AMF	Appears only if the new cell changes the registration-area context.	Important to separate pure reselection from area-change signaling.
Registration Accept	NAS	AMF -> UE	Confirms the updated mobility context if an area update was needed.	Lets you confirm that idle mobility and core reachability stayed aligned.

Important Parameters to Inspect

Parameter	What it is	Where it appears	Why it matters	Common issues
RSRP / RSRQ / SINR	Measured quality of serving and neighbor cells.	Idle measurements	Explain why the UE preferred one camping cell over another.	Weak measurements alone do not explain outcome without thresholds.
Priority and threshold configuration	Operator-configured reselection logic.	Broadcast system information	Determines whether the UE is allowed or encouraged to move.	Bad tuning creates ping-pong or sticky camping.
Cell suitability and barring	Whether the candidate cell can legally be selected.	System information	Separates strong-but-unsuitable cells from usable targets.	Often missed in quick RF-only analysis.
Registration area / TAI context	Core-network mobility area tied to the camped cell.	Post-reselection check	Explains whether NAS mobility signaling should follow the reselection.	Wrong area assumptions cause paging and update trouble.
Paging success after reselection	Reachability result once camping changed.	Post-reselection validation	Best practical proof that idle mobility ended well.	This matters more than a pretty RF graph.

Success Criteria

The UE camps on the best suitable cell according to configured rules.
Paging reachability remains intact after reselection.
Registration updates happen only when area-change logic requires them.
The UE avoids unnecessary mobility churn and battery waste.

Common Failures and Troubleshooting

Symptom	Likely cause	Where to inspect	Relevant message(s)	Relevant interface(s)	Likely next step
Frequent reselection or ping-pong camping	Thresholds, priorities, or RF overlap are unstable.	Measurement trend, priority settings, and repeated camping changes.	System information and measurement history	NR-Uu	Treat this as a mobility-tuning problem, not only a radio-coverage problem.
UE camps on a weak or wrong cell	Selection logic, priorities, or barring interpretation is wrong.	Serving-versus-neighbor suitability and broadcast rules.	System information	NR-Uu	A stronger cell may still be unsuitable or lower priority.
Paging fails after idle mobility	The UE reselected but lost reachability alignment with the network.	Paging identity, registration-area context, and post-reselection camping cell.	Paging, Registration Update if present	NR-Uu, N1	This is the operational test that matters most.
Too many registration updates follow reselection	Area planning and idle mobility behavior are not aligned.	TAI changes, update timers, and reselection pattern.	Registration Update	N1	Excess NAS churn is often an area-design issue.

What to Check in Logs and Traces

Start with system information for thresholds, priorities, and barring.
Compare serving and neighbor measurements at the exact reselection point.
Check whether a Registration Update was actually required or just happened nearby.
Validate paging success after the move, not just the RF outcome.
When camping oscillates, correlate priority tuning with the RF overlap pattern.

Related sub-procedures

Related message reference pages

Related troubleshooting pages

FAQ

What is 5G Idle Mode Mobility?

It is the UE-driven process of cell selection and reselection while the UE is in RRC Idle.

Is it the same as handover?

No. Idle mobility is mainly local UE decision-making, while connected-mode handover is network-controlled.

What proves success?

The UE camps on the best suitable cell and remains reachable for paging and later service.

When does NAS signaling appear?

Usually only when reselection changes the registration-area context and a Mobility Registration Update is required.

What should I inspect first?

Start with broadcast reselection rules, then serving-versus-neighbor measurements, then paging behavior afterward.