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

Glossary term · Mobility

Network-initiated NBIFOM

Network-initiated Network-Based IP Flow Mobility

Mobility →

Network-initiated NBIFOM is a mode of Network-Based IP Flow Mobility in which the network, rather than the UE, decides and initiates movement of specific IP flows between 3GPP and non-3GPP access.

Introduced
Rel-13
Where
Core Network › 5G Core
Specifications
2 specs
Network-initiated NBIFOM Description Purpose Neighbours Specifications

Description

Network-Based IP Flow Mobility (NBIFOM) is a 3GPP feature, specified in TS 23.161 with study material in TR 23.861, that allows individual IP flows of a PDN connection to be routed over different access networks — typically one flow over 3GPP access (e.g., LTE/5G NR) and another over a non-3GPP access (e.g., Wi-Fi) — while keeping a single PDN connection and IP address. NBIFOM is 'network-based' because the mobility anchor and routing decisions reside in the core network using GTP (for 3GPP access) and PMIPv6 (for trusted non-3GPP access) rather than requiring client-based DSMIPv6 on the UE.

Network-initiated NBIFOM is the variant where the network decides to move an IP flow from one access to another and triggers the procedure. The decision can be made by the core network based on policy from the PCRF/PCF (via ANDSF or direct policy), access network conditions, subscription data, or operator preferences. The network then signals the UE using dedicated NBIFOM signaling over the existing PDN connection — specifically, the NBIFOM routing rules are conveyed via the WLAN Control Protocol (WLCP) over trusted WLAN access or via NAS signaling, depending on the access technology.

The mechanism relies on routing rules and routing access information exchanged between the UE and the network. Each routing rule associates a traffic filter (e.g., IP 5-tuple) with a routing access (3GPP or non-3GPP) and an access preference. In network-initiated mode, the network sends a request to add, modify, or delete routing rules, and the UE acknowledges and applies them. The PDN Gateway (P-GW) acts as the IP anchor and enforces flow routing via the S5/S8 bearers toward the Serving Gateway for 3GPP access and via the S2a PMIPv6 tunnel toward the Trusted WLAN Access Gateway (TWAG) for non-3GPP access.

Key network elements include the P-GW (anchor and enforcement point), the TWAG/TWAP for trusted WLAN, the MME/SGSN for 3GPP access control, the PCRF/PCF for policy, and the AAA server for authentication and authorization on the non-3GPP side. The UE must support NBIFOM and indicate its capability during PDN connection establishment; the network then indicates whether NBIFOM is supported and in which mode (UE-initiated, network-initiated, or both).

Network-initiated NBIFOM is valuable because it lets the operator steer traffic without requiring UE-side intelligence or user intervention, enabling seamless Wi-Fi offload, policy-driven traffic steering, and improved user experience. It complements UE-initiated NBIFOM, where the UE requests flow mobility. The definition text is unchanged across Rel-13 through Rel-19, indicating a stable, mature specification.

Purpose & Motivation

As smartphones and multi-access devices proliferated, operators wanted to exploit Wi-Fi and other non-3GPP accesses to offload traffic and improve coverage without breaking application sessions. Earlier approaches such as DSMIPv6-based IP flow mobility required client support on the UE and were complex to deploy. NBIFOM was created to move the intelligence into the network, using GTP and PMIP anchors already deployed, so that flow mobility could work with minimal UE impact.

Within NBIFOM, the network-initiated variant exists to give the operator direct control over traffic steering. Operators can respond to congestion, policy changes, or subscription tiers by moving selected flows to Wi-Fi or back to cellular, without waiting for a UE request. This is essential for dynamic network management, QoS enforcement, and service differentiation.

The feature addresses the limitation of access-network-only selection (e.g., basic ANDSF or access network discovery), which operates at the connection level rather than the flow level. By enabling per-flow steering initiated by the network, NBIFOM supports scenarios like keeping voice on cellular while offloading video to Wi-Fi, all under operator policy control.

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-13 Initial

Initial definition: IP Flow Mobility based on network mobility protocols (GTP and PMIP) where the network initiates the IP flow mobility. Introduces network-initiated routing rule signaling and P-GW-based flow enforcement.

Definition text unchanged from Rel-13; the term carried over without modification.

Definition text unchanged from Rel-13; the term carried over without modification.

Definition text unchanged from Rel-13; the term carried over without modification.

Definition text unchanged from Rel-13; the term carried over without modification.

Definition text unchanged from Rel-13; the term carried over without modification.

Definition text unchanged from Rel-13; the term carried over without modification.

Defining Specifications

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

SpecificationTitleRelease
TS 23.161 vj00 Network-based IP Flow Mobility (NBIFOM) Rel-19 read
TS 23.861 vd00 Network-Based IP Flow Mobility (NBIFOM) Rel-13 read