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

Glossary term · Core Network

Iu-flex

Iu Flex

Core Network →

Iu-flex is a routing functionality that allows a radio access network node to connect to multiple core network nodes for load balancing and redundancy in UMTS and GSM networks.

Introduced
R99
Where
Services
Specifications
2 specs
Iu-flex Description Purpose What changed Neighbours Specifications

Description

Iu-flex is a key architectural feature in 3GPP networks that provides routing functionality for the intra-domain connection of radio access network (RAN) nodes to multiple core network (CN) nodes. In traditional networks, each RAN node (such as a base station or radio network controller) was connected to a single CN node (such as an MSC or SGSN) for each domain. Iu-flex changes this by allowing a RAN node to be connected to multiple CN nodes within the same domain, typically in a pool. This enables load sharing, redundancy, and more efficient use of network resources.

The mechanism works by introducing a network resource identifier (NRI) that is used to route messages from the RAN to the appropriate CN node. When a mobile station attaches to the network, the RAN selects a CN node from the pool based on load balancing algorithms. The selected CN node then assigns a temporary identity to the mobile station that includes the NRI. For subsequent transactions, the RAN uses the NRI to route messages to the same CN node, ensuring session continuity. This is particularly important for services that require a persistent connection, such as packet-switched data sessions.

Iu-flex is defined for both circuit-switched (CS) and packet-switched (PS) domains. In the CS domain, it allows a Radio Network Controller (RNC) or Base Station Controller (BSC) to connect to multiple Mobile Switching Centers (MSCs) in a pool. In the PS domain, it allows connection to multiple Serving GPRS Support Nodes (SGSNs). The feature is specified in 3GPP TS 23.236 for the core network aspects and TS 25.410 for the UTRAN Iu interface. It is also applicable to GERAN in Iu mode, as specified in TS 43.051.

The benefits of Iu-flex are significant. First, it provides load balancing across CN nodes, preventing any single node from becoming a bottleneck. This improves overall network efficiency and can delay the need for capacity upgrades. Second, it offers redundancy: if one CN node fails, the RAN can route traffic to other nodes in the pool, enhancing service availability. Third, it simplifies network expansion, as new CN nodes can be added to the pool without reconfiguring the RAN. Fourth, it reduces the number of interfaces required, as a single RAN node can serve multiple CN nodes, leading to cost savings.

Despite its advantages, Iu-flex requires careful planning and configuration. The NRI must be unique within the pool, and the RAN must support the necessary routing functionality. Interoperability between different vendors' equipment is ensured through standardized procedures. The feature has been supported since early releases of UMTS and continues to be relevant in modern networks, although its usage may decline as networks evolve towards flat architectures like LTE and 5G, where similar concepts are implemented differently (e.g., MME pools in EPS).

In summary, Iu-flex is a foundational technology for flexible and resilient core network connectivity in 3G networks. It exemplifies the principles of pool-based architectures that have become common in later generations.

Purpose & Motivation

Iu-flex was created to address the limitations of traditional hierarchical core network architectures, where each RAN node was hardwired to a single CN node. This one-to-one relationship led to inefficient resource utilization, as CN nodes could not share traffic loads, and it created single points of failure. If a CN node failed, all subscribers served by its connected RAN nodes would lose service. Additionally, capacity upgrades required adding new CN nodes and reconfiguring the RAN, which was complex and costly.

The primary motivation for Iu-flex was to enable load balancing and redundancy in the core network. By allowing a RAN node to connect to multiple CN nodes, traffic can be distributed evenly, preventing overload situations. This is particularly important in networks with uneven traffic patterns, such as those with busy hours or special events. Redundancy is achieved because if one CN node fails, the RAN can redirect traffic to other nodes in the pool, ensuring service continuity. This improves network availability and user experience.

Another motivation was to simplify network expansion and reduce operational costs. With Iu-flex, operators can add new CN nodes to a pool without having to reconfigure the RAN or disrupt existing services. This scalability is essential for growing networks. Furthermore, Iu-flex reduces the number of physical interfaces required, as a single RAN node can serve multiple CN nodes, leading to savings in transmission and equipment costs.

Historically, Iu-flex was introduced in 3GPP Release 99 (R99) as part of the UMTS specifications. It built upon the concept of the Iu interface, which provided the necessary separation between RAN and CN. The feature was later extended to GERAN in Iu mode, demonstrating its versatility. While newer technologies like LTE and 5G have adopted similar pool concepts (e.g., MME pools, AMF pools), Iu-flex remains a significant milestone in the evolution of mobile core networks, paving the way for more flexible and resilient architectures.

What changed in its specifications

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

TR 21.905Rel-17 → Rel-18

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

Full comparison in TR 21.905 →

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.

R99 Initial

Initial definition introduced: 'Routing functionality for intra domain connection of RAN nodes to multiple CN nodes.' This established the fundamental concept of Iu-flex for load balancing and redundancy.

Definition carried over unchanged from R99.

Definition carried over unchanged from R99.

Definition carried over unchanged from R99.

Definition carried over unchanged from R99.

Definition carried over unchanged from R99.

Definition text was reformatted (line breaks removed), but the meaning remained identical to R99.

Definition carried over unchanged from R99.

Definition carried over unchanged from R99.

Definition carried over unchanged from R99.

Definition text was reformatted (line breaks removed), but the meaning remained identical to R99.

Definition text was reformatted (line breaks removed), but the meaning remained identical to R99.

Definition carried over unchanged from R99.

Definition text was reformatted (line breaks removed), but the meaning remained identical to R99.

Definition carried over unchanged from R99.

Definition text was reformatted (line breaks removed), but the meaning remained identical to R99.

Defining Specifications

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

SpecificationTitleRelease
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TR 22.951 vj00 Network Sharing Requirements and Scenarios Rel-19 read