This paper provides information about Windows® 7 support for Mobile Broadband. It provides guidelines for hardware manufacturers, original equipment manufacturers, and mobile network operators on developing logo-compliant Mobile Broadband drivers for chipsets/modules that are already commercially deployed.
This information applies for the Windows 7 operating system.
References and resources discussed here are listed at the end of this paper.
The NETWORK-0137 logo requirement requiresthatall Mobile Broadband (MB) drivers comply with the Windows 7 MB driver model specification (http://msdn.microsoft.com/en-us/library/dd445701.aspx). Microsoft has received feedback from independent hardware vendor (IHV) and original equipment manufacturer (OEM) partners that this requirement might require changes to the firmware of existing chipsets/devices. These partners are concerned about the potential cost and effort of recertification and their ability to meet the schedule for logo certification.
In response to this feedback, we are providing additional guidance to our ecosystem partners on implementation of the logo requirements. Based on our analysis, chipsets currently deployed in the field can comply with the MB driver model specification without any changes in firmware. This document provides recommendations to help accomplish this goal.
This document refers only to devices/chipset/modules that are already commercially deployed.
Based on the feedback from our partners, we have identified three MB requirements that existing devices might not support directly. We strongly recommend that devices support MB driver model requirements in the firmware wherever possible. However if this is not practical, the following recommendations can help meet the requirements through driver implementation:
Raw Internet Protocol (IP) support. MB drivers should use raw IP frames for sending and receiving data from Network Driver Interface Specification (NDIS). Some existing devices may not expose the raw IP–based interface for miniport drivers to send and receive data. These devices support the Ethernet-based interface for sending and receiving data from the driver.
MB drivers for such devices can support raw IP frames in software. The driver must register itself with the operating system as capable of supporting raw IP frames. In the sending path, the driver must add an additional Ethernet header to the NDIS-supplied raw IP frame before sending it to the device. Similarly, on the receiving path, the driver must remove the additional Ethernet header from the frame received from the device before sending it to NDIS.
Network error code support. When a mobile network generates an error, MB drivers should indicate the network error code (also known as the cause code) to the MB service. Some devices might not have a software interface for the miniport driver to get the network error code information from the device.
NDIS logo tests related to network error codes do not result in test failures, only in warnings. Therefore, drivers for older devices can still pass the logo tests even if they do not report network error codes.
Miniport driver without Dynamic Host Configuration Protocol (DHCP) spoofing. Mobile broadband drivers should use IP helper APIs to inform the system about the IP address, default gateway, Domain Name System (DNS) address, etc. The operating system DHCP client uses DHCP to configure the system with these network settings. Some older devices might not have a mechanism for the driver to get these parameters from the device. These devices implement the DHCP server in the device firmware.
Miniport drivers for older devices can implement a lightweight DHCP client in the driver. The driver should expose the device to the operating system as a DHCP-disabled device. It should internally use DHCP to get network configuration parameters from device. Then it should call IP helper APIs to inform the system about the configuration.
By following the recommendations in this document, older devices can meet all the MB driver model requirements without changing their firmware. Microsoft recommends that partners plan and provide native MB support for all new devices.
Want to know more? Contact us at email@example.com.
Mobile Broadband Driver Development in Windows 7 [WinHEC 2008; 2.1 MB]
Windows 7: Mobile Broadband APIs For Application Development [WinHEC 2008; 1.5 MB] http://download.microsoft.com/download/5/E/6/5E66B27B-988B-4F50-AF3A-C2FF1E62180F/MBL-T603_WH08.pptx
MSDN : Mobile Broadband API specification
MSDN : Mobile Broadband driver model specification
Windows 7 Beta Software Development Kit (SDK) for connection manager development:
IDL and header files for developing applications (with Mobile Broadband sample code located at Program Files\Microsoft SDKs\Windows\v7.0\Samples\NetDs\MB\mbapi; does not include MB APIs)
Windows Driver Kit (WDK) for Windows 7 Beta for driver development:
Header files for Mobile Broadband driver development http://www.microsoft.com/whdc/DevTools/WDK/WDKbeta.mspx
Windows Logo Kit for driver quality assessment:
Windows Logo Kit (WLK) 1.3 at Microsoft Connect (logon required)
Windows Logo Program:
General information about the Windows Logo Program