[WWAN SERVICE] DEVICE SEVICE METHOD response difference by windows version

Xipe 1 Reputation point
2022-08-24T10:45:23.747+00:00

I checked the Device Service list through IMbnDeviceServicesContext::EnumerateDeviceServices, and even though it is the same modem, different results were obtained in Windows 10 and Windows 11. Each result is as follows (UUID, Service name).

Windows 10:
{4BF38476-1E6A-41DB-B1D8-BED289C25BDB} , (Phonebook)
{D8F20131-FCB5-4E17-8602-D6ED3816164C} , (STK)
{68223D04-9F6C-4E0F-822D-28441FB72340} , (MS SAR)

Windows 11:
{4BF38476-1E6A-41DB-B1D8-BED289C25BDB} , (Phonebook)
{D8F20131-FCB5-4E17-8602-D6ED3816164C} , (STK)
{3D01DCC5-FEF5-4D05-0D3A-BEF7058E9AAF} , (MS Basic Connect Extensions)
{68223D04-9F6C-4E0F-822D-28441FB72340} , (MS SAR)

The question is:

  1. What causes these differences?
  2. How can I use Basic Connect Extensions on Windows 10?
  3. My modem also has UICC service, but why is it not on the list?
  4. Is there a way to use services (Basic Connect, SMS, etc.) provided through mbnapi.h as individual MBIM CIDs through IMbnDeviceService::QueryCommand?
Windows API - Win32
Windows API - Win32
A core set of Windows application programming interfaces (APIs) for desktop and server applications. Previously known as Win32 API.
2,412 questions