TECHNICAL SEMINAR

REPORT
ON
WIRELESS APPLICATION
PROTOCOL
A technical seminar report submitted in
partial fulfillment of the requirement for
the degree of the bachelor of engineering
under BPUT
SUBMITTED BY
VIJAY KUMAR
Regd no: 0701288308

DEPARTMENT OF
ELECTRONICS & COMMUNICATION ENGINEERING

NM INSTIUTE OF ENGINEERING &

TECHNOLOGY
 ABSTRACT

In the first decade of the 21st century, most people will access the Internet from wireless
handheld devices like personal digital assistants and mobile cellular telephones. Decisions
made today about the protocols that form the technical basis of wireless Internet access
markets are as important as the decisions made about the design of the first Internet
protocols in the 1960s.

This paper takes a closer look at the Wireless Application Protocol (WAP), which is
emerging as the dominant standard in the wireless data transmission protocols market
segment. A policy analysis of WAP reveals that its network architecture inherently results
in tight vertical integration of content with conduit. WAP limits end-user choice of access
to Internet-based content and value-added services. This vertical integration and
consumer choice limitations caused by WAP will become important policy concerns in
the Internet and telecommunications convergence space.

By: VIJAY KUMAR

Re
gd no: 0701288308
Branch: ECE
.
 ACKNOWLEDGEMENT

I am heartily thankful to the authority of my college and Electronics & Communication

Engineering Department for permitting me to undergo this Useful & interesting seminar
on the topic of “Wireless Application Protocol”. This topic mainly deals with the effects
of technology in each and every individual’s life.

I am graceful to H.O.D L. N. Sarangi, seminar guide S.K Biswal & all faculty members
of Electronics & communication who had given valuable guidance throughout the study
of this topic.

Vijay kumar
Regd.No:-0701288308
Branch:- ECE
B.Tech, 7th SEM
 CONTENTS

1. INTRODUCTION 1
2. BACKGROUND 2
3. BASIC PRINCIPLE OF WAP 4
4. WHY TO CHOOSE WAP 5
5. DEFINITION AND ABBRIVIATIONS 6
6. ARCHITECTURE OVERVIEW 8
6.1 Fig. World Wide Web Programming Model
6.2 Fig. WAP Programming Model
7. COMPONENTS OF WAP ARCHITECTURE 10
7.1 Fig. WAP Architecture
1. WIRELESS APPLICATION ENVIRONMENT
2. WIRELESS SESSION PROTOCOL
3. WIRELESS TRANSACTION PROTOCOL
4. WIRELESS TRNSPORT LAYER SECURITY
5. WIRELESS DATAGRAM PROTOCOL
6. BEARERS
8. EXAMPLE OF WAP NETWORK 14
8.1 Fig. Example of WAP Network
9. WORKING OF WAP 15
9.1 Fig. WAP enabled devices
10. WAP MECHANISM 16
10.1 Fig. WAP Architecture
11. COMPETITORS OF WAP 18
12. FUTURE OF WAP 19
13. CONCLUSION 20
14. REFERENCES 21
 INTRODUCTION

Wireless Application Protocol –

Introduction
Wireless application protocol (WAP) is an application environment and set of
communication protocols for wireless devices designed to enable manufacturer-, vendor-,
and technology-independent access to the Internet and advanced telephony services.WAP
bridges the gap between the mobile world and the Internet as well as corporate Intranets
and offers the ability to deliver an unlimited range of mobile value-added services to
Subscribers independent of their network, bearer, and terminal. Mobile subscribers can
access the same wealth of information from a pocket-sized device as they can from the
desktop.

For end-users WAP allows easy, secure access to relevant Internet / Intranet information
and other services through mobile phones, pagers, or other wireless devices.

