User's Manual

Class 1 Bluetooth v2.0 Module
User’s Guide
Americas: [phone] Option 2
Europe: [phone]
Hong Kong: [phone]
www.lairdtech.com/bluetooth
78
CONN-GUIDE-BT730_v0.9
9. OBEX PROFILE COMMANDS
This section describes the OBEX implementation on BTM430/431 which allows performing the role of
‘Obex Push Client’ as illustrated in the diagram below.
Figure 24: OBEX Push client and server
The Obex Push profile implementation provides the capability to a host to act as an ‘Obex Push client’ to
a peer device providing an ‘obex push server’ profile.
An Obex Push client capability implies the ability to send and optionally receive a default file. The
Bluetooth Obex Push server profile specification describes the profile as one built on Obex Exchange
(OBEX) which is in turn built on SPP.
The Object Push Profile [3] describes the profile as having the three following features:
 Object Push – Mandatory
 Business Card Pull – Optional
 Business Card Exchange – Optional
This implementation only offers the Mandatory Object Push feature.
The implementation on BTM430/431 allows a host attached to the module to send and receive files and
to manipulate files and folders.
The format used in this document for describing this protocol is a series of message sequence charts with
accompanying notes as appropriate, which unambiguously convey how a host and the module shall
interact to perform the task.
9.1 Generic Notes and Guidance
In the message sequence charts the following abbreviations apply:
 <crlf> shall mean a two character sequence made up of the ASCII characters 0x0D (carriage return)
and 0x0A (line feed).
 <cr> shall mean a one character sequence made up of the ASCII character 0x0D.
 <lf> shall mean a one character sequence made up of the ASCII character 0x0A.
 <bd_addr> shall mean a 12 digit string consisting of only hexadecimal digits 0-9, A-F, and a-f.
 <filename> shall mean a string delimited by the “ character. For example, “hello.txt”.
 <foldername> shall mean a string delimited by the “ character.