Nokia Mobile Phones Limited disclaims all liability, including liability for infringement of any proprietary rights,
relating to the implementation of information presented in this document. Nokia Mobile Phones Limited does not
warrant or represent that such use will not infringe such rights.
Nokia Mobile Phones Limited retains the right to make changes to this specification at any time without notice.
License:
A license is hereby granted to download and print a copy of this specification for personal use only. No other license
to any other intellectual property rights is granted herein.
This Service Developer's Guide for the Nokia 9110i Communicator provides information and practical
examples for developers who want to develop WAP services for Nokia 9110i. 9110i Communicator is an
advanced communications device with a feature-rich WAP services application. The document will
highlight the possibilities, limitations and requirements of service development and provides a good
introduction to the Nokia style of designing user interfaces.
The Wireless Application Protocol (WAP) will enhance the functionality of mobile handsets through
real-time interactive services. The protocol has been designed specially for small screens and low
bandwidth, and it offers a wide variety of wireless services over the Internet using handsets. However,
in 9110i especially the WAP services screen size differ a lot from common handsets and should be
taken into account when designing services that are both fast and easy to use, and offer the user
maximum enjoyability. In addition to 9110i-specific issues, many of the instructions in this document
can be used to maximize interoperability and ease of use on various other browsers.
This guide is not written for service developers only, but essentially for anyone involved in creating the
wireless information society and who needs to know more about service creation on small mobile
terminals. It can be used in conjunction with the Nokia WAP Toolkit.
4 (26)
The Toolkit offers developers an environment for creating, testing and demonstrating WAP applications.
This allows service providers to evaluate the usability of wireless applications and services together
with their end-user organization.
We at Nokia are very proud of our user interfaces and we have spent a lot of effort in constantly
improving them. In this guide we have collected a lot of what we have learned to help developers
improve their services. We believe that good usability will increase use and satisfaction and
subsequently revenues for service providers.
This guide is not intended to be a detailed WAP document and it is not meant to replace any WAP
specification.
1.1 References
User's guide for the Nokia 9110
The Nokia WAP Toolkit can be downloaded from http://www.forum.nokia.com/
Wireless Application Specifications http://www.wapforum.org/
Information about Nokia products can be obtained from http://www.nokia.com/
1.2 Contact information
Developer support can be obtained through Forum Nokia web-page http://www.forum.nokia.com/
Terminology
5 (26)
Card
A single WML unit of navigation and user interface.
Deck
A collection of WML cards that is the smallest download unit. You cannot download a single card in a
deck, but must download the entire Deck. Service developers should be aware of this, and not do a
giant application in one big Deck.
Hyperlink
A link within a document or card that allows quick navigation to another document (card).
Do element
A way of defining a binding between events (e.g. a user selection) and a task (e.g. to go somewhere).
Input element
A mark-up element that allows for interaction with the user, i.e. letting the user input textual values.
These can be used for inputs to locally stored scripts, or for parsing to origin servers.
Proportional fonts
A font, in which the letters don’t necessarily take up the same amount of pixels in the width. ‘W’ and ‘I’
are good examples.
Navigation
The principle of moving between menu items, decks and cards.
PDA
Personal Digital Assistant
CMT
Cellular Mobile Terminal
2. WIRELESS APPLICATION PROTOCOL - WAP
2.1 Introduction
The Wireless Application Protocol (WAP) is a set of protocols that allow the development of
applications and services for use with Mobile Phones and other mobile devices. These protocols and
their related standards and specifications are maintained by the WAP Forum.
The WAP Forum consists of a number of hi-tech companies from the Information Technology, Software
and Telecommunications industries. The objectives of the WAP Forum are to:
• Bring Internet content and advanced data applications to digital cellular phones.
• Create a global wireless protocol specification that works across different wireless network
technologies.
• Enable the creation of content and applications that scale across a wide range of bearer networks
and device types.
• Embrace existing standards and technology wherever possible.
2.2 WAP Architecture
6 (26)
2.2.1 WAP and Internet Architecture
In order to leverage on the existing Internet standard as much as possible, the WAP stack closely
follows the Internet model. This is illustrated in Figure 1.
Internet
HTML
JavaScript
TM
HTTP
TLS - SSL
TCP/IP
UDP/IP
Figure 1 – Comparison of Internet and WAP Architecture
Wireless Application
Wireless Application
Environment (WAE)
Wireless Session Layer (WSP)
Wireless Transaction Protocol (WTP)
Wireless Transport Layer Security (WTLS)
Wireless Datagram Protocol (WDP)
Bearers:
SMS USSDCSD
IS-136
CDMA CDPD PDC-P Etc..
Other Services
and
Applications
This layered architecture allows applications to utilize the features of the WAP stack through welldefined interfaces. This close link to the Internet architecture allows developers to utilize their existing
knowledge and expertise when developing applications for mobile terminals.
2.2.2 Wireless Application Environment (WAE)
The Wireless Application Environment (WAE) is a general-purpose application environment that uses a
combination of Internet and mobile terminal technology. It provides a framework for the development
of applications on a mobile terminal.
The WAE contains support for the following functionality:
Wireless Mark-up Language (WML) - a lightweight presentation language, similar to HyperText Markup Language (HTML) but optimized for use with mobile terminals.
Wireless Mark-up Language Script (WMLS) - a lightweight script language, similar to Java Script
Wireless Telephony Application / Interface (WTA / WTAI) - telephony services and programming
interfaces.
Content Formats - defined data formats, such as vCard and vCalendar.
2.2.3 Wireless Session Protocol (WSP)
The Wireless Session Protocol (WSP) provides the application layer of WAP with an interface for two
session services. The first is a connection-oriented service that operates above the transaction layer
protocol. The second is a connectionless service that operates above a secure or non-secure datagram
service.
The WSP is optimized for low bandwidth bearer networks with long latency.
2.2.4 Wireless Transport Protocol (WTP)
7 (26)
TM
.
The Wireless Transport Protocol (WTP) runs on top of the datagram service and provides a lightweight
transaction-oriented protocol suitable for use in mobile terminals. WTP operates over secure or nonsecure wireless datagram networks
2.2.5 Wireless Transport Layer Security (WTLS)
The Wireless Transport Layer Security (WTLS) is based on the industry standard Transport Layer Security
(TLS) and is optimized for used over narrow band communication channels. WTLS may be used for
secure communication between terminals, and applications can selectively enable WTLS features.
2.3 Developing Applications with WAP
Application Developers can use the principles of WAP to develop new services or adapt existing
Internet applications for use with mobile terminals. Applications are written in the Wireless Mark-up
Language (WML) and the WMLScript, and stored on either a normal web server (origin server) or
directly on the WAP Gateway. The content stored on the web server will be accessible from the mobile
terminals via the cellular network and a WAP gateway or proxy.
The Proxy Server acts as a gateway between the cellular network and the Inter/Intranet. The data sent
between the origin server and the handset is binary encoded to optimize transmission over the narrow
bandwidth of the cellular network. Note that the content stored on the web server might be in either
textual or binary format. When the WAP gateway fetches textual content, it automatically compiles
this to the encoded format to minimize network load.
Figure 2 shows the network-related elements required for developing and offering services to mobile
users.
.
Web
Server
HTML
WML
HTML
Filter
WML
WAP
Proxy
Wireless
Network
Binary WML
WTA
Server
Binary
WML
Figure 2 – Network-Related Elements for WAP Applications
8 (26)
Web Server
The Web Server stores the applications written in WML. Alternatively, existing HTML applications can
be used.
HTML Filter
Any applications written in HTML will have to be converted to WML before they are sent to the mobile
terminal. This HTML Filter may form part of the Web Server or the WAP Proxy.
WAP Proxy
The WAP Proxy acts as the gateway between the cellular network and the Inter/Intranet. It binary
encodes the information which is to be sent to the mobile terminal and decodes information sent from
the mobile terminal.
WTA Server
The WTA server handles network-specific applications. These applications are not discussed in this
document.
2.4 Further Information
Further information about WAP is available on the Internet at www.wapforum.org.
:
:
:
:
Loading...
+ 18 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.