User guide

Developers guidelines | AT commands
300 June 2010
OBEX Formats
OBEX file system overview
One of the most basic and desirable uses of the IrDA infrared communication
protocols is simply to send an arbitrary data object from one device to another and to
make it easy for both application developers and users to do so. This is referred to as
object exchange.
With the exception of Level 1 Information Exchange, whereby the objects are pushed
into a device inbox, the object names passed to OBEX PUT and GET operations
always include the path information.
The paths are specified in the IrMC specification from IrDA.
File name Description Supported operations
Device Info
telecom/devinfo.txt Information hardware version, software
version, serial number, and so on.
Character sets
GET
telecom/rtc.txt The Real Time Clock Object contains the
current date and time of the device
GET/PUT
Phonebook
telecom/pb.vcf Level 2 access (access entire phone
book database)
GET/PUT
telecom/pb/luid/.vcf Add new entry PUT
telecom/pb/0.vcf Own business card GET/PUT
telecom/pb/###.vcf Level 3 static index access GET/PUT
telecom/pb/luid/*.vcf Level 4 unique index access GET/PUT
telecom/pb/info.log Supported properties and memory info GET
telecom/pb/luid/
###.log
Change log GET
telecom/pb/luid/
cc.log
Change counter GET
Calendar
telecom/cal.vcs Level 2 access GET/PUT
telecom/cal/luid/.vcs Add new entry PUT
telecom/cal/###.vcs Level 3 static index access GET/PUT
Telecom/cal/luid/*.vcs Level 4 unique index access GET/PUT
Telecom/cal/info.log Supported properties and memory info GET
Telecom/cal/luid/
###.log
Change log GET
Telecom/cal/luid/
cc.log
Change counter GET