MCPC-TR-002 Hands-Free Profile 1.5 Application Guideline ...

©Copyright 2006-2011 Mobile Computing Promotion Consortium (MCPC)MCPC TR-002 Hands-Free Profile 1.5 Guideline Version 1.51 Appendix A2. Phonebook transfer features of the cellular phoneRegarding the phonebook transfer of the cellular phone, the following features shall be supported as theOBEX Client/Server operations. This table shows which feature shall be Mandatory(M), Option(O), Not-Recommended(N/R) or Not-Applied(N/A). If the cellular phone does not have phonebook storing ability, itssupported feature is N/A.“OBEX Authentication” in the table below is a kind of certifying operation in order to identify whether theremote device is the correct target requested to connect when OBEX is initiated. The details of OBEXAuthentication are described in the next section.IrMCLevelOBEX Authentication(Note-1)Support OperationOBEXClientSupportOBEXServerSupportLevel 1 (Note-1)OBEX PUT object in InboxO N/R M MLevel 2OBEX PUT Entire Object StoreM O M MLevel 2N/RM OOBEX GET Entire Object Store(Note-3)MLevel 3N/RM OOBEX GET/PUT Objects by Static Indices(Note-4)OLevel 4OOBEX GET/PUT Objects by Unique Indices, M M(Note-2)Change Log Support, Change Counter SupportONote-1 Regarding OBEX Authentication,- Level 1: Object transfer with an indefinite device. OBEX Authentication is not recommendedto operate in this case.- Level 2/3: Object transfer between devices of same user. OBEX Authentication isrecommended to operate in this case. (Refer to IrMC Errata 990714 No.5)- Level 4 is based on the Synchronization Profile Specification of Bluetooth SIG. OBEXAuthentication shall be operated.Note-2 When Synchronization is realized, the Server shall support OBEX Authentication. However, theClient features so that the cellular phone initiates OBEX Authentication might be Optional.Note-3 Since supporting the PUT Client features enables entire object transfer and providing both thePUT/GET Client features makes user operations complicated, OBEX Authentication is notrecommended to support for Level 2.Note-4 Since providing the PUT/GET Client features with specified Static Index makes user operationscomplicated, OBEX Authentication is not recommended to support for Level 3.Note-5 When Level 1 is initiated, input value in the Name header of transfer objects shall avoid onewhich can be confused with Level 2 object name, such as “pb.vcf” etc.3. OBEX AuthenticationThe cellular phone shall support OBEX Authentication. During OBEX session establishment, the cellularphone shall execute Authentication Sequence specified in the section 3.1 and use Authentication Keyspecified in the section 3.2.4