Offload Preference Indicator

Description

The Offload Preference Indicator (OPI) is a network-provided parameter used within the Access Network Discovery and Selection Function (ANDSF) framework and later evolved policies to guide User Equipment (UE) behavior in selecting between different radio access technologies. Its primary role is to indicate the network's preference for offloading data traffic from 3GPP cellular networks (like LTE or NR) to non-3GPP networks (most commonly Wi-Fi). The OPI is not a direct command but an influential value that the UE uses in conjunction with other policies and thresholds to make its final access selection decision.

Technically, the OPI is delivered to the UE via management objects, such as ANDSF policies (specified in TS 24.312) or, in later 5G systems, via UE policies from the Policy Control Function (PCF). It is typically an integer value. The UE's decision logic, often implemented in its operating system or modem firmware, evaluates the OPI against locally configured thresholds or other received policy rules. For example, a network might set a high OPI value for a congested cell, strongly encouraging UEs with Wi-Fi capability to connect to an available Wi-Fi network. Conversely, a low OPI value might indicate a preference for the UE to remain on or return to the 3GPP network, perhaps because the cellular network is under-utilized or offers a specific service (like voice) with higher quality.

The OPI works in tandem with other parameters like the WLANSP (WLAN Selection Policy) and RANSP (RAN Selection Policy). A key mechanism is its interaction with the Offloadability Indicator. The network may mark certain traffic flows (based on APN or DNN) as 'offloadable' or 'non-offloadable'. The OPI preference typically applies only to offloadable traffic. For critical services like IMS voice, the network might set them as non-offloadable, ensuring they stay on the 3GPP network regardless of the OPI value. This granular control allows operators to implement sophisticated traffic steering strategies, such as offloading best-effort web browsing to Wi-Fi in dense urban areas while keeping latency-sensitive gaming traffic on a managed 5G connection.

Purpose & Motivation

The OPI was introduced to address the growing need for intelligent traffic steering between heterogeneous networks, specifically the explosion of Wi-Fi availability alongside ubiquitous 3GPP coverage. Early smartphone implementations often used simple, user-controlled, or device-centric Wi-Fi selection (e.g., 'connect to known SSID'), which could lead to poor user experience—such as a device clinging to a very weak Wi-Fi signal instead of switching to a strong LTE signal—and inefficient network resource utilization. Operators lacked a standardized, network-controlled mechanism to influence this decision.

The purpose of the OPI is to provide the operator with a policy-based tool to optimize overall network performance and user experience. It solves the problem of uncontrolled offloading by allowing the network to express its load conditions and preferences. This enables key use cases like load balancing: during peak hours in a stadium, the network can set a high OPI to encourage UEs to use the deployed Wi-Fi network, alleviating congestion on the cellular RAN. It also supports service continuity; an operator might use a low OPI to steer a UE back to the cellular network as it moves out of a Wi-Fi coverage area to avoid a sudden drop. By centralizing this steering logic in network policies rather than device algorithms, operators can implement consistent, network-wide strategies for traffic management across diverse device types and operating systems.

Key Features

• Network-provided integer value indicating offload preference strength
• Delivered via standardized policy frameworks (ANDSF, UE Policy)
• Influences UE's autonomous access network selection decision
• Works in conjunction with Offloadability Indicator for per-flow granularity
• Supports dynamic network steering based on real-time load conditions
• Enables coexistence with user preferences and device-based rules

Evolution Across Releases

Defining Specifications