Drivers Mobile Stream

Purpose

Install Apple Mobile Device Support without iTunes. If you want to install Apple Mobile Device Support on Windows 10 without iTunes, there are two things you can try. Apple Mobile Device Support – Windows update. Windows 10 automatically installs drivers when new hardware is connected and an iPhone is no exception. This is a prerecorded playlist from trips on the Bergen Line. It is not possible to stream live from a train due to safety reasons and lack of internet cover.

The Intel® Driver & Support Assistant enables you to scan computing devices for the latest drivers available from Intel. This tool has the main interface hosted on Intel’s support website and provides a more integrated support experience to users. It has an enhanced detection engine to ensure that customers are given complete and accurate information and a scan frequency option to change from a “run-once” tool to a persistent experience that can provide customers with driver updates more quickly.

App

Products supported: Graphics drivers, wireless networking, Intel® SSDs, Intel® NUCs, and Intel® Compute Sticks

Mobile
  • Microsoft provides three multimedia class driver models: port class, stream class, and AVStream. The vendor writes a minidriver that runs under one of these three class driver models. These class drivers are implemented as export drivers (kernel-mode DLLs) in the system files portcls.sys, stream.sys, and ks.sys.
  • LG Mobile Drivers and Software. Learn how to use, update, maintain and troubleshoot your LG devices and appliances.
  • Stream Go mobile driver App helps improve customer service Real-time information collected through the App enables ETAs, driver location, order statuses and proof of delivery details are continually updated – and visible online. Proactive notifications and warnings can be triggered, based on the latest updates coming back from the App.

Issues with upgrading Intel® Driver & Support Assistant to a newer version? Please try our Uninstaller.

Required to install and use utility

  • A broadband Internet connection is required to use this utility.
  • Operating system requirements for installation: This application installs on Windows 7*, Windows 8*, Windows 8.1*, and Windows® 10.
  • We recommend performing a Windows* update to bring your operating system up to date with the latest .NET.
  • This application does not support Internet Explorer* browser. We recommend using Chrome*, Firefox*, or Edge* (version 44.17763/18.17763 or newer) browsers.

Instructions for launching

  1. Uninstall any previous versions (optional).
  2. Download and save locally on your device.
  3. Double-click Intel® Driver & Support Assistant Installer.exe file.
  4. Read and agree to the license terms and conditions
  5. Select Install.
  6. Click Launch button; the tray icon will start and automatically opens default browser

What's new in version 21.1.5.2?

  • Bug fixes for endless scanning issues
  • Improved screen reader compatibility of Installer
  • Improved network resiliency
  • UI improvements
  • General bug fixes and improvements

What's in previous version 20.11.50.9?

  • Improved support for Intel® SSD software
  • UI improvements
  • General bug fixes and improvements

Languages supported: Chinese, English, French, German, Japanese, Italian, Korean, Portuguese (Brazilian), Russian, Spanish, Thai, Vietnamese, Indonesian, Polish and Turkish.

Related topic

-->

This topic provides guidance to Mobile Broadband (MB) module manufacturers intending to support firmware upgrade devices via Windows Update (WU). 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.

The information in this topic applies to:

  • Windows 8

Device Requirements

To support firmware updates on Mobile Broadband using Windows Update, module or device manufacturers need to comply with the following requirements:

  • UMDF (User Mode Driver Framework) based driver developed by the module or device manufacturer, packaged along with the INF file and firmware payload. Sample INF file and details are provided in the later part of this document
  • Device firmware to implement the following functionalities:
    • Firmware ID Device Service (FID). For more information, see FID Device Service.
    • Firmware to support a firmware update device service. 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.