WAP is a global standard and is not controlled by any single company. Ericsson, Nokia,
Motorola, and Unwired Planet founded the WAP Forum in the summer of 1997 with the
initial purpose of defining an industry-wide specification for developing applications over
wireless communications networks. The WAP specifications define a set of protocols in
application, session, transaction, security, and transport layers, which enable operators,
manufacturers, and applications providers to meet the challenges in advanced wireless
service differentiation and fast/flexible service creation. WAP also defines a wireless
application environment (WAE) aimed at enabling operators, manufacturers, and content
developers to develop advanced differentiating services and applications including a
microbrowser, scripting facilities, e-mail, World Wide Web (WWW)–to-mobile-handset
messaging, and mobile-to-telefax access.

The WAP specifications continue to be developed by contributing members, who,

through interoperability testing, have brought WAP into the limelight of the mobile data
marketplace with fully functional WAP–enabled devices
 BACKGROUND

BACKGROUND

WAP is positioned at the convergence of two rapidly evolving network technologies,

wireless data and the Internet. Both the wireless data market and the Internet are growing
very quickly and are continuously reaching new customers. The explosive growth of the
Internet has fuelled the creation of new and exciting information services. Most of the
technology developed for the Internet has been designed for desktop and larger computers
and medium to high bandwidth, generally reliable data networks. Mass-market, hand-held
wireless devices present a more constrained computing environment compared to desktop
computers. Because of fundamental limitations of power and form-factor, mass-market
handheld devices tend to have:
• Less powerful CPUs,
• Less memory (ROM and RAM),
• Restricted power consumption,
• Smaller displays, and
• Different input devices (eg, a phone keypad).
Similarly, wireless data networks present a more constrained communication environment
compared to wired networks. Because of fundamental limitations of power, available
spectrum, and mobility, wireless data networks tend to have:
• Less bandwidth,
• More latency,
• Less connection stability, and
• Less predictable availability.
Mobile networks are growing in complexity and the cost of all aspects for provisioning of
more value added services is increasing. In order to meet the requirements of mobile
network operators, solutions must be:
• Interoperable – terminals from different manufacturers communicate with services in
the mobile network; BACKGROUND
• Scaleable – mobile network operators are able to scale services to customer needs;
• Efficient – provides quality of service suited to the behavior and characteristics of the
mobile network;
• Reliable – provides a consistent and predictable platform for deploying services; and
• Secure – enables services to be extended over potentially unprotected mobile networks
while still preserving the integrity of user data; protects the devices and services from
security problems such as denial of service.
Many of the current mobile networks include advanced services that can be offered to
end-users. Mobile network operators strive to provide advanced services in a useable and
attractive way in order to promote increased usage of the mobile network services and to
decrease the turnover rate of subscribers. Standard features, like call control, can be
enhanced by using WAP technology to provide customized user interfaces.
For example, services such as call forwarding may provide a user interface that prompts
the user to make a choice between accepting a call, forwarding to another person,
forwarding it to voice mail, etc. The WAP specifications address mobile network
characteristics and operator needs by adapting existing network technology to the special
requirements of mass-market, hand-held wireless data devices and by introducing new
technology where appropriate.
 THE BASIC PRINCIPLE OF WAP:

THE BASIC PRINCIPLE OF WAP:

A complete wireless Internet solution must use:

Existing standards: WAP runs in all networks including IP networks and with W3C on
HTTP NG.

Provide air interface independence: This principle allows the largest number of service
providers, software developers and handset manufacturers to benefit from one unified
specification. Service providers can implement a common solution across their own
disparate networks so that every subscriber has the best possible user experience on each
network.

Provide device independence: Device independence offers similar benefits to bearer

independence. applications developed for one standard can operate on a wide variety of
devices that implement the specification; network operators gain a consistent user
interface for their services across multiple vendors' handsets; application developers do
not have to write separate versions of their code for different devices; and service
providers can choose any standard compliant device that meets their own
unique market requirements.
 WHY TO CHOOSE WAP?

WHY TO CHOOSE WAP?

