WAP

Presented By :Nitika Chowdhary Mtech(CSE) 1190120211 PIT, Kapurthala

1. Introduction
1.1 What is WAP? WAP stands for Wireless Application Protocol WAP is an application communication protocol WAP is used to access services and information WAP is inherited from Internet standards WAP is for handheld devices such as mobile phones

 WAP is a protocol designed for micro browsers WAP enables the creating of web applications for mobile devices.

WAP uses the mark-up language WML (not HTML)

WML is defined as an XML 1.0 application

1.2. The Wireless Application Protocol The WAP is the leading standard for information services on wireless terminals like digital mobile phones. The WAP standard is based on Internet standards (HTML, XML and TCP/IP).

1.3. History of WAP WAP is published by the WAP Forum, founded in 1997 by Ericsson, Motorola, Nokia, and Unwired Planet.

Forum members now represent over 90% of the global

handset market, as well as leading infrastructure providers, software developers and other organizations.

2.1 Web-Model

2. WAP Model

Client

Server

req. resp.

WAP: Main Features

Browser Micro browser, similar to existing web browsers Markup language Similar to HTML, adapted to mobile devices Script language Similar to Javascript, adapted to mobile devices Gateway Transition from wireless to wired world Server Wap/Origin server, similar to existing web servers Protocol layers Transport layer, security layer, session layer etc. Telephony application interface Access to telephony functions

2.1 Internet Model

The Internet model makes it possible for a

client to reach services on a large number of origin servers. Each services is addressed by a unique Uniform Resource Locator (URL).

 The content stored on the servers is of various formats, but HTML is the predominant. HTML provides the content developer with a means to

describe the appearance of a service in a flat document

structure. If more advanced features like procedural logic are needed, then scripting languages such as JavaScript or VB Script may be utilised.

Internet Model

HTML

HTTP
TLS/SSL TCP/IP

 The figure above shows how a WWW client request a resource stored on a web server. On the Internet, standard communication protocols, like HTTP and Transmission Control Protocol/Internet Protocol (TCP/IP) are used. The content available at the web server may be static or dynamic. Static content is produced once and not changed or updated very often, for example a company presentation.

 Dynamic content is needed when the information provided by the service changes more often, for example timetables, news, stock quotes and account

information. Technologies such as Active Server Pages

(ASP), Common Gateway Interface (CGI), and Servlets allow content to be generated dynamically.

2.2 WAP Model

The figure below shows the WAP

programming model. Note the similarities with the Internet model. Without the WAP Gateway/Proxy the two models would have been practically identical.

WAP I model: Translator WAP - WEB

Client encoded req.

WAE User Agent

Gateway

Server

req.
Encode & Decode

encoded resp.

resp.

cgi scripts etc.

WAP I

WEB

 WAP Gateway/Proxy is the entity that connects the wireless domain with the Internet. We should make a note that the request that is sent

from

the

wireless

client

to

the

WAP

Gateway/Proxy uses the Wireless Session Protocol (WSP). In its essence, WSP is a binary version of HTTP.

 A markup language - the Wireless Markup Language (WML) has been adapted to develop optimized WAP applications. In order to save

valuable bandwidth in the wireless network,

WML can be encoded into a compact binary format. Encoding WML is one of the tasks performed by the WAP Gateway/Proxy.

2.3 How WAP Model Works? When it comes to actual use, WAP works like this:

 The user selects an option on their mobile device that has a URL with Wireless Markup language (WML) content assigned to it. The phone sends the URL request via the phone network to a WAP gateway, using the binary encoded WAP protocol.

 The gateway translates this WAP request into a conventional HTTP request for the specified URL, and sends it on to the Internet. The appropriate Web server picks up the HTTP request. The server processes the request, just as it would any other request. If the URL refers to a static WML file, the server delivers it. If a CGI script is requested, it is processed and the content

returned as usual.

 The Web server adds the HTTP header to the WML content and returns it to the gateway. The WAP gateway compiles the WML into binary form. The gateway then sends the WML response back to the phone. The phone receives the WML via the WAP protocol. The micro-browser processes the WML and displays the content

