• Driver Implementation
  • Conclusion
  • Resources
  • Feedback
  • Abstract This paper provides information about Windows® 7 support for Mobile Broadband. It provides guidelines for hardware manufacturers, original equipment manufacturers




    Download 27.79 Kb.
    Sana24.03.2020
    Hajmi27.79 Kb.



    Windows 7 — Mobile Broadband Certification for Existing Chipsets

    March 17, 2009



    Abstract

    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.


    Disclaimer: This is a preliminary document and may be changed substantially prior to final commercial release of the software described herein.
    The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. 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 presented after the date of publication.
    This White Paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT.
    Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
    Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
    Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, email address, logo, person, place or event is intended or should be inferred.
    © 2009 Microsoft Corporation. All rights reserved.
    Microsoft, Windows, and Windows Vista are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
    The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

    Document History



    Date

    Change










    March 17, 2009

    First publication

    Contents

    Introduction 3

    Driver Implementation 3

    Conclusion 4

    Resources 5

    Feedback 6



    Introduction


    The NETWORK-0137 logo requirement requires that all 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.

    Driver Implementation


    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.

    Conclusion


    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.





    Resources


    Want to know more? Contact us at win7mb@microsoft.com.

    WinHEC Presentations:

    • Mobile Broadband Driver Development in Windows 7 [WinHEC 2008; 2.1 MB]
      http://download.microsoft.com/download/5/E/6/5E66B27B-988B-4F50-AF3A-C2FF1E62180F/MBL-T602_WH08.pptx

    • 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

    Specifications:

    • MSDN : Mobile Broadband API specification
      http://msdn.microsoft.com/en-us/library/dd323271(VS.85).aspx

    • MSDN : Mobile Broadband driver model specification
      http://msdn.microsoft.com/en-us/library/dd445701.aspx

    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)
      http://www.microsoft.com/downloads/details.aspx?FamilyID=A91DC12A-FC94-4027-B67E-46BAB7C5226C

    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)
      https://connect.microsoft.com/site/sitehome.aspx?SiteID=668

    Windows Logo Program:

    • General information about the Windows Logo Program
      http://www.microsoft.com/whdc/winlogo/default.mspx

    Mobile Broadband specifications, development guides, and integration guides:

    • Mobile Broadband site at Microsoft Connect

    1. Go to http://connect.microsoft.com.

    2. Sign in using your .NET Passport.

    3. In Were you invited to join Connect, enter the following invitation ID for the Windows WWAN Program:

    WWAN Pre-Beta Distribution [PreB-WJ96-VGHW]

    1. Send an e-mail to win7mb@microsoft.com with your e-mail ID that was used for registration.

    2. Attach a scanned copy of the NDA if this is the first time your company is requesting access.

    Feedback


    Please send us your feedback at win7mb@microsoft.com.




    Download 27.79 Kb.




    Download 27.79 Kb.

    Bosh sahifa
    Aloqalar

        Bosh sahifa



    Abstract This paper provides information about Windows® 7 support for Mobile Broadband. It provides guidelines for hardware manufacturers, original equipment manufacturers

    Download 27.79 Kb.