Operational Overview

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.

  • When the WWAN Service detects the arrival of new MB device, it will check if device support Firmware ID (FID) Device Service. If it is present, it will retrieve the FID, which is defined to be GUID. The Firmware Device Service specification that the IHV needs to the support on the device is described below.
  • WWAN Service (Windows OS) will generate “soft device-node” using the FID obtained above as the device hardware Id. This referred to as “Soft Dev Node” in the diagram above. The creation of the dev-node will kick start PnP subsystem (Windows OS) to find the best matched driver. 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 inbox NULL driver will used be used as default if better match driver is not available to eliminate “Driver Not Found” issue.
  • The IHV WU package, based on the FID match, is pulled down to the machine and installed. It is expected that the FID represents a unique firmware SKU (uniqueness here is defined by combination device VID/PID/REV and MNO). WU package would contain an IHV authored UMDF driver as well as a firmware payload.
  • Once the IHV UMDF is loaded on the soft dev-node it is responsible for controlling the firmware update flow. It should be noted that the life time of the soft dev-node is tied to physical presence of the MBIM device. The UMDF driver shall perform the following steps to performing firmware updates
    • 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 entire firmware upgrade process, including reboots, should take place no more than 60 seconds.
    • After the firmware update is completed and device has reverted to MBIM mode, Windows should be notified. This is done by clearing the previously set DEVPKEY_Device_PostInstallInProgress property. https://msdn.microsoft.com/library/windows/hardware/hh451399(v=vs.85).aspx describes how to set a property on dev-node. A previously set property can be cleared using DEVPROP_TYPE_EMPTY.
    • During OnPrepareHardware UMDF callback, the UMDF driver shall check if the firmware on the device needs to be updated. This is done by comparing the version of the firmware on the device against the one that came in via Windows Update. Additional guidance is provided later in the document regarding placement location of firmware binary. If firmware update is required, the UMDF driver should:
      • Schedule a work-item as described in https://msdn.microsoft.com/library/windows/hardware/hh463997(v=VS.85).aspx. The actual firmware upgrade happens in the context of the work-item.
      • Once the work-item is successfully scheduled, notify Windows about the start of firmware update. It is done by setting the DEVPKEY_Device_PostInstallInProgress property on the soft dev-node in the context of OnPrepareHardware UMDF callback.
      • It is important not to block the OnPrepareHardware callback while the firmware update is in progress. It is expected that OnPrepareHardware callback is completed within a second or two at the most.

Sample INF file for the WU Package

This section provides a sample INF that is part of the WU package. The key points to note in INF file are:

  • The firmware binaries are independent of the UMDF driver.
  • The firmware binaries are located a well-known, pre-defined location as shown below to filename collisions. The binaries cannot be not be executable files containing PE/COFF headers.
  • %windir%Firmware<IHVCompanyName><UniqueBinaryName>.bin
  • The UMDF driver is aware of this predefined well-known location.
  • The sample INF template below has highlighted items that need to be filled by the IHV.

Firmware Identification Device Service (FID Device Service)

The MBIM compliant device will implement and report the following device service when queried by CID_MBIM_DEVICE_SERVICES. The existing well-known services are defined in the NCM MBIM spec in section 10.1. Microsoft Corporation extends this to define the following service.

Mobihand

Service Name = Microsoft Firmware ID

UUID = UUID_MSFWID UUID

Value = e9f7dea2-feaf-4009-93ce-90a3694103b6

Specifically, the following CID is defined for UUID_MSFWID device service:

CID = CID_MBIM_MSFWID_FIRMWAREID

Command Code = 1

Query = Yes

Set = No

Event = No

Set InformationBuffer payload = N/A

Drivers Mobile Stream

Query InformationBuffer payload = N/A

Completion InformationBuffer payload = UUID

CID_MBIM_MSFWID_FIRMWAREID

The command returns the MNO or IHV assigned Firmware ID for the device. The UUID is encoded based on the guidelines in the MBIM specification.

Mobile Stream Center

Query = InformationBuffer on MBIM_COMMAND_MSG not used. UUID returned in InformationBuffer MBIM_COMMAND_DONE.

Set = Unsupported

Drivers

Unsolicited Event = Unsupported

Code snippets for behavior of UMDF driver

Mobihand

As indicated earlier, the UMDF driver should indicate to the Windows when it starts and completes firmware upgrade. This section provides code snippets that show how the driver should notify Windows of these events.