Motorola maxx V6 Draft Subject to Change 41/201, Bluetooth Control Center, Device Property Table

Java ME Developer Guide

Chapter 7 - JSR-82 - Bluetooth API

∙OBEX

￿OBEX is a separate API from the core Bluetooth API

(￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿) and is a part of the ￿￿￿￿￿￿￿￿￿￿ package.

In addition, the following Bluetooth profiles must be supported:

∙Generic Access Profile (GAP)

∙Service Discovery Application Profile (SDAP)

∙Serial Port Profile (SPP)

∙Generic Object Exchange Profile (GOEP)

7.2.2Bluetooth Control Center

The JSR-82 API requires that a Bluetooth Control Center (BCC) be in place to control the Bluetooth connection and be a repository for local device settings.

According to the API, the following are features the BCC must support:

∙A list of remote Bluetooth devices (not necessarily in the vicinity) that are already known to the local Bluetooth device

∙A list of remote Bluetooth devices (not necessarily in the vicinity) that are trusted by the local Bluetooth device

∙A mechanism to bond two devices trying to connect for the first time

∙A mechanism to provide authorization of connection requests

∙The base security settings of the local device, including the security modes defined in the Bluetooth specification

7.2.3Device Property Table

Table 9 lists the Motorola Bluetooth device properties for current products. These device properties must be available to the MIDlet suite.

Device Property	Description
bluetooth.api.version	The version of the Java APIs for Bluetooth wire-
	less technology that is supported. For this ver-
	sion it will be set to "1.0".
bluetooth.l2cap.receiveMTU.max	The maximum ReceiveMTU size in bytes suppor-
	ted in L2CAP. The string will be in Base 10 di-
	gits, e.g., "672". This value is product depend-
	ent. The maximum value is 64 Kb.
bluetooth.connected.devices.max	The maximum number of connected devices
	supported (includes parked devices). The string

DRAFT - Subject to Change [41/201]