The WiNET Driver package consists of three separate parts. The WiNET driver resides in the NDIS stack. The WiNET driver receives data for devices or applications connected to the NDIS stack. The Radio and Bus Management driver handles the different radio controls and interactions for the WiNET Device. The user interaction to setup and associate devices with the driver is handled in an Interface application. All modules are necessary items for a WiNET Device to function.

The WiNET driver is implemented according to the WiNET specification released by the WiMedia Alliance. The WiNET driver is a miniport driver at the bottom of the NDIS stack. WiNET supports Internet Protocol version 4 and Internet Protocol version 6. This driver routes the inbound protocol to the appropriate stack. The outbound data receives a header added on to the data to inform the Radio Management driver how to route the data packet. This driver also handles Address Mapping, Bandwidth Negotiation and Quality of Service issues.

The Radio and Bus Management functions are handled in a separate driver to allow other protocols that may be supported in the WiNET device to have access to the radio control functions. This allows a WiNET driver to be able to request bandwidth or get radio status on the same radio that the Wireless USB uses. This management in one common place allows equal access for multiple protocols. This driver is loaded upon plug in of the WiNET Device. The driver queries the device and then enumerates a driver for the different protocols supported by the device. This driver will also be responsible for routing of data to the appropriate protocol or device. Using the functions defined in the WiMedia specification, the Radio and Bus Management driver will pass the commands to the device to control the radio. The Radio and Bus Management driver will also handle beacon control, channel scanning and changing, Distributed Reservation Protocol (DRP) Management and radio status.

Something unique to a wireless driver is the need for an interface application. Most drivers are transparent to the user and require no interaction. In a wireless ituation, there is a need to associate a device with a host. This initial ceremony requires user interaction. These interactions with the device will be handled in the interface application. Also, important information such as devices connected, link status and association status will be shown in this application.

For the hardware developer, this application has been expanded into a special OrangeWare Utility. This Utility application will enable the developer have a greater insight into how the WiNET Device is functioning. The Utility application will show performance statistics on transfers and radio performance. Mechanisms will be available to help the developer analyze and tune features. These functions will aid the developer in design and debugging of their product.

These three items provide a base for your WiNET product. OrangeWare also realizes that not all products are created equal, nor should they be. We invite any developer with special enhancements to their products to contact us so we can lend a hand in your development effort and provide any necessary driver modifications or APIs as required.