In the past, wireless Internet access has been limited by the capabilities of handheld devices and
wireless networks. WAP utilizes Internet standards such as XML, user datagram protocol (UDP),
and IP. Many of the protocols are based on Internet standards such as hypertext transfer protocol
(HTTP) and TLS but have been optimized for the unique constraints of the wireless environment:
low bandwidth, high latency, and less connection stability. Internet standards such as hypertext
markup language (HTML), HTTP, TLS and transmission control protocol (TCP) are inefficient
over mobile networks, requiring large amounts of mainly text-based data to be sent. Standard
HTML content cannot be effectively displayed on the small-size screens of pocketsized mobile
phones and pagers. WAP utilizes binary transmission for greater compression of data and is
optimized for long latency and low bandwidth. WAP sessions cope with intermittent coverage and
can operate over a wide variety of wireless transports.

WML and wireless markup language script (WML Script) are used to produce WAP content.
They make optimum use of small displays, and navigation may be performed with one hand.
WAP content is scalable from a two-line text display on a basic device to a full graphic screen on
the latest smart phones and communicators. The lightweight WAP protocol stack is designed to
minimize the required bandwidth and maximize the number of wireless network types that can
deliver WAP content. Multiple networks will be targeted, with the additional aim of targeting
multiple networks. These include global system for mobile, communications (GSM) 900, 1,800,
and 1,900 MHz; interim standard (IS)–136; digital European cordless communication (DECT);
time-division multiple access (TDMA), personal communications service (PCS), FLEX, and code
division multiple access (CDMA). All network technologies and bearers will also be supported,
including short message service (SMS), USSD, circuit-switched cellular data (CSD), cellular
digital packet data (CDPD), and GPRS. As WAP is based on a scalable layered architecture, each
layer can develop independently of the others. This makes it possible to introduce new bearers or
to use new transport protocols without major changes in the other layers.

DEFINITIONS AND ABBREVIATIONS

DEFINITIONS AND ABBREVIATIONS

Author – an author is a person or program that writes or generates WML, WMLScript or

other content.
Client – a device (or application) that initiates a request for a connection with a server.
Content – subject matter (data) stored or generated at an origin server. Content is
typically displayed or interpreted by a user agent in response to a user request.
Content Encoding – when used as a verb, content encoding indicates the act of
converting content from one format to another. Typically the resulting format requires
less physical space than the original is easier to process or store and/or is encrypted.
When used as a noun, content encoding specifies a particular format or encoding
Standard or process.
Content Format – actual representation of content.
Device – a network entity that is capable of sending and receiving packets of information
and has a unique device Address. A device can act as both a client and a server within a
given context or across multiple contexts. For example, a device can service a number of
clients (as a server) while being a client to another server.
JavaScript – a de facto standard language that can be used to add dynamic behavior to
HTML documents. JavaScript is one of the originating technologies of ECMAScript.
Man-Machine Interface – a synonym for user interface.
Origin Server – the server on which a given resource resides or is to be created. Often
referred to as a web server or an HTTP server.
Resource – a network data object or service that can be identified by a URL. Resources
may be available in multiple representations (eg, multiple languages, data formats, size
and resolutions) or vary in other ways.
Server – a device (or application) that passively waits for connection requests from one
or more clients. A server may accept or reject a connection request from a client.

DEFINITIONS AND ABBREVIATIONS

Terminal – a device providing the user with user agent capabilities, including the ability
to request and receive information. Also called a mobile terminal or mobile station.
User – a user is a person who interacts with a user agent to view, hear, or otherwise use a
resource.
User Agent – a user agent is any software or device that interprets WML, WMLScript,
WTAI or other resources.This may include textual browsers, voice browsers, search
engines, etc.
WMLScript – a scripting language used to program the mobile device. WMLScript is an
extended subset of the JavaScript scripting language.

Abbreviations:-

For the purposes of this specification, the following abbreviations apply.

