It is acceptable for the device to reboot multiple times during the firmware update process, but would cause the UMDF driver to get unloaded/reloaded.

The UMDF driver shall perform the following steps to performing firmware updates It should be noted that the life time of the soft dev-node is tied to physical presence of the MBIM device.

Once the IHV UMDF is loaded on the soft dev-node it is responsible for controlling the firmware update flow.

WU package would contain an IHV authored UMDF driver as well as a firmware payload. It is expected that the FID represents a unique firmware SKU (uniqueness here is defined by combination device VID/PID/REV and MNO).

The IHV WU package, based on the FID match, is pulled down to the machine and installed.

The inbox NULL driver will used be used as default if better match driver is not available to eliminate “Driver Not Found” issue. In Windows 8, PnP system will first attempt to install a driver from the local store, if one is available, and in parallel OS will attempt to fetch a better matched driver from WU. The creation of the dev-node will kick start PnP subsystem (Windows OS) to find the best matched driver. This referred to as “Soft Dev Node” in the diagram above.

WWAN Service (Windows OS) will generate “soft device-node” using the FID obtained above as the device hardware Id.

The Firmware Device Service specification that the IHV needs to the support on the device is described below. If it is present, it will retrieve the FID, which is defined to be GUID.

When the WWAN Service detects the arrival of new MB device, it will check if device support Firmware ID (FID) Device Service.

The following diagram shows the high level design and interaction between the three components involved: MBIM device, Windows 8 Operating System and IHV supplied firmware upgrade driver. This is a device manufacturer specific device service that provides the ability for an UMDF driver to call into and execute/download the firmware payload and start the firmware update process.

Firmware to support a firmware update device service.

For more information, see FID Device Service.

Device firmware to implement the following functionalities:.

Sample INF file and details are provided in the later part of this document

UMDF (User Mode Driver Framework) based driver developed by the module or device manufacturer, packaged along with the INF file and firmware payload.

To support firmware updates on Mobile Broadband using Windows Update, module or device manufacturers need to comply with the following requirements: The information in this topic applies to:

The devices must be compliant with the USB NCM Mobile Broadband Interface Model (MBIM) V1.0 specification released by the USB-IF Device Working Group. This topic provides guidance to Mobile Broadband (MB) module manufacturers intending to support firmware upgrade devices via Windows Update (WU).

Map mas ios driver dell