WAP gateway/proxies convert mobile content retrieved over HTTP into a compressed format that is then transferred over a wireless network to a mobile device – this reduces the overhead required to transfer content over a bandwidth limited mobile network. In the same way, other technologies such as MMS utilize this feature to efficiently transfer content to mobile subscribers.

The mobile browser within a mobile device sends a request to the WAP gateway through the mobile network, typically using a packet switched bearer; for example GPRS, WCDMA or CDMA. The gateway then extracts the page request and uses the HTTP protocol to send a standard HTTP request towards the web server that hosts the content. The web server sends a response back to the gateway, where it is converted to WAP format (binary coded). The browsing content is then sent back through the mobile network and is displayed on the mobile device.

The objective of WAP 2.0 is to merge wireless and internet services as bandwidth increases and devices become more powerful. WAP 2.0 uses W-HTTP and W-TCP to transport content to the handset, and it defines a mobile extension of XHTML to make WAP pages more versatile and easier to create. WAP 2.0 aims to provide richer content to more users.

WAP gateways/proxies not only act as a point of conversion of content for transfer to mobile devices, but they also add a lot of features and capabilities for application developers. This node is one of many components, services enablers, of the service layer, a set of nodes residing in an operator network that can help add functionality to any mobile application.

WAP is an important part of the Open Mobile Alliance (OMA). OMA is responsible for the development of the WAP specifications.

WAP is an essential component in the Multimedia Messaging solution. For example, Ericsson WAP gateway MIEP can be used to send out MMS notifications.

The WAP gateway translates the binary WAP protocol to Hypertext Transfer Protocol (HTTP) for a HTTP server. This allows the mobile device to access a web container on the internet, because a web container only accepts HTTP requests. However, WAP 2.0-enabled mobile devices, for example smart phones, can communicate with web containers directly using the HTTP protocol. WAP 2.0 thus enhances the security by enabling end-to-end SSL connections using the Java EE web container security model.