• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 55 subscribers
  • Views 2540 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Licensing Requirements for Bluetooth Low Energy / Smart

sunny singh
Prodigy 10 points

Other Parts Discussed in Thread: CC2540, CC2541

In the Fees Section the Bluetooth Sig lists it’s fees to include

https://www.bluetooth.org/Technical/Qualification/fees.htm

One (1) Year Profile Tuning Suite (PTS) License with Unlimited Users

The PTS Adopter Company-Wide license enables adopter members of a given company to use the PTS as long as they have a valid login username and password with the Bluetooth SIG and thus have access to the www.bluetooth.org website.

$7,500.00

Our project involves using the standard published Profiles for cc2540 that have been qualified by TI.

Is it still necessary to obtain a subscription for the Profile Testing Suite even if use a “standard” profile ?

Secondly, since the standard profile is being used, do you need a GATT 4.0 profile ?

GATT 4.0 (Low Energy)

Test suite for verification of Generic attribute profile 4.0. The test suite runs on Low Energy only and also requires a CSR Bluetooth Low energy radio. Adopter members, please note that the Profile Tuning Suite is required when using this protocol test suite and licensed separately. This is a one year license that has to be renewed after expiration.

$750.00

Finally, what about

Security Manager 4.0 (Low Energy)

Test suite for verification of Security Manager 4.0. The test suite runs on Low Energy and also requires a CSR Bluetooth Low energy radio. Adopter members, please note that the Profile Tuning Suite is required when using this protocol test suite and licensed separately. This is a one year license that has to be renewed after expiration.

$750.00

Sunny

 

  • 0
    Prodigy 50 points

    I am wondering about this as well, so I hope that posting here may help the question get answered by someone knowledgeable.

    I am developing a bluetooth LE module and would also like to understand the licensing and regulatory requirements - is there a good reference?  My searches only lead me to this unanswered question.

  • 0 in reply to Tyler Bryant
    TI__Guru 57865 points

    Hi Tyler,

    When using our CC2540 or CC2541 with our stack, you can use our existing certifications to create an End Product Listing (EPL) on bluetooth.org. The sub-system certifications you'll need to refer to are;

    • B016552: TI BLE Controller Subsystem – Core 4.0
    • B017183: TI BLE HOST Subsystem
    We are working on a guide for this which we will post on the wiki as soon as possible.
    Best Regards
  • 0 in reply to J Lindh
    Prodigy 50 points

    Thanks Nick, and I will keep an eye out for the guide on the wiki.

  • 0 in reply to J Lindh
    Prodigy 10 points

    Hi Nick,

    How is this guide going?  

    I am particularly interested in whether any bluetooth-specific RF qualification is needed (i.e. other than EMC).

    Strangely, I notice that most of the related EPL listings at bluetooth.org use only one of these QPLs.

  • 0 in reply to Timothy Fosdike
    TI__Guru 57865 points

    Hi Timothy,

    A quick guide (using our QDIDs) can be found here. If you want to qualify your own design I suggest you read about the qualification in the Bluetooth SIG website, they have some good guides.

    Generally, it's recommended to do the RF 4.0 Tests (TRM-LE and RCV-LE) even if you use a Controller Subsystem. I think that typically costs up to $2500 but a test house could give you a quote on that. I can recommend AT4 Wireless or 7Layers.

    Best Regards.

  • 0 in reply to Timothy Fosdike
    TI__Guru 57865 points

    Timothy Fosdike said:
    I notice that most of the related EPL listings at bluetooth.org use only one of these QPLs.

    An EPL must include, at minimum, a Host Subsystem QDID and a Controller Subsystem QDID unless the product functions as a Host only (e.g. Operating System) or Controller only (e.g. USB Dongle).

    Best Regards