RSCP collector with nrf52840 and ncs

[Bibop]

We are currently developing a nrf52840 firmware which should support RSCP as collector.

Setup:

nrf52840

ncs2.9 with

Q322804 NCS Host

Q331587 SoftDevice Controller Subsystem

Now we run into some unresolvable ics issues with RSCP as collector:

RSCP 2_2 "Profile supportted over LE" is used

which leads to

RSCP 13_4 "No security requirements" being mandatory

which has a Inter Layer Dependency to

GAP 37b_4 "No security requirements".

However the currently used ncs 2.9.0 nor the latest 3.2.x enable this.

Are we correct to assume that the current ncs without requalification/testing cant be used to implement RSCP as collector?

We already contacted SIG for this matter and are still waiting for their response.

[Vidar Berg]

Hello,

Bibop said:

However the currently used ncs 2.9.0 nor the latest 3.2.x enable this.

I don't see any characteristics in this service that is set to require encryption or authentication: 

https://github.com/nrfconnect/sdk-nrf/blob/9b81efa54e8390011739d482463e793fdffbfe79/subsys/bluetooth/services/rscs.c#L249 

Not sure if I am missing something? 

Best regards,

Vidar

[Bibop]

Thanks for the quick answer,

you pointed to the RSC Sensor implementation, however we are implementing a RSC Collector and per ICS Spec we have to set RSCP 13_4 as this is mandatory which requires the ICS GAP37b_4 which the prequalified ncs GAP does not have.

On a side note RSCP collector even requires 13_5 "Unauthenticated no MITM protection" and 13_6 "Authenticated MITM protection" as mandatory. 

Maybe I am missing something, My understanding is that the RSCP collector needs to be able to support No security, unauthenticated and authenticated connections to the RSCP sensor to fulfil the RSCP spec. Now my problem is not that i cant implement this, the problem is purely from a qualification standpoint as the ICS 13_4 requires GAP 37b_4 which the ncs doesnt provide.

Im very grateful for any furhter guidance, best regards,

Christoph

[Vidar Berg]

Thanks for the clarification, I was a bit too quick to reply earlier. I am checking internally now with people who has more experience with bluetooth qualification. At the moment the requirements seem a bit contradictory to me. Will update as soon as I know more.

[Vidar Berg]

It turns out we should have selected GAP37b_4 in our qualification listing, but haven’t done so until now. We will start doing this from the v3.3.1 release (Note: we cannot add this to existing listings, it requires re-doing the qualification). It is a bit surprising that this does not seem to have come up before. I hope updating to SDK v3.3.1 is an option for you once it is released.