HTML HyperText Markup Language
HTTP HyperText Transfer Protocol
PDA Personal Digital Assistant
PICS Protocol Implementation Conformance Statement
RFC Request For Comments
SSL Secure Sockets Layer
TLS Transport Layer Security
URL Uniform Resource Locator [RFC1738]
W3C World Wide Web Consortium
WAE Wireless Application Environment [WAE]
WAP Wireless Application Protocol [WAP]
WDP Wireless Datagram Protocol [WDP]
WML Wireless Markup Language [WML]
WSP Wireless Session Protocol [WSP]
WTA Wireless Telephony Application [WTA]
WTLS Wireless Transport Layer Security [WTLS]
WTP Wireless Transaction Protocol [WTP]
WWW World-Wide Web ARCHITECTURE OVERVIEW

ARCHITECTURE OVERVIEW

The World-Wide Web Model

The Internet World-Wide Web (WWW) architecture provides a very flexible and
powerful programming model (Figure 1). Applications and content are presented in
standard data formats, and are browsed by applications known as web browsers. The web
browser is a networked application, i.e., it sends requests for named data objects to a
network server and the network server responds with the data encoded using the standard
formats.

The WWW protocols define three classes of servers:

• Origin server – The server on which a given resource (content) resides or is to be
created.
• Proxy – An intermediary program that acts as both a server and a client for the purpose
of making requests on behalf of other clients. The proxy typically resides between clients
and servers that have no means of direct communication, e.g. across a firewall.
• Gateway – A server which acts as an intermediary for some other server. it receives
requests as if it were the origin server for the requested resource. The requesting client
ARCHITECTURE OVERVIEW
may not be aware that it is communicating with a gateway.

The WAP Model

The WAP programming model (Figure 2) is similar to the WWW programming model.
This provides several benefits to the application developer community, including a
familiar programming model, a proven architecture, and the ability to leverage existing
tools (e.g., Web servers, XML tools, etc.). Optimizations and extensions have been made
in order to match the characteristics of the wireless environment. Wherever possible,
existing standards have been adopted or have been used as the starting point for the WAP
technology.

WAP content and applications are specified in a set of well-known content formats based
on the familiar WWW content formats. A micro browser in the wireless terminal co-
ordinates the users interface and are analogous to a standard web browser. The WAP
content types and protocols have been optimized for mass market, hand-held wireless
devices. WAP utilizes proxy technology to connect between the wireless domain and the
WWW. The WAP proxy typically is comprised of the following functionality:
• Protocol Gateway – The protocol gateway translates requests from the WAP protocol
stack (WSP, WTP, WTLS, and WDP) to the WWW protocol stack (HTTP and TCP/IP).
• Content Encoders and Decoders – The content encoders translate WAP content into
compact encoded formats to reduce the size of data over the network.
COMPONENTS OF THE WAP ARCHITECTURE

COMPONENTS OF THE WAP ARCHITECTURE

The WAP architecture provides a scaleable and extensible environment for application
development for mobile communication devices. This is achieved through a layered
design of the entire protocol stack (Figure 4). Each of the layers of the architecture is
accessible by the layers above, as well as by other services and applications.

The WAP layered architecture enables other services and applications to utilize the
features of the WAP stack through a set of well-defined interfaces. External applications
may access the session, transaction, security and transport layers directly. The following
sections provide a description of the various elements of the protocol stack architecture.
 COMPONENTS OF THE WAP ARCHITECTURE

Wireless Application Environment (WAE)

The Wireless Application Environment (WAE) is a general-purpose application

environment based on a combination of World Wide Web (WWW) and Mobile
Telephony technologies. The primary objective of the WAE effort is to establish an
interoperable environment that will allow operators and service providers to build
applications and services that can reach a wide variety of different wireless platforms in
an efficient and useful manner. WAE includes a micro-browser environment containing
the following functionality:
• Wireless Markup Language (WML) – a lightweight markup language, similar to
HTML, but optimized for use in hand-held mobile terminals;
• WMLScript – a lightweight scripting language, similar to JavaScript™;
• Wireless Telephony Application (WTA, WTAI) – telephony services and programming
interfaces
• Content Formats – a set of well-defined data formats, including images, phone book
records and calendar information.

