Question for setting IO capability parameter for RegisterAgent

Question for setting IO capability parameter for RegisterAgent

[Xian Pan]

Hi,

I confuse the relationship between the 4 pairing mode in SSP with the IO capability parameter for the agent. From the agent-api.txt file, the capability parameter can have 5 values: DisplayOnly, DisplayYesNo, KeyboardOnly, NoInputNoOutput and KeyboardDisplay. I think there are only 4 pairing mode in SSP: just works, numeric comparison, out of band, and passkey entry. How the 5 IO capabilities can map to those 4 pairing modes?

Thanks a lot.

BEST
Xian

Re: Question for setting IO capability parameter for RegisterAgent

[Johan Hedberg]

Hi Xian,

On Wed, Dec 19, 2012, Xian Pan wrote:
> I confuse the relationship between the 4 pairing mode in SSP with the
> IO capability parameter for the agent. From the agent-api.txt file,
> the capability parameter can have 5 values: DisplayOnly, DisplayYesNo,
> KeyboardOnly, NoInputNoOutput and KeyboardDisplay. I think there are
> only 4 pairing mode in SSP: just works, numeric comparison, out of
> band, and passkey entry. How the 5 IO capabilities can map to those 4
> pairing modes?

Low Energy SMP based pairing introduces the additional KeyboardDisplay
IO capability. If you want to support LE it's recommended you provide
that as your agent capability and BlueZ will then automatically
downgrade it to DisplayYesNo for BR/EDR (SSP) pairing and use it as is
for LE SMP pairing.

Johan

Re: Question for setting IO capability parameter for RegisterAgent

[Marcel Holtmann]

Hi Johan,

> > I confuse the relationship between the 4 pairing mode in SSP with the
> > IO capability parameter for the agent. From the agent-api.txt file,
> > the capability parameter can have 5 values: DisplayOnly, DisplayYesNo,
> > KeyboardOnly, NoInputNoOutput and KeyboardDisplay. I think there are
> > only 4 pairing mode in SSP: just works, numeric comparison, out of
> > band, and passkey entry. How the 5 IO capabilities can map to those 4
> > pairing modes?
> 
> Low Energy SMP based pairing introduces the additional KeyboardDisplay
> IO capability. If you want to support LE it's recommended you provide
> that as your agent capability and BlueZ will then automatically
> downgrade it to DisplayYesNo for BR/EDR (SSP) pairing and use it as is
> for LE SMP pairing.

we should mention that in the documentation.

And additionally that "" maps to DisplayYesNo for BR/EDR and
KeyboardDisplay for LE.

Regards

Marcel

Re: Question for setting IO capability parameter for RegisterAgent

[Xian Pan]

Hi Johan,

Thanks for your help. It is more clear now. The 5 io capability is related to low energy smp. And the first 4 IO capability parameters are the same as the values for SSP.
And the DisplayYesNo IO capability can support the numeric comparison mode in SSP.

right?
Thanks a lot.

BEST
Xian


On Dec 20, 2012, at 2:55 AM, Johan Hedberg wrote:

> Hi Xian,
> 
> On Wed, Dec 19, 2012, Xian Pan wrote:
>> I confuse the relationship between the 4 pairing mode in SSP with the
>> IO capability parameter for the agent. From the agent-api.txt file,
>> the capability parameter can have 5 values: DisplayOnly, DisplayYesNo,
>> KeyboardOnly, NoInputNoOutput and KeyboardDisplay. I think there are
>> only 4 pairing mode in SSP: just works, numeric comparison, out of
>> band, and passkey entry. How the 5 IO capabilities can map to those 4
>> pairing modes?
> 
> Low Energy SMP based pairing introduces the additional KeyboardDisplay
> IO capability. If you want to support LE it's recommended you provide
> that as your agent capability and BlueZ will then automatically
> downgrade it to DisplayYesNo for BR/EDR (SSP) pairing and use it as is
> for LE SMP pairing.
> 
> Johan

Re: Question for setting IO capability parameter for RegisterAgent

[Johan Hedberg]

Hi Xian,

First of all, please don't top-post. It's particularly confusing when
mixed with inline quoting (which is the only quoting style you should
use on this list).

On Thu, Dec 20, 2012, Xian Pan wrote:
> Thanks for your help. It is more clear now.

I'm glad I could help.

> The 5 io capability is related to low energy smp. And the first 4 IO
> capability parameters are the same as the values for SSP.
> And the DisplayYesNo IO capability can support the numeric comparison
> mode in SSP.
> 
> right?

Right.

Johan