Windows Logo Program For Wireless USB Best practicesZach LittleProgram ManagerMicrosoft Corporation

Key Takeaways

Lead in advancement of 64-bit computingAdopt best practices and new toolsPartner on new hardware directionsEnsure partner understanding around the Wireless USB Windows Logo Program

Agenda

Unclassified Driver Signatures for 3rd party software stacksGoals of the Windows Logo Program (WLP) for Wireless USBWireless USB USB-IF CertificationReview WUSB WLP requirements

Provide the rationale used to select these requirements

Timeline for initial requirements

Unclassified Driver Signatures

Drivers from driver categories that are not currently defined as part of the Windows Logo Program requirements are allowed to submit drivers for signatures under the Unclassified Program

Please work with Microsoft if you have any questions about this program: http://www.microsoft.com/whdc/winlogo/drvsign/dqs.mspx

Unclassified Driver Signatures

Vendors developing their own WUSB host software stack on the PC need to use the Vista Unclassified Driver Signature Program

The hardware must still comply with the WLP

Dos and Donts for partnersPartner CAN get package digitally signed

Partner CAN NOT include Certified for Windows Vista or Works with Windows Vista Logos

Partner CAN NOT create a press release stating that they have received certification

Similar programs have been employed by other bus stacks like Bluetooth and 1394b

Wireless USB WLP Goals

Ensure a great and consistent end user experienceDrive towards supreme performance

Large buffer sizeR-pipe requirementsPCI vs USB attachedPower Management

Minimize interoperability issues

Build on existing programs from USB-IF and WiMedia

Overall Process For Devices

WiMedia Certification

Wireless USB Certification (from USB IF)

Windows Logo Program

Wireless USB Certification From USB-IF

USB-IF Wireless USB certification

Silicon program - Available NowDevice Program - Coming soon

Helps communicate the brand promise to consumersSign that the industry is ready to ship products

Companies with Wireless USB Certification (as of May 2007)

NECIntelAlereon

Required for Microsoft WLP certification

Wireless USB Requirements

Hosts and Devices must obtain USB-IF and WiMedia certification (Connect-0078)

Devices must support association models described in USB-IF specification(Connect-0066, Connect -0068)

Peripherals must operate in function mode when connecting to a PC (Connect-0067)

Hosts and Devices must obtain a Certified Wireless USB Logo from the USB-IF (Connect-0079)

Wireless USB Requirements

Native Wireless USB Devices based on the Certified Wireless USB Specification must pass all relevant wired USB device class tests (Connect-0080)

Ensures consistent experience with wired USB

Devices based on the Certified Wireless USB specification must be self beaconing (Connect-0082)

Microsoft does not currently have plans to support directed beaconing

Native Wireless USB devices based on the Certified Wireless USB specification must support all data rates (Connect-0083)

Helps mitigate interoperability issues

Native Wireless USB Devices must work with HWA and WHCI hosts(Connect-0084)

Devices need to be compatible with all hosts types

Wireless USB Requirements

All devices based on the Certified Wireless USB specification must support the ability to connect to different hosts (Connect-0086)

Does NOT mean multiple hosts simultaneously

A Host Wire Adapter must support at least 10 simultaneously connected devices(Connect-0089)

Should support of all major user scenarios

A Host Wire Adapter or a Device Wire Adapter must support a minimum of 64 R pipes (Connect-0087)

Needed for supporting many devices simultaneously

A Host Wire Adapter or a Device Wire Adapter must have at least 192k of buffer space(Connect-0088)

Derived from a 3k per R-pipe requirement

Enables top performance

Wireless USB Requirements

A Host Wire Adapter must support at least 64 devices (Connect-0090)

Premium logo requirement

Connected simultaneously

A Host Wire Adapter must pass all tests a Wired USB device is required to pass (Connect-0091)

Goal is to mitigate any issues around power management/ system sleep-hibernate modes

DWA Association functionality must be present downstream of a hub (Connect-0092)

Composite hubs are not allowed

Wireless USB Requirements

An internal non-removable host controller must be PCI attached(HWA not permitted) (Connect-0093)

PCI attached = WHCIThis encompasses any host controller that is not a dongle form factor

Mini-card is considered non-removable

This requirement is about performance and power management

WHCI Versus HWA

14

WHCI HWAPerformance Bandwidth

Latency

Optimal

1.5x faster, can accommodate higher PHY rates (future)Low latency

Lower than WHCI

Bandwidth limited by USB 2.0 speeds and protocol overheadHigher latency than WHCI

Power Management

Better power management

Standard system power management

Form Factor PCI/PCMCIA/Express CardEmbedded (MiniPCI/Motherboard)

USB dongle / Express Card

Required for Internal Radios

Native Device Versus DWA Embedded Device

15

Native Device* DWA Embedded Device

Key Points More appropriate for newly designed devices

Easy to enhance current wired USB devices

Less hardware Need extra hardware (DWA controller)

PerformanceBandwidthLatency

Optimal performance

Less latency

Consumes more bandwidth for equivalent throughputAdded USB transfers increase latency

Radio Power Management

Custom power management possible

Standard DWA power management

Time to market

A design cycle necessary Quick upgrade* Native devices have several categories

Wireless USBPerformance

Many ways to measure performanceThroughput, Number of Errors, Data Rate

Environment dependantMajor focus of the WLP to ensure great performance in the majority of scenariosNumbers should only get better going forward

Mass Storage Performance

DWA + USB2 HD Native HD

HWA

Scenario A:Theoretical max: 80 MbpsBest seen to-date:40 Mbps

Scenario B:Theoretical max: 160 MbpsBest seen to-date: 70 Mbps

WHCI

Scenario C:Theoretical max: 160 MbpsBest seen to-date: 60 Mbps

Scenario D:Theoretical max: 220 MbpsBest seen to-date: 140 Mbps

Host

Device

Using 32K transfer requests from Mass Storage Driver

EHCI Baseline/Wired HD performance: 260 Mbps* Performance numbers are calculated and observed. Numbers will likely vary depending on test environment and Implementation. Information provided by USB-IF.

Wireless USB WLP – Timeline

Program goes into effect June 2008Complete list of requirements available in WLP v3.09 document

Tests online: TBDContact Microsoft Wireless USB team for updates on thisMajority of USB-IF and WiMedia certification tests are available nowRegulatory related tests per region left to device manufacturer

Call To Action

Silicon ManufacturersEnsure your hardware is compatible with the WLP requirements for Wireless USBWork with Microsoft to have your devices/hosts in our lab for testing!

IHVs/OEMsMake sure your devices are using silicon that is USB-IF certified and WLP certifiableDrive towards WHCIGet your latest devices in Microsoft's lab!

Questions?

CON-C430 – Windows Device Connectivity Chalk Talk

Additional ResourcesWeb Resources

Wireless USB Specs: http://www.usb.org

UWB Specs: http://www.wimedia.org

Wireless USB PDK: http://www.usb.org/developers/estoreinfo/

Windows Hardware Developers Central: http://www.microsoft.com/whdc/

Windows Logo Program: http://www.microsoft.com/whdc/winlogo/hwrequirements.mspx

Related SessionsShort Range Wireless Device Connectivity (CON-T413)

Contact InformationWireless USB:

UWB Feedback:

Wusbbeta @ microsoft.com

Uwbfb @ microsoft.com

© 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.

The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date

of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.