NOTICE: The Processors Wiki will End-of-Life on January 15, 2021. It is recommended to download any files or other content you may need that are hosted on processors.wiki.ti.com. The site is now set to read only.

How to Certify your Bluetooth product (如何认证你的蓝牙产品)

From Texas Instruments Wiki
Jump to: navigation, search

Back to Bluetooth SensorTag main page

为了能让你的BLE 产品能在欧洲以及北美市场销售, 你的最终产品必须遵守美国的FCC(Federal Communications Committee)的监管要求, 欧洲的R&TTE, 以及加拿大的IC (Industry Canada). In order to sell your Bluetooth low energy product in EU and on the North American market, your equipment needs to comply with the regulatory requirements of FCC (Federal Communications Committee), European Commission (R&TTE) and IC (Industry Canada). For a Bluetooth device there is also a need for Bluetooth Compliance and Certification. The Bluetooth Compatibility Certification aims to deliver a seamless user experience through the vast number of Bluetooth mobile devices that are available in the market.

FCC certification[edit]

Fcc logo black.png

Under Part 15 of the FCC rules, all electronic devices with a clock or oscillator exceeding 9 kHz need to be verified that they are not causing harmful radiated emissions. FCC Part 15 covers unintentional testing and evaluation as well as low power un-licensed transmitters. In addition, all transmitters must be registered and certified by the FCC to  ensure they are not causing harmful emissions and interference on regulated frequencies.


Section 15.209 of the radio contains general radiated emission limits that apply to all Part 15 transmitters using frequencies at and above 9kHz. Section 15.247 and 15.249 give more detailed information about the emission requirements in the unlicenced 2.4GHz ISM band.


There are two ways of getting a FCC certification, either directly from the FCC or through a TCB (Telecommunications Certification Body). For almost all devices one can chose either to use a TCB or FCC for the certification, the exception is when the equipment uses new technology or when the test methods are undefined or unclear – then FCC is the only party that can provide certification.

FCC ID[edit]

The FCC-ID is a unique identifier, 4-17 characters, for the equipment and consists of two elements, the Grantee Code and the Equipment Product Code. The Grantee code is a three character alphanumeric string representing the Grantee/Applicant. The Grantee Code always begins with an alphabetic character and does not contain the numbers one and/or zero. The Grantee Code is assigned by the Commission permanently to a company for authorization of all radio frequency equipment.The Product Code is the non-grantee code portion of the FCC ID that begins after the first three characters. The Product Code may include hyphens and/or dashes (-). The Product code shal consist of minimum 1 and maximum 14 characters. An example would be: FCC ID: ZAT2541SENSOR.
The FFC-ID must be permanently marked either directly on the transmitter, or on a tag that is permanently affixed to it. The FCC ID label must be readily visible to the purchaser at the time of purchase.

Documentation[edit]

The following information must be submitted for FCC certification:

  • Cover Letter
  • Test Report from Lab
  • User's Manual
  • Schematics with part list
  • Block Diagram
  • Photo of the Test Setup
  • Internal/External photos
  • FCC ID label and placement on device
  • Operational description

Product changes[edit]

There are several permissive changes (PC)/modifications that can be made to an RF device without the need for filing for a new equipment authorization, however changes to the basic frequency determining and stabilizing circuitry (including clock and data rate), frequency multiplication stages, basic modulator circuit or maximum power or field strength will always require a new FCC ID and a new equipment authorization to the FCC. There are 3 – three – classes of permissive changes:

  • Class 1: Changes that do not degrade the characteristics reported to the FCC and do not require a modification of the grant – No Filing is required
  • Class 2: Changes that degrade the performance reported to the FCC but are still in compliance with the limits and changes to the grant – Filing required
  • Class 3: Changes to software for a software defined/cognitive radio – Filing required

Class 1 changes could be changes on digital traces Please note that if there are no filing required there is a requirement to document the changes. If uncertain whether the change is a Class1 or Class 2 permissive change please consult with subject matter experts prior to asking the certification test house / TCB for guidance.

