Unit – 5

Wireless Application Protocol

Protocols and Tools: Wireless Application Protocol-WAP (Introduction.

Protocol architecture, and treatment of protocols of all layers), Bluetooth
(User scenarios, physical layer, MAC layer, networking, security, link
management) and J2ME.

The Wireless Application Protocol (WAP) is an open, global specification that empowers mobile
users with wireless devices to easily access and interact with information and services instantly.

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.

All solutions must be:

 interoperable, i.e., allowing terminals and software from different vendors to

communicate with networks from different providers
 scaleable, i.e., protocols and services should scale with customer needs and number of
customers
 efficient, i.e., provision of QoS suited to the characteristics of the wireless and mobile
networks
 Wireless Application Protocol (WAP)
Bluetooth, J2ME

 reliable, i.e., provision of a consistent and predictable platform for deploying services;
and
 secure, i.e., preservation of the integrity of user data, protection of devices and services
from security problems.

Why 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 Internet
protocol (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 pocket-sized 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 general packet radio service (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.

2
 Wireless Application Protocol (WAP)
Bluetooth, J2ME

 WAP will provide multiple applications, for business and customer markets such as banking,
corporate database access, and a messaging interface.

WAP Architecture
The following figure gives an overview of the WAP architecture, its protocols and components,
and compares this architecture with the typical internet architecture when using the World
Wide Web. The basis for transmission of data is formed by different bearer services. WAP does
not specify bearer services, but uses existing data services and will integrate further services.
Examples are message services, such as short message service (SMS) of GSM, circuit-switched
data, such as high-speed circuit switched data (HSCSD) in GSM, or packet switched data, such as
general packet radio service (GPRS) in GSM. Many other bearers are supported, such as CDPD,
IS-136, PHS.

WDP: The WAP datagram protocol (WDP) and the additional Wireless control message protocol
(WCMP) is the transport layer that sends and receives messages via any available bearer
network, including SMS, USSD, CSD, CDPD, IS–136 packet data, and GPRS. The transport layer

3
 Wireless Application Protocol (WAP)
Bluetooth, J2ME

service access point (T-SAP) is the common interface to be used by higher layers independent
of the underlying network.

WTLS: The next higher layer, the security layer with its wireless transport layer security protocol
WTLS offers its service at the security SAP (SEC-SAP). WTLS is based on transport layer security
(TLS, formerly SSL, secure sockets layer). WTLS has been optimized for use in wireless networks
with narrow-band channels. It can offer data integrity, privacy, authentication, and (some)
denial-of-service protection.

WTP: The WAP transaction protocol (WTP) layer provides transaction support, adding reliability
to the datagram service provided by WDP at the transaction SAP (TR-SAP).

WSP: The session layer with the wireless session protocol (WSP) currently offers two services at
the session-SAP (S-SAP), one connection-oriented and one connectionless if used directly on
top of WDP. A special service for browsing the web (WSP/B) has been defined that offers
HTTP/1.1 functionality, long-lived session state, session suspend and resume, session migration
and other features needed for wireless mobile access to the web.

WAE: The application layer with the wireless application environment (WAE) offers a
framework for the integration of different www and mobile telephony applications.

Working of WAP
WAP does not always force all applications to use the whole protocol architecture. Applications
can use only a part of the architecture. For example, if an application does not require security
but needs the reliable transport of data, it can directly use a service of the transaction layer.
Simple applications can directly use WDP.

4
 Wireless Application Protocol (WAP)
Bluetooth, J2ME

Different scenarios are possible for the integration of WAP components into existing wireless
and fixed networks. On the left side, different fixed networks, such as the traditional internet
and the public switched telephone network (PSTN), are shown. One cannot change protocols
and services of these existing networks so several new elements will be implemented between
these networks and the WAP-enabled wireless, mobile devices in a wireless network on the
right-hand side.

Wireless Datagram Protocol (WDP)

Wireless Datagram Protocol defines the movement of information from receiver to the sender
and resembles the User Datagram Protocol in the Internet protocol suite.

WDP offers a consistent service at the Transport Service Access Point to the upper layer
protocol of WAP. This consistency of service allows for applications to operate transparently
over different available bearer services. WDP can be mapped onto different bearers, with
different characteristics. In order to optimise the protocol with respect to memory usage and
radio transmission efficiency, the protocol performance over each bearer may vary.

5
 Wireless Application Protocol (WAP)
Bluetooth, J2ME

WDP offers source and destination port numbers used for multiplexing and demultiplexing of
data respectively. The service primitive to send a datagram is TDUnitdata. req with the
destination address (DA), destination port (DP), Source address (SA), source port (SP) , and
user data (UD) as mandatory parameters. Destination and source address are unique
addresses for the receiver and sender of the user data. These could be MSISDNs (i.e., a
telephone number), IP addresses, or any other unique identifiers. The T-DUnitdata.ind service
primitive indicates the reception of data. Here destination address and port are only optional
parameters.

WDP service primitives

If a higher layer requests a service the WDP cannot fulfil, this error is indicated with the
T-DError.ind service primitive. An error code (EC) is returned indicating the reason for the
error to the higher layer. WDP is not allowed to use this primitive to indicate problems with the
bearer service. It is only allowed to use the primitive to indicate local problems, such as a user
data size that is too large. If any errors happen when WDP datagrams are sent from one WDP
entity to another, the wireless control message protocol (WCMP) provides error handling
mechanisms for WDP and should therefore be implemented. WCMP contains control messages
that resemble the internet control message protocol messages and can also be used for
diagnostic and informational purposes. WCMP can be used by WDP nodes and gateways to
report errors.

Typical WCMP messages are destination unreachable (route, port, address

unreachable), parameter problem (errors in the packet header), message too big, reassembly
failure, or echo request/reply. An additional WDP management entity supports WDP and
provides information about changes in the environment, which may influence the correct
operation of WDP.

6
 Wireless Application Protocol (WAP)
Bluetooth, J2ME

Wireless Transport Layer Security (WTLS)

WTLS can provide different levels of security (for privacy, data integrity, and authentication)
and has been optimized for low bandwidth, high-delay bearer networks. WTLS takes into
account the low processing power and very limited memory capacity of the mobile devices for
cryptographic algorithms. WTLS supports datagram and connection-oriented transport layer
protocols. WTLS took over many features and mechanisms from TLS, but it has an optimized
handshaking between the peers.

Before data can be exchanged via WTLS, a secure session has to be established. This session
establishment consists of several steps: The following figure illustrates the sequence of service
primitives needed for a so-called ‘full handshake’.

The first step is to initiate the session with the SEC-Create primitive. Parameters are source
address (SA), source port (SP) of the originator, destinationaddress (DA), destination port
(DP) of the peer. The originator proposes a key exchange suite (KES) (e.g., RSA, DH, ECC), a
cipher suite (CS) (e.g., DES, IDEA ), and a compression method (CM). The peer answers with
parameters for the sequence number mode (SNM), the key refresh cycle (KR) (i.e., how
often keys are refreshed within this secure session), the session identifier (SID) (which is
unique with each peer), and the selected key exchange suite (KES’), cipher suite (CS’),
compression method (CM’). The peer also issues a SEC-Exchange primitive. This indicates
that the peer wishes to perform public-key authentication with the client, i.e., the peer

7
 Wireless Application Protocol (WAP)
Bluetooth, J2ME

requests a client certificate (CC) from the originator. The first step of the secure session
creation, the negotiation of the security parameters and suites, is indicated on the originator’s
side, followed by the request for a certificate. The originator answers with its certificate and
issues a SEC-Commit.req primitive. This primitive indicates that the handshake is completed
for the originator’s side and that the originator now wants to switch into the newly negotiated
connection state. The certificate is delivered to the peer side and the SEC-Commit is indicated.
The WTLS layer of the peer sends back a confirmation to the originator. This concludes the full
handshake for secure session setup.

WTLS datagram transfer

After setting up a secure connection between two peers, user data can be exchanged. This is
done using the simple SEC-Unitdata primitive as shown in above figure. SEC-Unitdata has
exactly the same function as T-DUnitdata on the WDP layer, namely it transfers a datagram
between a sender and a receiver. This data transfer is still unreliable, but is now secure. This
shows that WTLS can be easily plugged into the protocol stack on top of WDP.

Wireless Transaction Protocol (WTP)

WTP has been designed to run on very thin clients, such as mobile phones. WTP offers several
advantages to higher layers, including an improved reliability over datagram services, improved
efficiency over connection-oriented services, and support for transaction-oriented services such
as web browsing. WTP offers many features to the higher layers. The basis is formed from three
classes of transaction service. Class 0 provides unreliable message transfer without any result
message. Classes 1 and 2 provide reliable message transfer, class 1 without, class 2 with, exactly
one reliable result message (the typical request/response case). WTP achieves reliability using
duplicate removal, retransmission, acknowledgements and unique transaction identifiers.

8
 Wireless Application Protocol (WAP)
Bluetooth, J2ME

WTP allows for asynchronous transactions, abort of transactions, concatenation of messages,

and can report success or failure of reliable messages (e.g., a server cannot handle the
request). The three service primitives offered by WTP are TR-Invoke to initiate a new
transaction, TR-Result to send back the result of a previously initiated transaction, and TR-
Abort to abort an existing transaction.

The PDUs exchanged between two WTP entities for normal transactions are the invoke PDU,
ack PDU, and result PDU. A special feature of WTP is its ability to provide a user
acknowledgement or, alternatively, an automatic acknowledgement by the WTP entity.

WTP Class 0
Class 0 offers an unreliable transaction service without a result message. The transaction is
stateless and cannot be aborted. The service is requested with the TR-Invoke.req primitive as
shown below. Parameters are same as in WDP.

Additionally, with the A flag, the user of this service can determine, if the responder WTP entity
should generate an acknowledgement or if a user acknowledgement should be used. The WTP
layer will transmit the user data (UD) transparently to its destination. The class type C
indicates here class 0. Finally, the transaction handle H provides a simple index to uniquely

9
 Wireless Application Protocol (WAP)
Bluetooth, J2ME

identify the transaction and is an alias for the tuple (SA, SP, DA, DP), i.e., a socket pair, with only
local significance. The WTP entity at the initiator sends an invoke PDU which the responder
receives. The WTP entity at the responder then generates a TR-Invoke.ind primitive with the
same parameters as on the initiator’s side, except for H’ which is now the local handle for the
transaction on the responder’s side. WTP class 0 augments the transaction service with a simple
datagram like service for occasional use by higher layers.

WTP Class 1
Class 1 offers a reliable transaction service but without a result message. Again, the initiator
sends an invoke PDU after a TR-Invoke.req from a higher layer. This time, class equals ‘1’, and
no user acknowledgement has been selected as shown below.

The responder signals the incoming invoke PDU via the TR-Invoke.ind primitive to the higher
layer and acknowledges automatically without user intervention. 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.

If a user of the WTP class 1 service on the initiator’s side requests a user acknowledgement on
the responder’s side, the sequence diagram looks like the following figure.

10
 Wireless Application Protocol (WAP)
Bluetooth, J2ME

Now the WTP entity on the responder’s side does not send an acknowledgement automatically,
but waits for the TR-Invoke.res service primitive from the user. This service primitive must
have the appropriate local handle H’ for identification of the right tra nsaction. The WTP entity
can now send the ack PDU. Typical uses for this transaction class are reliable push services.

WTP Class 2
class 2 transaction service provides the classic reliable request/response transaction known
from many client/server scenarios. Depending on user requirements, many different scenarios
are possible for initiator/responder interaction. Three examples are presented below.

Example-1 scenario is shown below. A user on the initiator’s side requests the service and the
WTP entity sends the invoke PDU to the responder. The WTP entity on the responder’s side
indicates the request with the TR-Invoke.ind primitive to a user. The responder now waits for
the processing of the request, the user on the responder’s side can finally give the result UD* to
the WTP entity on the responder side using TR-Result.req. The result PDU can now be sent
back to the initiator, which implicitly acknowledges the invoke PDU.

Example 1: WTP Class 2 Transaction, no user acknowledgement, no hold on

The initiator can indicate the successful transmission of the invoke message and the result with
the two service primitives TR-Invoke.cnf and TR-Result.ind. A user may respond to this result
with TR-Result.res. An acknowledgement PDU is then generated which finally triggers the TR-
Result.cnf primitive on the responder’s side. This example clearly shows the combination of

11
 Wireless Application Protocol (WAP)
Bluetooth, J2ME

two reliable services (TR-Invoke and TR-Result) with an efficient data

transmission/acknowledgement.

In example-2, the user on the responder’s side now explicitly responds to the Invoke PDU using
the TR-Invoke.res primitive, which triggers the TR-Invoke.cnf on the initiator’s side via an
ack PDU. The transmission of the result is also a confirmed service, as indicated by the next
four service primitives. This service will likely be the most common in standard
request/response scenarios as, e.g., distributed computing.

Example 2:- WTP Class 2 Transaction, user ack

Example 3: WTP Class 2 Transaction, hold on, no user ack

12
 Wireless Application Protocol (WAP)
Bluetooth, J2ME

If the calculation of the result takes some time, the responder can put the initiator on “hold on”
to prevent a retransmission of the invoke PDU as the initiator might assume packet loss if no
result is sent back within a certain timeframe, which is shown above. After a time-out, the
responder automatically generates an acknowledgement for the Invoke PDU. This shows the
initiator that the responder is still alive and currently busy processing the request. After more
time, the result PDU can be sent to the initiator.

Wireless Session Protocol (WSP)

The wireless session protocol (WSP) has been designed to operate on top of the datagram
service WDP or the transaction service WTP. WSP provides a shared state between a client and
a server to optimize content transfer. WSP offers the following general features needed for
content exchange between cooperating clients and servers:

 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. The
capabilities of suspending and resuming a session are important to mobile applications.
 Capability negotiation: Clients and servers can agree upon a common level of protocol
functionality during session establishment. Example parameters to negotiate are
maximum client SDU size, maximum outstanding requests, protocol options, and server
SDU size.
 Content encoding: WSP also defines the efficient binary encoding for the content it
transfers. WSP offers content typing and composite objects, as explained for web
browsing.

While WSP is a general-purpose session protocol, WAP has specified the wireless session
protocol/browsing (WSP/B) which comprises protocols and services most suited for browsing-
type applications, which offers the following features adapted to web browsing.

 HTTP/1.1 functionality: WSP/B supports the functions HTTP/1.1 offers, such as

extensible request/reply methods, composite objects, and content type negotiation.
 Exchange of session headers: Client and server can exchange request/reply headers
that remain constant over the lifetime of the session
 pull data transfer: Pulling data from a server is the traditional mechanism of the web.
This is also supported by WSP/B using the request/response mechanism from HTTP/1.1.
Additionally, WSP/B supports three push mechanisms for data transfer: a confirmed
data push within an existing session context, a non-confirmed data push within an

13
 Wireless Application Protocol (WAP)
Bluetooth, J2ME

existing session context, and a non-confirmed data push without an existing session
context.
 Asynchronous requests: Optionally, WSP/B supports a client that can send multiple
requests to a server simultaneously. This improves efficiency for the requests and
replies can now be coalesced into fewer messages.

WSP/B over WTP

WSP/B uses the three service classes of WTP where, Class 0 is used for unconfirmed push,
session resume, and session management. Confirmed push uses class 1, method invocation,
session resume, and session management class 2.

The first example of session establishment of WSP/B using WTS class 2 transactions is shown
below:

With the S-Connect.req primitive, a client can request a new session. Parameters are the
server address (SA), the client address (CA), and the optional client header (CH) and
requested capabilities (RC). The session layer directly uses the addressing scheme of the layer
below. WTP transfers the connect PDU to the server S-SAP where an S-Connect.ind primitive
indicates a new session. Parameters are the same, but now the capabilities are mandatory. If
the server accepts the new session it answers with an S-Connect.res, parameters are an
optional server header (SH) with the same function as the client header and the negotiated
capabilities (NC) needed for capability negotiation. WTP now transfers the connreply PDU
back to the client; S-Connect.cnf confirms the session establishment and includes the server
header (if present) and the negotiated capabilities from the server. WSP/B includes several
procedures to refuse a session or to abort session establishment.

14
 Wireless Application Protocol (WAP)
Bluetooth, J2ME

A very useful feature of WSP/B session suspension and session resume is shown below. A client
can suspend the session because of several reasons. Session suspension will automatically
abort all data transmission and freeze the current state of the session on the client and server
side. A client suspends a session with S-Suspend.req, WTP transfers the suspend PDU to the
server with a class 0 transaction, i.e., unconfirmed and unreliable. WSP/B will signal the
suspension with S-Suspend.ind on the client and server side. The only parameter is the reason
R for suspension. Reasons can be a user request or a suspension initiated by the service
provider.

WSP/B session suspend/resume

Also shown above that, a client can later resume a suspended session with S-Resume.req.
Parameters are server address (SA) and client address (CA). Resuming a session is a
confirmed operation. It is up to the server’s operator how long this state is conserved.

Terminating a session is done by using the S-Disconnect.req service primitive as shown below.

WSP/B session termination

15
 Wireless Application Protocol (WAP)
Bluetooth, J2ME

This primitive aborts all current method or push transactions used to transfer data.
Disconnection is indicated on both sides using S-Disconnect.ind. The reason R for
disconnection can be, e.g., network error, protocol error, peer request, congestion, and
maximum SDU size exceeded.

The S-MethodInvoke primitive is used to request that an operation is executed by the server.
The result, if any, is sent back using the S-MethodResult primitive as shown below:

WSP/B method invoke

A client requests an operation with S-MethodInvoke.req. Parameters are the client
transaction identifier CTID to distinguish between pending transactions, the method M
identifying the requested operation at the server, and the request URI (Uniform Resource
Identifier RU. The WTP class 2 transaction service now transports the method PDU to the
server. A method PDU can be either a get PDU or a post PDU.

On the server’s side, S-MethodInvoke.ind indicates the request. In this case, a server
transaction identifier STID distinguishes between pending transactions. The server confirms
the request, so WSP/B does not generate a new PDU but relies on the lower WTP layer.
Similarly, the result of the request is sent back to the client using the SMethodResult primitive.
Additional parameters are now the status (S), the response header (RH), and the response
body (RB).

16
 Wireless Application Protocol (WAP)
Bluetooth, J2ME

WSP does not introduce PDUs or service primitives just for the sake of symmetric and aesthetic
protocol architecture. The following figure shows how WSP (thus also WSP/B) uses the
underlying WTP services for its purposes. The S-MethodInvoke.req primitive triggers the TR-
Invoke.req primitive, the parameters of the WSP layer are the user data of the WTP layer. The
invoke PDU of the WTP layer carries the method PDU of the WSP layer inside.

For the confirmation of its service primitives the WSP layer has none of its own PDUs but uses
the acknowledgement PDUs of the WTP layer. S-MethodInvoke.res triggers TR-Invoke.res,
the ack PDU is transferred to the initiator, here TR-Invoke.cnf confirms the invoke service
and triggers the S-MethodInvoke.cnf primitive which confirms the method invocation service.
This mingling of layers saves a lot of redundant data flow but still allows a separation of the
tasks between the two layers.

With the help of push primitives, a server can push data towards a client if allowed. The
simplest push mechanism is the non-confirmed push as shown below.

17
 Wireless Application Protocol (WAP)
Bluetooth, J2ME

The server sends unsolicited data with the S-Push.req primitive to the client. Parameters are
the push header (PH) and the push body (PB) again, these are the header and the body
known from HTTP. The unreliable, unconfirmed WTP class 0 transaction service transfers the
push PDU to the client where S-Push.ind indicates the push event.

A more reliable push service offers the S-ConfirmedPush primitive as shown below.

Here the server has to determine the push using a server push identifier (SPID). This helps to
distinguish between different pending pushes. The reliable WTP class 1 transaction service is
now used to transfer the confpush PDU to the client. On the client’s side a client push
identifier (CPID) is used to distinguish between different pending pushes.

WSP/B as connectionless session service

WSP/B could be run on top of the connectionless, unreliable WDP service. As an alternative to
WDP, WTLS can always be used if security is required. The service primitives are directly
mapped onto each other. The following figure shows the three service primitives available for
connectionless session service: S-Unit-MethodInvoke.req to request an operation on a server,
S-Unit-MethodResult.req to return results to a client, and S-Unit-Push.req to push data onto
a client. Transfer of the PDUs (method, reply and push) is done with the help of the standard
unreliable datagram transfer service of WDP.

Besides the server address (SA), the client address (CA), the method (M), and the
request URI (RU), the user of the S-Unit-MethodInvoke.req primitive can determine a
transaction identifier (TID) to distinguish between different transactions on the user level. TID
is communicated transparently from service user to service user.

18
 Wireless Application Protocol (WAP)
Bluetooth, J2ME

The function of the S-Unit-MethodResult primitive remains the same as explained above: the
status (S), response header (RH), and response body (RB) represent the result of the
operation. The S-Unit-Push primitive has the parameters client address (CA), server address
(SA), push identifier (PID), push header (PH), and push body (PB).

Wireless application environment (WAE)

The main idea behind the wireless application environment (WAE) is to create a general-
purpose application environment based mainly on existing technologies and philosophies of the
world wide web. One global goal of the WAE is to minimize over-the-air traffic and resource
consumption on the handheld device, which is reflected in the logical model shown below:

19
 Wireless Application Protocol (WAP)
Bluetooth, J2ME

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 the handheld device.
Decoders in a gateway now translate this encoded request into a standard request as
understood by the origin servers. This could be a request to get a web page to set up a call.
The gateway transfers this request to the appropriate origin server as if it came from a standard
client. Origin servers could be standard web servers running HTTP and generating content using
scripts, providing pages using a database, or applying any other (proprietary) technology.

The origin servers will respond to the request. The gateway now encodes the response
and its content (if there is any) and transfers the encoded response with the content to the
client. The WAE logical model not only includes this standard request/response scheme, but it
also includes push services. Then an origin server pushes content to the gateway. The gateway
encodes the pushed content and transmits the encoded push content to the client. Several user
agents can reside within a client. User agents include such items as: browsers, phonebooks,
message editors etc. WAE does not specify the number of user agents or their functionality, but
assumes a basic WML user agent that supports WML, WMLscript, or both (i.e., a ‘WML
browser’). However, one more user agent has been specified with its fundamental services, the
WTA user agent. This user agent handles access to, and interaction with, mobile telephone
features (such as call control). As over time many vendor dependent user agents may develop,
the standard defines a user agent profile (UAProf), which describes the capabilities of a user
agent.

Wireless Markup Language (WML)

The wireless markup language (WML) is based on the standard HTML known from the www
and on HDML. WML is specified as an XML document type. Several constraints of wireless
handheld devices had to be taken into account, when designing WML.

WML follows a deck and card metaphor. A WML document is made up of multiple cards. Cards
can be grouped together into a deck. A WML deck is similar to an HTML page, in that it is
identified by a URL and is the unit of content transmission. A user navigates with the WML
browser through a series of WML cards, reviews the contents, enters requested data, makes
choices etc. The WML browser fetches decks as required from origin servers. Either these decks
can be static files on the server or they can be dynamically generated.WML describes the intent
of interaction in an abstract manner. The user agent on a handheld device has to decide how to

20
 Wireless Application Protocol (WAP)
Bluetooth, J2ME

best present all elements of a card. This presentation depends much on the capabilities of the
device.

WML includes several basic features:

 Text and images: WML gives, as do other mark-up languages, hints how text and
images can be presented to a user
 User interaction: WML supports different elements for user input. Examples are: text
entry controls for text or password entry, option selections or controls for task
invocation. Navigation: As with HTML browsers, WML offers a history mechanism with
navigation through the browsing history, hyperlinks and other intercard navigation
elements.
 Context management: WML allows for saving the state between different decks
without server interaction, i.e., variable state can last longer than a single deck, and so
state can be shared across different decks.

WML script
WMLScript complements to WML and provides a general scripting capability in the WAP
architecture. While all WML content is static (after loading on the client), WMLScript offers
several capabilities not supported by WML:
 Validity check of user input: before user input is sent to a server, WMLScript can check
the validity and save bandwidth and latency in case of an error.
 Access to device facilities: WMLScript offers functions to access hardware components and
software functions of the device.
 Local user interaction: Without introducing round-trip delays, WMLScript can directly and
locally interact with a user, show messages or prompt for input.
 Extensions to the device software: With the help of WMLScript a device can be configured
and new functionality can be added even after deployment.

WMLScript is based on JavaScript, but adapted to the wireless environment. WMLScript is

event-based, i.e., a script may be invoked in response to certain user or environment events.
WMLScript also has full access to the state model of WML, i.e., WMLScript can set and read
WML variables. WMLScript provides many features known from standard programming
languages such as functions, expressions, or while, if, for, return etc. The WAP Forum
has specified several standard libraries for WMLScript (WAP Forum, 2000i). These libraries
provide access to the core functionality of a WAP client so they, must be availa ble in the client’s
scripting environment. The six libraries defined are Lang, Float, String, URL, WML browser and
Dialogs.

21
 Wireless Application Protocol (WAP)
Bluetooth, J2ME

BLUETOOTH
"Bluetooth" was the nickname of Harald Blåtland II, king of Denmark from 940 to 981, who
united all of Denmark and part of Norway under his rule. Bluetooth is a proprietary open
wireless technology standard for exchanging data over short distances (using short wavelength
radio transmissions in the ISM band from 2400-2480 MHz) from fixed and mobile devices,
creating personal area networks (PANs) with high levels of security. The Bluetooth technology
aims at so-called ad-hoc piconets, which are local area networks with a very limited coverage
and without the need for an infrastructure.

Bluetooth Features
 Bluetooth is wireless and automatic. You don't have to keep track of cables, connectors, and
connections, and you don't need to do anything special to initiate communications. Devices
find each other automatically and start conversing without user input, expect where
authentication is required; for example, users must log in to use their email accounts.
 Bluetooth is inexpensive. Market analysts peg the cost to incorporate Bluetooth technology
into a PDA, cell phone, or other product at a minimum cost.
 The ISM band that Bluetooth uses is regulated, but unlicensed. Governments have
converged on a single standard, so it's possible to use the same devices virtually wherever
you travel, and you don't need to obtain legal permission in advance to begin using the
technology.
 Bluetooth handles both data and voice. Its ability to handle both kinds of transmissions
simultaneously makes possible such innovations as a mobile hands-free headset for voice
with applications that print to fax, and that synchronize the address books on your PDA,
your laptop, and your cell phone.
 Signals are omni-directional and can pass through walls and briefcases. Communicating
devices don't need to be aligned and don't need an unobstructed line of sight like infrared.
 Bluetooth uses frequency hopping. Its spread spectrum approach greatly reduces the risk
that communications will be intercepted.

Bluetooth Applications
 File transfer.
 Ad-hoc networking: Communicating devices can spontaneously form a community of
networks that persists only as long as it's needed

22
 Wireless Application Protocol (WAP)
Bluetooth, J2ME

 Device synchronization: Seamless connectivity among PDAs, computers, and mobile

phones allows applications to update information on multiple devices automatically
when data on any one device changes.
 Peripheral connectivity.
 Car kits: Hands-free packages enable users to access phones and other devices without
taking their hands off the steering wheel
 Mobile payments: Your Bluetooth-enabled phone can communicate with a Bluetooth-
enabled vending machine to buy a can of Diet Pepsi, and put the charge on your phone
bill.

The 802.11b protocol is designed to connect relatively large devices with lots of power and
speed, such as desktops and laptops, where devices communicate at up to 11 Mbit/sec, at
greater distances (up to 300 feet, or 100 meters). By contrast, Bluetooth is designed to connect
small devices like PDAs, mobile phones, and peripherals at slower speeds (1 Mbit/sec), within a
shorter range (30 feet, or 10 meters), which reduces power requirements. Another major
difference is that 802.11b wasn't designed for voice communications, while any Bluetooth
connection can support both data and voice communications.

User scenarios
Many different user scenarios can be imagined for wireless piconets or WPANs:

Connection of peripheral devices: Today, most devices are connected to a desktop computer
via wires (e.g., keyboard, mouse, joystick, headset, speakers). This type of connection has
several disadvantages: each device has its own type of cable, different plugs are needed, wires
block office space. In a wireless network, no wires are needed for data transmission. However,
batteries now have to replace the power supply, as the wires not only transfer data but also
supply the peripheral devices with power.

Support of ad-hoc networking: Imagine several people coming together, discussing issues,
exchanging data (schedules, sales figures etc.). For instance, students might join a lecture, with
the teacher distributing data to their personal digital assistants (PDAs). Wireless networks can
support this type of interaction; small devices might not have WLAN adapters following the IEEE
802.11 standard, but cheaper Bluetooth chips built in.

Bridging of networks: Using wireless piconets, a mobile phone can be connected to a PDA or
laptop in a simple way. Mobile phones will not have full WLAN adapters built in, but could have
a Bluetooth chip. The mobile phone can then act as a bridge between the local piconet and,
e.g., the global GSM network.

23
 Wireless Application Protocol (WAP)
Bluetooth, J2ME

Networking in Bluetooth
Bluetooth operates on 79 channels in the 2.4 GHz band with 1 MHz carrier spacing. Each device
performs frequency hopping with 1,600 hops/s in a pseudo random fashion. A piconet is a
collection of Bluetooth devices which are synchronized to the same hopping sequence. One
device in the piconet can act as master (M), all other devices connected to the master must act
as slaves (S). The master determines the hopping pattern in the piconet and the slaves have to
synchronize to this pattern. Each piconet has a unique hopping pattern. If a device wants to
participate it has to synchronize to this. A typical piconet is shown below:

Parked devices (P) can not actively participate in the piconet (i.e., they do not have a
connection), but are known and can be reactivated within some milliseconds. Devices in stand-
by (SB) do not participate in the piconet. Each piconet has exactly one master and up to seven
simultaneous slaves. More than 200 devices can be parked. The first step in forming a piconet
involves a master sending its clock and device ID. All the Bluetooth devices have the same
capability to become a master or a slave and two or three devices are sufficient to form a
piconet. The unit establishing the piconet automatically becomes the master, all other devices
will be slaves. The hopping pattern is determined by the device ID, a 48-bit worldwide unique
identifier.

The phase in the hopping pattern is determined by the master’s clock. After adjusting
the internal clock according to the master a device may participate in the piconet. All active
devices are assigned a 3-bit active member address (AMA). All parked devices use an 8-bit
parked member address (PMA). Devices in stand-by do not need an address.

24
 Wireless Application Protocol (WAP)
Bluetooth, J2ME

A device in one piconet can communicate to another device in another piconet, forming a
scatternet. A master in one piconet may be a slave in another piconet. Both piconets use a
different hopping sequence, always determined by the master of the piconet. Bluetooth applies
FH-CDMA for separation of piconets. A collision occurs if two or more piconets use the same
carrier frequency at the same time. This
will probably happen as the hopping
sequences are not coordinated. If a device
wants to participate in more than one
piconet, it has to synchronize to the
hopping sequence of the piconet it wants
to take part in. If a device acts as slave in
one piconet, it simply starts to
synchronize with the hopping sequence of
the piconet it wants to join. After
synchronization, it acts as a slave in this
piconet and no longer participates in its
former piconet. To enable
synchronization, a slave has to know the
identity of the master that determines the
hopping sequence of a piconet. Before
leaving one piconet, a slave informs the current master that it will be unavailable f or a certain
amount of time. The remaining devices in the piconet continue to communicate as usual.

Bluetooth Protocol Stack

The Bluetooth protocol stack can be divided into a core specification, which describes the
protocols from physical layer to the data link control together with management functions, and
profile specifications describing many protocols and functions needed to adapt the wireless
Bluetooth technology to legacy and new applications.

A high-level view of the architecture is shown. The responsibilities of the layers in this stack are
as follows:

 The radio layer is the physical wireless connection. To avoid interference with other devices
that communicate in the ISM band, the modulation is based on fast frequency hopping.
Bluetooth divides the 2.4 GHz frequency band into 79 channels 1 MHz apart (from 2.402 to
2.480 GHz), and uses this spread spectrum to hop from one channel to another, up to 1600

25
 Wireless Application Protocol (WAP)
Bluetooth, J2ME

times a second. The standard wavelength range is 10 cm to 10 m, and can be extended to

100 m by increasing transmission power.

Bluetooth Protocol Stack

 The baseband layer is responsible for controlling and sending data packets over the radio
link. It provides transmission channels for both data and voice. The baseband layer
maintains Synchronous Connection-Oriented (SCO) links for voice and Asynchronous
Connectionless (ACL) links for data. SCO packets are never retransmitted but ACL packets
are, to ensure data integrity. SCO links are point-to-point symmetric connections, where
time slots are reserved to guarantee timely transmission. A slave device is allowed to
respond during the time slot immediately following an SCO transmission from the master. A
master can support up to three SCO links to a single slave or to multiple slaves, and a single
slave can support up to two SCO links to different slaves. Data transmissions on ACL links,
on the other hand, are established on a per-slot basis (using slots not reserved for SCO
links). ACL links support point-to-multipoint transmissions. After an ACL transmission from
the master, only a slave addressed specifically may respond during the next time slot; if no
device is addressed, the message is treated as a broadcast.
 The Link Manager Protocol (LMP) uses the links set up by the baseband to establish
connections and manage piconets. Responsibilities of the LMP also include authentication
and security services, and monitoring of service quality.
 The Host Controller Interface (HCI) is the dividing line between software and hardware. The
L2CAP and layers above it are currently implemented in software, and the LMP and lower
layers are in hardware. The HCI is the driver interface for the physical bus that connects
these two components. The HCI may not be required. The L2CAP may be accessed directly

26
 Wireless Application Protocol (WAP)
Bluetooth, J2ME

by the application, or through certain support protocols provided to ease the burden on
application programmers.
 The Logical Link Control and Adaptation Protocol (L2CAP) receives application data and
adapts it to the Bluetooth format. Quality of Service (QoS) parameters are exchanged at this
layer.

Link Manager Protocol

The link manager protocol (LMP) manages various aspects of the radio link between a master
and a slave and the current parameter setting of the devices. LMP enhances baseband
functionality, but higher layers can still directly access the baseband. The following groups of
functions are covered by the LMP:

 Authentication, pairing, and encryption: Although basic authentication is handled in the

baseband, LMP has to control the exchange of random numbers and signed responses. LMP
is not directly involved in the encryption process, but sets the encryption mode (no
encryption, point-to-point, or broadcast), key size, and random speed.
 Synchronization: Precise synchronization is of major importance within a Bluetooth
network. The clock offset is updated each time a packet is received from the master.
 Capability negotiation: Not only the version of the LMP can be exchanged but also
information about the supported features. Not all Bluetooth devices will support all
features that are described in the standard, so devices have to agree the usage of, e.g.,
multi-slot packets, encryption, SCO links, voice encoding, park/sniff/hold mode, HV2/HV3
packets etc.
 Quality of service negotiation: Different parameters control the QoS of a Bluetooth device
at these lower layers. The poll interval, i.e., the maximum time between transmissions from
a master to a particular slave, controls the latency and transfer capacity. A master can also
limit the number of slots available for slaves’ answers to increase its own bandwidth.
 Power control: A Bluetooth device can measure the received signal strength. Depending on
this signal level the device can direct the sender of the measured signal to increase or
decrease its transmit power.
 Link supervision: LMP has to control the activity of a link, it may set up new SCO links, or it
may declare the failure of a link.
 State and transmission mode change: Devices might switch the master/slave role, detach
themselves from a connection, or change the operating mode

27
 Wireless Application Protocol (WAP)
Bluetooth, J2ME

Bluetooth defines several low-power states for a device. The following figure shows the major
states of a Bluetooth device and typical transitions. Every device, which is currently not
participating in a piconet (and not switched off), is in standby mode. This is a low-power mode
where only the native clock is running. The next step towards the inquiry mode can happen in
two different ways. Either a device wants to establish a piconet or a device just wants to listen
to see if something is going on.

Major baseband states of a Bluetooth device

 A device wants to establish a piconet: A user of the device wants to scan for other
devices in the radio range. The device starts the inquiry procedure by sending an inquiry
access code (IAC) that is common to all Bluetooth devices. The IAC is broadcast over 32
so-called wake-up carriers in turn.
 Devices in standby that listen periodically: Devices in standby may enter the inquiry
mode periodically to search for IAC messages on the wake-up carriers. As soon as a
device detects an inquiry it returns a packet containing its device address and timing
information required by the master to initiate a connection. From that moment on, the
device acts as slave.

If the inquiry was successful, a device enters the page mode. The inquiry phase is not
coordinated, so it may take a while before the inquiry is successful. After a while , a Bluetooth
device sees all the devices in its radio range.

28
 Wireless Application Protocol (WAP)
Bluetooth, J2ME

During the page state two different roles are defined. After finding all required devices the
master is able to set up connections to each device, i.e., setting up a piconet. As soon as a
device synchronizes to the hopping pattern of the piconet it also enters the connection state.
The connection state comprises the active state and the low power states: park, sniff, and hold.
In the active state the slave participates in the piconet by listening, transmitting, and receiving.
ACL and SCO links can be used. A master periodically synchronizes with all slaves. All devices
being active must have the 3-bit active member address (AMA). To save battery power, a
Bluetooth device can go into one of three low power states:

 Sniff state: The sniff state has the highest power consumption of the low power states.
Here, the device listens to the piconet at a reduced rate (not on every other slot as is the
case in the active state). The interval for listening into the medium can be programed and is
application dependent. The master designates a reduced number of slots for transmission
to slaves in sniff state. However, the device keeps its AMA.
 Hold state: The device does not release its AMA but stops ACL transmission. A slave may
still exchange SCO packets. If there is no activity in the piconet, the slave may either reduce
power consumption or participate in another piconet.
 Park state: In this state the device has the lowest duty cycle and the lowest power
consumption. The device releases its AMA and receives a parked member address (PMA).
The device is still a member of the piconet, but gives room for another device to become
active (AMA is only 3 bit, PMA 8 bit). Parked devices are still FH synchronized and wake up
at certain beacon intervals for re-synchronization. All PDUs sent to parked slaves are
broadcast.

L2CAP
The logical link control and adaptation protocol (L2CAP) is a data link control protocol on top of
the baseband layer offering logical channels between Bluetooth devices with QoS properties.
L2CAP is available for ACLs only.

L2CAP provides three different types of logical channels that are transported via the ACL
between master and slave:

 Connectionless: These unidirectional channels are typically used for broadcasts from a
master to its slave(s).
 Connection-oriented: Each channel of this type is bi-directional and supports QoS flow
specifications for each direction. These flow specs follow RFC 1363 and define average/peak
data rate, maximum burst size, latency, and jitter.

29
 Wireless Application Protocol (WAP)
Bluetooth, J2ME

 Signaling: This third type of logical channel is used to exchanging signaling messages
between L2CAP entities.

Each channel can be identified by its channel identifier (CID). Signaling channels always use a
CID value of 1, a CID value of 2 is reserved for connectionless channels. For connection-oriented
channels a unique CID (>= 64) is dynamically assigned at each end of the channel to identify the
connection.

The following figure shows the three packet types belonging to the three logical channel types.

The length field indicates the length of the payload (plus PSM for connectionless PDUs). The
CID has the multiplexing/demultiplexing function. For connectionless PDUs a protocol/service
multiplexor (PSM) field is needed to identify the higher layer recipient for the payload. For
connection-oriented PDUs the CID already fulfills this function. Several PSM values have been
defined, e.g., 1 (SDP), 3 (RFCOMM), 5 (TCS-BIN). Values above 4096 can be assigned
dynamically. The payload of the signaling PDU contains one or more commands. Each
command has its own code (e.g., for command reject, connection request, disconnection
response etc.) and an ID that matches a request with its reply. The length field indicates the
length of the data field for this command.

Besides protocol multiplexing, flow specification, and group management, the L2CAP layer also
provides segmentation and reassembly functions. Depending on the baseband capabilities,
large packets have to be chopped into smaller segments.

30
 Wireless Application Protocol (WAP)
Bluetooth, J2ME

Security
The main security features offered by Bluetooth include a challenge response routine for
authentication, a stream cipher for encryption, and a session key generation. Each connection
may require a one-way, two-way, or no authentication using the challenge-response routine.
The security algorithms use the public identity of a device, a secret private user key, and an
internally generated random key as input parameters. For each transaction, a new random
number is generated on the Bluetooth chip. Key management is left to higher layer software.
The following figure shows several steps in the security architecture of Bluetooth.

Bluetooth security components and protocols

The first step, called pairing, is necessary if two Bluetooth devices have never met
before. To set up trust between the two devices a user can enter a secret PIN into both devices.
This PIN can have a length of up to 16 byte. Based on the PIN, the device address, and random
numbers, several keys can be computed which can be used as link key for authentication. The
authentication is a challenge-response process based on the link key, a random number
generated by a verifier (the device that requests authentication), and the device address of the
claimat (the device that is authenticated).

31
 Wireless Application Protocol (WAP)
Bluetooth, J2ME

Based on the link key, and again a random number an encryption key is generated
during the encryption stage of the security architecture. This key has a maximum size of 128
bits and can be individually generated for each transmission. Based on the encryption key, the
device address and the current clock a payload key is generated for ciphering user data. The
payload key is a stream of pseudo-random bits. The ciphering process is a simple XOR of the
user data and the payload key.

All Bluetooth-enabled devices must implement the Generic Access Profile, which contains all
the Bluetooth protocols and possible devices. This profile defines a security model that includes
three security modes:

 Mode 1 is an insecure mode of operation. No security procedures are initiated.

 Mode 2 is known as service-level enforced security. When devices operate in this mode, no
security procedures are initiated before the channel is established. This mode enables
applications to have different access policies and run them in parallel.
 Mode 3 is known as link-level enforced security. In this mode, security procedures are
initiated before link setup is complete.

Though Bluetooth offers a better security than WER in 802.11, it has several limitations. The
PIN’s are often fixed and some keys are permanently stored on the devices. The quality of the
random number generators has not been specified.

SDP
To find new services available in the radio proximity, Bluetooth defined the service discovery
protocol (SDP). SDP defines only the discovery of services, not their usage. Discovered services
can be cached and gradual discovery is possible. All the information an SDP server has about a
service is contained in a service record. This consists of a list of service attributes and is
identified by a 32-bit service record handle.

A service attribute consists of an attribute ID and an attribute value. The 16-bit attribute
ID distinguishes each service attribute from other service attributes within a service record. The
attribute ID also identifies the semantics of the associated attribute value. The attribute value
can be an integer, a UUID (universally unique identifier), a string, a Boolean, a URL (uniform
resource locator) etc.

32
 Wireless Application Protocol (WAP)
Bluetooth, J2ME

Bluetooth Profiles
Bluetooth profiles are intended to ensure interoperability among Bluetooth-enabled devices
and applications from different manufacturers and vendors. A profile defines the roles and
capabilities for specific types of applications. Profiles represent default solutions for a certain
usage model. They use a selection of protocols and parameter set to form a basis for
interoperability. Protocols can be seen as horizontal layers while profiles are vertical slices as
shown below:

The following basic profiles have been specified: generic access, service discovery, cordless
telephony, intercom, serial port, headset, dialup networking, fax, LAN access, generic object
exchange, object push, file transfer, and synchronization. Additional profiles are: advanced
audio distribution, PAN, audio video remote control, basic printing, basic imaging, extended
service discovery, generic audio video distribution, hands-free, and hardcopy cable
replacement. Some of the profiles are given below:

 The Generic Access Profile defines connection procedures, device discovery, and link
management. It also defines procedures related to use of different security models and
common format requirements for parameters accessible on the user interface level. At a
minimum all Bluetooth devices must support this profile.
 The Service Discovery Application and Profile defines the features and procedures for an
application in a Bluetooth device to discover services registered in other Bluetooth devices,
and retrieves information related to the services.
 The Serial Port Profile defines the requirements for Bluetooth devices that need to set up
connections that emulate serial cables and use the RFCOMM protocol.
 The LAN Access Profile defines how Bluetooth devices can access the services of a LAN using
PPP, and shows how PPP mechanisms can be used to form a network consisting of
Bluetooth devices.

33
 Wireless Application Protocol (WAP)
Bluetooth, J2ME

 The Synchronization Profile defines the application requirements for Bluetooth devices that
need to synchronize data on two or more devices.

Java 2 Micro Edition (J2ME)

Sun Microsystems defines J2ME as "a highly optimized Java run-time environment targeting a
wide range of consumer products, including pagers, cellular phones, screen-phones, digital set-
top boxes and car navigation systems." J2ME brings the cross-platform functionality of the Java
language to smaller devices, allowing mobile wireless devices to share applications. Java 2
Micro Edition maintains the qualities that Java technology has become known for:

 built-in consistency across products in terms of running anywhere, anytime, on any

device
 the power of a high-level object-oriented programming language with a large developer
base;
 portability of code;
 safe network delivery; and
 upward scalability with J2SE and J2EE

While connected consumer devices such as cell phones, pagers, personal organizers and set-top
boxes have many things in common, they are also diverse in form, function and features.
Information appliances tend to be special-purpose, limited-function devices. To address this
diversity, an essential requirement for J2ME is not only small size but also modularity and
customizability. The J2ME architecture is modular and scalable so that it can support the kinds
of flexible deployment demanded by the consumer and embedded markets. To support this
kind of customizability and extensibility, two essential concepts are defined by J2ME:

 Configuration. A J2ME configuration defines a minimum platform for a “horizontal”

category or grouping of devices, each with similar requirements on total memory budget
and processing power. A configuration defines the Java language and virtual machine
features and minimum class libraries that a device manufacturer or a content provider can
expect to be available on all devices of the same category.
 Profile. A J2ME profile is layered on top of (and thus extends) a configuration. A profile
addresses the specific demands of a certain “vertical” market segment or device family. The
main goal of a profile is to guarantee interoperability within a certain vertical device family
or domain by defining a standard Java platform for that market. Profiles typically include

34
 Wireless Application Protocol (WAP)
Bluetooth, J2ME

class libraries that are far more domain-specific than the class libraries provided in a
configuration.

J2ME software layer stack

Configurations
A configuration is a subset of profile. A configuration defines a Java platform for a “horizontal”
category or grouping of devices with similar requirements on total memory budget and other
hardware capabilities. More specifically, a configuration:

• specifies the Java programming language features supported,

• specifies the Java virtual machine features supported,
• specifies the basic Java libraries and APIs supported.
To avoid fragmentation, there will be a very limited number of J2ME configurations. Currently,
the goal is to define two standard J2ME configurations:

 Connected, Limited Device Configuration (CLDC). The market consisting of personal,

mobile, connected information devices is served by the CLDC. This configuration includes
some new classes, not drawn from the J2SE APIs, designed specifically to fit the needs of
small-footprint devices. It is used specifically with the KVM for 16-bit or 32-bit devices with
limited amounts of memory. This is the configuration (and the virtual machine) used for
developing small J2ME applications.
 Connected Device Configuration (CDC). The market consisting of shared, fixed, connected
information devices is served by the Connected Device Configuration (CDC). To ensure
upward compatibility between configurations, the CDC shall be a superset of the CLDC. This

35
 Wireless Application Protocol (WAP)
Bluetooth, J2ME

is used with the C virtual machine (CVM) and is used for 32-bit architectures requiring more
than 2 MB of memory.

J2ME Universe
 Wireless Application Protocol (WAP)
Bluetooth, J2ME

Profiles
The J2ME framework provides the concept of a profile to make it possible to define Java
platforms for specific vertical markets. Profiles can serve two distinct portability requirements:

 A profile provides a complete toolkit for implementing applications for a particular kind
of device, such as a pager, set-top box, cell phone, washing machine, or interactive
electronic toy.
 A profile may also be created to support a significant, coherent group of applications
that might be hosted on several categories of devices.

Foundation profile contains APIs of J2SE without GUIs. PersonalProfile is profile for embedded
devices. Two profiles have been defined for J2ME and are built on CLDC: KJava and Mobile
Information Device Profile (MIDP). These profiles are geared toward smaller devices.

MIDP 3.0 is the latest profile version, which is a profile for special-featured phones and
handheld devices. It provides improved UI’s, UI extensibility and interoperability between the
devices. It supports multiple network interfaces in a device, IPv6, large display devices and high
performance games. Development tools are used to develop MIDP applications. MIDP
applications are composed of two parts:

 JAR File – Contains all of the classes and resources used by the application

 JAD File – Application descriptor, describes how to run the MIDP application

Source Package Sets of Java class libraries

1 Java.lang standard java types and classes for String, Integer, Math, Thread,
Security and Exception

2 Java.io Standard java types and classes for input and output streams

3 Java.util A set of classes such as Timers, Calenders, Dates, Hashtables,

Vectors and others

4 Javax.microedition.rms A record management system (RMS) API to retrieve and save data
and limited querying capability

5 Javax.microedition.pim Personal information management API (optional), access the

device’s address book

6 Javax.microedition.pki Secure connections authenticate API’s

MIDP source packages and sets of Java class libraries

 Wireless Application Protocol (WAP)
Bluetooth, J2ME

K Virtual Machine

The KVM is a compact, portable Java virtual machine specifically designed from the ground up
for small, resource-constrained devices. The high-level design goal for the KVM was to create
the smallest possible “complete” Java virtual machine that would maintain all the central
aspects of the Java programming language, but would run in a resource-constrained device with
only a few hundred kilobytes total memory budget. More specifically, the KVM was designed to
be:

 small, with a static memory footprint of the virtual machine core in the range of 40
kilobytes to 80 kilobytes (depending on compilation options and the target platform,)
 clean, well-commented, and highly portable,
 modular and customizable, as “complete” and “fast” as possible without sacrificing the
other design goals.

The “K” in KVM stands for “kilo.” It was so named because its memory budget is measured in
kilobytes (whereas desktop systems are measured in megabytes). KVM is suitable for 16/32-bit
RISC/CISC microprocessors with a total memory budget of no more than a few hundred
kilobytes (potentially less than 128 kilobytes). This typically applies to digital cellular phones,
pagers, personal organizers, and small retail payment terminals.

38

www.jntuworld.com
 Wireless Application Protocol (WAP)
Bluetooth, J2ME

Assignment Questions

1. Explain the functions of radio, baseband and link manager in Bluetooth.

2. Explain about the wireless transaction protocol of the transaction layer.
3. Explain about the wireless application Environment (WAE) logical model.
4. Write about J2ME in briefly
5. Name mechanisms to improve web access for handheld devices. What is their common
problem and what led finally to the development of WAP?
6. Explain in detail about wireless marked language and its features
7. With a neat diagram explain the WAP architecture.
8. Discuss briefly the user scenarios of Bluetooth
9. Discuss the configuration and profile of J2ME in detail.
10. Explain briefly about the wireless Datagram protocol (WDP) of transport layer

39

www.jntuworld.com