on the screen.

3. WAP- Architecture

WAP Architecture

Client
WML

WAP Gateway
WML Encoder

Web Server
CGI Scripts etc. WML Decks with WML-Script
Source: WAP Forum

WMLScript WTAI Etc.

WSP/WTP

WMLScript Compiler Protocol Adapters

HTTP

Content

WAP Application Server

Client
WML WMLScript WTAI Etc.

WAP Application Server WML Encoder Application Logic

WML Decks with WML-Script
Source: WAP Forum

WSP/WTP

WMLScript Compiler

Protocol Adapters

Content

WAP I protocol stack

WAP WEB

Application (WAE)

Application

Session (WSP)
Transaction (WTP) Security (WTLS) Transport (WDP)
Medium: GSM, CDMA, UMTS ...

HTTP
TCP Security (TLS) IP/UDP
Medium: ...

 WAP is designed in a layered fashion so that it can be extensible,

flexible, and scalable. As a result, the WAP protocol stack is divided

into five layers. Application Layer

Wireless Application Environment (WAE). This layer is of most

interest to content developers because it contains, among other things, device specifications and the content development

programming languages, WML and WMLScript.

Session Layer Wireless Session Protocol (WSP). Unlike HTTP, WSP has been designed by the WAP Forum to provide fast

connection suspension and reconnection.

WSP-The WAP session protocol (WSP) layer provides a lightweight session layer to allow efficient exchange of data between applications.

Transaction Layer Wireless Transaction Protocol (WTP). The WTP runs on top of a datagram service such as User Datagram Protocol (UDP) and is part of the standard suite of TCP/IP protocols used to provide a simplified protocol suitable for low bandwidth wireless stations. WTP -- The WAP transaction protocol (WTP) layer provides

transaction support, adding reliability to the datagram service

provided by WDP.

 WDP -- The WAP datagram protocol (WDP) is the transport layer that sends and receives messages via any available bearer network, including SMS, USSD, CSD, CDPD and GPRS.

Security Layer Wireless Transport Layer Security (WTLS). WTLS incorporates security features that are based upon the established Transport Layer Security (TLS) protocol standard. It includes data integrity checks, privacy, service denial, and authentication services. WTLS -- Wireless transport layer security (WTLS), an optional security layer, has encryption facilities that provide the secure transport service required by many applications, such as e-commerce.

Transport layer Wireless Datagram Protocol (WDP). The WDP allows WAP to be bearer-independent by adapting

the transport layer of the underlying bearer. The WDP

presents a consistent data format to the higher layers of the WAP protocol stack, thereby offering the

advantage of bearer independence to application

developers.

 Each of these layers provides a well-defined interface to the layer. This means that the internal workings of any layer are transparent or invisible to the layers. The layered architecture allows other applications and services to utilize the features provided by the WAP-stack as well. This makes it possible to use the WAP-stack for services and

applications that currently are not specified by WAP.

The WAP protocol architecture is shown below alongside a typical Internet Protocol stack.

WSP - Wireless Session Protocol

Goals
HTTP 1.1 functionality Request/reply, content type negotiation, ... support of client/server transactions, push technology key management, authentication, Internet security services

WSP Services
provides shared state between client and server, optimizes content transfer session management (establish, release, suspend, resume) efficient capability negotiation content encoding push

WSP/B (Browsing)
HTTP/1.1 functionality - but binary encoded exchange of session headers push and pull data transfer asynchronous requests

WSP Overview
Session Management
WSP introduces sessions that can be established from a client to a server and may be long lived Sessions can also be released in an orderly manner Capabilities of suspending and resuming a session are important.

Capabilities (are defined for):

message size, client and server protocol options: Confirmed Push Facility, Push Facility, Session Suspend Facility, Acknowledgement headers maximum outstanding requests extended methods header code pages

Suspend and Resume