Class 2 changes could be a chip replacement of portions of the transmitter that performs some sub-functions such as an amplifier chip or for instance a oscillator chip. A class 2 change requires a description of the changes done and a re-test is needed to show that the devices are still in compliance and a test report showing compliance with the rules shall be provided to FCC. A class 2 change requires a filing to the FCC but the FCC ID will not changed.

Code Example[edit]

To see some code example used for FCC/ETSI test, have a look here

CE certification[edit]

CE logo.png

In order to CE Mark and place any radio equipment on the market in EU you need to demonstrate compliance with the R&TTE directive. CE marking is a mandatory conformance mark on products placed on the European market. A CE mark indicates that the manufacturer or its authorized EU representative has declared that the product or equipment complies with all applicable European Directives, and enables the free movements of product within the European market. The CE marking is a declaration by the manufacturer, importer, or the entity first placing the product on the market that the product conforms to the appropriate directives. This is confirmed by the legally binding signature on the Declaration of Conformity.


The R&TTE directive relies for its operation on Harmonized Standards developed by the recognized European Standards Organizations. These Harmonized Standards define technical characteristics which can be used to meet the essetnial requirements of the Directive, as:

  • Protection of health and safety
  • Electromagnetic compatibility
  • Effective use of the radio spectrum


For Short Range Devices operating in the 2.4GHz ISM band the relevant Harmonized Standards are::

  • EN 50371 - compliance to human exposure to electromagnetic fields'
  • EN 300 328 - radio equipment testing of data transmission equipment operating in the 2.4GHz ISM
  • EN 301 489 - electromagnetic compatibility


Download the Harmonized Standards for free at www.etsi.org.
There are several routes to demonstrate compliance with the R&TTE Directive, for most cases meeting with the requirements of the relevant Harmonized Standards will provide presumption of conformity required thus enabling you to sign a Declaration of Conformity with confidence. A certified test house will provide the necessary guidance and help required to place your radio product on the market.

Industry Canada (IC) certification[edit]

Industry Canada (IC) is the Canadian authorities for certifications and standards making. As for FCC certification can either be done through IC or a TCB. For an IC certification one is required to have a Canadian representative, and IC requires that a confirmation letter from the representative is submitted with the application.


IC-ID[edit]

As for equipment intended for the US market the radio/EVM needs to be marked with the IC-ID. The IC-ID consists of two pars; Company Number (CN) and a Unique Product Number(UPN) which is chosen by the manufacturer. To optain a CN number use the E-filling system, when submitted the required information an e-mail will be sent with the CN.

An excamble would be: IC: 451H-2541SENSOR


Documentation[edit]

The following information must be submitted for IC certification:

  1. A completed and signed original copy of Appendix A ― Application and Agreement for Certification Services;#a covering letter explaining the type of certification services requested and a brief description of the radio equipment;
  2. A completed and signed original copy of Appendix B ― Test Report Cover Sheet;
  3. A detailed test report meeting the technical requirements of the applicable Radio Standards Specification (RSS);
  4. A completed and signed copy of Appendix (A and B) or C of RSS-102 - Radio Frequency Exposure Compliance of Radiocommunication Apparatus (All Frequency Bands);
  5. Photographs and product literature of the new model;
  6. Achematic diagrams and block diagrams; and
  7. A drawing, sample or illustration of the product label.


There is no need for extra RF testing when applying for certification in Canada if the equipment is already certified by FCC and meets the following conditions:

  1. The test report must be less than one year old
  2. The test house must have their Test Site (OATS or Anechoic chamber) approved by IC
  3. A cross-reference table must be submitted with the test report to show that the equipment meets all of the applicable Canadian requirements.


Bluetooth certification[edit]

bSMART.png

