Different Obex services inside a device are addressed via a so-called UUID. The UUID selects which component inside the device is supposed to handle the particular request. It is like the server address in some HTTP URL - only that the UUID is only a 16 byte number. Several standardised UUIDs, and thus services, exist for OBEX. For easier reference, these UUIDs also got names. In case of the sync UUID, the 16 byte UUID is actually the ASCII codes of the characters ‘IRMC-SYNC’. For others, like the FBS UUID, it is just some number.
ObexFTP main and default service, File Transfer Profile. Uses the Folder Browsing Service UUID.
OBEX without connection and UUID.
OBEX without UUID.
Useful to access the Telecom/IrMC objects. Uses the Telecom/IrMC Service UUID, “IRMC-SYNC”.
||telecom/devinfo.txt||Information hardware||GET|| ||
||telecom/rtc.txt||The Real Time Clock||GET||PUT||
||telecom/pb.vcf||Level 2 access||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|| ||
||telecom/cal.vcs||Calendar 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|| ||