Find JSRs
Submit this Search


Ad Banner
 
 
 
 
JSRs: Java Specification Requests
JSR 82: JavaTM APIs for Bluetooth

Updates to the Original JSR

The following updates were made to the original proposal:

2013.04.15: The JCP Member acting as Maintenance Lead has changed from Aplix to Oracle.

Maintenance Lead: Jens Paetzold, Oracle

E-Mail Address: jens.paetzold@oracle.com

Telephone Number: +49 89 46008 1248

Fax Number: -

2012.10.18: The person acting as Maintenance Lead has changed.

Maintenance Lead: David Chen

E-Mail Address: david@aplix.co.jp

Telephone Number: -

Fax Number: -

2012.08.24: The person acting as Maintenance Lead has changed.

Maintenance Lead: Lakshmi Dontamsetti

E-Mail Address: lakshmi@aplixcorp.com

Telephone Number: -

Fax Number: -

2011.06.08:
The person acting as Maintenance Lead has changed.

Maintenance Lead: Angus Huang

E-Mail Address: angus@aplixcorp.com

Telephone Number: -

Fax Number: -

2011.01.21:
The person acting as Maintenance Lead has changed.

Maintenance Lead: Mark Hood

E-Mail Address: hood@aplixcorp.com

Telephone Number: -

Fax Number: - 2009.11.05:
The person acting as Maintenance Lead has changed.

Maintenance Lead: Tim Renouf

E-Mail Address: tpr@aplix.co.jp

Telephone Number: +44 1483 246712

Fax Number: +44 1483 245140

2009.06.01: Maintenance Lead changed from Motorola to Aplix Corporation.

Maintenance Lead: Mark Freudenberg

E-Mail Address: mark@aplixcorp.com

Telephone Number: -

Fax Number: -

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.