server knows when client can accept a push multi-bearer devices dynamic addressing allows the release of underlying bearer resources

WSP Overview
Header Encoding
compact binary encoding of headers, content type identifiers and other well-known textual or structured values reduces the data actually sent over the network

Capabilities negotiation
Clients and servers can agree upon a common level of protocol functionality during session establishment E.g. parameters to negotiate are max client SDU size, max outstanding requests, protocol options and server SDU size

Content encoding
WSP also defines the efficient binary encoding for the content it transfers Offers content typing and composite objects a

WSP/B (HTTP 1.1 and WSP)

HTTP 1.1
extensible request/reply methods extensible request/reply headers content typing composite objects asynchronous requests binary header encoding exchange of session headers confirmed and non-confirmed data push capability negotiation suspend and resume fully asynchronous requests connectionless service

WSP enhancements beyond HTTP

Why Not HTTP?

encoding not compact enough, inefficient capability negotiation no push facility

WSP Sessions
Session Context and Push
push can take advantage of session headers server knows when client can accept a push

Connection-mode
long-lived communication, benefits of the session state, reliability

Connectionless-mode
stateless applications, no session creation overhead, no reliability overhead

WSP/B over WTP

WSP/B uses 3 service classes of WTP : Class 0
Used for unconfirmed push, session resume and session management

Class 1
Used for confirmed push, method invocation, session resume and session management class 2 The following time sequence charts will give some examples

WSP/B session establishment

client S-SAP S-Connect.req (SA, CA, CH, RC) server S-SAP S-Connect.ind (SA, CA, CH, RC) S-Connect.res (SH, NC)

S-Connect.cnf (SH, NC) WTP Class 2 transaction

CH: Client Header RC: Requested Capabilities SH: Server Header NC: Negotiated Capabilities

Source: Schiller

WSP/B session suspend/resume

client S-SAP S-Suspend.req S-Suspend.ind (R) WTP Class 0 transaction server S-SAP S-Suspend.ind (R)

S-Resume.req (SA, CA)

R: Reason for disconnection

S-Resume.ind (SA, CA) S-Resume.res

S-Resume.cnf

WTP Class 2 transaction

Source: Schiller

WSP/B session termination

client S-SAP S-Disconnect.req (R) S-Disconnect.ind (R) WTP Class 0 transaction server S-SAP S-Disconnect.ind (R)

Source: Schiller

WSP/B completed transaction

client S-SAP server S-SAP S-MethodInvoke.req (CTID, M, RU) S-MethodInvoke.ind (STID, M, RU) S-MethodInvoke.res (STID) S-MethodResult.req (STID, S, RH, RB)

S-MethodInvoke.cnf (CTID) S-MethodResult.ind (CTID, S, RH, RB) S-MethodResult.res (CTID)

S-MethodResult.cnf (STID) CTID: Client Transaction ID

WTP Class 2 transaction

M: Method Invoked RU: Request URI

STID: Server Transaction ID

S: Response Status RH: Response Header RB: Response Body Source: Schiller

WSP utilization of WTP as lower layer

client S-SAP initiator TR-SAP responder TR-SAP server S-SAP

S-MethodInvoke.req TR-Invoke.req
TR-Invoke.ind S-MethodInvoke.ind TR-Invoke.res S-MethodInvoke.res S-MethodInvoke.cnf TR-Invoke.cnf

TR-Result.req S-MethodResult.req
S-MethodResult.ind S-MethodResult.res TR-Result.ind TR-Result.res TR-Result.cnf S-MethodResult.cnf

Source: Schiller

WSP/B over WTP - asynchronous, unordered requests client server

S-SAP S-MethodInvoke_1.req S-MethodInvoke_2.req S-SAP

S-MethodInvoke_2.ind
S-MethodInvoke_1.ind S-MethodInvoke_3.req S-MethodResult_1.ind S-MethodResult_3.ind S-MethodInvoke_4.req S-MethodInvoke_4.ind S-MethodResult_4.ind S-MethodResult_2.ind S-MethodResult_4.req S-MethodResult_1.req S-MethodInvoke_3.ind S-MethodResult_3.req S-MethodResult_2.req

