Wireless Application Protocol (WAP) is the worldwide standard for providing Internet communications and advanced services on digital mobile devices, such as handheld phones, pagers, and other wireless devices. This protocol is an open, global specification that enables users of these digital devices to securely access and interact with Internet, intranet, and extranet applications and services.

Many phones and PDAs currently have multimedia capabilities that include:

• Retrieving e-mail
• Accessing data from company databases
• Executing stock trading
• Paying bills
• Making travel reservations
• Online requests for maps and driving directions
• Running other exciting applications

The WAP Forum was founded in June 1997, by Ericsson, Motorola, Nokia, and Phone.com. It has drafted a global wireless specification for all wireless networks. The forum contributed to various industry groups, such as wireless service providers, handset manufacturers, infrastructure providers, and software developers.  WAP version 2 brings together open Internet standards and mobile networking as it adds optimized support for TCP and HTTP, Extended Hypertext Markup Language (XHTML), and Transport Layer Security.

The WAP environment

wireless devices lack the traditional desktop GUI like the Web browser. Other fundamental
limitations for handheld, wireless devices include:

• Less powerful CPUs
• Less memory
• Restricted power consumption
• Smaller displays
• Different input devices (for example, phone keypad and voice input)

Wireless data networks present many communications challenges compared to wired networks. For example, the wireless communication environment is constrained because wireless links have:

• Less bandwidth
• More latency
• Less connection stability
• Less predictable availability

As a result, protocols that provide wireless applicability must be tolerant of these types of problems


Key elements of the WAP specifications


WAP defines an open standard architecture and a set of protocols to implement wireless Internet access.

• Definition of the WAP programming model
• The Extended Hypertext Markup Language Mobile Profile (XHTMLMP).
• The Wireless Markup Language (WML).
• A lightweight protocol stack 
• A framework for wireless telephony

WAP Architecture



The WAP architecture illustrated in Figure

• The WAP client (the handheld device or WAP terminal)
• The application server
  

This programming model is the Web programming model with some extensions and enhancements to match the characteristics of the wireless clients. This programming model adds two enhancements to the Web programming model:

• Push
• Wireless Telephony Support (WTA)

Feature and performance-enhancing proxies


The WAP model recommends the use of proxies to optimize the connection between the wireless clients and the Web

A variety of functions are then provided by the WAP proxy, including:


Protocol gateway

Translates requests from a wireless protocol stack (for example, the WAP 1.x stack—WSP, WTP, WTLS, and WDP) to the WWW protocols (HTTP and TCP/IP). Also can perform DNS lookups for the URLs requested by the client.

Content encoders and decoders

Translates WAP content for better utilization of the underlying link, reducing the bandwidth use by different compression techniques.

User Agent Profile Manager


Used mainly to communicate the client’s device capabilities and personal preferences to the server
applications.


Caching proxy


Caching frequently accessed resources, a caching proxy can improve network utilization




Overall Architecture

 

Wireless Application Protocol

Here's what happens when you access a Web site using a WAP-enabled device:

• You turn on the device and open the minibrowser.
• The device sends out a radio signal, searching for service.
• A connection is made with your service provider.
• You select a Web site that you wish to view.
• A request is sent to a gateway server using WAP.
• The gateway server retrieves the information via HTTP from the Web site.
• The gateway server encodes the HTTP data as WML.
• The WML-encoded data is sent to your device.
• You see the wireless Internet version of the Web page you selected.

To create wireless Internet content, a Web site creates special text-only or low-graphics versions of the site. The data is sent in HTTP form by a Web server to a WAP gateway. This system includes the WAP encoder, script compiler and protocol adapters to convert the HTTP information to WML. The gateway then sends the converted data to the WAP client on your wireless device.
What happens between the gateway and the client relies on features of different parts of the WAP protocol stack. Let's take a look at each part of the stack:

• WAE - The Wireless Application Environment holds the tools that wireless Internet content developers use. These include WML and WMLScript, which is a scripting language used in conjunction with WML. It functions much like Javascript.

• WSP - The Wireless Session Protocol determines whether a session between the device and the network will be connection-oriented or connectionless. What this is basically talking about is whether or not the device needs to talk back and forth with the network during a session. In a connection-oriented session, data is passed both ways between the device and the network; WSP then sends the packet to the Wireless Transaction Protocol layer (see below). If the session is connectionless, commonly used when information is being broadcast or streamed from the network to the device, then WSP redirects the packet to the Wireless
  Datagram Protocol layer.

• WTP - The Wireless Transaction Protocol acts like a traffic cop, keeping the data flowing in a logical and smooth manner. It also determines how to classify each transaction request: Reliable two-way Reliable one-way Unreliable one-way The WSP and WTP layers correspond to Hypertext Transfer Protocol (HTTP) in the TCP/IP protocol suite.

• WTLS - Wireless Transport Layer Security provides many of the same security features found in the Transport Layer Security (TLS) part of TCP/IP. It checks data integrity, provides encryption and performs client and server authentication.

• WDP - The Wireless Datagram Protocol works in conjunction with the network carrier layer (see below). WDP makes it easy to adapt WAP to a variety of bearers because all that needs to change is the information maintained at this level.

• Network carriers - Also called bearers, these can be any of the existing technologies that wireless providers use, as long as information is provided at the WDP level to interface WAP with the bearer.

Once the information is received by the WAP client, it is passed to the minibrowser. This is a tiny application built into the wireless device that provides the interface between the user and the wireless Internet.

Wireless(WAP) Application Development

Wireless Markup Language

WAP uses Wireless Markup Language (WML), which includes the Handheld Device Markup Language (HDML) developed by Phone.com.

WML can also trace its roots to eXtensible Markup Language (XML). A markup language is a way of adding information to your content that tells the device receiving the content what to do with it. The best known markup language is Hypertext Markup Language (HTML). Unlike HTML, WML is considered a meta language. Basically, this means that in addition to providing predefined tags, WML lets you design your own markup language components. WAP also allows the use of standard Internet protocols such as UDP, IP and XML.

There are three main reasons why wireless Internet needs the Wireless Application Protocol:

• Transfer speed
• Size and readability
• Navigation

Most cell phones and Web-enabled PDAs have data transfer rates of 14.4 Kbps or less. Compare this to a typical 56 Kbps modem, a cable modem or a DSL connection. Most Web pages today are full of graphics that would take an unbearably long time to download at 14.4 Kbps. Wireless Internet content is typically text-based in order to solve this problem.

The relatively small size of the LCD on a cell phone or PDA presents another challenge. Most Web pages are designed for a resolution of 640x480 pixels, which is fine if you are reading on a desktop or a laptop. The page simply does not fit on a wireless device's display, which might be 150x150 pixels. Also, the majority of wireless devices use monochrome screens. Pages are harder to read when font and background colors become similar shades of gray.