LTE-WLAN Aggregation Adaptation Protocol

Description

The LTE-WLAN Aggregation Adaptation Protocol (LWAAP) is a crucial protocol layer defined within the 3GPP architecture for LTE-WLAN Aggregation (LWA), introduced in Release 13. It operates as a sublayer within the eNodeB (eNB) and is responsible for adapting Packet Data Convergence Protocol (PDCP) Protocol Data Units (PDUs) for transmission over a trusted WLAN access network. The LWAAP layer adds a small header to the PDCP PDU, which includes essential information such as a bearer identity and a sequence number. This adaptation is necessary because the WLAN link does not natively support the QoS and bearer management mechanisms of the LTE radio interface; the LWAAP header allows the receiving entity, the WT (WLAN Termination), to correctly reassemble and forward the data, maintaining the integrity and order of the data flow associated with a specific EPS bearer.

Architecturally, LWAAP resides between the PDCP layer and the lower layers responsible for transmission over the Xw interface (the interface between the eNB and the WT). The eNB, acting as the LWAAP transmitting entity, performs data splitting decisions at the PDCP layer. For bearers configured for LWA, the eNB can route some PDCP PDUs over the LTE-Uu air interface directly and others to the LWAAP layer. The LWAAP layer then processes these PDCP PDUs, encapsulates them with the LWAAP header, and forwards them via the Xw user-plane protocol stack (typically over GTP-U/UDP/IP) to the WT. The WT, upon receipt, removes the LWAAP header and delivers the original PDCP PDU to the WLAN modem for transmission to the UE over the IEEE 802.11 link.

The protocol's design ensures seamless aggregation from the UE's perspective. The UE receives PDCP PDUs from both radio links and delivers them to its single PDCP entity for reordering and in-sequence delivery to the higher layers. This process is transparent to the core network, as the S1-U interface remains terminated at the eNB. Key components involved are the LWAAP entity in the eNB, the corresponding entity in the WT, and the control-plane signaling over the Xw-C interface to establish and manage LWA bearers. LWAAP's role is fundamental to realizing the benefits of LWA, enabling operators to boost capacity and user experience by utilizing WLAN as a complementary radio resource under the tight control of the LTE network.

Purpose & Motivation

LWAAP was created to address the growing demand for higher data rates and better user experience in cellular networks, particularly in dense urban environments and indoor scenarios where WLAN is widely available. Prior to 3GPP integration, LTE and WLAN operated independently, with solutions like ANDSF (Access Network Discovery and Selection Function) providing policy-based steering, which was slow and reactive. This led to inefficient use of both networks, as the UE could only be connected to one at a time for a given IP flow, and the core network could not manage the WLAN resource directly.

The primary problem LWAAP solves is enabling the LTE network to utilize WLAN as a seamless, aggregated data pipe at the radio level. It allows for real-time, per-packet scheduling and splitting of traffic by the eNB, which was not possible with earlier offloading techniques. This tight integration solves the limitations of loose coupling by providing improved mobility performance, enhanced QoS support, and more efficient radio resource utilization. The motivation was to create a standardized, carrier-controlled method to leverage unlicensed spectrum (Wi-Fi) to augment licensed LTE capacity, improving throughput and network efficiency without requiring changes to the core network or the UE's IP layer.

Key Features

• Adapts PDCP PDUs for transmission over WLAN by adding an LWAAP header
• Supports bearer-specific identification via a Logical Channel ID in the header
• Includes sequence numbering for in-order delivery assistance over the WLAN link
• Enables per-packet level splitting and aggregation controlled by the eNB
• Operates transparently to the core network (S1-U terminated at eNB)
• Works with both collocated and non-collocated WT deployment scenarios

Evolution Across Releases

Defining Specifications