drowning in numbers

Question

Hi, 
 we are late stage development on NRF52840 with sdk 15.0 and softdevice 6.0. The mind turns to certification. It all seems very complex and confusing 
 1) Do we need to be members of the bluetooth sig? 
 2) Do we need to qualify our products? 
 3) Do we need a company bluetooth Community ID and if so where would we use it? 
 4) We have a device information service on our product, do we need an IEEE OUI? Can we just take the current random mac and format the system id according to the standard? 
 5) Can we use a CUI instead of an OUI? 
 Cheers Paul

run_ar · Accepted Answer

1. Yes. But it's enough to be an adopter member: https://www.bluetooth.com/develop-with-bluetooth/join/membership-benefits/ 
 2. You need to create an end product listing: But you can reference the nordic qualified design. Which covers qualification for LL and HOST. You can also reference our profile subsystem if you are using any Bluetooth defined profiles. e.g. device information service. We usually recommend that you do an RF-PHY test unless you are using a module. Note that if you follow our reference design and layout you might be able to claim similarity to our RF-PHY component that is part of the qualified design, thus avoiding this test. 
 3. Maybe. Some services requires a company id. 
 4. Have you checked the profile specification? Seems most/all characteristics are optional. But might be required by another profile. 
 5. Not sure I know these acronyms, sorry.

drowning in numbers

Top Replies