Go to JSR:
On this page:
 
Print Format
JSRs: Java Specification Requests
JSR 82: JavaTM APIs for Bluetooth

Bluetooth is an important emerging standard for wireless integration of small devices. The specification standardizes a set of Java APIs to allow Java-enabled devices to integrate into a Bluetooth environment.

  Status: Final              
  Stage       Start   Finish  
  Maintenance Draft Review 3   Download page   11 Apr, 2008   12 May, 2008  
  Final Release 2   Download page   28 Jun, 2006      
  Maintenance Draft Review 2   Download page   30 Mar, 2006   01 May, 2006  
  Maintenance Draft Review   Download page   13 Oct, 2005   14 Nov, 2005  
  Final Release   Download page   22 Mar, 2002      
  Final Approval Ballot   View results   19 Feb, 2002   04 Mar, 2002  
  Proposed Final Draft   Download page   29 Jan, 2002      
  Public Review   Download page   29 Nov, 2001   29 Dec, 2001  
  Community Draft Ballot   View results   06 Nov, 2001   12 Nov, 2001  
  Community Review   Login page   12 Oct, 2001   12 Nov, 2001  
  Expert Group Formation       03 Oct, 2000   09 Nov, 2000  
  JSR Review Ballot   View results   19 Sep, 2000   02 Oct, 2000  
   
JCP version in use: 2.1
Java Specification Participation Agreement version in use: 1.0
Please direct comments on this JSR to: jsr-82-comments@jcp.org
  
 
Specification Lead
Tim Thompson   Motorola 
 
Expert Group
Dawson, Peter   Ericsson Inc.   Extended Systems
IBM   Knudsen, Knud Steven   Mitsubishi Electric Corp.
Motorola   Nokia Corporation   Parthus Technologies PLC.
Research In Motion, LTD (RIM)   Rococo Software   Sharp Labs of America
Smart Fusion   Smart Network Devices GmbH   Sun Microsystems, Inc.
Symbian Ltd   Telcordia Technologies, Inc.   Threatt, Brad
Vaultus, Inc.   Zucotto Wireless
 

Updates to the Original JSR

The following updates were made to the original proposal:

2007.01.23: Maintenance Lead changed from Michael Milikich to Tim Thompson.

Maintenance Lead: Tim Thompson

E-Mail Address: timthompson@motorola.com

Telephone Number: +1 512 427 7365

Fax Number: +1 512 427 7365

2005.09.16: Maintenance Lead changed from Ravi Viswanathan to Michael Milikich.

Maintenance Lead: Michael Milikich

E-Mail Address: mike.milikich@motorola.com

Telephone Number: +1 512.996 4216

Fax Number: +1 512.895.3798

Original Java Specification Request (JSR)

Identification | Request | Contributions

Original Summary: Bluetooth is an important emerging standard for wireless integration of small devices. The specification will standardize a set of Java APIs to allow these Java-enabled devices to integrate into a Bluetooth environment.

Section 1. Identification

Submitting Participant (Spec Lead): Motorola

Name of Contact Person: Bala Kumar

E-Mail Address: c.bala.kumar@motorola.com

Telephone Number: +1 512.895.6559

Fax Number: +1 512.895.3798

Co-submitting Participant: Sun Microsystems Inc.

Name of Contact Person: Graham Hamilton

E-Mail Address: kgh@eng.sun.com

Telephone Number: +1 408.863.3000

Fax Number: +1 408.863.3195

List of Participants who endorse this JSR and plan to participate in the Expert Group:


IBM
Motorola
Nokia
Research in Motion
Sun
Symbian
Zucotto


Section 2: Request

2.1 Please describe the proposed Specification:

Bluetooth is an important emerging standard for wireless integration of small devices. The specification will standardize a set of Java APIs to allow these Java-enabled devices to integrate into a Bluetooth environment.

This spec will include basic support for, at least, the following Bluetooth protocols: RFCOMM, OBEX, and Service Discovery protocols. Additional protocol support may be added in future versions. The spec is primarily targetted at native Bluetooth protocols. (There are existing Java IP APIs which can be used to access IP networks from IP enabled Bluetooth devices.)

The Java APIs for Bluetooth are targeted at devices characterized as follows:

  • 512 K minimum total memory available (ROM/Flash and RAM). Application memory requirements are additional.
  • Bluetooth network connection.
  • Compliant implementation of the J2ME Connected Limited Device Configuration (see JSR-000030 J2ME Connected Limited Device Configuration).
The specification will define the APIs such that it will be extensible to other Bluetooth protocols which exist today (i.e. Home RF), or that might come about in the future. In addition, the APIs will be specified in a way to allow layering for more capable Java platforms such as the CDC, J2SE, and J2EE.

2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)

J2ME.

It is envisaged that the Java APIs for Bluetooth will be based on the Generic Connection Framework defined in the J2ME Connected Limited Device Configuration (CLDC) and will use the existing I/O classes of CLDC.

It is expected that the Java APIs for Bluetooth will often be used in conjunction with the Mobile Information Device Profile (MIDP). However, it is intended that the APIs should only depend on standard CLDC APIs, and should not require MIDP.

2.3 What need of the Java community will be addressed by the proposed specification?

This will provide standard Java APIs so that Java applications can be developed for the Bluetooth environment.

2.4 Why isn't this need met by existing specifications?

There are currently no standard Java APIs for the Bluetooth protocols.

2.5 Please give a short description of the underlying technology or technologies:

Bluetooth is an important emerging standard for connecting small hardware devices, such as cell-phones, pagers, headphones, etc.
  • The RFCOMM protocol provides basic stream connections between devices.
  • The OBEX protocol provides support for object oriented exchanges, and is the basis for higher level profiles, such as synchronization and file transfer.
  • The Service Discovery Protocol allows Bluetooth devices to find one another and to discover each other's services.

2.6 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)

None defined at present. Possibly "javax.microedition.bluetooth".

2.7 Does the proposed specification have any dependencies on specific operating systems, CPUs, or I/O devices that you know of?

These APIs will depend on the presence of a Bluetooth I/O device.

2.8 Are there any security issues that cannot be addressed by the current security model?

None anticipated. This specification will follow the existing Bluetooth security model.

2.9 Are there any internationalization or localization issues?

None anticipated.

2.10 Are there any existing specifications that might be rendered obsolete, deprecated, or in need of revision as a result of this work?

No.

Section 3: Contributions

3.1 Please list any existing documents, specifications, or implementations that describe the technology. Please include links to the documents if they are publicly available.

The Bluetooth Specification

3.2 Explanation of how these items might be used as a starting point for the work.

The Bluetooth Specification defines the protocols that must be supported.

 
Sun Microsystems
What's New
JSRs
JCP Procedures
Community Resources
Participation
Press & Success
What is the JCP