What Is Wireless Application Protocol?

Wireless Application Protocol (WAP) is a technical specification suite developed in the late 1990s to enable mobile handsets to access internet services over low-bandwidth, high-latency cellular networks. WAP defined a layered protocol stack that adapted the web's HTTP and HTML infrastructure to the severe constraints of second-generation cellular connections, where bandwidth was typically measured in kilobits per second and round-trip latency could exceed several seconds. The protocol was developed collaboratively by Ericsson, Motorola, Nokia, and Unwired Planet, who founded the WAP Forum in 1998 to formalize and extend the specifications. WAP represented the first industry-wide attempt to standardize mobile internet access and influenced the design of later mobile middleware, even as the arrival of broadband cellular networks eventually rendered the protocol obsolete.

The WAP architecture drew from existing internet standards but replaced components unsuited to mobile constraints. TCP was replaced by the Wireless Transaction Protocol (WTP), HTTP was replaced by the Wireless Session Protocol (WSP), and HTML was replaced by a compact markup language called WML. This substitution approach allowed WAP gateways, operated by carriers, to act as translating proxies between the conventional internet and the mobile network, converting standard web content and reassembling WAP sessions at the network boundary.

Protocol Stack Architecture

The WAP protocol stack comprises several layers designed to operate over heterogeneous wireless bearers. At the base, the Wireless Datagram Protocol (WDP) provides transport services analogous to UDP, adapting to the specific bearer network, whether GSM SMS, circuit-switched data, or packet-data services. Above WDP, the Wireless Transport Layer Security (WTLS) protocol provides optional encryption and authentication. The Wireless Transaction Protocol (WTP) handles request-response transactions with acknowledgment and retransmission optimized for lossy mobile channels. At the session layer, WSP offers both connection-oriented and connectionless communication modes. The Wireshark Wiki documentation of the WAP protocol family describes how these layers interact and identifies the common port numbers and encoding schemes used by WAP 1.x and WAP 2.0 devices.

WML and Content Delivery

WAP content was authored in the Wireless Markup Language (WML), derived from XML and structured around the concept of cards and decks. A deck was the unit of transfer, equivalent to an HTML page, and contained one or more cards, each representing a screen-sized unit of content. WML's compact binary encoding, transmitted as WBXML, reduced the byte overhead of markup to minimize transmission time. WAP Script, analogous to JavaScript, allowed limited client-side logic without a round-trip to the server. WAP gateways performed content transcoding, translating conventional web pages into WML where possible. The IGI Global dictionary definition of Wireless Application Protocol situates WAP within the broader context of early mobile computing architectures.

WAP 2.0 and Transition to Mobile Web

WAP 2.0, released in 2002, represented a significant architectural shift. Rather than a parallel protocol stack, WAP 2.0 adopted standard internet protocols, including TCP, HTTP, and XHTML Mobile Profile (XHTML-MP), eliminating the need for a WAP gateway as a translating intermediary. This moved the system much closer to the standard web browser model. The merger of the WAP Forum into the Open Mobile Alliance (OMA) in 2002 continued the standardization work under a broader organizational umbrella, but the arrival of 3G networks, full HTML browsers, and eventually smartphones running Safari and Chrome made WAP's adaptations unnecessary. The RF Page overview of Wireless Application Protocol traces the protocol's technical evolution and the market conditions that eventually displaced it.

Applications

Wireless Application Protocol found use in several areas of early mobile computing, including:

• Mobile banking and account balance inquiry over 2G cellular networks
• News, weather, and sports content delivery to mobile subscribers
• Carrier portals for ringtone and wallpaper downloads
• Mobile email access on feature phones
• Location-based services and mapping on early WAP-capable handsets