UltraWide Band (UWB) Architecture Preview

1. UltraWide Band (UWB) Architecture Preview

2. Outline • Microsoft’s Participation and Vision • Supported Protocols currently planned for UWB • Wireless USB • IP • Synergy between IHVs/ISVs and UWB Team • Call to action for partners • Summary

3. UWB Overview FCC ruling permits UWB spectrum overlay • UWB is presently approved for use only in the US • Regulatory activity underway in Europe, and Asia • Consistency “rules of the game” • Open standardization is critical for worldwide market adoption UWB Throughput • High speed at short range • 480 Mb/s at ~3m • Does not penetrate walls • Scaleable performance (Moore’s Law radio)

4. UWB in the Digital Home Local high throughput delivery Wired / Wireless Wired /Wireless Wired / Wireless Long range delivery wired & wireless (backbone) Wired / Wireless Wired / Wireless UWB delivers high speed interconnectivity at low power/proximity

5. UWB Project in Windows • Description • Create infrastructure to build on Microsoft’s huge investment in USB and IP class drivers over a new medium/transport • Project Goals • Reuse existing class drivers unchanged (except USB ISOCH) • Minimal changes to existing USB and IP core stack • Simple association model • High security (make it just as secure as cable scenarios) • Allow IHVs to write a single function driver on top of the appropriate PALs for wired and wireless scenarios • Class drivers should be developed on top of PALs. No new kernel/user APIs for UWB plan to be exposed

6. UWB Protocol Relationships on Windows Platforms Legend High customer interest Low customer interest Items with ‘*’ are being defined in WiMedia Other Applications Wireless 1394 Convergence Layer* Wireless USB IP (WiNet*) MBOA UWB MAC* MBOA UWB PHY* Protocol Abstraction Layer (PAL) - Various technology solutionsrunning over the common platform Common UltraWide Band Radio Platform

7. Wireless USB – Topology Overview DeviceAdapter External USB Hub USBCables USBCables Wireless USB protocol Host Adapters Wireless Storage Device Adapter Proprietaryprotocol/connection DeviceAdapter

8. Association – HARD Scenarios • Association Is One Of The Key Elements To UWB’s Success • Hard Scenario #1 – HID • Keyboard/Mouse/Human Input Device • Hard Scenario #2 – Far apart • Device and host are not physically close enough to use a cable • Device and host are heavy and not convenient to move them • Hard Scenario #3 – Headless hosts • How to associate a device with a headless server (no monitor for showing the PIN/user entry, etc.) • Hard Scenario #4 – OEM Install • Pre-associating devices at OEM (during OS setup/upgrade). • Hard Scenario #5 – OS + BIOS / Multiple OS. • Associating a device with a host in such a way that the device is also associated with the same PC/radio in BIOS mode. Solve the hard problems and the rest are no-brainers!!

9. Windows Connect Now And the solution is …… The Windows Networking and Device Connectivity Platform • Effortless • “It Just Works” experience for users • Simple protocols, APIs and DLLs for partners and developers • Secure and Reliable • Built-in security to enable higher user confidence • Make reliability a fundamental part of the solution • State of the art • Continue enabling compelling new user experiences

10. Wireless Host Side Architecture • UWB radio supported on these buses: • PCI (or PCIe) based solution • Can go in addin card slot • Cardbus or ExpressCard possible • Wired USB dongle • Cabled ‘base station’ variety • Small ‘key’ solutions • Microsoft preferred PALs required on UWB host side radio • WUSB • IP

11. Role of Convergence / Management Layer Bandwidth management and arbitration Between PALs Inform other hosts to optimize bandwidth Changing channels if congestion Handling PCI resources Function or PAL enumeration Beaconing and Topology management

12. Device Wire Adapter USB2.0 • Looks like a wireless hub • Great for scenarios like wireless port replicators • Single chip implementations can be integrated directly into devices

13. List of New Kernel Files Legend Yellow = New Component Grey = Existing Component

14. Hardware IDs for UWB PALs • PCI IDs for UWB PAL PDOs • Hardware IDs • Compatible IDs • Similar in style toPCI device ID • USB IDs for UWB PAL PDOs • Hardware IDs • Compatible IDs • Similar in style to USB device IDs Microsoft plans to match on IDs highlighted in BOLD

15. Industry and Windows Compliance Programs • Compliance programs • Industry – Being defined in WiMedia and USB-IF • Microsoft – Windows Logo Program • UWB • Focus on certified silicon • The PAL used by the radio should be compliant with Microsoft supported PALs. • Association • There's a lot of work/innovation going on in this space still • Use Microsoft supported association models – Windows Connect Now • Wireless USB is likely to affect wired USB devices • We may require all wired USB devices be tested downstream of a DWA • Isochronous devices (connected via WUSB) may need some software changes • Timelines • Initial Windows Logo Program requirements coming shortly • Logo program validation tools to follow release of drivers

16. Windows Logo Program Requirements • Host side radios • Must be compliant with either WHCI or HWA specifications (and related specifications) • Must support isoch transfers • Device wire adapters • DWA's with exposed ports need to provide 500ma on all ports • Must support isoch transfers • Possible requirements around number of RPipes • Devices • WUSB devices must have a unique serial number • Devices must be compatible with both HWA and WHCI hosts • No plans to logo non-beaconing devices

17. Industry Compliance Plans • Applications own compliance testing • Define requirements/assertions • Run workshops • Allow logo usage • WiMedia provides turn-key compliance solution for PHY,MAC, and radio cooperation • Application compliance will incorporate WiMedia tests forlogo requirements • Timelines • Test documents and testsdeveloped 2H05 • First compliance workshops in 1H06 WUSB IP Cooperation policy WiMedia UWB MAC WiMedia UWBPhy

18. Summary • Industry specs are nearly done and prototype hardware is available to IHVs • Microsoft committed to providing beta drivers to early IHVs for validation purposes • Training and tools are coming • Developer Conferences • Peripheral Development Kits • Interop Labs

19. Call to Action • IHVs • Share UWB plans with Microsoft and come up with a great Go-To-Market Strategy • Send sample devices to Windows UWB team for testing/self-hosting • Participation • Attend Wireless USB Developers Conference on May 24-25 in San Jose, to learn more on WUSB • Participate with Microsoft on beta opportunities.Send us your feedback • Test wired USB devices on • DWA + WHCI/HWA Scenarios • All platform architecture (x86, x64, Itanium)

20. Resources • Microsoft Resourceswww.microsoft.com/whdc • MSDN Newsgroups • Windows Development  Device Drivers • Windows Development  Windows DDK • Industry Resources www.usb.org www.wimedia.org • Technical Papers • FAQ on UWB developer.intel.com/technology/usb/spec.htm • Intro to WUSBwww.usb.org/WUSB

21. Additional Resources • Email: UWBFB @ microsoft.com – To answer questions from hardware vendors • Web Resources: • Microsoft Site: http://www.microsoft.com/whdc • Industry Sites: • http://www.usb.org/wusb • http://www.wimedia.org • http://www.intel.com/go/uwb or http://www.intel.com/go/wusb

22. © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.