Source: Schiller

WSP/B non-confirmed & confirmed push

client S-SAP S-Push.ind (PH, PB) server S-SAP S-Push.req (PH, PB)

WTP Class 0 transaction client S-SAP S-ConfirmedPush.ind (CPID, PH, PB) S-ConfirmedPush.res (CPID) WTP Class 1 transaction

PH: Push Header PB: Push Body SPID: Server Push ID

server CPID: Client Push ID S-SAP S-ConfirmedPush.req (SPID, PH, PB)

S-ConfirmedPush.cnf (SPID)

Source: Schiller

WSP/B as connectionless session service

S-Unit-MethodInvoke.req (SA, CA, TID, M, RU) client S-SAP server S-SAP S-Unit-MethodInvoke.ind (SA, CA, TID, M, RU) S-Unit-MethodResult.req (CA, SA, TID, S, RH, RB) S-Unit-Push.req (CA, SA, PID, PH, PB)

S-Unit-MethodResult.ind (CA, SA, TID, S, RH, RB) S-Unit-Push.ind (CA, SA, PID, PH, PB) WDP Unitdata service

Source: Schiller

WAP-Environment
The Wireless Application Environment (WAE) provides an environment that enables a wide range of applications to be used on wireless devices. The main idea behind WAE is to create a general-purpose application environment based mainly on existing technologies and philosophies of www.

"WAP - The wireless service enabler" the WAP WAE

programming model was introduced.

Addressing model A syntax suitable for naming resources stored on servers. WAP use the same addressing model as the one used on the Internet. ie: Uniform Resource Locators (URL).

Wireless Application Environment (WAE)

Goals
device and network independent application environment for low-bandwidth, wireless devices considerations of slow links, limited memory, low computing power, small display, simple user interface (compared to desktops) integrated Internet/WWW programming model high interoperability

WAE Components
Architecture Application model, Micro browser, Gateway, Server User Agents WML/WTA/Others content formats: vCard, vCalendar, Wireless Bitmap, WML, ... WML XML-Syntax, based on card stacks, variables, ... WMLScript procedural, loops, conditions, ... (similar to JavaScript) WTA telephone services, such as call control, text messages, phone book, ... (accessible from WML/WMLScript) Proxy (Method/Push)

WAE: Logical Model

Origin Servers
web server
response with content

Gateway
Method proxy
encoded response with content

Client
WTA user agent

other content server

Push proxy

push content
encoders & decoders request

encoded push content

WML user agent

encoded request

other WAE user agents

WML: Wireless Markup Language

Tag-based browsing language:
Screen management (text, images) Data input (text, selection lists, etc.) Hyperlinks & navigation support

Content (XML)

Takes into account limited display, navigation capabilities of devices XML-based language
describes only intent of interaction in an abstract manner presentation depends upon device capabilities

XSL Processor
WML Stylesheet HTML StyleSheet

Cards and Decks

document consists of many cards User interactions are split into cards Explicit navigation between cards cards are grouped to decks deck is similar to HTML page, unit of content transmission

WML Browsers

HTTP Browser

Events, variables and state mgmt

WML
The basic unit is a card. Cards are grouped together into Decks Document ~ Deck (unit of transfer) All decks must contain Document prologue XML & document type declaration <WML> element Must contain one or more cards WML File Structure
<?xml version="1.0"?> <!DOCTYPE WML PUBLIC "-//WAPFORUM//DTD WML 1.0//EN" "http://www.wapforum.org/DTD/wml.xml">

<WML> ... </WML>

WML Example
Navigation <WML> <CARD> <DO TYPE=ACCEPT> <GO URL=#eCard/> </DO Welcome! </CARD> <CARD NAME=eCard> <DO TYPE=ACCEPT> <GO URL=/submit?N=$(N)&S=$(S)/> </DO> Enter name: <INPUT KEY=N/> Choose speed: <SELECT KEY=S> <OPTION VALUE=0>Fast</OPTION> <OPTION VALUE=1>Slow</OPTION> <SELECT> </CARD> </WML>

