JavaTM APIs for BluetoothTM Wireless Technology (JSR-82)
This document, produced as a result of Java Specification Request 82 (JSR-82), defines the optional
package for Bluetooth wireless technology for Java 2 Platform, Micro Edition (J2ME). The goal of this
specification is to define the architecture and the associated APIs required to enable an open, third party
Bluetooth application development environment.
This API is designed to operate on top of the Connected, Limited Device Configuration (CLDC), which
is described in Connected, Limited Device Configuration (JSR-30), Sun Microsystems, Inc. This API is
an optional package that can be used to extend the capability of a J2ME profile, such as the Mobile
Information Device Profile (JSR 37) [5].
Because this API is based on CLDC, the reader is assumed to have some familiarity with the CLDC
specification and the Generic Connection Framework (GCF) described therein.
The specification for Bluetooth wireless communications is developed by the Bluetooth Special Interest
Group (SIG) led by promoter companies 3Com, Ericsson, Intel, IBM, Agere, Microsoft, Motorola, Nokia
and Toshiba. The Bluetooth specification is available from the SIG’s web site,
http://www.bluetooth.com. The Bluetooth specification defines protocols and application profiles but
does not define any APIs.
The JSR-82 specification defines APIs that can be used to exercise certain Bluetooth protocols defined in
the Bluetooth specification volume 1 [1], and certain profiles defined in the Bluetooth specification
volume 2 [2]. Those profiles are listed in Section 2.3. This API is defined in such a way as to make it
possible for additional and future profiles to be built on top of this API. This assumes that future changes
to the Bluetooth specification remain compatible with this API. This API is based on the Bluetooth
specification version 1.1. However, nothing in this specification is intended to preclude operating with
version 1.0 compliant stacks or hardware. In addition, if future versions are backward compatible with
version 1.1, then implementations of this specification should operate on those versions of stacks or
hardware as well.
0