This topic covers recommendations for Mobile Broadband components in devices that run Windows 10.
Windows supports combinations of the GSM-based and CDMA-based mobile broadband technologies including LTE. The minimum connectivity capability for a Mobile Broadband device is 3G connectivity. 2G connectivity is optional. Devices for the various broadband technologies must follow the specifications of standards bodies and be certified by the preferred mobile operator.
The following table summarizes the recommended mobile broadband hardware features.
USB-SSIC (USB 3.0)
USB-HSIC for surface mounted solutions
USB for connector mounted solutions (the device must continue to work while in USB selective suspend mode and capable of waking up the device)
|Idle power||<10 mW (Connected Standby platform)|
|SIM Connector||User accessible|
Embedded module solutions must always have mobile broadband functionality available without any USB hub design inside the chipset.
Idle mode power for 3GPP devices covers:
- PDP context activated but no network traffic state
- PDP context de-activated state
Idle mode power for 3GPP2 devices covers:
- Connected state with no network traffic state
- Disconnected state
USB based devices for GSM and CDMA technologies (3GPP/3GPP2 standards based) must be firmware compliant with the Mobile Broadband Interface Model specification. The USB Forum must certify these drives for compliance (when that certification becomes available for mobile broadband devices).
The following table summarizes the additional features, as specified by NDIS, that we recommend the firmware support.
|No pause on suspend||Support|
|Wake reason reporting||Support|
|USB SS||Support if USB-based|
Drivers and software
Non-USB devices for GSM and CDMA use IHV developed Mobile broadband drivers. The drivers must comply with the Mobile Broadband Driver Model. IHV developed MB drivers must pass the tests for validating mobile broadband functionality, such as the Windows Hardware Lab Kit (HLK) tests.
- Devices based on the SPI peripheral bus need SPI driver support from the platform vendor. The SPI driver must comply with the features listed in Simple Peripheral Bus (SPB).
- USB devices must be compliant with the Microsoft USB driver stack and not require any IHV or third-party drivers for the mobile broadband functionality.
- In case of MB+GNSS multi-function device, the GNSS driver can be an IHV driver as compliant with GNSS and power requirements. Please see GNSS requirements for more information.
- No serial port devices enumerated for the purposes of diagnostics, device management or firmware upgrade etc. in the final production image.
- Serial/AT command port, for the purposes of Mobile Network Operator (MNO) certification or OEM factory diagnostics/configuration should be supported through an IHV driver stack solution only. This IHV software stack / port drivers must be removed in the shipping image.
- No IHV software based function SKUs to enumerate (or not enumerate) other functions in case of multi-function MB device solutions.
- All functions, including any virtual functions (where needed) that are enumerated by the MB device need to be power-aware and respect Connected Standby and power states and cannot use legacy, non-power aware or non-PnP friendly solutions.
We recommend using Connection Manager. There is no additional Connection Manager software necessary for the operation of mobile broadband devices. Value-add Mobile Broadband Connection Managers, if implemented, must implement the Mobile Broadband API.
The mobile broadband driver or device must implement the power management optimizations as required by NDIS.
Behavior in ACPI S3
If the platform supports ACPI S3 operating system power states, wireless devices shall not be removed from the bus upon entering S3.
If the device features a SIM card, we recommend the SIM card socket is accessible to the user to ease the activation process. If the device has a removable battery pack, the recommended location is inside the battery compartment.
- In any direction, the gain of at least one antenna attached to the device should be better than -15dBi.
- The directive gain in any direction should not be higher than 6dB.
- The antenna efficiency should be better than 50%. Antenna efficiency includes losses due to impedance mismatch and the radiation efficiency.