7.2.6 Communication
Communication covers establishing connections to other devices via specific
Bluetooth profiles or protocols. Bluetooth connections established using this API are
based on the following three protocols:
•
RFCOMM
•
L2CAP
•
OBEX
Additionally, other profiles can be built upon these three basic protocols, but the pro-
files would have to be emulated by the MIDlet suite.
The implementation must support opening a connection with either a server connec-
tion URL or a client connection URL, with the default mode of READ_WRITE.
Serial Port Profile (SPP)
General Rules:
•
SPP uses RFCOMM as its protocol.
•
Only one RFCOMM session can exist between any pair of devices at any
time.
•
Negotiation of connection parameters and flow control between two
Bluetooth devices must be handled automatically by the SPP connection
implementation.
•
A SPP server application must initialize the services it offers and register
those services in the SDDB.
•
Before an SPP client can establish a connection to an SPP service, it
must discover that service via service discovery.
•
A service discovery is not required if the SPP service had been
discovered previously.
Object Exchange (OBEX)
OBEX is a protocol used for "pushing" and "pulling" objects (i.e. files or data) from
one device to another. OBEX is not limited to Bluetooth only. OBEX can be used over
Bluetooth, IrDA, and USB.
Java ME Developer Guide
Chapter 7 - JSR-82 - Bluetooth API
[44/201]
DRAFT - Subject to Change