[Bluez-devel] BlueZ Qualification FAQ.htm
From: Halam Rose <hidden>
Date: 2003-03-05 18:31:22
BlueZ Qualification FAQ
Authored Halam Rose 7 layers UK
Contact halam.rose@7layers-UK.com
<mailto:halam.rose@7layers-UK.com>
Version 5 March 2003 a
Introduction.
BlueZ is an open source project under the GNU GPL which provides a Bluetooth
stack for Linux. BlueZ has been incorporated into the Linux kernel but at
this time it has no recognition from the Bluetooth SIG. 7 layers UK are a
Bluetooth test facility and have offered to help with the Qualification of
BlueZ. This document is intended to collect the questions we discuss about
BlueZ Qualification, some of the answers will develop into a project plan.
Please appreciate that this is living document which will evolve and future
versions may contain changes due to inaccuracies or changes in policy by the
contributors. The answers have been reviewed by a BQB but since they are
fairly general they are expected to need adjustment as the issues become
clearer.
What does Qualified mean?
Whats involved in Qualification?
What are the legal implications of not having BlueZ Qualified?
What are the benefits of Qualifying BlueZ?
To the BlueZ Project?
To BlueZ end users?
To manufacturers incorporating BlueZ in their products?
To manufacturers of Bluetooth modules?
To 7 layers UK
What are the limitations of Qualifying BlueZ ?
To the BlueZ Project?
To BlueZ end users?
To manufacturers incorporating BlueZ in their products?
To manufacturers of Bluetooth modules?
What parts of BlueZ will be Qualified?
Which version of BlueZ will be Qualified?
What Platform will be used for Qualification? (Hardware, Distribution,
Kernel)
What costs are involved in Bluetooth Qualification?
Who will meet those costs for BlueZ?
Who owns BlueZ?
Where can I find out more about BlueZ?
Who will own the Qualified Product Listing?
Who will sign the conformance statements?
Who will control the Qualified Product Listing?
What does a Qualified Product Listing look like?
What other issues are there in taking a product to market?
Where can I find out about Bluetooth?
As a user ?
As a developer or manufacturer?
Specifically Qualification?
How can I help?
What happens when BlueZ is updated?
How are different versions of Linux covered?
What does Qualified mean?
Qualified means a product is listed on the Bluetooth Qualified Product List
(QPL)
http://qualweb.opengroup.org/Template2.cfm?LinkQualified=QualifiedProducts
which is the licensing mechanism for the patents that protect the Bluetooth
IP.
Whats involved in Qualification?
An individual called a Bluetooth Qualification Body (BQB) has to be
satisfied that the product meets the requirements laid out by the Bluetooth
SIG. He examines a Compliance Folder that contains test results referring
to the Bluetooth test spec
http://qualweb.opengroup.org/Template2.cfm?LinkID=1 along with declarations
and other documents. More information can be found in the Programme
Reference Document (PRD)
http://qualweb.opengroup.org/Template2.cfm?LinkID=5.
A fee is collected by the BQB on behalf of the Bluetooth SIG which is
typically $7500.
What are the legal implications of not having BlueZ Qualified?
Without Qualification there is no licence to use the Bluetooth patents.
What are the benefits of Qualifying BlueZ?
To the BlueZ Project?
Right now I dont think any distributions claim or document Bluetooth
support. It deserves proper recognition. Presumably the Distros avoid
mention of Bluetooth because of the qualification issue.
To BlueZ end users?
A Qualified BlueZ stack would enable manufactures to claim Linux support for
their Bluetooth adaptors. That would give users confidence that they are
buying product that is proven to work and that they can get proper support
from the manufactures.
To manufacturers incorporating BlueZ in their products?
BlueZ will be qualified as part of a reference design so manufacturers will
still need to do some qualification work and have their own product listing.
They will however know that BlueZ is qualifiable and depending on their
implementation they may be able to refer to BlueZ as a Qualified Subsystem
and not have to repeat its testing. Profile interop testing results can not
be referred to this way however except when combining products which are
listed on the Complementary Subsystem List of the other (in which case no
testing may be necessary).
To manufacturers of Bluetooth modules?
Manufacturers will be able to list BlueZ as a Qualified Subsystem and be
listed as a Complementary Subsystem of BlueZ. This will allow manufacturers
to claim Linux support without breaching their Bluetooth SIG membership
agreement. I would rather buy products from companies who make a public
commitment to Linux wouldnt you? There will be a BQB who is familiar
with BlueZ and able to make good quality decisions on what of the existing
qualification can be re-used by you.
To 7 layers UK
7 Layers UK want to establish themselves as the best Bluetooth Qualification
facility to handle Linux products, and in the process to make money by
providing Bluetooth Qualification services of value to manufacturers who
want to take advantage of BlueZs Qualified status. The original BQB
remains responsible for adding to the Compatible Subsystems List, though
other BQBs will be able to list BlueZ as a Complementary Subsystem of
products they are handling.
What are the limitations of Qualifying BlueZ ?
To the BlueZ Project?
Testing for the Bluetooth Qualification process may bring up some issues
that for a user are of no consequence but cause test case failure. The
BlueZ developers must be committed to resolving these. Users of the
Bluetooth IP have to accept conformity with the specification.
To BlueZ end users?
Initially only part of the full BlueZ functionality will be included in the
listing, but this does not imply that anything in BlueZ is non-compliant.
Can you think of any other down sides?
To manufacturers incorporating BlueZ in their products?
Initially only part of the full BlueZ functionality will be included in the
listing, but this does not imply that anything in BlueZ is non-compliant. If
you submit your own test results they may allow the BlueZ listing to be
extended for everyones benefit. It will be a BQB decision about how much
retesting will have to be done for your application. The best informed BQB
will be the 7 layers UK BQB who would make the first listing.
To manufacturers of Bluetooth modules?
Initially only part of the full BlueZ functionality will be included in the
listing, but this does not imply that anything in BlueZ is non-compliant.
If you submit your own test results they may allow the BlueZ listing to be
extended for everyones benefit. You will be able to qualify your products
with BlueZ as a Qualified Subsystem but must come through the 7 layers UK
BQB to be included on the BlueZ Complementary Subsystems List.
What parts of BlueZ will be Qualified?
It makes sense to make a basic listing first then extend it as more testing
is completed. The minimum for qualification is GAP which would make BlueZ a
type 1 product under the definition in section 5.5.2.1 of the PRD.
Which version of BlueZ will be Qualified?
TBD
What Platform will be used for Qualification? (Hardware, Distribution,
Kernel)
TBD,
Kernel 2.4.21-pre5 includes all Bluetooth fixes and updates (except the SCO
support for USB). Intel platform with Redhat 7.3 is available as is a CSR
Casira which can be used as a serial or USB bluetooth adaptor.
What costs are involved in Bluetooth Qualification?
Testing, report writing, BQB time, Bluetooth SIG listing fee Usually $7500
Who will meet those costs for BlueZ?
Current thinking is that the initial work will be done by 7 layers UK
without charge but help with the listing fee will be requested. The listing
fee is paid to the Bluetooth SIG, not retained by 7 layers UK. The fees
fund the activities of the SIG, promoting Bluetooth technology.
Who owns BlueZ?
Copyright belongs to Qualcomm. is this entirely correct?
Where can I find out more about BlueZ?
http://bluez.sourceforge.net/
Who will own the Qualified Product Listing?
Not yet clear, usually listings are made in the name of a manufacturer is
there actually a BlueZ organisation??
Who will sign the conformance statements?
TBD one of the BlueZ developers.
Who will control the Qualified Product Listing?
The BQB from 7 layers UK, It is normal for the same BQB to continue to
maintain and update a listing once it is established.
What does a Qualified Product Listing look like?
http://qualweb.opengroup.org/Template2.cfm?LinkQualified=QualifiedProducts&D
etails=Yes&ProductID=1086
<http://qualweb.opengroup.org/Template2.cfm?LinkQualified=QualifiedProducts&
Details=Yes&ProductID=1086> shows Widcoms Bluetooth stack for Windows.
What other issues are there in taking a product to market?
Apart from Bluetooth Qualification governments regulate market access
through Regulatory Approvals mechanisms and the use of standards like CE
marking in Europe, UL or equivalent safety standards in USA. Testing to FCC
part 15, ETS 300328 and ETS 300489 are usually required before filing a
compliance folder with the various authorities around the world. This kind
of stuff is non trivial and requires some expertise and local knowledge.
Here I can plug another service available from 7 layers UK. It is important
to understand the different role of regulation (CE marking, approvals,
certifications to meet regulatory purposes) and Bluetooth Qualification
which allows a company to benefit from the work done to create the Bluetooth
Specification, controlled by patent, copyright and licensing..
Where can I find out about Bluetooth?
As a user ?
http://www.bluetooth.com/ <http://www.bluetooth.com/>
As a developer or manufacturer?
http://www.bluetooth.org <http://www.bluetooth.org/>
specifications etc
Specifically Qualification?
http://qualweb.opengroup.org/ <http://qualweb.opengroup.org/>
test specifications, test case status, qualified product list
How can I help?
We are currently in a brainstorming phase so any input is useful:
Can you enhance these answers?
Can you ask any important questions?
What benefits to Qualification do you see?
What resources can you offer?
How would you like to help?
What Happens when BlueZ is updated?
The listing can be revised subject to appropriate evidence that the BQB will
specify when the changes are understood. Minor changes, bug fixes and the
likes can be aggregated every few months.
How are different versions of Linux covered?
The Widcom listing
http://qualweb.opengroup.org/Template2.cfm?LinkQualified=QualifiedProducts&D
etails=Yes&ProductID=1086
<http://qualweb.opengroup.org/Template2.cfm?LinkQualified=QualifiedProducts&
Details=Yes&ProductID=1086> is an example where the same stack is run on
different versions of Windows. The same principle applies to the flavours
of Linux but the exact extent, the range of processors, distros and kernels
is still under discussion.