Card

Variables

Deck

Input Elements

A Deck of Cards
<WML> <CARD> <DO TYPE="ACCEPT" LABEL="Next"> <GO URL="#card2"/> </DO> Acme Inc.<BR/>Directory </CARD> <CARD NAME="card2"> <DO TYPE="ACCEPT"> <GO URL="?send=$type"/> </DO> Services <SELECT KEY="type"> <OPTION VALUE="em">Email</OPTION> <OPTION VALUE="ph">Phone</OPTION> <OPTION VALUE="fx">Fax</OPTION> </SELECT> </CARD> </WML>

Acme Inc. Directory _____________ Next

Services 1>Email 2 Phone ____________ OK

Source: WAP Forum

The DO Element
Binds a task to a user action
Action type: Label: Task: Destination: Post data: ACCEPT, OPTIONS, HELP PREV, DELETE, RESET Text string or image (optional) GO PREV, REFRESH, NOOP URL if METHOD=POST

<DO TYPE="ACCEPT" LABEL="Next"> <GO URL="http://www.mysite.com/myapp.wml"/> </DO>

Source: WAP Forum

Anchored Links
Bind a task to the ACCEPT action, when cursor points to a link
TITLE= sets the label string (default = Link) Links are not allowed in select list options

<CARD> Please visit our <A TITLE="Visit"> <GO URL="home.wml"/>home page</A> for details. </CARD>

Please visit our home page for ____________ Visit

Source: WAP Forum

The TEMPLATE Element

Defines actions & events for all cards in a deck
<WML> <TEMPLATE> <DO TYPE="OPTIONS" LABEL="Main"> <GO URL="main_menu.wml"/> </DO> </TEMPLATE> <CARD NAME="msg1"> <DO TYPE="ACCEPT" LABEL="Next"> <GO URL="#msg2"/> </DO> First story </CARD> <CARD NAME="msg2"> Second story </CARD> </WML>

First story _____________ Next Main

Second story ... _____________ OK Main

Source: WAP Forum

Handling User Input

Select lists
Choose from a list of options

Input fields
Enter a string of text or numbers

KEY variables
Set by SELECT and INPUT elements How user input is passed to other cards and the application server
Source: WAP Forum

The SELECT Element

Display a list of options
Each option may set the KEY variable and/or bind a task to the ACCEPT key TITLE= dynamically sets the label string

MULTIPLE=TRUE: Allows user to pick multiple items

<CARD> <DO TYPE="ACCEPT" LABEL="View"> <GO URL="getcity.cgi?location=$city"/> </DO> Forecast <SELECT KEY="city"> <OPTION VALUE="ber">Berlin</OPTION> <OPTION VALUE="rom">Rome</OPTION> <OPTION TITLE="Find" ONCLICK="find.cgi">New </SELECT> </CARD>

Forecast 1 Berlin 2 Rome 3>New City ____________ Find

City</OPTION>

Source: WAP Forum

The INPUT Element

Prompts user to enter a string of text
DEFAULT=key_value; Default KEY variable (displayed to user)

FORMAT=format_specifier; If omitted, free-form entry is allowed

EMPTYOK="TRUE; Browser will accept null input TYPE="PASSWORD; Special entry mode handled by the browser MAXLENGTH=number; Maximum number of allowed characters
Soc. Security:

<CARD> <DO TYPE="ACCEPT"> <GO URL="?get=person" METHOD="POST" POSTDATA="userid=$ssn"/> </DO> Soc Security: <INPUT KEY="ssn" FORMAT="NNN\-NN\-NNNN"/> </CARD>

287-33- _ ____________ NUM

Soc. Security:
287-33- 7629 ____________ OK

Source: WAP Forum

WML Content Formats

Common interchange formats, for interoperability Formats:
Business cards: IMC vCard standard Calendar: IMC vCalendar standard Images: WBMP (Wireless BitMaP) Compiled WML, WMLScript

