Description
The Wireless LAN Control Plane Protocol (WLCP) is a key protocol defined for the S2a-based trusted WLAN access architecture in 3GPP. It operates between the User Equipment (WLAN-UE) and the Trusted WLAN Access Gateway (TWAG), which is the network entity that connects a trusted WLAN to the Evolved Packet Core (EPC). WLCP is conceptually analogous to the control plane part of the GTP protocol used over the S1-U and S5/S8 interfaces, but it is adapted for the WLAN access stratum. It uses UDP as its transport layer protocol.
The primary function of WLCP is to manage Packet Data Network (PDN) connections for a UE attached via trusted WLAN. It carries signaling messages for PDN connectivity procedures: PDN Connection Establishment, PDN Connection Modification, and PDN Connection Release. During PDN connection establishment, the UE uses WLCP to send a PDN Connectivity Request to the TWAG. The TWAG then interacts with the PGW (via GTP-C on S2a) to establish the connection and returns the assigned IP address(es) and other parameters to the UE via a WLCP response. WLCP also supports bearer-level control, allowing the establishment, modification, and deletion of dedicated bearers to provide different Quality of Service (QoS) levels for different traffic flows over the WLAN access.
WLCP messages are encapsulated within EAP over WLAN (specifically, within EAPoL-Key frames) for transmission over the IEEE 802.11 link between the UE and the WLAN Access Point (which is part of the trusted WLAN). This encapsulation ensures the signaling is carried securely over the WLAN link after the initial EAP-based authentication is complete. The protocol includes necessary elements like TEIDs (Tunnel Endpoint Identifiers) to identify specific connections and bearers, and it supports error handling and recovery procedures. By providing this standardized control plane, WLCP enables the trusted WLAN to be integrated into the EPC as a true, QoS-aware access network on par with 3GPP radio access.
Purpose & Motivation
WLCP was created to address a fundamental gap in the initial 3GPP-WLAN interworking architectures: the lack of a standardized, bearer-aware control plane for trusted WLAN access. Early interworking (e.g., via ePDG for untrusted access) focused on IPsec tunneling and did not support native, efficient QoS differentiation or seamless mobility procedures that were standard in 3GPP accesses. The motivation was to enable the "trusted WLAN" concept, where the operator has full control over the WLAN infrastructure, to offer services with the same reliability and quality as cellular.
The problem it solved was how to extend the EPC's PDN and bearer model—central to LTE's QoS architecture—over a non-3GPP IEEE 802.11 access link. Without WLCP, a trusted WLAN could only provide simple IP connectivity without the ability to establish dedicated bearers for guaranteed bit rate services or to efficiently manage multiple PDN connections (e.g., for IMS and internet simultaneously). WLCP provided the necessary signaling protocol to bring the rich connectivity and policy control of the EPC directly to the WLAN-attached UE.
Introduced in Release 12 as part of the S2a-based trusted WLAN access (TWAN) feature, WLCP was a critical enabler for deep network integration. It allowed operators to deploy carrier Wi-Fi that could not only offload data but also deliver voice over Wi-Fi (VoWiFi) with proper QoS, support seamless session continuity, and be managed as an integral part of the mobile network. This protocol laid groundwork for the later convergence of access types in 5G's Common Core.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (34 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-12, normative work from Rel-15.
In Release 15, the WLCP function was enhanced to support multiple dedicated bearers per PDN connection, introducing specific setup, modification, and release procedures for QoS differentiation. This included defining corresponding WLCP sublayer states for these multiple bearers and refining abnormal case handling for the new bearer procedures. The release also clarified the usage of the TWAG MAC address for WLCP bearers and provided mechanisms for user plane identity per WLCP bearer.
- Enabling ePDG selection using 5GS TAI information TS 23.402CR2984
- Support multiple WLCP bearers TS 24.244CR0041
- WLCP sublayer states for multiple bearer PDN connectivity TS 24.244CR0044
- WLCP bearer setup procedure for QoS differentiation TS 24.244CR0046
- WLCP bearer modification procedure for QoS differentiation TS 24.244CR0047
- WLCP bearer release procedure for Qos differentiation TS 24.244CR0048
+ 21 more changes
In Release 16, the WLCP function was enhanced to support a P-CSCF restoration extension for trusted WLAN access, introducing a new WLCP PDN connection modification request procedure for the TWAN to transparently forward updated P-CSCF addresses to the UE. This required the TWAN to advertise its support for this WLCP procedure during IMS PDN connection establishment or handover. Additionally, corrections were made to update the referenced IKEv2 protocol specification to RFC 7296.
In Release 17, the WLCP function was enhanced to support a P-CSCF restoration extension for trusted WLAN access, specifically requiring the TWAN to advertise support for and initiate a WLCP PDN connection modification request procedure. This procedure is used to transparently forward updated P-CSCF addresses from the PGW to the UE, and it is triggered when the TWAN indicates support for the WLCP PDN connection modification during IMS PDN connection establishment or handover.
In Release 18, the WLCP function was enhanced to support an extended P-CSCF restoration mechanism for trusted WLAN access. This included defining that the TWAN must advertise its support for the WLCP PDN connection modification procedure and, when triggered by the PGW, use this procedure to forward updated P-CSCF addresses to the UE. Additionally, clarifications were provided for ePDG handling of 5GS parameters and authentication procedures.
In Release 19, the new WLCP function introduced a standardized P-CSCF restoration mechanism for WLAN access, which includes an extended procedure where the TWAN can initiate a WLCP PDN connection modification request to transparently forward updated P-CSCF addresses to the UE. This release also specified that the TWAN must advertise its support for this WLCP PDN connection modification procedure during IMS PDN connection establishment or handover. Furthermore, enhancements were made for the ePDG to treat the UE with priority as part of this restoration framework.
- Notes on ePDG treating the UE with priority TS 29.273CR0552
Explore further
Broader topics and technologies where WLCP plays a role.
Defining Specifications
3GPP specifications that define or reference WLCP, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.380 vj10 | IMS Restoration Procedures | Rel-19 |
| TS 23.402 vj00 | EPC for Non-3GPP Access (PMIP) | Rel-19 |
| TS 23.852 vc00 | Study on GTP-based S2a for WLAN Access | Rel-12 |
| TS 24.161 vj00 | Network-Based IP Flow Mobility (NBIFOM) | Rel-19 |
| TS 24.244 vj00 | Wireless LAN Control Plane Protocol | Rel-19 |
| TS 24.302 vj00 | Access to EPC via non-3GPP networks; Stage 3 | Rel-19 |
| TS 29.273 vj10 | AAA Protocols for Non-3GPP Access in EPS & 5GS NSWO | Rel-19 |
| TS 29.826 vd10 | P-CSCF Restoration Enhancements for WLAN | Rel-13 |