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

Glossary term · Mobility

Directed retry

Directed Retry

Mobility →

Directed retry is a radio resource management procedure, triggered by RAB Assignment and using relocation procedures, that assigns a UE to a radio resource not belonging to the serving RNC, typically under congestion.

Introduced
Rel-8
Where
Radio Access Network › UTRAN (3G)
Specifications
2 specs
Directed retry Description Purpose What changed Neighbours Specifications

Description

Directed retry is a mobility and radio resource management procedure defined in 3GPP specifications 25.413 (RANAP) and 48.008 (BSSAP). It is the process of assigning a User Equipment to a radio resource that does not belong to the serving Radio Network Controller (RNC), for example in situations of congestion. The procedure is triggered by the RAB Assignment procedure and employs relocation procedures to move the UE's connection to a different RNC or radio resource.

In a UMTS Terrestrial Radio Access Network (UTRAN), the serving RNC manages the radio resources for a UE. When the serving RNC cannot provide sufficient resources—due to congestion, capacity limits, or radio conditions—it may decide to redirect the UE to another RNC or cell that has available resources. This is the essence of directed retry: rather than simply rejecting the RAB assignment, the network attempts to serve the UE using resources outside the current serving RNC's domain.

The procedure is initiated during RAB Assignment. If the serving RNC determines that it cannot fulfill the requested RAB within its own resources, it can trigger a relocation to a target RNC. The relocation procedures (such as SRNS relocation) are used to transfer the UE's context and connection to the target RNC, which then provides the radio resource. This involves signaling between the RNCs and the core network, and the UE is instructed to access the target cell.

Key components include the serving RNC, the target RNC, the core network (MSC/SGSN), and the UE. The RAB Assignment procedure is the trigger, and relocation procedures are the mechanism. Directed retry is closely related to load balancing and congestion control in UTRAN. It allows the network to maintain service continuity and improve resource utilization by moving UEs to less loaded cells or RNCs.

The concept has been stable across releases from Rel-8 through Rel-19, with the definition unchanged. It remains a relevant procedure in legacy UTRAN deployments and is documented in the RANAP and BSSAP specifications. While 5G and LTE have their own load balancing and mobility mechanisms, directed retry is an important historical and operational concept for UTRAN.

Purpose & Motivation

Directed retry exists to improve resource utilization and service continuity in UTRAN when the serving RNC experiences congestion or resource shortages. Without directed retry, a UE requesting a RAB during congestion might be rejected, leading to failed service attempts and poor user experience. By redirecting the UE to another RNC or radio resource, the network can serve the request and maintain connectivity.

The procedure was motivated by the need for efficient load balancing in early 3G networks. As UTRAN deployments scaled, operators needed mechanisms to manage uneven load across RNCs and cells. Directed retry provides a standardized way to move UEs to available resources during RAB Assignment, leveraging relocation procedures to ensure seamless transfer.

The concept addresses the limitations of simple admission control, which would otherwise reject requests when local resources are insufficient. By allowing the serving RNC to redirect the UE to a target RNC, directed retry enhances network flexibility and improves the success rate of service requests. Its stability across releases reflects its continued relevance in UTRAN operations.

What changed in its specifications

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

TS 25.413Rel-11 → Rel-12

Release 12 adds LIPA and SIPTO procedural handling with new IEs, an MBMS Session Re-establishment Indicator IE, and BDS support including GANSS ID coding value 101.

Full comparison in TS 25.413 →
TS 48.008Rel-17 → Rel-18

Rel-18 brings only minor changes to TS 48.008: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 48.008 →

Release Timeline

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

Initial definition established Directed retry as the process of assigning a UE to a radio resource not belonging to the serving RNC, triggered by RAB Assignment and employing relocation procedures. This defined the core mechanism for congestion-driven redirection in UTRAN.

The definition carried over unchanged, maintaining the same description of the procedure.

The definition remained unchanged, confirming stability of the concept.

The definition was carried over unchanged.

The definition remained unchanged.

The definition was carried over unchanged.

The definition remained unchanged.

The definition was carried over unchanged.

The definition remained unchanged.

The definition was carried over unchanged.

The definition remained unchanged.

The definition was carried over unchanged, indicating continued stability of the term across releases.

Defining Specifications

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

SpecificationTitleRelease
TS 25.413 vj00 Radio Access Network Application Part (RANAP) Rel-19 read
TS 48.008 vj00 BSS-MSC Interface Layer 3 Procedures Rel-19 read