Newly defined formats:

WML text and tokenized format WMLScript text and bytecode format WBMP image format

Binary format for size reduction

Bytecodes/tokens for common values and operators Compressed headers Data compression (e.g. images)

General-purpose transport compression can still be applied

Displaying Images
Insert app images or local icons within display text
1-bit BMP format

Images are ignored by non-bitmapped devices

Check HTTP_ACCEPT for image/bmp

<CARD> <DO TYPE="ACCEPT"> <GO URL="#c2"/> </DO> Continue <IMG LOCALSRC="righthand" ALT="forward..."/> </CARD> <CARD NAME="c2"> <IMG SRC="../images/logo.wbmp" ALT="Unwired Planet"/> <BR/>Welcome! </CARD>

Source: WAP Forum

WML (other features)

Setting card styles to create forms

Using variables to cache user data

Using card intrinsic events to trigger transparent tasks Using timers Securing WML decks Bookmarking decks

Wireless Markup Language

A lightweight markup language designed to meet the

constraints of a wireless environment with low bandwidth and small handheld devices. The Wireless Markup Language is WAPs analogy to HTML used on the WWW. WML is based on the Extensible

Markup Language (XML).

WAP - WML Syntax

The topmost layer in the WAP architecture is made up of WAE (Wireless

Application Environment), which consists of WML and WML scripting

language. WML scripting language is used to design applications that are sent over

wireless devices such as mobile phones. This language takes care of the
small screen and the low bandwidth of transmission. WML is an application of XML, which is defined in a document-type

definition.

 WML pages are called decks. They are constructed as a set of cards,

related to each other with links.

When a WML page (decks) is accessed from a mobile phone, all the cards in the page are downloaded from the WAP server to mobile phone

showing the content.

WML commands and syntaxes are used to show content and to navigate between the cards. Developers can use these commands to declare

variables, format text, and show images on the mobile phone.

WAP Program Structure

A WML program is typically divided into two parts: the document prolog
and the body. Consider the following code.
<?xml version="1.0"?>

<!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.2//EN"

"http://www.wapforum.org/DTD/wml12.dtd"> <wml> <card> ... </card> . ..more cards...

</wml>

Navigation

Variables

Input Elements

<WML> <CARD> <DO TYPE=ACCEPT> <GO URL=#eCard/> </DO Welcome! </CARD> <CARD NAME=eCard> <DO TYPE=ACCEPT> <GO URL=/submit?N=$(N)&S=$(S)/> </DO> Enter name: <INPUT KEY=N/> Choose speed: <SELECT KEY=S> <OPTION VALUE=0>Fast</OPTION> <OPTION VALUE=1>Slow</OPTION> <SELECT> </CARD> </WML>

WAE - WML

Card

Deck

 The first line of this text says that this is an XML document and the version

is 1.0.
The second line selects the document type and gives the URL of the document type definition (DTD). This DTD gives the full XML definition of

WML.
The DTD referenced is defined in WAP 1.1, but this header changes with the versions of the WML. The header must be copied exactly so that the

tool kits automatically generate this prolog.

 The body is enclosed within a <wml>...</wml> tag pair as shown above.

The body of a WML document can consist of one or more of the following:
Deck Card Content to be shown Navigation instructions

Decks and Cards WML pages are often called "decks". A deck contains a set of cards. A card element can contain text, markup, links, input-fields, tasks, images and more. Cards can be related to each other with links. Navigation between the cards is done by the phone computer - inside the phone - without any extra access trips to the server.

WML Commands: The commands used in WML are summarized as follows: Formatting:
Command <p> <b> <big> <em> <I> <small> <strong> <u> <br> Description Paragraph Bold Large Emphasized Italicized Small Strongly Emphasized Underlined Line Break

 Inserting images:
<img src="image-path/image - name" alt="Picture not available" />

Using Tables:

Command

Description

<table>
<tr> <td> <Thead>

