Thursday, June 26, 2008

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.



PURPOSE OF WAP
To enable easy, fast delivery of relevant information and services to mobile users.


THE DEVICES WHICH WILL USE WAP
Handheld digital wireless devices such as mobile phones, pagers, two-way radios, smartphones, and communicators -- from low-end to high-end.


With minimal risk and investment, WAP enables operators to decrease churn, cut costs, and increase revenues by improving existing, value-added services and offering exciting new informational services.


Why are equipment manufacturers interested in WAP?

Being a global open specification suite, WAP has generated the critical mass for manufacturers. This has opened up new product and marketing opportunities in the wireless industry and provides new revenue to participating companies.



How does Bluetooth relate to WAP?

Bluetooth is a local area low power radio link between devices. Many of the usage scenarios for Bluetooth will also involve one of the devices communicating over the air using WAP. While many Bluetooth members are also WAP members, and it is expected that many future handheld wireless devices will deploy both Bluetooth and WAP technology, the two technologies fundamentally address different problems.





WAP IN THE FUTURE
Will WAP comply with Third Generation wireless standards?

Yes, WAP has been designed to be as independent as possible from the underlying network technology.


Is WAP necessary with higher bandwidth 3G networks?

Even as bandwidths increase, the cost of that bandwidth does not fall to zero. These costs result from higher power usage in the terminals, higher costs in the radio sections, greater use of RF spectrum, and increased network loading. In addition, the original constraints WAP was designed for -- intermittent coverage, small screens, low power consumption, wide scalability over bearers and devices, and one-handed operation -- are still valid in 3G networks. Finally, we can expect the bandwidth required by application users to steadily increase. Therefore, there is still a need to optimize the device and network resources for wireless environments. We can expect WAP to optimize support for multimedia applications that continue to be relevant. If WAP is very successful in mass-markets on 2.5G networks, 3G networks may be needed purely for capacity relief.

No comments: