12.07.2015 Views

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

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

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

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

©Copyright 2006-2011 Mobile Computing Promotion Consortium (<strong>MCPC</strong>)<strong>MCPC</strong> <strong>TR</strong>-<strong>002</strong> <strong>Hands</strong>-<strong>Free</strong> <strong>Profile</strong> <strong>1.5</strong> <strong>Guideline</strong> Version <strong>1.5</strong>1 Appendix A6.5 3.2 Authentication KeyUsers can setup the following Authentication Key.Session Key: 4 digits numeric key. The device of Server side requests the Session Key during“Normal Authentication”. The value of the Session Key shall be same between theClient and the Server. The Session Key is canceled during OBEX session release afterend of object transfer.Example. “Normal Authentication” sequence and the Session Key usageUser inputs:Session Key1234User inputs:Session Key1234ClientNormal Auth. Connect RequestH ( Time stamp : Private_key )- Unique value like serial No.- Hidden from a userAuth. Challenge ()H ( : 1234 ) Generate ""Refer to the Session Keyof the Client side.H ( : 1234 )Generate "c"Refer to the Session Key of theServer side.Generate "s"Auth. Response (c)If c=s, then OKOKServerAuthentication Complete6

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!