In order to release a Bluetooth product to market, the solution need to be qualified.

  1. If a TI reference designs (CC2540EM, CC2541EM) is strictly followed and the profiles are not changed, the customers do not need to do certification again. They can do the End Product Listing (EPL) on SIG website for free.
  2. If you create your own proprietary profiles, it is optional for you to do certification.
  3. There is not a fine line to tell whether or not a additional certification is needed (For example RF test cases, which are strictly dependent on RF circuitry). Normally, it Should be up to a Bluetooth Qualification Expert (BQE) to tell. The BQE is normally from an authorized testing houses (such as 7Layers or AT4wireless).

Qualification Process

Qualification Process[edit]

Qualification Process

Initial Questions[edit]

  • Are you using a 3rd party qualified design? (Following CC2540EM or CC2541EM)
    • If YES, reuse TI Subsystems (See Qualified Design Listing section)
    • If NO, follow steps to qualify your own Bluetooth design
  • What product type are you using?
    • End Product, Subsystem, Component etc. Understanding intention and benefits of product types is Key.
  • Are you making any changes to the qualified design during implementation into your product?
    • If adding new functionality defined in adopted Specification (new PICS items) then new qualification is required
    • If simply referencing someone else's complete qualified design you may only need EPL


So there are basically two roads to take:

  1. If the design is qualified as a Subsystem product type, a new QDL/QDID is NOT required if the designs are implemented as originally qualified and are designed to combined with complimentary Subsystems in an End Product.  From Qualification perspective, only an EPL associated with the implemented Subsystems is required (no Qualification testing needed). 
  2. If a Member wishes to create a new QDL/QDID using Subsystems, the complete design must be reassessed to ensure it meets the current Qualification requirements.  You are not allowed to inherit evidence, rather assess to confirm the evidence meets the current test requirements and perform any new test cases introduced since the original Qualification. 

Two ways

Design Product Types[edit]

  1. Bluetooth End Product
  2. Bluetooth Controller Subsystem Product
  3. Bluetooth Host Subsystem Product
  4. Bluetooth Profile Subsystem Product
  5. Bluetooth Component Product
  6. Bluetooth Test Equipment
  7. Bluetooth Development Tool
Component Subsystem End Product
Intention Allow partial product to be qualified and require that Component integration must always result in a new Qualified Design Listing (QDL). Allow partial product types (Controller or Host) to be qualified with intention and ability to be combined to meet definition of End Product type. Allow qualification for entire Core Configuration in one Qualified Design (QDL).
Benefit Testing inheritance. Conformance testing for the Component’s qualified layers can be inherited, provided that:
  • Assessment Date of Component within the last 3 years limit
  • The integration complies with the tested Component’s RIN
  • No compliance change is made to the tested Component
  • The integration results in a Bluetooth Subsystem or End Product
When used correctly, no further qualification is required if matching two or more complementary Subsystems.
  • Applies if the combined Subsystems are used as designed and originally qualified.
End Products can be combined or sold as is without limitations on the license. End Products represent a complete Bluetooth wireless solution.
  • Changes to End Products are assessed in accordance with the current PRD, section 2.2 and via the Product Change Checklist.

End Product Listing[edit]

"The End Product Listing (EPL) is free of charge and constitutes the Bluetooth SIG's definitive list that publicly displays qualified market products on www.bluetooth.com. Here, consumers can verify that the manufacturers have fully met the requirements of qualification and be better assured of interoperability with other Bluetooth enabled products. If shipping your product, having your product listed on the EPL will indicate to customs officials that the product is genuine and meets both the requirements of qualification and trademark licensing, preventing the product from being destroyed by customs.

The End Product Listing (EPL) tracks the usage of a qualified design within new Bluetooth product implementations released to the market.

The Bluetooth SIG will market your EPL product on www.bluetooth.com within the Product Directory. Bluetooth.com receives approximately half a million monthly visits with the Product Directory. If you would like to know how to create an EPL, please follow the easy-to-follow guide. Remember that an EPL can be updated (with pictures, descriptions, URLs, etc.) at any time."

- Reference: Bluetooth.org

Qualified Design Listing[edit]

Texas Instruments Single Mode Bluetooth low energy solutions have the following Qualified Design Listings (QDL) with corresponding Qualified Design Identification (QDID)

