Professional Documents
Culture Documents
Unit4 (Second Part)
Unit4 (Second Part)
This time, class equals „1, and no user acknowledgement has been selected as
shown in Figure 10.15. The responder signals the incoming invoke PDU via the
TR-Invoke.ind primitive to the higher layer and acknowledges automatically
without user intervention. The specification also allows the user on the responders
side to acknowledge, but this acknowledgement is not required. For the initiator
the transaction ends with the reception of the acknowledgement. The responder
keeps the transaction state for some time to be able to retransmit the
acknowledgement if it receives the same invoke PDU again indicating a loss of the
acknowledgement.
WSP Services
• provides shared state between client and server, optimizes content transfer
• – session management (establish, release, suspend, resume)
• Policy and Planning – from strategic planning and concept of operations development
to legislative coordination, to the intersection between ITS, tolling, managed lanes,
and traffic engineering; our practice brings this full spectrum of understanding and
rich experience in planning to the table for easy integration with your existing
programs.
• Engineering and Integration – from roadside infrastructure assistance to
telecommunications expertise, data management to asset and configuration
management to C/AV research; we offer our unique experience in having actually
deployed roadside infrastructure as part of multiple projects, and with the most current
standards.
The WAE specifications outline an application programming model that supports browsing, scripting, and
extensions that allow cellular network operators to offer network services within WAP..
The WAE defines user agents, services, and formats. User agents are simply applications that run inside a
WAP-capable device such as a mobile phone. The standards support independent user agents to allow for
expanded device functionality and to ensure that special services such as mobile network access are
isolated from regular Internet services. The services that comprise the WAE include an eXtensible
Markup Language (XML)-compliant Wireless Markup Language, a scripting language (WMLScript) and
supporting libraries, as well as telephony services provided by the Wireless Telephony Application
libraries. Each class of information within the WAE is identified by a unique format. Encoding and
decoding of content (e.g., WML) ensures that information sent between a user agent and the WAP
gateway uses minimal bandwidth.
• A client issues an encoded request for an operation on a remote server.(encoding is necessary to
minimize data sent over the air and to save resources on hand held devices)
• Decoders in a gateway translate this encoded request into a standard request understood
by origin servers
• The origin servers will respond to this request by encoding the response and its content and
transfers it to client.
• WAE logical model also includes push services.
• Several user agents reside within the client
• WML user agent supports WML, WMLscript or both.
• WTA user agent handles access to and interaction with,mobile telephone features (such as call
control)
• The standard defines a user agent profile (UAProf) which describes capabilities of user agents.
–telephony functions
–Call control
–Network text messaging
–Phone book interface
–Event processing
WML Versions:
WAP Forum has released a latest version WAP 2.0. The markup language defined in
WAP 2.0 is XHTML Mobile Profile (MP). The WML MP is a subset of the XHTML. A
style sheet called WCSS (WAP CSS) has been introduced alongwith XHTML MP. The
WCSS is a subset of the CSS2.
Most of the new mobile phone models released are WAP 2.0-enabled. Because WAP
2.0 is backward compatible to WAP 1.x, WAP 2.0-enabled mobile devices can display
both XHTML MP and WML documents.
WML 1.x is an earlier technology. However, that does not mean it is of no use, since a
lot of wireless devices that only supports WML 1.x are still being used. Latest version
of WML is 2.0 and it is created for backward compatibility purposes. So WAP site
developers need not to worry about WML 2.0.
• A WAP enabled Web Server: You can enable your Apache or Microsoft IIS to serve all the
WAP client request.
• A WAP Gateway Simulator: This is required to interact to your WAP server.
• A WAP Phone Simulator: This is required to test your WAP Pages and to show all the
WAP pages.
You can write your WAP pages using the following languages:
A WML program is typically divided into two parts: the document prolog and the body.
Consider the following code:
Following is the basic structure of a WML program:
<?xml version="1.0"?>
<!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.2//EN"
"http://www.wapforum.org/DTD/wml12.dtd">
<wml>
</p>
</card>
</wml>
Text Elements
WML Elements Purpose
Image Elements
WML Elements Purpose
Anchor Elements
WML Elements Purpose
Event Elements
WML Elements Purpose
Input Elements
WML Elements Purpose
Variable Elements
WML Elements Purpose
<setvar> Defines and sets a variable
WML - Formatting
Line Break:
The <br /> element defines a line break and almost all WAP browsers supports a line
break tag.
The <br /> element supports the following attributes:
<wml>
</wml>