Definition of a table
Defining a row Defining a column Table header

 Variables:

Declared as
<setvar name="x" value="xyz"/>

Used as:
$ defines as identifier

 Forms:
Command <select> Description Define single or multiple list

<input>
<option> <fieldset> <optgroup>

Input from user

Defines an option in a selectable list Defines a set of input fields Defines an option group in a selectable list

 Task Elements

Command

Description Represents the action of switching to a new card Says that nothing should be done Represents the action of going back to the previous card Refreshes some specified card

<go>
<noop> <prev>

<refresh>

variables.

 Events:
Command <do> <onevent> <postfield> <ontimer> <onenterforward> <onenterbackward> <onpick> Description Defines a do event handler Defines an onevent event handler Defines a postfield event handler Defines an ontimer event handler Defines an onenterforward handler Defines an onenterbackward handler Defines an onpick event handler

Sample WML Program

<?xml version="1.0"?> <!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.1//EN" "http://www.wapforum.org/DTD/wml_1.1.xml">

<wml>

<card id="no1" title="Card 1">

<p>Hello World!</p>
</card>

<card id="no2" title="Card 2">

<p>Welcome to our WAP Tutorial!</p>

</card>

</wml>

 The result will look something like this in a mobile phone (note that only one card is displayed at a time):
------ Card 1 -----Hello World!

Queries!!!

What is the purpose of WAP?

To enable easy, fast delivery of relevant information and services to mobile users. It consists of a WML language specification, a WMLScript specification, and a Wireless Telephony Application Interface (WTAI) specification.

What type of devices will use WAP?

Handheld digital wireless devices such as mobile phones, pagers, two-way radios, smartphones, and communicators -- from lowend to high-end.

Which wireless networks does WAP work with?

WAP is designed to work with most wireless networks such as CDPD, CDMA, GSM, PDC, PHS, TDMA, FLEX, ReFLEX, iDEN, TETRA, DECT, DataTAC, Mobitex.

What operating systems are compatible with WAP?

WAP is a communications protocol and an application environment. It can be built on any operating system including PalmOS, EPOC, Windows CE, FLEXOS, OS/9, JavaOS,

etc. It provides service interoperability even

between different device families.

Why are network operators behind WAP?

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.

Will WAP comply with Third Generation wireless standards?

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

 Even as bandwidths increase, the cost of that bandwidth does not fall to zero. These costs result from higher power usage in

Is WAP necessary with higher bandwidth 3G networks?

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

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.

Can we use WAP in other country?

Yes, if the service provider in that country supports roaming & WAP on their network.
Can we access all WAP sites?

We can only access WAP sites available on WAP server of our service provider.

Is WAP service expensive and how we can activate it?

WAP service is very cheap (check with our service provider). We need to have a WAP enabled phones & our SIM card should support data/fax communications. Check with our service provider regarding WAP services.

Examples of WAP use

Checking train table information

Ticket purchase
Flight check in Viewing traffic information Checking weather conditions Looking up stock values Looking up phone numbers Looking up addresses Looking up sport results

WAP: Killer Applications

Location-based services
Real-time traffic reporting, Event/restaurant recommendation

Enterprise solutions
Email access, Database access, global intranet access Information updates pushed to WAP devices

Financial services
Banking, Bill-paying, Stock trading, Funds transfers

Travel services
Schedules and rescheduling, Reservations

Gaming and Entertainment

Online, real-time, multi-player games Downloadable horoscopes, cartoons, quotes, advice

M-Commerce
Shopping on the go Instant comparison shopping Location-based special offers and sales

References and Resources

Books
Mobile communications: Jochen Schiller, Addison Wesley 2000 Understanding WAP:

Official Website (specifications)

www.wapforum.org

Technical/Developer Info and tools

www.palopt.com.au/wap www.wap.net

Major players
www.nokia.com/wap www.ericsson.se/wap phone.com

OpenSource effort
www.wapgateway.org (Kannel WAP gateway project)

Any More Queries?!

Thank You