Bluetooth SIG with nRF52832

[m.hendelja]

Hi, our company one new product using you nRF52832. We already prepared everything for CE (RED ) and FCC certification process. Only thing that is unclear is Bluetooth SIG.

We are using you nRF52832 with soft device v5.0.0 with our PCB antenna, that was made by your reference design.

1)What do we need to do to comply with Bluetooth SIG standards? That includes Bluetooth trademark name.

2)If we don't want to use Bluetooth name in any of our datasheet, can we bypass SIG fee?

3. We are developing our devices for other companies, will those companies need to register by SIG as well? If so, do we need to register in SIG, or only they?

4. What are we even paying with SIG registration?

5. If we make any antenna that isn't made by reference design, is it possible that you can review it so that it's easier for us to certificate it?

Thank you for your time, hopefully you can help us with this questions, and it will be useful for other users.

[bjorn-spockeli]

Q1: In order if you're using our nRF52832 SoC and the S132 v5.0.0, then they are already pre-qualified and you will only need to declare your product with the Bluetooth SIG, as explained here.

Q2: No, Bluetooth is a licensed technology, so in order to obtain the license you will have to become a member of the Bluetooth SIG. As a member of the Bluetooth SIG you are obligated to pay all membership, declaration, enforcement and other fees set by Bluetooth SIG. This is clearly stated in the Bluetooth license agreements, found here.

Q3: No, if you're developing products for a 3rd party, that intend to sell/market these devices as Bluetooth devices, then its the 3rd party that should declare/qualify the products with the Bluetooth SIG. This is of course something that you may do on behalf of the 3rd party.

Q4: Again, Bluetooth is a licensed technology, so you're paying the Bluetooth Listing fee to use the technology as well as the use of the Bluetooth trademark and logo.

Q5: Yes, we will review your shematics and hardware layout as well as perform tuning of the RF circuitry once we are satisfied with your layout. We offer this service free-of-chare to our customers through our Mypage Support portal.

[Aakash MALVIYA]

Hello Sir, I have a similar question please answer my question

Q: We are using 

IC: nRF52832
Soft Device: s132_nrf52_6.1.1_softdevice.hex
Modified PCB Antenna (very different from the reference design in the datasheet)
other ICs circuitry on PCB (not related with Bluetooth)

for Bluetooth SIG Qualification two paths mentioned on this official page 

https://www.bluetooth.com/develop-with-bluetooth/qualification-listing/  

-----------------------------------------------------------------------------------------------------

Path 1: Qualification Process with No Required Testing

If you are:

Using another member organization’s qualified Bluetooth End-Product or Subsystem in your product without changes or additions to the Bluetooth capabilities
Purchasing a product manufactured by a third party and distributing it with your company’s name or logo
Creating combinations involving only qualified Bluetooth Subsystem Products and/or qualified Bluetooth End Products provided no design changes were made during the combination

Path 2: Qualification Process with Required Testing

If you are:

Creating any product or combination other than those involving only qualified Bluetooth Subsystem Products and/or qualified Bluetooth End-Products

-----------------------------------------------------------------------------------------------------

which path I should choose path 1 or path 2 since we have modified the antenna and also you mentioned  

bjorn-spockeli said:

Q1: In order if you're using our nRF52832 SoC and the S132 v5.0.0, then they are already pre-qualified and you will only need to declare your product with the Bluetooth SIG, as explained here.

so I am confused. Please tell me path 1 or path 2.

After reading the answer on https://devzone.nordicsemi.com/f/nordic-q-a/34028/bluetooth-sig-qualification---timelines-ics . I guess we need to choose path 2.

[bjorn-spockeli]

From a Bluetooth perspective you only need to choose path 2 if you are modifying the PHY , Host or Controller parts of the Bluetooth protocol stack or modifying one of the Bluetooth SIG services( 16bit UUID). So if you are  S132 v6.1.1 SoftDevice on a nRF52832 and use the Bluetooth SIG services in our SDK unmodified, then you can choose path 1. 

The layout of the PCB and the RF frontend will have to be tested according to FCC/ETSI or any other applicable teleregulatory requirements. 

[Aakash MALVIYA]

Thanks for the answer.

One more small question just confirming. it is very important for me. Please answer this
Q: I have a custom Bluetooth service but I haven't modified any of the Bluetooth SIG services ( 16bit UUID ) so then can I still choose path 1?

[bjorn-spockeli]

Yes, you do not need to qualify custom services if they use a 128-bit UUID. So in that case you can go with Path 1: Qualification Process with No Required Testing.

[Aakash MALVIYA]

Thank you very much for the Info.