<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Is BLE qualification required for proprietary service?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/6335/is-ble-qualification-required-for-proprietary-service</link><description>Since related topic Is BLE changing licensing policy? was marked as resolved I moved my question to new one.
My company is ready to get SIG membership for BLE usage and pay the fee. The only question is whether we need to pass qualification test if:</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 03 Apr 2015 11:59:28 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/6335/is-ble-qualification-required-for-proprietary-service" /><item><title>RE: Is BLE qualification required for proprietary service?</title><link>https://devzone.nordicsemi.com/thread/22091?ContentTypeID=1</link><pubDate>Fri, 03 Apr 2015 11:59:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7a656d8b-1417-4a5f-8465-cb6a1bf02537</guid><dc:creator>John</dc:creator><description>&lt;p&gt;To be honest, I do not know if we used PTS at all. We hired a test house who then assigned a Bluetooth Qualification Engineer who dealt with all of the SIG rules and interactions. It wasn&amp;#39;t a lot of money and so worth it to not have to figure all of this out ourselves.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Is BLE qualification required for proprietary service?</title><link>https://devzone.nordicsemi.com/thread/22090?ContentTypeID=1</link><pubDate>Thu, 02 Apr 2015 19:34:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:783be635-d186-423f-bb6a-165eabad88ce</guid><dc:creator>Volodymyr</dc:creator><description>&lt;p&gt;Thank you again, you are pushing me to solution. As far as I understood, Nordic provides papers for Soft Device that is a FW on a chip. The chip is controlled over HCI. So, open source Bluez could easy work with that chip.&lt;/p&gt;
&lt;p&gt;In your case you passed partial qualification &amp;quot;Start B&amp;quot; in &lt;a href="https://www.bluetooth.org/en-us/test-qualification/qualification-overview"&gt;www.bluetooth.org/.../qualification-overview&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;As far as I know, my chip passed RF test, need to double check.
But I don&amp;#39;t understand what is relation between RF and product listening.
I see next ways:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Change chip to Nordic one(small probability), get papers from Nordic, get product listing, pay SIG&lt;/li&gt;
&lt;li&gt;Ask current vendor for papers (almost impossible), get product listing, pay SIG&lt;/li&gt;
&lt;li&gt;Do whole qualification of the current chip ourself by creating test FW, get product listing, pay SIG
Tough life. :-(&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Did you try to use PTS to test and  pass qualification?&lt;/p&gt;
&lt;p&gt;Thank you for your help.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Is BLE qualification required for proprietary service?</title><link>https://devzone.nordicsemi.com/thread/22089?ContentTypeID=1</link><pubDate>Thu, 02 Apr 2015 18:36:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:88aa23e9-6c51-48da-83b1-1bbf72d78880</guid><dc:creator>John</dc:creator><description>&lt;p&gt;We did a proprietary service as well. That did not need to be qualified. However we did need to use Nordics qualifications for the Soft Device, and have RF testing done at a test house to generate the product listing that you have to pay the SIG for.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Is BLE qualification required for proprietary service?</title><link>https://devzone.nordicsemi.com/thread/22088?ContentTypeID=1</link><pubDate>Thu, 02 Apr 2015 16:41:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f1a193c0-b7c6-47bd-a917-2880e5f63f3b</guid><dc:creator>Volodymyr</dc:creator><description>&lt;p&gt;Thank you John for an effort. Unfortunately, I cannot use qualified module.
We are going to use open-source Bluez with a chip without qualification.
It is OK to pay the fee for our product, probably we already have got SIG membership.&lt;/p&gt;
&lt;p&gt;BUT: We are using the only proprietary BLE service which won&amp;#39;t be easy to qualify using PTS.
To pass that qualification we need for sure to implement separate FW image which will support mandatory BLE options. It will take some time.
The time, as usual, is the most expensive thing in our life. :-(&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Is BLE qualification required for proprietary service?</title><link>https://devzone.nordicsemi.com/thread/22087?ContentTypeID=1</link><pubDate>Thu, 02 Apr 2015 13:10:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:675d408f-127f-4a34-b211-93115b1fc8af</guid><dc:creator>John</dc:creator><description>&lt;p&gt;Hi Volodymyr, I don&amp;#39;t know if I have the correct answer to your question so I am posting this as a comment. My interpretation based on sitting in on the SIG conference call and reading their documentation last year is that you have to pay the fee for each product you ship that contains Bluetooth technology. You are essentially paying them for using the intellectual property in each product. Prior to last February you could buy an already qualified module and not pay a fee, but they were not able to fund their desired activity level with that model so they went to requiring a fee for each product.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>