Wireless Session Protocol (WSP)

The Wireless Session Protocol (WSP) provides the application layer of WAP with a
consistent interface for two session services. The first is a connection-oriented service that
operates above the transaction layer protocol WTP.The second is a connectionless service
that operates above a secure or non-secure datagram service (WDP).The Wireless Session
Protocols currently consist of services suited for browsing applications (WSP/B).
WSP/Provides the following functionality:
• HTTP/1.1 functionality and semantics in a compact over-the-air encoding,
• Long-lived session state,
• Session suspend and resume with session migration,
• A common facility for reliable and unreliable data push, and
• Protocol feature negotiation. COMPONENTS OF THE WAP ARCHITECTURE

Wireless Transaction Protocol (WTP)

The Wireless Transaction Protocol (WTP) runs on top of a datagram service and provides
as a light-weight transaction-oriented protocol that is suitable for implementation in
“thin” clients (mobile stations). WTP operates efficiently over secure or non-secure
wireless datagram networks and provides the following features:
• Three classes of transaction service:
• Unreliable one-way requests,
• Reliable one-way requests, and
• Reliable two-way request-reply transactions;
• Optional user-to-user reliability - WTP user triggers the confirmation of each received
message.

Wireless Transport Layer Security (WTLS)

WTLS is a security protocol based upon the industry-standard Transport Layer Security
(TLS) protocol, formerly known as Secure Sockets Layer (SSL). WTLS is intended for
use with the WAP transport protocols and has been optimised for use over narrow-band
communication channels. WTLS provides the following features:
• Data integrity – WTLS contains facilities to ensure that data sent between the terminal
and an application server is unchanged and uncorrupted.
• Privacy – WTLS contains facilities to ensure that data transmitted between the terminal
and an application server is private and cannot be understood by any intermediate parties
that may have intercepted the data stream.
• Authentication – WTLS contains facilities to establish the authenticity of the terminal
and application server.
• Denial-of-service protection – WTLS contains facilities for detecting and rejecting data
that is replayed or not successfully verified. WTLS makes many typical denial-of-service
attacks harder to accomplish and protects the upper protocol layers.
COMPONENTS OF THE WAP ARCHITECTURE
WTLS may also be used for secure communication between terminals, eg, for
authentication of electronic business card exchange. Applications are able to selectively
enable or disable WTLS features depending on their security requirements and the
characteristics of the underlying network (eg, privacy may be disabled on networks
already providing this service at a lower layer).

Wireless Datagram Protocol (WDP)

The Transport layer protocol in the WAP architecture is referred to as the Wireless
Datagram Protocol (WDP). The WDP layer operates above the data capable bearer
services supported by the various network types. As a general transport service, WDP
offers a consistent service to the upper layer protocols of WAP and communicate
transparently over one of the available bearer services. Since the WDP protocols provide
a common interface to the upper layer protocols the Security, Session and Application
layers are able to function independently of the underlying wireless network. This is
accomplished by adapting the transport layer to specific features of the underlying bearer.
By keeping the transport layer interface and the basic features consistent, global
interoperability can be achieved using mediating gateways.

BEARERS

The WAP protocols are designed to operate over a variety of different bearer services,
including short message, circuit-switched data, and packet data. The bearers offer
differing levels of quality of service with respect to throughput, error rate, and delays. The
WAP protocols are designed to compensate for or tolerate this varying level of service.
Since the WDP layer provides the convergence between the bearer service and the rest of
the WAP stack, the WDP specification [WDP] lists the bearers that are supported and the
techniques used to allow WAP protocols to run over each bearer. The list of supported
bearers will change over time with new bearers being added as the wireless market
evolves.
EXAMPLE OF WAP NETWORK

