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

More documents

Recommendations

Info

©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
©Copyright 2006-2011 Mobile Computing Promotion Consortium (MCPC)MCPC TR-002 Hands-Free Profile 1.5 Guideline Version 1.51 Appendix A6.4 3.1 Authentication Sequence“Normal Authentication” allows IrMC Level 1/2/3 OBEX operations. This enables accessing data in“telecom/####” except “/luid/#####”. “Normal Authentication” shall be used for Level 2/3 OBEXAuthentication when the cellular phone is the Client.When the PUT Client/Server transfers only one object, it is not needed to execute OBEXAuthentication. However, when the remote device requests OBEX Authentication, the local device shallrespond with “Normal Authentication”. An example of “Normal Authentication” (PUT operation) is shownbelow. The details shall be referred in IrOBEX version 1.2, IrDA Object Exchange Protocol version 1.2,Infrared Data Association.Example. Normal Authentication (PUT operation)1 Client2 Server3 Client4 Server5 Client6.4.1.1.1.1 PUTRequest6 Server 6.4.1.1.1.3 PUT Responsew/ one object1 st Connect Requestw/ Authentication Challengew/o Target header1 st Connect Responsew/ Authentication Challenge2 nd Connect Requestw/ Authentication Response2 nd Connect Responsew/ Authentication Complete6.4.1.1.1.2 PUTRequestw/ “teexcept “telec“#####” represents any object name.5
Page 7 and 8:
©Copyright 2006-2011 Mobile Comput
Page 9 and 10:
Page 11 and 12:
Page 14 and 15:
Page 16 and 17:
Page 19:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 46 and 47:
Page 48 and 49:
Page 50 and 51:
Page 52 and 53:
Page 54 and 55:
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Page 62 and 63:
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
Page 74 and 75:
Page 76 and 77:
Page 78 and 79:
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101: ©Copyright 2006-2011 Mobile Comput
Page 160: ©Copyright 2006-2011 Mobile Comput
show all

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

Create successful ePaper yourself

Delete template?

Save as template?