Subsystem Controller Host Profile
QDID B016552 B017183 B020954
Includes HCI
Link Layer
RF PHY
GAP
GATT
ATT
SMP
L2CAP
HCI
Health Thermometer Profile/Service

Device Information Service
Find Me Profile
Immediate Alert Service
Link Loss Service
Proximity Profile
Tx Power Service
Heart Rate Profile/Service
Time Profile
Phone Alert Status Profile
Alert Notification Profile
Blood Pressure Profile/Service
Battery Service
HID Service
Scan Parameters Service
HID over GATT Profile
Scan Parameters Profile
Running Speed and Cadence Profile/Service
Cycling Speed and Cadence Profile/Service

These can be used as reference when creating an End Product Listing.

Create an End Product Listing[edit]

If you have copied a TI CC2540EM or CC2541EM design, simply;

  1. Follow the EPL guide
  2. Use our QDIDs as a reference when completing the EPL Form


If you have created your own RF Circuitry, you need to perform PHY test before creating the EPL to ensure that your design is compliant.

FAQ[edit]

I have created a design similar to the CC2541EM but smaller, can I refer to the TI QDIDs in my EPL?
If you have created your own RF Circuitry, you need to perform PHY test before creating the EPL to ensure that your design is compliant. Contact a test house (including BQE) for a consultation .

What TI BLE stack components have passed the certification?
See table in the Qualified Design Listing section.

What is the difference between QDL and EPL?
QDL is qualified as a design, requires member to pay a listing fee. EPL is for products that reference the QDL and is FREE.

What is a Bluetooth Qualification Expert (BQE)

  • Individual recognized by the Bluetooth SIG to provide a Bluetooth member with qulification related services
  • Expert in understanding the qualification policy and process
  • Optional for members to use them


Back to Bluetooth SensorTag main page

E2e.jpg {{
  1. switchcategory:MultiCore=
  • For technical support on MultiCore devices, please post your questions in the C6000 MultiCore Forum
  • For questions related to the BIOS MultiCore SDK (MCSDK), please use the BIOS Forum

Please post only comments related to the article How to Certify your Bluetooth product (如何认证你的蓝牙产品) here.

Keystone=
  • For technical support on MultiCore devices, please post your questions in the C6000 MultiCore Forum
  • For questions related to the BIOS MultiCore SDK (MCSDK), please use the BIOS Forum

Please post only comments related to the article How to Certify your Bluetooth product (如何认证你的蓝牙产品) here.

C2000=For technical support on the C2000 please post your questions on The C2000 Forum. Please post only comments about the article How to Certify your Bluetooth product (如何认证你的蓝牙产品) here. DaVinci=For technical support on DaVincoplease post your questions on The DaVinci Forum. Please post only comments about the article How to Certify your Bluetooth product (如何认证你的蓝牙产品) here. MSP430=For technical support on MSP430 please post your questions on The MSP430 Forum. Please post only comments about the article How to Certify your Bluetooth product (如何认证你的蓝牙产品) here. OMAP35x=For technical support on OMAP please post your questions on The OMAP Forum. Please post only comments about the article How to Certify your Bluetooth product (如何认证你的蓝牙产品) here. OMAPL1=For technical support on OMAP please post your questions on The OMAP Forum. Please post only comments about the article How to Certify your Bluetooth product (如何认证你的蓝牙产品) here. MAVRK=For technical support on MAVRK please post your questions on The MAVRK Toolbox Forum. Please post only comments about the article How to Certify your Bluetooth product (如何认证你的蓝牙产品) here. For technical support please post your questions at http://e2e.ti.com. Please post only comments about the article How to Certify your Bluetooth product (如何认证你的蓝牙产品) here.

}}

Hyperlink blue.png Links

Amplifiers & Linear
Audio
Broadband RF/IF & Digital Radio
Clocks & Timers
Data Converters

DLP & MEMS
High-Reliability
Interface
Logic
Power Management

Processors

Switches & Multiplexers
Temperature Sensors & Control ICs
Wireless Connectivity