EXAMPLE OF WAP NETWORK

The following is for illustrative purposes only. An example WAP network is shown in
Figure 3.

In the example, the WAP client communicates with two servers in the wireless network.
The WAP proxy translates WAP requests to WWW requests thereby allowing the WAP
client to submit requests to the web server.
The proxy also encodes the responses from the web server into the compact binary format
understood by the client. If the web server provides WAP content (e.g., WML), the WAP
proxy retrieves it directly from the web server. However, if the web server provides
WWW content (such as HTML), a filter is used to translate the WWW content into WAP
content. For example, the HTML filter would translate HTML into WML. The Wireless
Telephony Application (WTA) server is an example origin or gateway server that
responds to requests from the WAP client directly. The WTA server is used to provide
WAP access to features of the wireless network provider’s telecommunications
infrastructure.
WORKING OF WAP

WORKING OF WAP

WAP defines an application environment (WAE) aimed at enabling operators,

manufacturers, and content developers to develop advanced differentiating services and
applications including a micro browser, scripting facilities, e-mail, World Wide Web
(WWW) – to mobile handset messaging, and mobile access to fax. The WAP
specifications continue to be developed by contributing members, who, through
interoperability testing, have brought WAP into the limelight of the mobile data
marketplace with fully functional WAP–enabled devices (see
Fig).

WAP MECHANISM

WAP MECHANISM

The WAP programming model is similar to the WWW programming model. This
provides several benefits to the application developer community, including a familiar
programming model, a proven architecture, and the ability to leverage existing tools (e.g.,
Web servers, XML tools, etc.). Optimizations and extensions have been made in order to
match the characteristics of the wireless environment. Wherever possible, existing
Standards have been adopted or have been used as the starting point for the WAP
technology. The overall mechanism of WAP is shown in the below diagram.
WAP content and applications are specified in a set of well-known content formats based
on the familiar WWW content formats. Content is transported using a set of standard
communication protocols based on the WWW communication protocols. A micro
browser in the wireless terminal co-ordinates the user interface and WAP
is analogous to a
MECHANISM
standard web browser.
WAP defines a set of standard components that enable communication between mobile
terminals and network servers, including:

1. Standard naming model – WWW-standard URLs are used to identify WAP content on
the origin servers. WWW-standard URLs are used to identify local resources in a device,
e.g. Call Control functions.

2. Content typing – All WAP content is given a specific type consistent with WWW
typing. This allows WAP user agents to correctly process the content based on its type.

3. Standard content formats – WAP content formats are based on WWW technology and
Include display markup, calendar information, electronic business card objects, images
and scripting language.

4. Standard communication protocols – WAP communication protocols enable the

communication of browser requests from the mobile terminal to the network web server.
The WAP content types and protocols have been optimized for mass market, and hand-
held wireless devices. WAP utilizes proxy technology to connect between the wireless
domain and the WWW. The WAP proxy typically is comprised of the following
functionality:

5. Protocol Gateway – The protocol gateway translates requests from the WAP protocol
stack (WSP, WTP, WTLS, and WDP) to the WWW protocol stack (HTTP and TCP/IP).

6. Content Encoders and Decoders – The content encoders translate WAP content into
Compact encoded formats to reduce the size of data over the network. This infrastructure
ensures that mobile terminal users can browse a wide variety of WAP content and
applications, and that the application author is able to build content services and
applications that run on a large base of mobile terminals. The WAP proxy allows content
and applications to be hosted on standard WWW servers and to be developed using
proven WWW technologies such as CGI scripting.
COMPETITORS OF WAP

COMPETITORS OF WAP

Competition for WAP protocols could come from a number of sources:

