Wi-Fi Alliance Certification Methods

(1)

Wi-Fi CERTIFIED™ Makes it Wi-Fi

Wi-Fi Alliance

Certification Methods

(2)

Overview

• There are various certification methods available to Wi-Fi Alliance members*

• Some require testing, some do not • Overview of all certification methods

• Emphasis on certification methods that do NOT require testing

*Note: Adopter members are not eligible to participate in “plug fests,” purchase test bed equipment, nor certify products.

(3)

Wi-Fi Alliance Confidential 3

Wi-Fi Certification Overview

• Only Wi-Fi Alliance members may submit products for certification testing (regardless of certification method) • All products must demonstrate interoperability for the

standard tests

– 802.11 band support (a/b/g)

– Security support (Wi-Fi Protected Access 2, WPA2™)

• Optional tests include

– WMM®

– WMM Power Save™ – Wi-Fi Protected Setup™

– 802.11h (Spectrum and Trasmit Power Management Extensions)

(4)

Wi-Fi Certification Methods

• Standard testing • Module Policy* • Transfer Policy*

• Application Specific Device (ASD) testing

*

These methods do not require testing at an Alliance Authorized Test Laboratory (ATL).

(5)

Standard Testing

• Defined test plans and testbeds

– Testbeds consist of specific equipment in specific configurations

– DUT must demonstrate interoperability with all equipment in test bed

• Performance measurements

• Conformance to published specifications • Compatibility with test bed devices

• Tests may be performed at any Wi-Fi Alliance Authorized Testing Laboratory (ATL)

– See our web site for a current list of ATLs: http://www.wi-fi.org/authorized_labs.php

(6)

Alternative Test Methods

• The next slides detail alternatives to our standard testing process

• Our policies and alternative test methods allow for some flexibility

• If you have questions about the application of one of our policies or alternative test methods please contact the Wi-Fi Alliance by sending an email to:

(7)

(8)

Module Policy Overview

The Module Policy

• Allows products using the same wireless equipment to be Wi-Fi CERTIFIED without undergoing certification testing

• Is an “Intra-Company” policy – the policy is only applicable WITHIN a single company

Terminology

• Equipment that may be incorporated into multiple products can be classified as a “Module” as long as:

1. the module is Wi-Fi CERTIFIED through actual certification testing; and

2. the module will employ the same basic configuration (hardware/software/firmware, etc.) in later products.

• A product that incorporates a Wi-Fi CERTIFIED module and is certified using the Module Policy is referred to as a “Dependent Product”

(9)

Module Policy Costs

• The cost to designate a device as a module is US$500 and can be designated:

1. at the time of the initial certification application; or 2. retroactively through the Certification System.

• The cost for a dependent product certification is US$300 per dependent product and requires:

1. the module be previously designated; and

2. only a completed declaration form through the Certification System for certification.

(10)

Illustration: Module Example

Module

Tested and Certified

Second Dependent Product

Certified without Testing

First Dependent Product

Tested and Certified

Model A

(11)

(12)

Transfer Policy Overview

The Transfer Policy

• Allows products that are Wi-Fi CERTIFIED by an OEM or supplier to be Wi-Fi CERIFIED for your company without undergoing certification testing (the

product certification can be transferred an unlimited number of times)

• Is an “Inter-Company” policy – for transferring an existing product certification from a supplier product to your company – transfers initiated from other

companies, not within your own company

Applicability

• A certification transfer is applicable for re-branded products, where the only changes affect the branding, packaging, or cosmetics of the product.

• Member requesting transfer must agree to the following: – Product will only be re-branded as above

– Transferred certification becomes independently owned by member requesting transfer (no burden on member who tested product at lab) – Member requesting transfer accepts all future certification responsibilities

(13)

Transfer Policy Costs

• The cost to transfer an existing certification to your company is US$500 and requires:

1. completing a transfer certification application through the Certification System;

2. providing one application for each product certification transfer (i.e., one application per product); and

3. providing (as part of the application) a complete description of the differences between the supplier product and your company’s product.

(14)

Transfers Allowed Under Policy

• Hardware changes associated with cosmetic packaging • Software changes associated with GUI and re-branding • Application of module policy against a product that was

CERTIFIED using this policy

• Different members invoking this policy for same originally tested product

• One transfer per transaction (i.e., each product with transferred certification must have its own

(15)

Transfer Policy Scenarios

Company A

Tested and Certified

Company B

Certified via Transfer

Company C

Tested and Certified

Company D

Company F

Company E

Certified via Transfer D

E

(16)

Transfers Not Allowed

Company A Tested and Certified Company B Applied and Certified via Transfer Company C Transfer does Not Apply Company C Applied and Certified via Transfer

(17)

Application Specific Device (ASD)

Testing

(18)

ASD Program Overview

• The Application Specific Device (ASD) Testing Program was developed for equipment that cannot easily be

tested using standard test methods

– Many devices cannot be categorized as traditional STA or AP

– Device dimensions have changed considerably

– Media applications have evolved to incorporate 802.11 functionality

• Currently, members must develop and propose alternative test method

• Members must convince the Alliance of the need for any deviation from standard test methods

(19)

ASD Program Overview

• Approved ASD test plans become part of the certification program

• Approved test plans can also be used by other members

• Once approved, any Authorized Test Lab can perform ASD testing

(20)

ASD Program Overview

• Certification process for ASD testing is no different than standard testing

• The Alliance will consider standardizing popular ASD test methods

• Complete process documentation available on members-only web site

(21)

ASD Test Plan Development

Process Flow

(22)

ASD Migration Plan

• Migration from current process to new process and policies incorporating Test Engine as a major

component

• Allow WFA staff to focus on Test Engine development and support

(23)

Test Engine Architecture Overview

• The Test Engine Architecture seeks to simplify the current ASD process with a standard platform for testing

• The purpose of Test Engine is to allow standard station tests to be streamlined for any type of product, including stations that previously were categorized as ASDs.

• The key component is a framework for client testing which is extensible to Wi-Fi clients of any form, without compromising the integrity of the comprehensive series of Wi-Fi tests developed over the years that ensure

device interoperability.

• A Test Engine Architecture System Overview can be downloaded from the members-only web site

(24)

Closing

• If you have any questions, please send an email to:

[email protected]

• If you have any questions about Wi-Fi Alliance membership, please send an email to:

(25)

(26)

Combination Scenarios

• Member A tests and certifies Product X

• Member B intends to resell Product X as Alpha, Beta and

Gamma

• Member B will not need to test these products

– Certification for Alpha can be achieved via Transfer policy – Alpha can be retroactively classified as a Module

– Beta and Gamma can achieve certification as dependent products of Alpha

• Alpha, Beta and Gamma are now Wi-Fi CERTIFIED without testing

(27)

Combination Scenarios

• Member A tests and certifies product W as Module in Dependent Product X

• Member A also then invokes Module Policy to certify Dependent Products Y and Z

• You intend to sell exactly same Module and Dependent Products (w, x, y, z) and maybe another Dependent Product (p)

• You will not need to test at lab

– You invoke Certifications Transfers Policy twice to certify in your brand your product w (=W), and x (=X)

– You classify w as a module

– You invoke the module policy to certify y(=Y), z (=Z) and p as dependent products (p must be functionally the same as X)