SIG Qualification based on existing qualified NRF51822 with S130

[Ron]

Hey

I am working for the first time on qualification process with SIG, my device is nrf51822 and softdevice - S130 (version 2.0.2) and I understand that D030168 / QDID-80592 was qualified with version 2.0.0, (with the following statement “This qualification covers all device variants in the nRF51 series in combination with v2.x of the Sx3x SoftDevice stack”)

I have to specify whether I use qualified or altered versions of the following layers : GAP, ATT, GATT, LLACP, Security Manager Protocol, LE Link Layer and Low Energy RF Phy,

I would appreciate some insights on whether and what layers I have to qualify,

* since I use and added manufacturer specific data I assume I will have to qualify the GAP, but do I have to qualify the LE Link Layer? 

* I am using standard services (such as battery service) as well as my own custom services, I assume that I have to qualify my GATT, however I am not sure whether I should also re-qualify the ATT.

* My device is only a peripheral interacting with one central, and it is using just LE protocol so I think there is no need for Logical Link Control and Adaption Protocol?

* I assume that having my own custom hardware Antenna means I need to qualify my Phy layer.

* I assume that I do not have to qualify Security Manager Protocol if I do not use pairing or bonding?

Thanks!

 

[Andreas]

Hi,

 

If you refer to the end-product QDID you do not need to worry about the any component QDID.

 

* since I use and added manufacturer specific data I assume I will have to qualify the GAP, but do I have to qualify the LE Link Layer? 

 No. Changing the manufacturer specific data does not change anything from a compliance perspective, this is pretty much as intended.

 

* I am using standard services (such as battery service) as well as my own custom services, I assume that I have to qualify my GATT, however I am not sure whether I should also re-qualify the ATT.

 No, as above.

 

* My device is only a peripheral interacting with one central, and it is using just LE protocol so I think there is no need for Logical Link Control and Adaption Protocol?

If you have enabled this through configuring the Softdevice it is allowed.

 

 

* I assume that having my own custom hardware Antenna means I need to qualify my Phy layer.

 You should not qualify anything. List your product, refer to our QDID, test RF-PHY and save the logs.

 

* I assume that I do not have to qualify Security Manager Protocol if I do not use pairing or bonding?

Not needed.

 

Best regards,

Andreas

[Ron]

Hi Andreas,

Thank you for your response.

Andreas said:

If you refer to the end-product QDID you do not need to worry about the any component QDID

That is the link to the deceleration details https://launchstudio.bluetooth.com/ListingDetails/14825 , 

It is for an 'end product', but what exactly do you mean by 'not to worry about component QDID', If I use my own custom Antenna I should test it, is that not part of creating a new QDID? or will I be testing while maintain Nordic's QDID?

Does that also goes for the GATT? testing but not qualifying?

Andreas said:

refer to our QDID, test RF-PHY and save the logs.

Image below is part of the form on the SIG website (using launch studio) -"Qualification Project with required Testing",  Do you know if I am to mark the RF-PHY and GATT checkbox as "my own" or under Nordic existing QDID

Andreas said:

If you have enabled this through configuring the Softdevice it is allowed

I am not using LLACP at all, Do you happen to know how should I apply for qualification here since there is just options to state that I "use my own selection" or under Nordic's QDID..

Thanks again!

[Andreas]

Hi,

 

By referring to the end product QDID you inherit all the link-layer, GATT etc. listings, meaning these do not have to be tested or qualified. Using your own antenna does not change the stack behaviour, provided the PCB design is done properly and thus passes the RF-PHY tests. You should not test or qualify GATT.

 

With regards to your image, you should choose the different path: Qualification process with no required testing. 'Required testing' in this sense is a little ambiguous, I can understand the confusion.

 

 

Ron said:

I am not using LLACP at all, Do you happen to know how should I apply for qualification here since there is just options to state that I "use my own selection" or under Nordic's QDID..

 No, this is fine. As with all the other, use our end-product QDID only.

 

Best regards,

Andreas

[Ron]

Hi Andreas,

I appreciate your answers, 

Andreas said:

you should choose the different path: Qualification process with no required testing. 'Required testing' in this sense is a little ambiguous, I can understand the confusion

This is indeed very confusing, could you please clarify further, I am going through testing anyway, even if I don't chose the 'required Testing' ? 

what kind of tests? beside RF-Phy?

What is the difference between the testing in the two paths? if there are RF-Phy testing in both paths what is the difference or sense in that?

Have a great day and thanks again

[Andreas]

Hi,

 

Required testing in this sense is that you test the entire 'Bluetooth Module' HW+Stack against the entire TCRL, which e.g. is what we do with our Softdevice releases.

 

The no required testing can be chosen if (from the BT SIG site):

• 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

As per the name, RF-PHY testing is not required and not a part of the 'no required testing path'. We just recommend that you do it separately to ensure you have replicated our reference design (which is the qualified end product) that change its Bluetooth capabilities. A poorly done HW design will not change the stack behaviour, but can/will change the physical performance of the radio, and to what degree it is compliant with RF-PHY requirements.

 

Best regards,

Andreas

[Ron]

Hi

I am surprised to hear that adding my own Antenna will not require RF-PHY testing, because it does say 

Andreas said:

Using another member organization’s qualified Bluetooth End-Product or Subsystem in your product without changes or additions to the Bluetooth capabilities

Changing the Antenna is not "changes"? Also I was actually told specifically (by a regulatory expert, not from SIG) that changing the Antenna will require testing, But I am glad to hear this is not the case, I already have test results for my antenna, will sending it to them speed things up?

As for the software, Are you saying that there is nothing that my implementation would possibly do that will require me to go thought the testing path? (as long as I use the softdevice ofcourse) 

I have received a replies for inquiry from "Bluetooth SIG Team" that suggest that using standard services such as "Device Information" and "Battery" services will, however, require testing."

This is the email reply from the Bluetooth SIG Team:

What do you make of this answer? Is there a way around it? that also said that they dont care about my custom services, only the standard services, why would that be? 

Thank you again so much from your help!