Description
The WLAN Termination (WT) is a functional entity introduced in 3GPP Release 13 as part of the LTE-WLAN Radio Level Integration (LWIP) and LTE-WLAN Aggregation (LWA) features. It acts as a gateway or termination point for the WLAN side in these tight integration architectures. As defined in TS 36.300, the WT terminates the user plane and control plane protocols towards the WLAN Access Point (AP) and communicates with the LTE eNodeB (eNB) over a standardized interface (specifically, the Xw interface for control plane and user plane in LWA).
Architecturally, the WT sits between the eNB and one or more WLAN APs. In LWA, the WT terminates the PDCP protocol for the data radio bearers that are offloaded to WLAN. It receives PDCP Protocol Data Units (PDUs) from the eNB over the Xw user plane and forwards them to the WLAN AP for transmission to the UE, and vice versa. In LWIP, the WT acts more as an IPsec gateway, establishing secure tunnels with the UE for IP traffic offload. The WT is managed by the eNB, which makes centralized decisions on traffic steering, splitting, and switching between LTE and WLAN based on radio conditions.
Key components of the WT functionality include the termination of the Xw application protocol (Xw-AP) for control signaling with the eNB, management of data forwarding over the Xw user plane (using GTP-U or IPSec), and its interface with the WLAN AP (which is implementation-specific but logically controlled by the WT). Its role is critical for enabling the eNB to treat WLAN as a secondary cell group or a managed flow-offload path, allowing for true radio-level integration with coordinated scheduling, mobility, and QoS management across the two radio technologies. This provides a significantly better user experience compared to loose network-level interworking.
Purpose & Motivation
The WT was created to address the limitations of earlier 3GPP-WLAN interworking solutions (like I-WLAN and ANDSF-based steering), which operated at the core network or policy level and could not perform fast, radio-aware traffic management. These earlier approaches suffered from suboptimal user experience due to lack of coordination between LTE and WLAN radios, leading to issues like sticky clients and inefficient load balancing. The motivation for the WT arose from the need for tighter, radio-layer integration to fully exploit the combined capacity and coverage of LTE and Wi-Fi.
This technology solves the problem of uncoordinated dual connectivity. By introducing the WT as a subordinate node to the eNB, 3GPP enabled the LTE network to directly control and manage WLAN resources at the radio bearer level. This allows for seamless aggregation of data flows (LWA) or secure, network-controlled IP flow mobility (LWIP), improving throughput, reliability, and mobility performance. It represented a paradigm shift from network-level interworking to true access network convergence, driven by operator demands for more efficient use of all available radio assets.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (17 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-13, normative work from Rel-15.
In Release 15, the specification introduced the derivation of the key **S-K_WT** from K_eNB for the WT function to support LTE-WLAN Aggregation (LWA). This key derivation, detailed in an annex, uses specific input parameters including a WT Counter. The release also included the related derivation of **LWIP-PSK** for LTE WLAN integration using IPSec.
- Correction to FDD/TDD Diff for NR PDCP Capabilities TS 36.331CR3674
- Introducing PDCP suspend procedure TS 36.331CR3794
- Remove PDCP change indication in SN modification request message TS 36.423CR1095
- Correction for PDCP Duplication TS 36.423CR1152
- Notification of PDCP SN length change TS 36.423CR1196
- Addition of the RLC Mode information for PDCP transfer TS 36.423CR1237
+ 5 more changes
In Release 16, enhancements for the WT function included deriving the S-K WT security key from the K eNB for LTE-WLAN Aggregation (LWA) to secure the connection. The release also introduced mechanisms to avoid security risks for RLC bearers during a termination point change and allowed for a PDCP version change without requiring a handover.
In Release 17, the key enhancement for the WLAN Termination (WT) function was the introduction of support for User Plane IP for EPC-connected architectures using NR PDCP. This change specifically enabled the derivation of the S-K WT key from the K eNB during procedures like LTE-WLAN Aggregation, utilizing the defined WT Counter parameter. The update formalized the security mechanisms for user plane data protection over the WT interface at the PDCP layer, aligning with the established key derivation procedures.
Explore further
Broader topics and technologies where WT plays a role.
Defining Specifications
3GPP specifications that define or reference WT, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 33.401 vj10 | EPS Security Architecture | Rel-19 |
| TS 36.300 vj00 | E-UTRAN Radio Interface Protocol Architecture Overview | Rel-19 |
| TS 36.331 vj00 | LTE RRC Protocol Specification | Rel-19 |
| TS 36.423 vj10 | X2 Application Protocol (X2AP) Specification | Rel-19 |
| TS 36.462 vj00 | Xw Interface Signalling Transport | Rel-19 |
| TS 36.463 vj00 | XwAP Protocol Specification | Rel-19 |
| TS 36.464 vj00 | Xw Interface User Plane Protocol | Rel-19 |
| TS 36.465 vj00 | Xw User Plane Protocol Specification | Rel-19 |
| TS 37.870 vd00 | Study on Multi-RAT Joint Coordination | Rel-13 |
| TR 38.804 ve00 | Study on New Radio Access Technology; Radio Interface Protocol Aspects | Rel-14 |