WAP is an open international standard for applications that use wireless communication. Its principal application is to enable access to the Internet from a mobile phone or PDA.
A WAP browser provides all of the basic services of a computer based web browser but simplified to operate within the restrictions of a mobile phone. The Japanese i-mode system is another major competing wireless data protocol.
WAP sites are websites written in, or dynamically converted to, WML (Wireless Markup Language) and accessed via the WAP browser.
Before the introduction of WAP, service providers had extremely limited opportunities to offer interactive data services. Interactive data applications are required to support now commonplace activities such as:
Email by mobile phone
Tracking of stock market prices
Sports results
News headlines
Music downloads
Technical specifications
The bottom-most protocol in the suite is the WAP Datagram Protocol (WDP), which is an adaptation layer that makes every data network look a bit like UDP to the upper layers by providing unreliable transport of data with two 16-bit port numbers (origin and destination). WDP is considered by all the upper layers as one and the same protocol, which has several "technical realizations" on top of other "data bearers" such as SMS, USSD, etc. On native IP bearers such as GPRS, UMTS packet-radio service, or PPP on top of a circuit-switched data connection, WDP is in fact exactly UDP.
WTLS provides a public-key cryptography-based security mechanism similar to TLS. Its use is optional.
WTP provides transaction support (reliable request/response) that is adapted to the wireless world. WTP supports more effectively than TCP the problem of packet loss, which is common in 2G wireless technologies in most radio conditions, but is misinterpreted by TCP as network congestion.
Finally, WSP is best thought of on first approach as a compressed version of HTTP.
This protocol suite allows a terminal to emit requests that have an HTTP or HTTPS equivalent to a WAP gateway; the gateway translates requests into plain HTTP.
Wireless Application Environment (WAE)
In this space, application-specific markup languages are defined.
The primary language of the WAE is WML, the Wireless Markup Language, which has been designed from scratch for handheld devices with phone-specific features.
Maintenance and evolutions
The WAP Forum has consolidated (along with many other forums of the industry) into OMA (Open Mobile Alliance), which covers virtually everything in future development of wireless data services.
WAP 2.0
WAP 2.0 is a re-engineering of WAP using a cut-down version of XHTML with end-to-end HTTP (i.e., dropping the gateway and custom protocol suite used to communicate with it). A WAP gateway can be used in conjunction with WAP 2.0; however, in this scenario, it is used as a standard proxy server. The WAP gateway's role would then shift from one of translation to adding additional information to each request. This would be configured by the operator and could include telephone numbers, location, billing information, and handset information.
XHTML Mobile Profile (XHTML MP), the markup language defined in WAP 2.0, is made to work in mobile devices. It is a subset of XHTML and a superset of XHTML Basic. A version of cascading style sheets (CSS) called WAP CSS is supported by XHTML MP.
WAP Push
WAP Push, has been incorporated into the specification to allow WAP content to be pushed to the mobile handset with minimum user intervention. A WAP Push is basically a specially encoded message which includes a link to a WAP address. WAP Push is specified on top of WDP; as such, it can be delivered over any WDP-supported bearer, such as GPRS or SMS.
In most GSM networks there are a wide range of modified processors, however, GPRS activation from the network is not generally supported, so WAP Push messages have to be delivered on top of the SMS bearer. On receiving a WAP Push, a WAP 1.2 or later enabled handset will automatically give the user the option to access the WAP content. This is also known as WAP Push SI (Service Indication).
The network entity that processes WAP Pushes and delivers them over an IP or SMS Bearer is known as a Push Proxy Gateway.
A WAP browser provides all of the basic services of a computer based web browser but simplified to operate within the restrictions of a mobile phone. The Japanese i-mode system is another major competing wireless data protocol.
WAP sites are websites written in, or dynamically converted to, WML (Wireless Markup Language) and accessed via the WAP browser.
Before the introduction of WAP, service providers had extremely limited opportunities to offer interactive data services. Interactive data applications are required to support now commonplace activities such as:
Email by mobile phone
Tracking of stock market prices
Sports results
News headlines
Music downloads
Technical specifications
The bottom-most protocol in the suite is the WAP Datagram Protocol (WDP), which is an adaptation layer that makes every data network look a bit like UDP to the upper layers by providing unreliable transport of data with two 16-bit port numbers (origin and destination). WDP is considered by all the upper layers as one and the same protocol, which has several "technical realizations" on top of other "data bearers" such as SMS, USSD, etc. On native IP bearers such as GPRS, UMTS packet-radio service, or PPP on top of a circuit-switched data connection, WDP is in fact exactly UDP.
WTLS provides a public-key cryptography-based security mechanism similar to TLS. Its use is optional.
WTP provides transaction support (reliable request/response) that is adapted to the wireless world. WTP supports more effectively than TCP the problem of packet loss, which is common in 2G wireless technologies in most radio conditions, but is misinterpreted by TCP as network congestion.
Finally, WSP is best thought of on first approach as a compressed version of HTTP.
This protocol suite allows a terminal to emit requests that have an HTTP or HTTPS equivalent to a WAP gateway; the gateway translates requests into plain HTTP.
Wireless Application Environment (WAE)
In this space, application-specific markup languages are defined.
The primary language of the WAE is WML, the Wireless Markup Language, which has been designed from scratch for handheld devices with phone-specific features.
Maintenance and evolutions
The WAP Forum has consolidated (along with many other forums of the industry) into OMA (Open Mobile Alliance), which covers virtually everything in future development of wireless data services.
WAP 2.0
WAP 2.0 is a re-engineering of WAP using a cut-down version of XHTML with end-to-end HTTP (i.e., dropping the gateway and custom protocol suite used to communicate with it). A WAP gateway can be used in conjunction with WAP 2.0; however, in this scenario, it is used as a standard proxy server. The WAP gateway's role would then shift from one of translation to adding additional information to each request. This would be configured by the operator and could include telephone numbers, location, billing information, and handset information.
XHTML Mobile Profile (XHTML MP), the markup language defined in WAP 2.0, is made to work in mobile devices. It is a subset of XHTML and a superset of XHTML Basic. A version of cascading style sheets (CSS) called WAP CSS is supported by XHTML MP.
WAP Push
WAP Push, has been incorporated into the specification to allow WAP content to be pushed to the mobile handset with minimum user intervention. A WAP Push is basically a specially encoded message which includes a link to a WAP address. WAP Push is specified on top of WDP; as such, it can be delivered over any WDP-supported bearer, such as GPRS or SMS.
In most GSM networks there are a wide range of modified processors, however, GPRS activation from the network is not generally supported, so WAP Push messages have to be delivered on top of the SMS bearer. On receiving a WAP Push, a WAP 1.2 or later enabled handset will automatically give the user the option to access the WAP content. This is also known as WAP Push SI (Service Indication).
The network entity that processes WAP Pushes and delivers them over an IP or SMS Bearer is known as a Push Proxy Gateway.
