28-04-2011, 03:25 PM
[attachment=13028]
UltraWide Band (UWB) Architecture Preview
UWB Overview
UWB in the Digital Home
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
UWB Protocol Relationships on Windows Platforms
Wireless USB – Topology Overview
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.
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
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
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
Device Wire Adapter
Looks like a wireless hub
Great for scenarios like wireless port replicators
Single chip implementations can be integrated directly into devices
List of New Kernel Files
Hardware IDs for UWB PALs
PCI IDs for UWB PAL PDOs
Hardware IDs
Compatible IDs
Similar in style to PCI device ID
USB IDs for UWB PAL PDOs
Hardware IDs
Compatible IDs
Similar in style to USB device IDs
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
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
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 for logo requirements
Timelines
Test documents and tests developed 2H05
First compliance workshops in 1H06
UltraWide Band (UWB) Architecture Preview
UWB Overview
UWB in the Digital Home
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
UWB Protocol Relationships on Windows Platforms
Wireless USB – Topology Overview
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.
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
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
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
Device Wire Adapter
Looks like a wireless hub
Great for scenarios like wireless port replicators
Single chip implementations can be integrated directly into devices
List of New Kernel Files
Hardware IDs for UWB PALs
PCI IDs for UWB PAL PDOs
Hardware IDs
Compatible IDs
Similar in style to PCI device ID
USB IDs for UWB PAL PDOs
Hardware IDs
Compatible IDs
Similar in style to USB device IDs
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
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
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 for logo requirements
Timelines
Test documents and tests developed 2H05
First compliance workshops in 1H06
