Upload
lucas-barrett
View
216
Download
0
Tags:
Embed Size (px)
Citation preview
January, 2000
Kevin Marquess, Hyper CorporationSlide 1
doc.: IEEE 802.15-00/016r0
Submission
Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs)Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs)
Submission Title: [Introduction to the Bluetooth Qualification Program]Date Submitted: [11 January 2000]Source: [Kevin Marquess] Company [Hyper Corporation]Address [315 Iron Horse Court, Alamo, CA 94507, USA]Voice:[(925) 280-7779], FAX:[(925) 280-7751], E-Mail:[[email protected]]
Re: [Introduction to the Qualification Program Requirements documents (Bluetooth PRD v0.8)]
Abstract: [This presentation introduce the Bluetooth Qualification Program so that members of the group are aware of the proper channels to address Interoperability and Coexistence issues within the Bluetooth SIG. Also, for the individual members to be aware of the processes that are involved helping their sponsoring companies in bringing their products to market.]
Purpose: [Education of the Bluetooth “organization” with respect to Coexistence.]
Notice: This document has been prepared to assist the IEEE P802.15. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein.Release: The contributor acknowledges and accepts that this contribution becomes the property of IEEE and may be made publicly available by P802.15.
January, 2000
Kevin Marquess, Hyper CorporationSlide 2
doc.: IEEE 802.15-00/016r0
Submission
Introduction to Bluetooth Qualification Program
Hyper Corporation“Bluetooth Qualification Services”SM
www.bluetoothbqb.com
Kurt Fischer Kevin Marquess
January, 2000
Kevin Marquess, Hyper CorporationSlide 3
doc.: IEEE 802.15-00/016r0
Submission
Overview
• Qualification Program– Why have a Qualification Program?– Organization– Process
• Roadmap• Required Documents
– Adaptations of Qualification Process
January, 2000
Kevin Marquess, Hyper CorporationSlide 4
doc.: IEEE 802.15-00/016r0
Submission
Qualification is Brand Approval - Not Type Approval
January, 2000
Kevin Marquess, Hyper CorporationSlide 5
doc.: IEEE 802.15-00/016r0
Submission
Regulatory Type Approval
• Bluetooth RF Test Specification• Country Requirements:
– USA: FCC 15.205, 15.209, 15.247
– Canada: IC (Industry Canada) Document GL36
– Europe -- ETSI Standards• ETS 300 328• ETS 300 826
– France: Europe requirements + SP/DGPT/ATAS/23
– Spain: Europe requirements + Supplemento Del Numero 164 Del Boletin Oficial Del Estado
– Japan: ARIB RCR STD-33A (MPT - Ministry of Post and Telecommunication)
• NOTE: New EU Directive (R&TTE Directive) will effect above requirements.
January, 2000
Kevin Marquess, Hyper CorporationSlide 6
doc.: IEEE 802.15-00/016r0
Submission
Why Qualification?
January, 2000
Kevin Marquess, Hyper CorporationSlide 7
doc.: IEEE 802.15-00/016r0
Submission
Bluetooth Qualification Organization
Bluetooth SIG
Bluetooth
Qualification
Administrator
(BQA)
Bluetooth Qualification
Body (BQB)
Bluetooth
Technical
Advisory Board
(BTAB)
Bluetooth Qualification Review Board(BQRB)
Bluetooth Qualification Test Facility
(BQTF)
.
January, 2000
Kevin Marquess, Hyper CorporationSlide 8
doc.: IEEE 802.15-00/016r0
Submission
Qualification Process
Member
ICS & IXIT
Testplan
Compliance Folder
-Test Reportdirectly from
member
Check of thecompliance folder
BQA
BQTF
BQB
Declares category“C” test cases
Performs category “B” test cases
Performscategory "A" testcases forconformance andInteroperability
Conformance test report
Interoperability test report
test plan ICS & IXIT
Test Specs
Test case-reference list
PICS proformaTestcase mapping
Qualifiedproduct list
January, 2000
Kevin Marquess, Hyper CorporationSlide 9
doc.: IEEE 802.15-00/016r0
Submission
Qualification Process Diagram
Member BQB
BQ A
ListedProductsDatabase
DocumentDatabase
BQTF
Adopter'sAgreement
January, 2000
Kevin Marquess, Hyper CorporationSlide 10
doc.: IEEE 802.15-00/016r0
Submission
Roadmap - Steps to Listing Product
1) Executes Adopters Agreement (to become a Bluetooth Member)
2) Obtaining the appropriate Bluetooth Qualification Documentation from web-site (www.bluetooth.com/member.asp)
3) Member selects BQB for guidance and assistance during process
4) Submission of material necessary for Compliance Folder to BQB
5) Submission for Bluetooth Product Qualification to BQB for each unique Bluetooth product
6) Member performs all required tests (with only Category A tests performed by an accredited BQTF). Test reports or evidence of successful test completion to be included in Compliance Folder.
January, 2000
Kevin Marquess, Hyper CorporationSlide 11
doc.: IEEE 802.15-00/016r0
Submission
Qualification Program Documents
• Bluetooth Specifications– Core (Volume 1) – Profile (Volume 2)
• Program Reference Document (PRD)• Test Specifications• Test Case Reference List (TCRL)• Test Case Mapping Table (TCMT)• ICS & IXIT Proforma• Declaration of Compliance (DoC)• Bluetooth Brand Book
January, 2000
Kevin Marquess, Hyper CorporationSlide 12
doc.: IEEE 802.15-00/016r0
Submission
Member Documents Submitted to BQB• Member Inputs to Qualification Process (5.2)
– Compliance Folder (5.2.1)• Description of the Product (5.2.1.1)
• Declaration of Compliance (DoC) (5.2.1.4)
• Test Plan (5.2.1.2)– Test Case Selection (5.3)
• Test Case Mapping Table (TCMT) (5.3.1)• Test Case Reference List (TCRL) (5.3.2)
– ICS/IXIT (5.2.1.3)
• Test Report (5.2.1.5)– Types of Testing (5.4)
• Protocol Testing and Golden Units (5.5)• Profile Testing (5.6)• Application for Product Listing (5.2.2)
– Assigned Name/Number (5.8)• [Follow documented] Request process (5.8.4)
January, 2000
Kevin Marquess, Hyper CorporationSlide 13
doc.: IEEE 802.15-00/016r0
Submission
• Compliance Folder (5.2.1)– Description of Product (5.2.1.1)
• Name
• Model Number
• HW Version Number
• Software Version Number
• Bluetooth Profiles Supported
• Sufficient Technical Documentation (minimum):– User manual– Functional Block Diagram– Components:
• Reference Design Schematics• Parts Lists• PCB Layouts• Reference Design Application Note
Member Documents Submitted to BQB
January, 2000
Kevin Marquess, Hyper CorporationSlide 14
doc.: IEEE 802.15-00/016r0
Submission
Member Documents Submitted to BQB
• Test Plan (5.2.1.2)– Test Case Selection (5.3)
• Test Case Mapping Table (5.3.1)– Every test specification contains a test case mapping table.
– TCMT = identifies all related test cases which are required depending on the supported capabilities (Profiles) specified in ICS
• Test Case Reference List (5.3.2)– Specifies all conformance and interoperability test cases and identifies the
category of each test case.
– Types of Testing (5.4)• Bluetooth Conformance Testing (5.4.1)• Protocol Testing and Golden Units (5.5)• Profile Testing (5.6)
– Product Changes (5.7)• Class I (5.7.2.1)• Class II (5.7.2.2)• Class III (5.7.2.3)
January, 2000
Kevin Marquess, Hyper CorporationSlide 15
doc.: IEEE 802.15-00/016r0
Submission
Test Case Reference List
Key to the Categories
• Category A– Validated and commercially available. The test case is
mandatory and has to be performed at a recognized BQTF.
• Category B– The test case has to be performed and a declaration with
evidence is required. The instructions given in the test specification have to be followed.
• Category C– Declaration without evidence.
• Category D– Informative. A preliminary test case with no official qualification
value. The purpose is to inform the manufacturer about an upcoming test case.
January, 2000
Kevin Marquess, Hyper CorporationSlide 16
doc.: IEEE 802.15-00/016r0
Submission
Backup Information -- More detail
January, 2000
Kevin Marquess, Hyper CorporationSlide 17
doc.: IEEE 802.15-00/016r0
Submission
Protocol Testing and Golden Units (5.5)
• Definition (5.5.1)– Qualification program launched before validated
conformance test systems are available.– Improve likelihood of interoperability BQRB
allowed GU = Golden Unit – Initially provided by Ericsson and Nokia– More info on BT web
January, 2000
Kevin Marquess, Hyper CorporationSlide 18
doc.: IEEE 802.15-00/016r0
Submission
Golden Unit Testing (5.5.2)
• Protocol Tests using GUs is used to establish confidence in interoperability
• Protocol Tests using GUs shall be used to develop evidence when satisfying applicable Category B test cases in TCRL for following Test Specifications:– Part B: Test Suite Structure (TSS) and Test Purpose (TP) for
Baseband
– Part C: TSS and TP for Link Manager
– Part D: TSS and TP for L2CAP
– Part E: TSS and TP for Service Discovery Protocol
• DO NOT relieve Member of responsibility for complying with controlling specifications
• Member is NOT required to prove that designated GU is noncompliant
January, 2000
Kevin Marquess, Hyper CorporationSlide 19
doc.: IEEE 802.15-00/016r0
Submission
Golden Unit Testing - Positive Results
• The fact that two independently developed implementations interoperate supports a claim of compliance. (Does not prove compliance!)
• Failure to comply with the specification is the responsibility of the Adopter who does not comply.
January, 2000
Kevin Marquess, Hyper CorporationSlide 20
doc.: IEEE 802.15-00/016r0
Submission
Golden Unit Testing - Negative Results
• Does not prove product is not compliant - GU is not warranted to comply
• Adopter must document compliance through other means
• Adopter is responsible for developing a reasonable explanation for the failure
• No responsibility to prove that GU is non-compliant
January, 2000
Kevin Marquess, Hyper CorporationSlide 21
doc.: IEEE 802.15-00/016r0
Submission
Compliance Folder: Module or Component
• Reference Design Schematics• Parts List• PCB Layout• Reference Design Application Note
• Additional information so that BQB can determine which test case results are intrinsic to the pre-qualified component (not just the reference design TC)
January, 2000
Kevin Marquess, Hyper CorporationSlide 22
doc.: IEEE 802.15-00/016r0
Submission
Compliance Folder: Component Integrator
• Supporting information on pre-qualified component sufficient so that BQB can determine which test cases are covered
• Component reference design to application note• End-product engineering documentation enable BQB
to determine if component was integrated per the application note
January, 2000
Kevin Marquess, Hyper CorporationSlide 23
doc.: IEEE 802.15-00/016r0
Submission
Test Type vs. Number of Samples
Profile Interoperability Product to Product Product to GU Product to validated reference
test system
2 samples
Protocol Product to GU (or Product) Product to validated protocol
conformance test systems
2 samples
Regulatory and TA FCC, ETSI, and EMC Product Safety & LVD TTE or RTTE
2 samples plus extrasamples of power supply
January, 2000
Kevin Marquess, Hyper CorporationSlide 24
doc.: IEEE 802.15-00/016r0
Submission
Project Plan
• Interactive with other vendors– HW, SW, Modules and Components
• Anticipate delays and retesting• Many judgement areas that may require
BQRB ruling• Sample Project Plan
January, 2000
Kevin Marquess, Hyper CorporationSlide 25
doc.: IEEE 802.15-00/016r0
Submission
Project Plan