Subscriber Identity Module (SIM) toolkit—the use of SIMs or smart cards in wireless
devices is already widespread and used in some of the service sectors.
Windows CE—This is a multitasking, multithreaded operating system from Microsoft
designed for including or embedding mobile and other space-constrained devices.
JavaPhone™—Sun Microsystems is developing Personal Java™ and a JavaPhone™
API, which is embedded in a Java™ virtual machine on the handset. NEPs will be able to
build cellular phones that can download extra features and functions over the Internet;
thus, customers will no longer be required to buy a new phone to take advantage of
improved features.
The advantages that WAP can offer over these other methods are the following:
__ Open standard, vendor independent.
__ Network-standard independent.
__ Transport mechanism–optimized for wireless data bearers.
__ Application downloaded from the server, enabling fast service creation and
introduction, as opposed to embedded software.
 THE FUTURE OF WAP

THE FUTURE OF WAP

The tremendous surge of interest and development in the area of wireless data in
recent times has caused worldwide operators, infrastructure manufacturers, terminal
manufacturers, and content developers to collaborate on an unprecedented scale. This
collaboration is happening in an area notorious for the diversity of standards and
protocols. The collaborative efforts of the WAP Forum have devised and continue to
develop a set of protocols that provide a common environment for the development of
advanced telephony services and Internet access for the wireless market. If the WAP
protocols were to be as successful as transmission control protocol (TCP)/Internet
protocol (IP), the boom in mobile communications would be phenomenal. Indeed, the
WAP browser should do for mobile Internet what Netscape did for the Internet.

As mentioned earlier, industry players from content developers to operators can

explore the vast opportunity that WAP presents. As a fixed-line technology, the Internet
has proved highly successful in reaching the homes of millions worldwide. However,
mobile users until now have been forced to accept relatively basic levels of functionality,
over and above voice communication are beginning to demand the industry to move from
a fixed to a mobile environment, carrying the functionality of a fixed environment with it.

Initially, services are expected to run over the well-established SMS bearer, which
will dictate the nature and speed of early applications. Indeed, GSM currently does not
offer the data rates that would allow mobile multimedia and Web browsing. With the
advent of general packet radio services (GPRS) aiming at increasing the data rate to 115
KBPS along with other emerging high-bandwidth bearers, the reality of access speeds
equivalent or higher to that of a fixed-line scenario becomes evermore believable. GPRS
is seen by many as the perfect partner for WAP, with its distinct time slots serving to
manage data packets in a way that prevents users from being penalized for holding
standard circuit switched connections.
 CONCLUSION

CONCLUSION

The WAP specification is a truly open standard that enables public content,
Corporate intranet and operator-specific solutions to reach wireless subscribers
Today. The WAP specification leverages and extends existing Internet standards,
Enabling application developers to tailor their content to the special needs of
wireless users. Handset manufacturers can enhance their product lines at
minimal cost with new usability benefits. Wireless service providers can
establish a new and powerful way to interact with their subscribers through a
vital point of control in their own network. The ultimate beneficiaries are
wireless subscribers who can be more productive than ever before.
 REFERENCES

REFERENCES

1. “WAP White Paper.” AU-System Radio White Paper (1999): n. page.

World Wide Web. April, 2000.
Available: www.wapguide.com/wapguide/Auwap.pdf.

2. “Wireless Application Protocol draws criticism.”

Computing News Story (Technology Section) on CNN Interactive (2000): n. page.
World Wide Web. April, 2000.
Available: http://www.cnn.com/2000/TECH/computing/03/14/wap.critics.idg/index.html

3. “WAP White Paper: Wireless Application Protocol.” Wireless Internet Today (1999):
page. World Wide Web. April, 2000.
Available: www.wapforum.com/what/WAP_white_pages.pdf.

4. Shirky, Clay. “WAP is in the Air.” The Daily Feed from FEED Magazine (2000): n.
page. World Wide Web. April, 2000.
Available: www.feedmag.com/daily/dy020300.html.

5. Wireless application protocol: writing applications for the mobile internet, Pearson
education.
By-Sandeep Singhal, Thomas Bridgman Daniel Mauney, David Bevis