Obex Formats; Obex File System Overview - Ericsson T39 At Command Reference

Hide thumbs Also See for T39:
Table of Contents

Advertisement

6 OBEX Formats

6.1 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 (un-capitalized), and it is the subject of this section.
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 shall always include the path information.
The paths are specified in the IrMC specification from IrDA.
Filename
Device Info
telecom/devinfo.txt
telecom/rtc.txt
Phone Book
telecom/pb.vcf
telecom/pb/luid/.vcf
telecom/pb/0.vcf
telecom/pb/###.vcf
telecom/pb/luid/*.vcf
telecom/pb/info.log
telecom/pb/luid/###.log Change log
telecom/pb/luid/cc.log
Calendar
telecom/cal.vcs
telecom/cal/luid/.vcs
telecom/cal/###.vcs
Telecom/cal/luid/*.vcs
Telecom/cal/info.log
Telecom/cal/luid/###.log Change log
Telecom/cal/luid/cc.log
Description
Information hardware
version, software version,
serial number, etc.
Character sets
The Real Time Clock
Object contains the current
date and time of the device
Level 2 access (Access
entire phonebook database)
Add new entry
Own business card
Level 3 static index access GET/PUT
Level 4 unique index access GET/PUT
Supported properties and
memory info
Change counter
Level 2 access
Add new entry
Level 3 static index access GET/PUT
Level 4 unique index access GET/PUT
Supported properties and
memory info
Change counter
Supported operations
GET
GET/PUT
GET/PUT
PUT
GET/PUT
GET
GET
GET
GET/PUT
PUT
GET
GET
GET
OBEX Formats
205

Advertisement

Table of Contents
loading

Table of Contents