This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Cant figure out steps to certify BLE module with NRF51822, info incomplete.

Hello, we have finished all prototyping with BLE modile from Taiyu Tuden, this module: https://www.yuden.co.jp/wireless_module/document/datareport2/en/TY_BLE_EYSGJNZ_DataReport_V1_9_20180530E.pdf

And according to their documentation they have all necessary tests done for certification however I cannot get straight and complete information so I have to ask maybe someone can help here.

According to datasheet, in order to fully comply to law and start selling product in USA, Europe, and Canada, product needs to be certified by Bluetooth SIG (if I understand correctly)

And again, according to datasheet, certification needs to be provided for following layers:

And certification happening by registering with Bluetooth SIG, providing them QDID for above mentioned layers along with copy of lab tests and they issue a "go" to start selling product, right?

I have QDID from BLE module manufacturer (Taiyo Yuden), which is what called 'PHY" in the chart above, and I also have all related copies of tests from manufacturers.

The link and Host layers need to be provided by Nordic Semiconductors, we built our code with NRF51, soft device is 130 v2.1, and I found these two QDIDs, are they correct?

  • S13x nRF5x v2.0.0 host layer: 79303
  • S13x nRF5x v2.0.0 link layer: 65785

So if those QDIDs are correct, where can I get Profile QDID? 

Do I need anything else to start selling our product?

Thank you, any help is appreciated as I find it quite confusing to understand what exactly needs to be done.

Parents
  • You can find the QDID's for the nRF51 series in the infocenter.

    The separate components, link and host layers, you refer to are outdated, so you must refer to one of the the qualified designs you find in the link above. 

    You'll combine this with the RF-PHY QDID from Taiyo Yuden for this specific module. 

    For the profile QDID, go to https://launchstudio.bluetooth.com/listings/search, clock advanced search and fill out "Nordic Semiconductor" as the Company and "Profile Subsystem" in the Product Type.

    We do not have an official document for the Profile subsystem, but here is a list i made:

    Most services in our SDK are qualified as part of our profile subsystem. You can see the qualified services by looking at the end product listing:

    44613

    HID Service

    HID over GATT Profile

    45222

    Health Thermometer Profile/Service

    Device Information Service (use the newer version)

    Immediate Alert Service

    Link Loss Service

    Proximity Profile

    Tx Power Service

    Heart Rate Profile (Sensor)

    Blood Pressure Profile/service

    Battery Service (use the newer version)

    Running Speed and Cadence Profile/Service

    49943

    Device Information Service

    Alert Notification Profile

    Battery Service

    Glucose Profile/Service

    Cycling Speed and Cadence Profile/Service

    60576

    Heart Rate Profile (collector)

    70915

    Time Profile

    You can combine components from the different profile subsystem QDID's. The service interfaces is the same across SDK versions, so not depending on the SDK version. If we change the service interface we will re-qualify it (if the change require re-qualification that is), this means you should use the latest id for services listed in multiple subsystem (battery and Device information service). For SDK 10 BAS is listed in 49943.

    I hope this clarifies things.

Reply
  • You can find the QDID's for the nRF51 series in the infocenter.

    The separate components, link and host layers, you refer to are outdated, so you must refer to one of the the qualified designs you find in the link above. 

    You'll combine this with the RF-PHY QDID from Taiyo Yuden for this specific module. 

    For the profile QDID, go to https://launchstudio.bluetooth.com/listings/search, clock advanced search and fill out "Nordic Semiconductor" as the Company and "Profile Subsystem" in the Product Type.

    We do not have an official document for the Profile subsystem, but here is a list i made:

    Most services in our SDK are qualified as part of our profile subsystem. You can see the qualified services by looking at the end product listing:

    44613

    HID Service

    HID over GATT Profile

    45222

    Health Thermometer Profile/Service

    Device Information Service (use the newer version)

    Immediate Alert Service

    Link Loss Service

    Proximity Profile

    Tx Power Service

    Heart Rate Profile (Sensor)

    Blood Pressure Profile/service

    Battery Service (use the newer version)

    Running Speed and Cadence Profile/Service

    49943

    Device Information Service

    Alert Notification Profile

    Battery Service

    Glucose Profile/Service

    Cycling Speed and Cadence Profile/Service

    60576

    Heart Rate Profile (collector)

    70915

    Time Profile

    You can combine components from the different profile subsystem QDID's. The service interfaces is the same across SDK versions, so not depending on the SDK version. If we change the service interface we will re-qualify it (if the change require re-qualification that is), this means you should use the latest id for services listed in multiple subsystem (battery and Device information service). For SDK 10 BAS is listed in 49943.

    I hope this clarifies things.

Children
  • Thank you very much for detailed information and help, that does spill more clarity on this matter for me: I do have a follow up question though:

    We only use Nordic UART service so this is how I sun it up, please correct if wrong and there is also a question below:

    1. We will need PHY QDID from BLE module manufacturer - CHECK

    2. For Link and Host layers there is one QDID to be used and in order to determine which one I first need to determine which IC revision we have using this matrix

    Then after determined that we will use this matrix to determine proper QDID

    3. Now we need to determine which QDID to use for profile, and that is where I have follow up question: I used the search as you suggested and 8 listings have been returned by search, illustration below.

    We only use Nordic UART in our code, used SDK v12, Soft Device 130, chip is nRF51822, do we need any of these QDIDs at all?  I mostly asking because I simply do not know not can fully understand profile QDID is so I am hoping you can just point to specific one I can use?

     .

    4. And then it seems after these QDIDs have been determined that is all it take to get listed in SIG and have approval to go to market? 

    Thanks again.

  • Yep, that seems correct. You don't need a profile subsystem for the Nordic UART service.

Related